Database Users

[ROM]-MOKEE-UNOFFICIAL-MK51.1-aries-201508071513

MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application: http://www.mfunz.com/en/developer-application, you can host your unofficial MoKee builds on our server!
Forum:http://bbs.mfunz.com
Guide:http://bbs.mfunz.com/thread-754544-1-1.html
Statistics:http://stats.mokeedev.com
Review:http://review.mfunz.com
Download:http://download.mokeedev.com
Github:https://github.com/MoKee
Bug Tracker:http://issues.mokeedev.com/
Credits:
Google, Qualcomm, Motorola, Samsung, Lge, TI, Nvidia, Intel, Sony,
CyanogenMod, Omnirom, Slim Roms, Koush for open-sourced SuperUser
Code:
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
Found on Chinese MIUI forum.
->Download Link1<-
->Download Link2<-
LATEST VERSION 19-08-2015
Found on Chinese MIUI forum.
->Download Link<-
Not merged/Unmerged partition patch
->Download<-
Latest version 13-10-2015 can be found here:
http://www.miui.com/thread-3012343-1-1.html

Tested and works fine

for which layout type is this rom? I'm using the old one... with previous Mokee version...

New version found by the dev in Chinise Forum
I am installing this right now. Wait for Dropbox to Upload because baidu _____ and i want to help you download this faster
https://dl.dropboxusercontent.com/u/54386997/MK51.1-aries-201508181111-UNOFFICIAL.zip

NightHeron said:
New version found by the dev in Chinise Forum
I am installing this right now. Wait for Dropbox to Upload because baidu _____ and i want to help you download this faster
https://dl.dropboxusercontent.com/u/54386997/MK51.1-aries-201508181111-UNOFFICIAL.zip
Click to expand...
Click to collapse
Thanks but I already got a more recent version uploaded, see first post.

SWADED said:
Thanks but I already got a more recent version uploaded, see first post.
Click to expand...
Click to collapse
The patch is for merged partitions?Cause till now i think it was for not merged.

T3sla said:
The patch is for merged partitions?Cause till now i think it was for not merged.
Click to expand...
Click to collapse
It is for not merged, you are right.

already flash it on my mi 2s, awesome, thanks dude

Simple guide to update from not merged data-sdcard mokee official 4.4.4 to the last mokee unofficial 5.1.1 with merged partition 30/12/2015 update
1) optional - make a full nandroid backup in case anything went wrong
2)REPARTITION TO MERGED DATA
- download MIUI 5.9.2 fastboot package from official miui.com site or from here
- flash it via MiFlash, selecting "flash_all.bat" from advanced properties (the flash_all.bat is inside the miui 5.9.2 fastboot package)
-reboot from fastboot and wait (10 minutes more or less) until miui rom finally boot to the home screen
3)FLASH CUSTOM RECOVERY TWRP 2.8.7.0 FOR MERGED PARTITION
-use this guide (point 2) to flash TWRP via fastboot
4)FLASH MOKEE 5.1.1 ROM + GAPPS
-from twrp wipe data, system, caches -> flash MK51.1-aries-201511292011-UNOFFICIAL -> flash OTA-MK51.1-aries-201511292011-201512311830-UNOFFICIAL.zip -> flash gapps -> reboot
tested on MI2 32GB with mokee 4.4.4, use at your own risk
thanks to zipalign and swaded

I see the files is't same, i will try another file source, the dropbox files i got loss my imei

NightHeron said:
New version found by the dev in Chinise Forum
I am installing this right now. Wait for Dropbox to Upload because baidu _____ and i want to help you download this faster
https://dl.dropboxusercontent.com/u/54386997/MK51.1-aries-201508181111-UNOFFICIAL.zip
Click to expand...
Click to collapse
Hi, on my mi2s installed success, but imei is gone, how to fix this? i already restore EFS but if use mokee its still Unknow imei

gonewild87 said:
Simple guide to update from not merged data-sdcard mokee official 4.4.4 to the last mokee unofficial 5.1.1 with merged partition 30/12/2015 update
1) optional - make a full nandroid backup in case anything went wrong
2)REPARTITION TO MERGED DATA
- download MIUI 5.9.2 fastboot package from official miui.com site or from here
- flash it via MiFlash, selecting "flash_all.bat" from advanced properties (the flash_all.bat is inside the miui 5.9.2 fastboot package)
-reboot from fastboot and wait (10 minutes more or less) until miui rom finally boot to the home screen
3)FLASH CUSTOM RECOVERY TWRP 2.8.7.0 FOR MERGED PARTITION
-use this guide (point 2) to flash TWRP via fastboot
4)FLASH MOKEE 5.1.1 ROM + GAPPS
-from twrp wipe data, system, caches -> flash MK51.1-aries-201511292011-UNOFFICIAL -> flash OTA-MK51.1-aries-201511292011-201512311830-UNOFFICIAL.zip -> flash gapps -> reboot
tested on MI2 32GB with mokee 4.4.4, use at your own risk
thanks to zipalign and swaded
Click to expand...
Click to collapse
:fingers-crossed: it's work good for my aries, just one my problem, the diel USSD Code is Chines languange, how to fix this i already change the locale, change font, but still chines :crying:

[WIP] Multiboot Project For Oneplus 3

Multiboot project is a work done by @chenxiaolong , I do not own any of the work presented over here.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Project
* before installing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
About Multiboot : A project to handle different ROMS at the same time so that you actually can use different ROMS without having to wipe up device to flash ROMS, it allows installation of more thn one ROM with all the features enabled.
USAGE​1. Decrypt your phone by following THIS guide, else you won't be able to use Multiroms.
2. Boot into your primary ROM and install the Dual Boot Patcher app
3. Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
4. Go to "Patch ZIP file" in the navigation drawer and patch the ROM or zip you want to install. If you can't select the ZIP file without opening it (OxygenOS's file explorer does that as example) use Solid Explorer, ES File Explorer seems to crash the App for some reason.
5. If you want to dual-boot with OxygenOS you'll most likely have too less space in /system. Instead use the Data-Slot and give a name for it when asked.
6. (Optional) Before flashing GApps refer to the section "In-app flashing" below and come back once you've done that.
7. (Optional) Download GApps from HERE, select ARM64 and the version you want, download it onto your phone, choose "Patch ZIP file" once again and select the Data-Slot which it created for you already.
8. (Optional) To flash GApps simply refer to the section "In-app flashing" again.
In-app flashing​
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
DOWNLOAD: https://snapshots.noobdev.io/
Download the "Android" file and the "Utilities" file
ORIGINAL THREAD: http://forum.xda-developers.com/showthread.php?t=2447534
CURRENT ISSUES​
#since this is a work in progress please do consider having a look here
1. If you update ramdisk and reboot then the phone will reboot to recovery and not boot to rom. You will have to reflash your rom for it to boot.
2. Lots of other issues.
3. When setting a lock-code in your second ROM and boot back to your main ROM you'll probably be greeted with "Wrong PIN/Pattern". To fix this either delete the following files in TWRP or via ADB:
In /data/system: password.keym pattern.key, locksettings.db, locksettings.db-shm, locksettings.db-wal
After this step you can go back into your main ROM and set a lock-code again, now it should work.
DONATION (this donation directly goes @chenxiaolong ,I do not take any of it) : http://forum.xda-developers.com/donatetome.php?u=4277844 #if not sure about the link kindly visit:
http://forum.xda-developers.com/member.php?u=4277844
CREDITS​
All credits goes to @chenxiaolongfor his hard work on this project,
kindly say thanks to him
Thanks to @hunter_bruhh too. He did the pull request on github.
I am currently in need of testers so if anyone is interested, please pm me on tapatalk chat, xda pm or telegram to https://telegram.me/RKRohk
XDA:DevDB Information
Multiboot Project For Oneplus 3, Tool/Utility for the OnePlus 3
Contributors
rkrohan, hunter_bruhh, epiclper, @chenxiaolong
Version Information
Status: Alpha
Created 2016-07-03
Last Updated 2016-07-07

Seems like no rom is working with this. I have informed @chenxiaolong but till then, I need logs from anyone who is trying this on any custom rom. You can find logs in the multiboot folder in your internal storage. Thank you.

If you remove encryption then this should work. Try using the data slot to install a custom ROM while you are on a custom ROM and please let me know if it worked. For those getting ramdisk issues, ?*just flash /sdcard/MultiBoot/primary/boot.img.before-ramdisk-update.img from TWRP.

Reserved
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
---------- Post added at 10:42 AM ---------- Previous post was at 10:42 AM ----------
Waiting for it to boot properly..
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

http://forum.xda-developers.com/oneplus-3/development/patcher-dual-boot-rom-oneplus-3-t3409591
what's the difference？

dlhxr said:
http://forum.xda-developers.com/oneplus-3/development/patcher-dual-boot-rom-oneplus-3-t3409591
what's the difference？
Click to expand...
Click to collapse
@hunter_bruhh and I worked on this not the guy who made the other thread

Anyone get dual boot successfully? I tried install Cm13 as secondary in data slot, but end up with vibrations and boot into recovery.

youlun.zhai12 said:
Anyone get dual boot successfully? I tried install Cm13 as secondary in data slot, but end up with vibrations and boot into recovery.
Click to expand...
Click to collapse
no...same with Paranoid ROM...

youlun.zhai12 said:
Anyone get dual boot successfully? I tried install Cm13 as secondary in data slot, but end up with vibrations and boot into recovery.
Click to expand...
Click to collapse
I tried almost every rom but it dosen't work. I need logs from a guy who is not on stock rom. I have informed @chenxiaolong about this. Hope it gets fixed soon

How do I decrypt the OnePlus 3 tho? The Security>Encryption option does exactly nothing when I touch it...

Thanks…
I install second rom ResurrectionRemix-M-v5.7.0-20160703-oneplus3
But how I can switch to boot secondary rom??

EpicLPer said:
How do I decrypt the OnePlus 3 tho? The Security>Encryption option does exactly nothing when I touch it...
Click to expand...
Click to collapse
In bootloader mode > "fastboot format userdata" > done. But all your data will be lost. So make a backup on your pc first...

Want to decrypt your device in order for this to work?
Here's how you can do that!
http://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228/

Managed to recover from a "disaster" after trying to upgrade my main, primary ROM (OxygenOS)...
So, I downloaded OxygenOS 3.2.1 and SuperSU and patched it via Dualboot Patcher, so far so good.
Then I booted into my secondary ROM (Resurrection Remix) since flashing on the currently running ROM is not allowed.
Started the Flash on the second ROM, however I accidentally hit the recent apps key, once I switched back to Dualboot Patcher it crashed...
I panicked a little, I booted into TWRP and flashed both files from there (first OOS, then SuperSU to prevent it from encrypting again).
After that I rebooted, however immediately after rebooting the OnePlus logo came on, went black and rebooted into the OnePlus logo again. Well, nothing much wrong so far, that's usual SuperSU behavior.
After the second reboot my phone was stuck in a bootloop and got extremely hot, I left it sit there thinking it'd encrypt again due to me doing something wrong (this happens when you forget to flash SuperSU after OOS)
After almost 40 minutes, still nothing. So I went to my PC and took a look what logcat says: Java Fatal Exception, something battery related wasn't able to load up.
So I force-shutdown the device and booted back up, not even 20 seconds later it booted into Android like nothing before happened...
Lesson of this story: NEVER flash your primary ROM from the secondary one... ALWAYS patch the ZIP files first, then boot into TWRP, then flash them.

I installed a dual system rom for mistake and obviously cannot use it, I also installed a data dual rom which is working fine, my issue is that when I try to remove the dual system rom I cannot do it, even if I move to raw/system/multiboot and try to delete I can't, I tried to change the permission, to set raw folder as a writable folder but none of this tries work..any help?

I have been using multirom on nexus. I saw multirom is also there for OP3. currently on OP3 I have flashed multirom(that similar to Nexus) , then i came across this THREAD.
Just a noob question - how different it is from multirom?
No disrespect to the developer intended.

Tried with RR and AOSPA, didnt work, i think its not flashing the second ROM properly..?

[Official][TWRP Recovery][3.2.1]TWRP 3.2.1.0 For Xiaomi Redmi 4X (SANTONI)

Team Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Download : TWRP 3.2.1.0 For Santoni
Source Device Tree: Device Tree For Building TWRP

Woow . Thank you so much for the official update bro keep rocking

The encryption issue exists in this version??

Thanks

k_vki said:
The encryption issue exists in this version??
Click to expand...
Click to collapse
+1

Nope... But you sud upgraded from 3.1.1.0

k_vki said:
The encryption issue exists in this version??
Click to expand...
Click to collapse
Yes, The encryption issue exists in this version as well..

I upgraded directly from 3.1.0(no encryption problem) to 3.2.1 through twrp app downloaded from play store and there is no encryption problem...

@gunsheriff . . . Bro i want urgent help plzz anyone help me fasst as u can possible . . I am on miui9 v7.12.8 beta and unlocked bootloader and i am going to install this latest twrp3.2.1 via fastboot . . . I seen some warning about dmverity and device encrypt not booting somthing like that . . . So my question is want to flash lazyflasher after flashing this recovery to avoid bootloop??? Or want to do anymore steps for stablize the twrp without bootloop??and what are the steps ?? Plzz anyone help faaast because i am going to install twrp tonight ?

gunsheriff said:
Team Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Download : TWRP 3.2.1.0 For Santoni
Source Device Tree: Device Tree For Building TWRP
Click to expand...
Click to collapse
Changelog?

Go throught twrp.me website...

Ramakrishnan ? said:
@gunsheriff . . . Bro i want urgent help plzz anyone help me fasst as u can possible . . I am on miui9 v7.12.8 beta and unlocked bootloader and i am going to install this latest twrp3.2.1 via fastboot . . . I seen some warning about dmverity and device encrypt not booting somthing like that . . . So my question is want to flash lazyflasher after flashing this recovery to avoid bootloop??? Or want to do anymore steps for stablize the twrp without bootloop??and what are the steps ?? Plzz anyone help faaast because i am going to install twrp tonight ?
Click to expand...
Click to collapse
Do you use any custom recover before in your device..

vicky083_ said:
I upgraded directly from 3.1.0(no encryption problem) to 3.2.1 through twrp app downloaded from play store and there is no encryption problem...
Click to expand...
Click to collapse
really?

with encryption issue you mean that it's not possible to mount an encrypted data partition as even with the right password you'll always get a failure message? because that's what i get. is there a workaround known or does this mean you have to factory reset every time you want to flash something?

Riy12 said:
really?
Click to expand...
Click to collapse
Yup, try to upgrade from 3.1.0 to 3.2.1 through twrp official app.. Avoid version 3.1.1..

vicky083_ said:
I upgraded directly from 3.1.0(no encryption problem) to 3.2.1 through twrp app downloaded from play store and there is no encryption problem...
Click to expand...
Click to collapse
Try for flash miui rom, because encyption issue exist when i flash miui rom

gunsheriff said:
Do you use any custom recover before in your device..
Click to expand...
Click to collapse
Flashed successfully everythink works great thank you dev for the official stable update ☺

Ramakrishnan said:
Flashed successfully everythink works great thank you dev for the official stable update
Click to expand...
Click to collapse
MAGILCHI

F2FS /data is broken. Once you format it to F2FS, TWRP can no longer mount it:
Failed to mount '/data' (No such device)

Did you try removing encription?
Can be done by wiping data partition: https://forum.xda-developers.com/xiaomi-redmi-4x/development/automatic-encryption-t3684422

[RECOVERY][3.4.0-14][toco]Unofficial TWRP Xiaomi Mi Note 10 Lite (TEST)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
Download:
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-13 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_toco
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-05-29

Oooo finally... Gonna test this out when I get home later.
Just to check, what happens if i flash and i get bootloop? How do I recover? By flashing the entire MIUI rom from official site?
Okay Im sure im being a noob... But err...
I wasnt able to mount data...
I tried to mount and install MAGISK via USB-OTG mounting and i get permission denied for system and vendor (and also Data unable to mount)
EDIT2: Oh cool... despite the errors Magisk got installed! Nice!

Hello, will there be more development for this terminal? and the note 10 lite thread? Thank you

Did anyone boot it?
hello, work boot it?
fastboot boot twrp.XXXX.img

StanGumn said:
hello, work boot it?
fastboot boot twrp.XXXX.img
Click to expand...
Click to collapse
Yes

iron maiden said:
Hello, will there be more development for this terminal? and the note 10 lite thread? Thank you
Click to expand...
Click to collapse
Let us hope so.

I would like to apologize in advance as I am a noob when it comes to the recent changes made by Google to android. So on a lot of the recent devices launched with android 10, an essential step before flashing Magisk is to disable the vbmeta partition by flashing the "vbmeta.img" using a fastboot command with the --disable-verify and --disable-verification argument. My question is that is the "vbmeta.img" modified by developers or is this the same identical file found in the stock firmware files?
I do apologize if this is the wrong thread but there's not many resources online or even on xda for this device.

Why its in mi note 10 general section? Isnt right to do separately section for mi note 10 lite since there is nothing in common just name.

Reanimax said:
Why its in mi note 10 general section? Isnt right to do separately section for mi note 10 lite since there is nothing in common just name.
Click to expand...
Click to collapse
ask to xda to make a dedicated section and i will ask to move this thread

mauronofrio said:
ask to xda to make a dedicated section and i will ask to move this thread
Click to expand...
Click to collapse
Yes. You right about it.

Kediraksith said:
Oooo finally... Gonna test this out when I get home later.
Just to check, what happens if i flash and i get bootloop? How do I recover? By flashing the entire MIUI rom from official site?
Okay Im sure im being a noob... But err...
I wasnt able to mount data...
I tried to mount and install MAGISK via USB-OTG mounting and i get permission denied for system and vendor (and also Data unable to mount)
EDIT2: Oh cool... despite the errors Magisk got installed! Nice!
Click to expand...
Click to collapse
Nowadays you have to unmount Data and mount vendor (just in case for Vendor) before flashing Magisk. Mounting data does not let Magisk install via TWRP. Follow the this process, same install process with the Mi Note 10, and assuming the Mi note 10 Lite. The reason why is because of encryption.
Update: 5/16/2020
1) Flash lastest TWRP unofficial 3.31-4 mauronofrio using Command prompt using the - fastboot flash recovery [XXXX].img. Note: it's easier to just rename the recover image to "twrp"
2) Then - fastboot boot [XXXX].img to reboot into TWRP recovery.
3) In my experience for thr Mi Note 10 that is, the reboot to RECOVERY did not happened, so instead i pressed - volume up and power button at the same time for thr phone to reboot until you see the boot splash screen, hold the two buttons for another 3 seconds ... and then let go of power button and then TWRP recovery will show up.
4) Ok...so first things first... flash the VBMETA PATCHER like the OP says on first page --> that way you don't lose TWRP after flashing the Rom and MAGISK. After install, reboot to RECOVERY. ***This is only if OP asks to flash VBMETA PATCHER, otherwise skip to Step 5***
5) Now....go to FORMAT DATA (Warning: DON'T use advanced wipe)... Instead, go to the FORMAT DATA, type in yes and press ok. Then go back to main menu, and reboot to RECOVERY again.
6) Now you can access your internel memory when connecting to USB... You can import the two neccesary files --> Xiaomi.EU and MAGISK 20.4. Now Flash the Rom and when flash MAGISK, make sure you unmount DATA and mount VENDOR to avoid flash error. After unticking DATA, you can now install Magisk.
7) Now you can go to REBOOT, and press SYSTEM, and the phone will boot to Xiaomi EU 11 or 12, etc. just follow this process and enjoy your ROM. ?
Note: When updating, flash EU rom and Magisk, dont forget to unmount Data when flashing Magisk. You can probably disable decryption because that is why you can't mount Data when flashing Magisk. **Just don't ask me about it because I normally don't flash Disable Decyption often.

Wmateria said:
Nowadays you have to unmount Data and mount vendor (just in case for Vendor) before flashing Magisk. Mounting data does not let Magisk install via TWRP. Follow the this process, same install process with the Mi Note 10, and assuming the Mi note 10 Lite. The reason why is because of encryption.
1) Flash lastest TWRP unofficial 3.31-4 mauronofrio using Command prompt using the - fastboot flash recovery [XXXX].img. Note: it's easier to just rename the recover image to "twrp"
2) Then - fastboot boot [XXXX].img to reboot into TWRP recovery.
3) In my experience for thr Mi Note 10 that is, the reboot to RECOVERY did not happened, so instead i pressed - volume up and power button at the same time for thr phone to reboot until you see the boot splash screen, hold the two buttons for another 3 seconds ... and then let go of power button and then TWRP recovery will show up.
4) Ok...so first things first... flash the VBMETA PATCHER like the OP says on first page --> that way you don't lose TWRP after flashing the Rom and MAGISK. After install, reboot to RECOVERY.
5) Now....go to FORMAT DATA (Warning: DON'T use advanced wipe)... Instead, go to the FORMAT DATA, type in yes and press ok. Then go back to main menu, and reboot to RECOVERY again.
6) Now you can access your internel memory when connecting to USB... You can import the two neccesary files --> Xiaomi.EU and MAGISK 20.4. Now Flash the Rom and when flash MAGISK, make sure you unmount DATA and mount VENDOR to avoid flash error. After unticking DATA, you can now install Magisk.
7) Now you can go to REBOOT, and press SYSTEM, and the phone will boot to Xiaomi EU 11 or 12, etc. just follow this process and enjoy your ROM.
Note: When updating, flash EU rom and Magisk, dont forget to unmount Data when flashing Magisk. You can probably disable decryption because that is why you can't mount Data when flashing Magisk. **Just don't ask me about it because I normally don't flash Disable Decyption often.
Click to expand...
Click to collapse
this post is gold! Coming back to xiaomi and twrp after 2 years with a huawei, hope to go smooth again with root magisk etc!

cerme said:
this post is gold! Coming back to xiaomi and twrp after 2 years with a huawei, hope to go smooth again with root magisk etc!
Click to expand...
Click to collapse
The root and flash process is basically the same process as the Mi 9T/K20, Mi Max 3, Mi Note 10 since decryption is now a common thing with Android 10... except for the VBmeta.zip, which is new and necessary to flash, as long as you follow the directions..you'll be fine.

Wmateria said:
The root and flash process is basically basically the same process as the Mi 9T/K20, Mi Max 3, Mi Note 10 since decryption is now a common thing with Android 10... except for the VBmeta.zip, which is new and necessary to flash, as long as you follow the directions..you'll be fine.
Click to expand...
Click to collapse
I understand. Last experience ti flash etc was on a mi5, so I have a little bit of rust with that. I do think that following instructions i shouldn't face major difficulties

cerme said:
I understand. Last experience ti flash etc was on a mi5, so I have a little bit of rust with that. I do think that following instructions i shouldn't face major difficulties
Click to expand...
Click to collapse
Same here, i was on the Mi 9T before, I didnt understood the whole new flashing process and carefully updating from EU Rom to AOSP Roms and back, I think i was messing with with thwe wipe and change partition feature (f2fs to ext 4 with an EU Rom) - then the Mi 9T bricked big time. Never recovered after that, luckily got it refunded for it but not many may have that second chance. After learning how to flash propeely and root, ect. I try to help out here when needed and ask too. I just got my Mi Note 10 2 weeks ago and rooted a week ago. So if anything, am willing to help out and repeat the following flash process or any changes in the future and feedback on future Roms.

Was thinking about which rom to use... does xiaomi.eu is stille faster with providing updates? what about the situation with OTA with that.
Now I have the phone with global rom, I want at least flash the EEA rom. But I also know that at some point i want to root, install magisk and get nice features. Still don't want to update manually everytime for an update...

will be watching this thread with much interest..
I recently bought this device (Global version) for use here in Australia.
my first time owning a Xiaomi - quite happy with it so far.
would be nice to have the themeing stuff work properly - I have used MIUI based ROMs back a LOoonggg time ago, in the days of the Nexus S and Galaxy Nexus etc.
used to have a new ROM flashed every couple of days lol, back then. But recent years I've stopped all that, no cool ROMs no snazzy kernels TWRP no nothing not even root lol, very boring!
anyway thanks for posting I hope to try this sometime soon

Hello is there any Eu rom for Mi note 10 lite?

Alisiddiqui75 said:
Hello is there any Eu rom for Mi note 10 lite?
Click to expand...
Click to collapse
yes, there is the EEA ROM you can find on miui website. You can flash it after unlocking bootloader with miFlash

Alisiddiqui75 said:
Hello is there any Eu rom for Mi note 10 lite?
Click to expand...
Click to collapse
I'm not sure if you mean the official ROM or xiaomi.eu.
The link to the official EEA(EU) ROM:
Recovery: https://bigota.d.miui.com/V11.0.7.0.QFNEUXM/miui_TOCOEEAGlobal_V11.0.7.0.QFNEUXM_7926bf9c02_10.0.zip
Fastboot: https://bigota.d.miui.com/V11.0.7.0...EUXM_20200508.0000.00_10.0_eea_4eb1c694c9.tgz
I have yesterday seen a xiaomi.eu Stable build for toco which is based on Global Stable ROM:
https://sourceforge.net/projects/xi...e10LITE_V11.0.4.0.QFNMIXM_v11-10.zip/download
I can not promise that it's working.

[GUIDE] [TB-X606F] [Lenovo M10 Plus FHD] How to flash TWRP, Generic System Image (Android 11, Android 12), and Root with Magisk

Hi, I'm a long-time lurker on these forums but recently had some success flashing a GSI and rooting the Lenovo Tab M10 Plus (FHD) (X606F) with TWRP, and wanted to share my exact steps here. This device is awesome for the price point but unfortunately not popular enough to have many guides available. The tablet is Project Treble compatible and uses A/B roms (although it is not an A/B device in terms of OTA updates). You can use the Treble Info app to confirm that the devices uses an ARM64 A/B operating system. This was tested with the CAOS 11 GSI based on Android 11; it may work on other GSIs and other Android versions but I have not tested those (NOTE: user below confirms working on Android 12). I've written this guide at a bird's-eye-view meant for users familiar with flashing.
A couple useful notes before we begin:
- Hardware force off: hold down both volume buttons + power button
- Hardware boot into bootloader: while powered off, hold volume down + power button
- Hardware boot into recovery: hold down both volume buttons + power button
- While in fastboot mode, the command `fastboot reboot recovery` does not work for me on this device. You may have to hardware boot into recovery using the hardware steps above (power off completely then hardware boot). [This command may work for some people. It does not work for my device.]
Obviously, make sure your bootloader is unlocked before starting.
1. I used Ubuntu since Windows was having trouble recognizing the device in fastboot mode; linux drivers seem to be better developed for this particular device. I used `sudo apt install android-sdk` to get the drivers. Much easier than the nonsense that you have to do on Windows to get this device to work. Unfortunately, the Lenovo rescue app is available only for Windows, so you'll need access to Windows to gain access to vbmeta.img for installing TWRP (below).
2. Install TWRP following this guide: https://forum.xda-developers.com/t/...rp-3-5-x-for-lenovo-tab-m10-fhd-plus.4222887/. It is important that you follow all these steps. After flashing the recovery, you must reboot into recovery to ensure that TWRP permanently installs. If the `fastboot reboot recovery` command does not work for you, hold down the power button to power off the device, then hardware boot into TWRP by holding down both volume buttons + power button to boot into TWRP. If you do not perform this step, the device will boot normally and TWRP will be erased. After booting into TWRP, wipe -> format data.
3. In TWRP, flash CAOS 11 GSI: https://forum.xda-developers.com/t/official-aosp-r-mod-caos11.4265059/. You can try with other GSIs - it will probably work - but I've only tested this particular one, and can attest for the stability of CAOS 11 on this device. The image you'll want is named with -arm64-bgZ. If you use another GSI, make sure to use the A/B arm64 image. CAOS 11 has gapps included, so no need to flash here; if you use another GSI that does not have, you'll need to flash the appropriate gapps yourself. You can also opt for the non-gapps download if you don't want Google spying on you.
4. (Optional/No longer necessary) In TWRP, flash to disable dm-versity: https://zackptg5.com/android.php#disverfe.
5. (Optional - many GSIs come with root) In TWRP, flash standard Magisk.zip: https://github.com/topjohnwu/Magisk. I didn't need to use Magisk-Phh.
6. Reboot system.
7. You may or may not get errors from Google Play saying that the device is not certified. Follow these steps:
- Sign into Google account on device via settings
- Download and install the Get ID app: https://f-droid.org/en/packages/makeinfo.com.getid/
- Open the app and Copy Google Service Framework Key
- Go to https://www.google.com/android/uncertified/
- Sign in and paste the copied value to it, register
- Reboot (this actually took me a few tries to get working, I believe the key is to make sure you're signed into your Google account)
- Google Play should be working
Feel free to ask any questions here.

I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.

dpn982 said:
I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.
Click to expand...
Click to collapse
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.

shnioob said:
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.
Click to expand...
Click to collapse
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.

dpn982 said:
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.
Click to expand...
Click to collapse
I think this tablet has always had an issue with Netflix due to lack of DRM or something of that nature - I wasn't able to get Netflix on the stock version. Disney+ is probably the same issue.
If you have some free time, it would be great if you can outline your steps for getting safetynet to pass. I haven't bothered with it.

Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.

Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error

emilio666 said:
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error
Click to expand...
Click to collapse
NEVERMIND, it got solved by just waiting a couple of hours after using the Google website: https://www.google.com/android/uncertified/

Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.

Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks for the clarifying info, updated the OP a bit. And thanks for providing us with a TWRP to make this possible. Otherwise this awesome tablet would be stuck on Android 10 forever.
vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Happy to help, glad it worked for you. I tried installing some other GSIs with and without flashing Magisk - LineageOS 12 boots but is very buggy, after reboot I was unable to get past the lockscreen. PixelExperience 11 and 12 cause a bootloop. If anyone has had success with PixelExperience I would love to get your input.

Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.

jebise101 said:
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.
Click to expand...
Click to collapse
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.

shnioob said:
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.
Click to expand...
Click to collapse
How do you go back to stock in case this does not work?
Is there a factory image?

jebise101 said:
How do you go back to stock in case this does not work?
Is there a factory image?
Click to expand...
Click to collapse
you can download the stock ROM from LMSA

I also have Lenovo tab m10 fhd plus but it is tb-x606v. Can I flash x606f rom on this device and flash twrp after.i don't want my device to be bricked.

vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Hi, I'm trying to follow what you did, but I'm having issues with the Gapps, do you have some pointers to solve it? Thank you in advance

Hello everybody!
I finally installed CAOS 11 and it's working like a charm. Gapps are definitely working as excpected and system seems to be stable as possible.
I have two question to those that installed it to :
Is anyone kow why some widgets on X606F are not clickable, an do not actualize till reboot?
Am I the only one that lost double tap to wake on CAOS?
Thank you all

I tried AOSP V412 12L too, we lost fingerprint sensor and face unlock, widevine DRM. There is some troubles on wifi, beside of this it is pleasant. Of course this not as smooth as android 10. I do not recommend it for daily basis.

I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.

garconblair said:
I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.
Click to expand...
Click to collapse
Thanks for the feedback. What about Widevine L1 and SafetyNet test with CAOS11? Are you able to play content at 1080p resolution with the Netflix App?