Database Users

[GUIDE][OSPREY] Moto G3 BEGIN: Unlock bootloader, Flash: TWRP, ROM, Root, Boot logo

Edited Dec 22 -2017 <-- I may not always change this, but this is a work in progress!
[GUIDE][OSPREY] Moto G3 2015 - BEGIN: How to Unlock bootloader, flash TWRP, flash ROM, flash Root, Flash boot logo.
I started this because while trying to explain it to a user I kept running in to old info.
Code:
/*
* Your warranty is now void.
*
* This may destroy your phone. As with any modification to a phone,
* you must be prepared/willing to THROW IT AWAY without thinking twice.
* If you need it or it is your daily driver, don't mess with it.
* I am 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 the suggestions in this guide
* before following it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This may well work on Merlin but I don't have one to test.
--> NOTE: I no longer use LineageOS so can't help there. Using AOSP 8. Should be no difference.
1a) Prep - before you do anything, in stock, go to settings/Development Options (which is turned on by tapping /settings/about phone/Build Number about 10 times.)
turn "OEM unlocking" ON
turn Debugging - "USB debugging" ON.
1b) Now! - To do anything, you must unlock your bootloader: This is done by going to the Motorola site and following their instructions completely.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
They want you to "Install the Android SDK.". You only need adb and fastboot on your PC (windows or Linux).
Try this guide to get ADB and FASTBOOT onto your computer: https://forum.xda-developers.com/showthread.php?t=2588979
For Ubuntu Linux simply type fastboot on the terminal and if it's missing a command will pop up as to how to add it - simple. same with adb.
ADDITIONAL THOUGHTS: a very helpful user suggested the following additional for unlock bootloader and getting adb and fastboot: @Dave here - see post 34ff.
Dave here said:
Glad it was helpful! Happy to be able to give something back. Here are some links I used...
LineageOS Osprey install guide:
wiki.lineageos.org/devices/osprey/install
LineageOS Using ADB and fastboot guide:
wiki.lineageos.org/adb_fastboot_guide.html
adb & fastboot: I used this link, which was in the LineageOS ADB guide and I think also the Motorola bootloader unlocking instructions:
Mac: dl.google.com/android/repository/platform-tools-latest-darwin.zip
Windows: dl.google.com/android/repository/platform-tools-latest-windows.zip
Linux: dl.google.com/android/repository/platform-tools-latest-linux.zip
Lenovo forum: "THERE IS AN ERROR WITH YOUR REQUEST! MOTO G ROOTING PROBLEM!" (it's actually about bootloader unlocking, not rooting):
forums.lenovo.com/t5/MOTO-G-MOTO-G-...EST-MOTO-G-ROOTING-PROBLEM/m-p/3458979#M27009
European Motorola unlocking URLs:
motorola-global-en-uk.custhelp.com/app/standalone/bootloader/unlock-your-device-a
motorola-global-portal-de.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
2) Now that your phone is "bootloader unlocked" you will get an ugly screen on every bootup - we'll get to that in step 4.
- Now you must set up a custom recovery so you can back things up and change things. To do that you need to flash a recovery from your PC.
-> Follow squid2's guide: https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Hint - to get into fastboot mode on your Osprey, power off, THEN, hold power and vol-down for maybe 8 seconds until the fastboot screen pops up, Then connect USB cable phone to PC.
I recommend flashing his latest.
I also recommend doing it twice in a row, simply because once in a while that is needed.
3) okay, now you can boot into TWRP: power off, hold power and vol-down for a few secs until fastboot screen pops up. use vol-down to step through the options. Choose Recovery and press power to select. 10 secs later, you're in TWRP. If you get the dead android it means you still have the stock recovery - boot to fastboot and flash TWRP again.
IMMEDIATELY tap Backup and select to put backup on external storage - your SDcard. NOTE - if your SDcard has been converted to "internal storage" you will have to choose "internal storage" (em0). I did it twice. This is your stock ROM. YOU WILL NEED THIS LATER.
-- > For TWRP BACKUP I use the default settings of "system,data, and boot". Here is a nice article that explains the differences: https://twrp.me/faq/whattobackup.html .
At this point I recommend you boot back into stock and connect your phone to your PC via USB (slide down) and copy that backup in the TWRP folder to your PC. at least once, maybe twice, for safe keeping. You will need this if you wish to test if a problem exists only on a custom ROM but not on the stock ROM. You will also need this if you simply choose to run stock, instead of a custom ROM. Remember, you are now testing ROMs - nothing is certain!
4. Getting rid of the nasty boot message:
This has some nice ones: https://forum.xda-developers.com/2015-moto-g/themes-apps/bootlogo-beautiful-logos-t3229167
Grab the one(s) you like and download - they're in .zip format. Put it on SDcard. Boot to TWRP, tap install, choose the one you want to flash. Voila.
Be aware there are some sites out there with logos that don't work on Moto G3.
5. To flash a custom ROM: Download to PC and put it on your SD card. Do same for gapps. (gapps - g-apps - google apps allow you to log in to your google account, use play store, etc. example http://opengapps.org/ (use arm, 7.1, whatever size you wish)(if you're new use full, mini, or micro until you know what you need. If you're on a 1GB phone, consider nano or pico.) )
https://download.lineageos.org/osprey or whatever ROM you want.
http://opengapps.org/ or whatever gapps you want.
Boot to TWRP.
Clean flash:
tap WIPE,
tap advanced, carefully checkmark:
Dalvic/ARTCache,
System,
Data,
Cache,
and then swipe the bottom swipe button. Takes a few sec. This is what makes a "clean flash".
Generally: Don't wipe "internal storage" or SDcard as this is where TWRP stores its backups/nandroids. - I always copy my TWRP backups to PC for safety.
Then back to menu screen and tap Install, select the rom, and swipe and let it do its thing.
Then back and tap Install, select the gapps and swipe to flash it.
THEN, and only then: tap Reboot (if you're at the main menu you also have to tap System to boot from system.)
The install takes 3 min or so before it starts asking questions.
Be sure to choose "Set up as New" or else you get whatever junk is in your google drive. This has cost errors and much time. <-----
6. Root: If you want to use bank apps, PokemonGo, etc, follow these instructions for Magisk:
https://forum.xda-developers.com/2015-moto-g/general/guide-pass-safetynet-custom-roms-t3603609
read the whole thread.
- Else go to https://download.chainfire.eu/1019
and download the zip form of Chainfire's SuperSU 2.79 and boot to TWRP and flash (install) it.
Many thanks to @acejavelin for inspiration and information(which I probably shamelessly stole from him), to @squid2 for his installation guide and his version of TWRP, to @Chainfire for the tons of work that continue to go into superSU, to @coolguy_16 for the safetynet/CTS work, and all the many Devs and helpers who make these ROMs possible, and as clean as they are! And to users like you who find bugs and file bug reports! Thank you!
Remember you are working with a Development ROM - a work in progress! (Even stock isn't perfect!!!)
Enjoy!

KrisM22 said:
I started this because while trying to explain it to a user I kept running in to old info.
As with any modification to a phone, you must be prepared/willing to throw it away without thinking twice. If you need it or it is your daily driver. don't mess with it. It is YOUR responsibility alone. If you break your phone, I will laugh.
1) To do anything, you must unlock your bootloader: This is done by going to a Motorola site and following their instructions completely.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2) Now that your phone is "bootloader unlocked" you will get an ugly screen on every bootup - we'll get to that later.
- Now you must set up a custom recovery so you can back things up and change things. To do that you need to flash a recovery from your PC.
a) you need to have fastboot support on your PC
Try this guide: https://forum.xda-developers.com/showthread.php?t=2588979
You do not need to put the whole SDK on as s9ome guides would have you do.
Follow squid2's guide: https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Hint - to get into fastboot mode, power off, THEN, hold power and vol-down for maybe 8 seconds until the fastboot screen pops up, Then connect USB cable phone to PC.
I recommend flashing his latest - twrp-osprey-3.1.0-r1.img
I also recommend doing it twice in a row, simply because once in a while that is needed.
3) okay, now you can boot into TWRP: power off, hold power and vol-down for a few secs until fastboot screen pops up. use vol-down to step through the options. Choose Recovery and press power to select. 10 secs later, you're in TWRP.
IMMEDIATELY tap Backup and select to put backup in internal (em0) storage. I did it twice. This is your stock ROM. YOU WILL NEED THIS LATER.
4. Getting rid of the nasty boot message:
This has some nice ones: https://forum.xda-developers.com/2015-moto-g/themes-apps/bootlogo-beautiful-logos-t3229167
Grab the one(s) you like and download - they're in .zip format. Put it on SDcard. Boot to TWRP, tap install, choose the one you want to flash. Voila.
5. To flash a custom ROM: Put it on your SD card. Boot to TWRP.
Clean flash: tap WIPE, tap advanced, carefully select Dalvic, Data, System, Cache, and then swip the bottom swipe thing. Takes a few sec. This is what makess a "clean flash".
Then back to menu screen and install, select the rom, and swipe and let it do its thing.
Then back and select gapps and flash it.
Then do supersu and flash that (optional)
Then "reboot".
6. Root:
Click to expand...
Click to collapse
nice information... hope this will help many friends..
Sent from my MotoG3 using Tapatalk

save1

save2

Subins Mani(Tintumonn) said:
nice information... hope this will help many friends..
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Thanks - hopefully it will help.

A factory reset is recommended. It wipes /data, /cache, ART cache as well as any remnant files in the internal and external storages, which are missed when manually wiping these partitions.
Wiping of /system is not always needed as the updater script of a ROM automatically wipes it before copying files. It is usually needed in case of updating ROMs where some persistent mods are needed to be removed such as gapps.
More on this here at TWRP FAQ.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
A factory reset is recommended. It wipes /data, /cache, ART cache as well as any remnant files in the internal and external storages, which are missed when manually wiping these partitions.
Wiping of /system is not always needed as the updater script of a ROM automatically wipes it before copying files. It is usually needed in case of updating ROMs where some persistent mods are needed to be removed such as gapps.
More on this here at TWRP FAQ.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I thought this was true but found my gapps was remaining residual in system - had to clear system to get rid of gapps.

KrisM22 said:
I thought this was true but found my gapps was remaining residual in system - had to clear system to get rid of gapps.
Click to expand...
Click to collapse
Yes you are correct, gapps won't get removed for new builds of the same ROM due to a persistent ROM script. However flashing a ROM different than the one currently installed usually ignores such scripts and does a clean wipe. Doing a manual wipe just to be sure is fine, even needed sometimes.
I just wanted to point out that not performing a factory reset (twrp>wipe>swipe to factory reset) can leave potential conflicting files in aforementioned places which can cause unexpected behaviours ranging from FCs to bootloop. The potential issues are rare but I think you know how much trouble it can bring to folks trying to capture real bugs (thanks for hard work at Linage ); it was all about removing the potential factors .
Broadcasted from Zeta Reticuli

The TWRP wipe-swipe does Data, Cache, and Dalvic. That's what I used to do. After messing up some tests this past week and wasting a lot of time, I now recommend adding system to that:
In advanced, checking data, cache, and dalvic/ARTcache, and, now, system. as far as i can see, I am leaving nothing other than internal storage and sd card (and of course whatever is in OTG if there's one attached). TBPro puts its backups on "internal storage". By the way I do appreciate your taking the time to look so closely at this!

KrisM22 said:
[GUIDE]
6. Root: Go to http://www.theandroidsoul.com/supersu-2-79-zip-apk-download/
and download the zip form of Chainfire's SuperSU 2.79 . Use it in step5 above.
NOTES: this has nothing to do with rooting your stock ROM which afaik can't be done.
Click to expand...
Click to collapse
To root stock ROM with SuperSU, you need to open a terminal in TWRP and type
Code:
echo "SYSTEMLESS=true" > /data/.supersu
This forces a systemless installation.
Edit: Not necessary anymore, just flash SuperSU zip and you're done
MagiskSU is an alternative to SuperSU and similar apps that hides root (to SafetyNet), so it's better to use that with stock ROM. It is also pre-installed on some ROMs like AICP.
If you're using LineageOS, it's best to use the official root package: https://download.lineageos.org/extras (direct link).

xMotoDA said:
To root stock ROM with SuperSU, you need to open a terminal in TWRP and type
Code:
echo "SYSTEMLESS=true" > /data/.supersu
This forces a systemless installation.
MagiskSU is an alternative to SuperSU and similar apps that hides root (to SafetyNet), so it's better to use that with stock ROM. It is also pre-installed on some ROMs like AICP.
If you're using LineageOS, it's best to use the official root package: https://download.lineageos.org/extras (direct link).
Click to expand...
Click to collapse
a) I have seen that but not tried it. I did add a note so you're now the authority!
b) not since SuperSU 2.79 - Those were invented because earlier SuperSUs had probs. I've been flashing 2.79 for a while now with no problems on Lineage.
Thanks for looking in!

KrisM22 said:
a) I have seen that but not tried it. I did add a note so you're now the authority!
b) not after SuperSU 2.78 (or 2.70 or something) - Those were invented because earlier SuperSUs had probs. I've been flashing 2.79 for a while now with no problems on Lineage.
Thanks for looking in!
Click to expand...
Click to collapse
SuperSU 2.79 "General Release" was the version of the change, anything prior needed the forced systemless command, all 2.79 or later versions include the correct check to flash on most Moto devices without the command. Using the echo command to create the file has no detrimental effects on later versions though. Note that using https://download.chainfire.eu/supersu/ as your download link will always get you the most current stable version of SuperSU available directly from the official source.
Magisk is the way to go to root most stock devices though, I would definitely agree with that.

acejavelin said:
SuperSU 2.79 "General Release" was the version of the change, anything prior needed the forced systemless command, all 2.79 or later versions include the correct check to flash on most Moto devices without the command. Using the echo command to create the file has no detrimental effects on later versions though. Note that using https://download.chainfire.eu/supersu/ as your download link will always get you the most current stable version of SuperSU available directly from the official source.
Magisk is the way to go to root most stock devices though, I would definitely agree with that.
Click to expand...
Click to collapse
Huge thanks for that!!! Changed above post.
Never played with Magisk - others (you!) are the authority on that. I think some were saying that was a way to get a custom rom to pass safteynet... Thanks!
Huge thanks for looking in!!!

edited/updated 5-4-17

Problem!
Resurreccion no me va bien en mi movil, se sobre calienta demaciado, por lo demas bien!

GermanRodriguez said:
Resurreccion no me va bien en mi movil, se sobre calienta demaciado, por lo demas bien!
Click to expand...
Click to collapse
This is possibly a problem with that rom - ask at that thread.
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-n-5-8-2-t3587204
or
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-t3478845

edited...

edited

update

changed.

*GUIDE* [Honor 8] Kali NetHunter Installation *UNOFFICIAL*

***WARNING***
This is NOT an official guide and I'm not affiliated with Offensive Security [ :crying: ].
This is just my personal guide.
I've been playing with this today and lot of my tries ended up with bricking my device.
Currently this method is working, but I am NOT responsible for any bricked devices.
If you never encountered/heard of bootloop/brick, please consider ignoring this tutorial.
DON'T FORGET TO MAKE A NANDROID BACKUP!!!
Hi guys! This is my quick-guide on how to install a Kali NetHunter on Huawei Honor 8.
It's quite simple, just read every step carefully.
This is just a guide. All credits goes to: CyanogenMod , TWRP, Offensive Security
So let's start!
*REQUIREMENTS*
- Rooted device
- Custom recovery TWRP/CWM
- A bit of patience
- Brain
You will need to flash a new recovery image through your old one .
So it's exactly very easy. I've already tested a lot of things and everything is working just fine.
So follow this steps:
1. Download CM 13 for Honor 8 and put it on your SD card. Link here.
2. Download this TWRP image for CM 13 / Honor 8 and put it on your SD card. Link here.
3. Download OpenGApps (Select arm64, 6.0, mini) and put in on your SD card. Link here.
4. Download Kali NetHunter (generic-arm64) and put in on your SD card. Full version: HERE. Minimal version: HERE. Just select the version you prefer. I'm using FULL, but I also tried minimal and it's working fine.
So after you downloaded all the files and you have it on your SD card:
1. Power off your Honor 8
2. When it's already off, press&hold Power and Volume Up button, until your device vibrates and the display starts up.
3. You should now be in your recovery. Press Install and select the TWRP recovery image, which you have downloaded on you SD card. Slide the panel to flash.
4. After you successfully flashed the image, head into main TWRP menu and select Reboot -> Recovery.
5. After you reboot into your recovery, choose cancel, if device ask for password key. If TWRP asks you if you want to allow write access to the system partition. IT IS VERY IMPORTANT THAT YOU ALLOW THIS. Check the box that says to never ask this question again.
6. Do a basic WIPE
7 . Flash the CM 13 then flash GApps
8. !IMPORTANT! Now reboot to your system and complete the basic "First-start" settings. Do NOT flash Kali NetHunter, if you haven't completed the first-time boot settings.
9. When you set up your phone and you are already on your Home Screen, power off your phone and boot to recovery again.
10. Now flash the Kali NetHunter, which you have downloaded on your SD card.
11. After the installation is complete, you can reboot to your system.
12. Press the power button on the Huawei Unlocked Bootloader warning screen. It will take a bit longer to boot than normal. It's completely fine. Just let it be for like 30 secs.
13. Now the Kali Bootanimation will start. Your phone will probably turn off during the bootanimation on your first boot. DON'T PANIC. It's fine. It will automatically restart and boot to your new system.
14. Now open up the NetHunter app. It will ask you for some permissions. It's important to ALLOW all the permissions.
15. After you allowed it all permissions, you can now close the NetHunter app and enjoy your Kali NetHunter
Sorry for my bad English
If you brick your phone, wipe your data and flash everything except the TWRP image again.
It's not my fault if you damage your phone by doing this. Remember that you are doing this on your own risk.
Have fun with your NetHunter on Honor 8
Screenshots:
http://imgur.com/a/8Wdyf
http://imgur.com/a/95dx0
http://imgur.com/a/YBxRS
http://imgur.com/a/E4gZ0
http://imgur.com/a/mkwet

will it works on stock rom??

Do I need to be on a specific build for this or does it not matter?

VenuGopalu said:
will it works on stock rom??
Click to expand...
Click to collapse
Unfortunately no. It requires some components from CyanogenMod.
FreeLineTM said:
Do I need to be on a specific build for this or does it not matter?
Click to expand...
Click to collapse
You mean specific NetHunter build or CyanogenMod build?
I tried one older build of NetHunter and it worked fine as well, but I'm not sure about the CyanogenMod. I think there are only 4 builds of CM13 for Honor 8 and this one is the newest. But I think the older builds would work too.

Flexy' said:
Unfortunately no. It requires some components from CyanogenMod.
You mean specific NetHunter build or CyanogenMod build?
I tried one older build of NetHunter and it worked fine as well, but I'm not sure about the CyanogenMod. I think there are only 4 builds of CM13 for Honor 8 and this one is the newest. But I think the older builds would work too.
Click to expand...
Click to collapse
I mean the EMUI stock build. I'm currently on FRD-L09C432B381

FreeLineTM said:
I mean the EMUI stock build. I'm currently on FRD-L09C432B381
Click to expand...
Click to collapse
Unfortunately no I tried it on stock build but without any success. It definitely requires CyanogenMod

it is working on my phone with stock mm rom ,, the boot animation was awesome ,, it was booted my device well and several apps were installed .i will attach a pic in below

Flexy' said:
Unfortunately no I tried it on stock build but without any success. It definitely requires CyanogenMod
Click to expand...
Click to collapse
I mean what build I need to be on to flash Cyanogen?
---------- Post added at 07:13 PM ---------- Previous post was at 06:55 PM ----------
Stuck on your device is booting now after flashing new TWRP and rebooting to recovery, but can still boot to system and flash old TWRP.

VenuGopalu said:
it is working on my phone with stock mm rom ,, the boot animation was awesome ,, it was booted my device well and several apps were installed .i will attach a pic in below
Click to expand...
Click to collapse
Wow, I couldn't get it working My phone always booted to the EMUI, but none of NetHunter components were installed. Strange.
FreeLineTM said:
I mean what build I need to be on to flash Cyanogen?
---------- Post added at 07:13 PM ---------- Previous post was at 06:55 PM ----------
Stuck on your device is booting now after flashing new TWRP and rebooting to recovery, but can still boot to system and flash old TWRP.
Click to expand...
Click to collapse
Oh, I don't know if there is a build number limitation, but you definitely need MM ROM firmware.
Link to the original CM 13 Honor 8 thread.
Hmm.. Strange. What version of TWRP were you using to flash the Honor 8 one?

Flexy' said:
Wow, I couldn't get it working My phone always booted to the EMUI, but none of NetHunter components were installed. Strange.
Oh, I don't know if there is a build number limitation, but you definitely need MM ROM firmware.
Link to the original CM 13 Honor 8 thread.
Hmm.. Strange. What version of TWRP were you using to flash the Honor 8 one?
Click to expand...
Click to collapse
It's not strange because I was on nougat with latest nougat TWRP when I tried the first time. But I rolled back to mm and completed the steps. However, the data partition was encrypted after rebooting to recovery with the new TWRP. I had to format data then reboot to recovery again. You should add this to the guide.

Flexy' said:
Wow, I couldn't get it working My phone always booted to the EMUI, but none of NetHunter components were installed. Strange.
Oh, I don't know if there is a build number limitation, but you definitely need MM ROM firmware.
Link to the original CM 13 Honor 8 thread.
Hmm.. Strange. What version of TWRP were you using to flash the Honor 8 one?
Click to expand...
Click to collapse
I have tested on twrp-3.0.2-0-frd.img&twrp-3.1.1-0-frd.img both are working without any issue
link for twrp:::: https://dl.twrp.me/frd/

I successfully flashed nethunter on stock Nougat (FRD-L09C432B360).. DriveDroid which is the only thing I want didn't work with stock because it couldn't find USB mass storage. I tried to install it via nethunter instead but it didn't work there either. Might be because I forgot to open nethunter once for setup though..

FreeLineTM said:
I successfully flashed nethunter on stock Nougat (FRD-L09C432B360).. DriveDroid which is the only thing I want didn't work with stock because it couldn't find USB mass storage. I tried to install it via nethunter instead but it didn't work there either. Might be because I forgot to open nethunter once for setup though..
Click to expand...
Click to collapse
Can you tell me how you installed Nethunter on FRD-L09? I am pretty new to this android scene , also you know if the fingerprint sensor works normally?

darkrsing said:
Can you tell me how you installed Nethunter on FRD-L09? I am pretty new to this android scene , also you know if the fingerprint sensor works normally?
Click to expand...
Click to collapse
I don't think fingerprint worked if I recall correctly. I installed NetHunter as any custom ROM if I remember correctly.

I have installed it on Stock rom by using Magisk (and root of course). Very simple, very powerful.

[Discussion] DualBootPatcher

I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.

Got now rr as primary rom and will try later on to flash some roms on the second space... Let you know if that works out.

Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk

superior8888 said:
Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk
Click to expand...
Click to collapse
I have also rr as primary but second rom install ended in error 1 in twrp. Maybe you can try to reset data of second rom with the dualboot patcher zip.

It might be helpful to read the Dual Boot Patcher thread for the OP5, as there may be some important info there that is relevant for getting it to work on the 5T.

I tried rr as primary, no problem. Tried adding 2nd rom as secondary, as data slot 1, and no dice. Even tried removing assert lines in the updater script as suggested in op5 with rr as 2nd rom but that didn't work either; either booted back to twrp or booted to a black screen. If anyone makes it work please document and share your work. I'm encrypted by the way, even though you're "supposed" to be decrypted I was able to switch between primary and the non-booting rom just fine.

Anyone having any luck with this?

matteosaeed said:
Anyone having any luck with this?
Click to expand...
Click to collapse
Nope primary install goes good with a oos rom not stock. But when you try to install a second rom it gives error 1 in twrp and rom don't boot up.

That's great! Old MultiROM user here!

Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?

superior888 said:
I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.
Click to expand...
Click to collapse
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN ?
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.

cubandanger05 said:
Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?
Click to expand...
Click to collapse
Thanks for updating us, I'm an old multirom user as well and I'm going to keep my eye on this.

cubandanger05 said:
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.
Click to expand...
Click to collapse
Thanks! I'll try this next days.

Thanks. Nothing works with Oreo as of yet i suppose :/

superior888 said:
Thanks. Nothing works with Oreo as of yet i suppose :/
Click to expand...
Click to collapse
It may be possible to have oreo as primary and flash Nougat as data slot roms. I tried with Phoenix as primary and I could boot into rr Nougat in data slot but Phoenix wouldnt boot. If someone can try rr oreo as primary and report back. I'm tempted to try with otg and see if I can install secondary roms using extsd option

*Quick update*
I was able to keep latest Phoenix oreo ROM as primary and install and boot Nougat RR as data-slot and as secondary using the latest dualbootpatcher app which may have fixed the "failed to update mbtool" error I was getting on Phoenix ROM. Also I used Magisk 14.0 for root as the latest version 16.0 kept booting back to recovery on non primary ROMs.
I'm still unable to flash Oreo ROMs as data-slot or secondary. At least we're able to keep Oreo as primary and test Nougat ROMs until dualbootpatcher app is compatible with Oreo or until some other fix is released.
Internal storage/data is still encrypted and unreadable on all non-primary ROMs; you must be decrypted prior to installing additional ROMs to have access to it, which I haven't tested yet.
See screenshots

Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.

es0tericcha0s said:
Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.
Click to expand...
Click to collapse
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Edit: Now that it's working almost as intended we should make an official "how to" thread

cubandanger05 said:
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Click to expand...
Click to collapse
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.

es0tericcha0s said:
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.
Click to expand...
Click to collapse
? understandable

[Port] [Recovery] BLU DASH M 2 - CTR Carliv Touch Recovery 6.6.1 - Root not required

We have the first port and root for this highly unpopular BLU phone.
BLU DASH M 2 - Carliv Touch Recovery 6.6.1 aka CTR​I have managed to replace the stock recovery and still keep the stock system since there are no customs roms at the moment. The recovery doesn't require you to be rooted but rooting is possible after flashing or booting this rom. Don't fall for the fake Dash files on youtube, I have downloaded them all and they are copies of similar phones and don't work.. This one is ported over from the D070Q by Carliv.
It will not flash a full custom rom but will flash ZIPs so you can root, recover, flash partitions and hopefully pave the way for a TWRP . I do have a TWRP ported over to the BLU Dash M 2 but the touch doesn't work so you can't pass the first swipe screen.
DOWNLOAD from uploadfiles.io @ https://ufile.io/8oc6k​
Instructions
- Make sure to backup any important files, this will wipe your data pics, vids, etc..
- Enable OEM unlock under developer options and power down phone
- Boot to stock recovery by holding PWR + VOL UP
- In recovery choose "Reboot to Bootloader" ( aka fastboot )
- You should now be at a blank screen with Fastboot mode: at the bottom
Open your terminal and type the following code, obviously replacing your paths with the correct ones.
fasboot devices < --- will return a serial number or something to indicate connection is OK
fastboot oem unlock <--- will prompt your phone screen to accept unlock request, chose VOL Up to accept and make sure it says "Unlock pass" at the bottom
For testing only
fastboot -c "lge.kcal=0|0|0|x" boot CTR_6.6.1_BLU_DASH_M2_D090U.img
For permanent flash
fastboot flash recovery CTR_6.6.1_BLU_DASH_M2_D090U.img
Don't power down, instead boot in the same recovery
fastboot -c "lge.kcal=0|0|0|x" boot CTR_6.6.1_BLU_DASH_M2_D090U.img
Inside CTR select Wipe cache, Dalvik cache, Userdata / Data.
Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
On first reboot it will reboot twice, then boot the stock system as if it was a factory reset.
This now paves the way for root with Magisk. See my post after this for rooting Blu Dash M2.
Enjoy !

RESERVED

Hey Thank you, got it working. Had to alter it a bit though. Had to select "Yes" for the fix as mine was restoring the old recovery.
Also when I followed your method, the system was not mounting the internal storage.
So I didn't wipe the data and used "Yes" when rebooting and the recovery is good.
I'll be looking out for the root constructions.
Great tutorial though.

73Hn said:
Hey Thank you, got it working. Had to alter it a bit though. Had to select "Yes" for the fix as mine was restoring the old recovery.
Also when I followed your method, the system was not mounting the internal storage.
So I didn't wipe the data and used "Yes" when rebooting and the recovery is good.
I'll be looking out for the root constructions.
Great tutorial though.
Click to expand...
Click to collapse
That will not work for root because Magisk needs the original boot rom. I'm sure it worked for you and that's a good start but wiping the partitions in order does work as well, I probably just left something out or got the order wrong. It's important we don't use CTR to patch because then Magisk complains about boot img being aleady patched and doesn't work.
Anyway you get the idea, it took me a few tries as well but in the end I managed to keep all 3 features intact, the stock rom + CTR + root. If you need to start again you don't need the full rom or sp flash, just flashing system.img to sytem partition works to restore everything.
I'm hoping to find the source code to the kernel and make a TWRP with touch working but the CTR is the only thing we have so far. It does flash zips just not full operating systems. It also flashes boot and recovery partitions.

Thanks, I can restore and try again. Do you have the tutorial for the magisk to root?

73Hn said:
Thanks, I can restore and try again. Do you have the tutorial for the magisk to root?
Click to expand...
Click to collapse
I think most can figure out Magisk from here, the real hurdle was the lack of a recovery because the stock rom doesn't allow Magisk to be flashed.

Thanks, I already started checking in on it... I'll update here once I get through.

How to Root Blu Dash M 2 with Magisk​
I have managed to root the stock system using Magisk. The stock recovery will not let you do this, as usual ignore the garbage on youtube and personal blogs, they're giving false info and fake files. This method works and I'm the first user who ported CTR 6.6 to allow for this.
DOWNLOAD Magisk from developer https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
FOLLOW THE ABOVE POST to replace stock recovery with CTR 6.6​
Instructions
- Follow first post to install CTR 6.6 recovery and reboot a couple of times to make sure it stuck.
- Enable OEM unlock under developer options and power down phone
- Boot to new CT 6.6 recovery by pressing PWR + VOL UP
- In recovery choose "Install Zip" and choose the "Magisk.zip" from your /SDCARD
Magisk installer will launch and if you did everything right, complete without errors.
- Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
Phone should now reboot twice and have Magisk installed. I have verified root by deleting protected files like default.prop and gave Root Explorer permanent root access. If something doesn't work just find the right sequence. I believe it was flash system, flash recovery. wipe partitions. flash magisk
Enjoy !

The only thing left do now is find the Blu kernel source code for the M2 so a working TWRP can be compiled from scratch, then any MT6580 rom should be flashable.

Perfectly... Got it working using your same method after reinstalling the firmware... only difference was.
After installing recovery and booting into it, I then installed Magisk via adb sideload.
Confirmed root works.
Thank you very much for your patience and assistance

graciaaas

romish said:
How to Root Blu Dash M 2 with Magisk
I have managed to root the stock system using Magisk. The stock recovery will not let you do this, as usual ignore the garbage on youtube and personal blogs, they're giving false info and fake files. This method works and I'm the first user who ported CTR 6.6 to allow for this.
DOWNLOAD Magisk from developer https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
FOLLOW THE ABOVE POST to replace stock recovery with CTR 6.6
Instructions
- Follow first post to install CTR 6.6 recovery and reboot a couple of times to make sure it stuck.
- Enable OEM unlock under developer options and power down phone
- Boot to new CT 6.6 recovery by pressing PWR + VOL UP
- In recovery choose "Install Zip" and choose the "Magisk.zip" from your /SDCARD
Magisk installer will launch and if you did everything right, complete without errors.
- Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
Phone should now reboot twice and have Magisk installed. I have verified root by deleting protected files like default.prop and gave Root Explorer permanent root access. If something doesn't work just find the right sequence. I believe it was flash system, flash recovery. wipe partitions. flash magisk
Enjoy !
Click to expand...
Click to collapse
Thank you very much! You do not know how much I needed to be root! I thought that this device was impossible to root. I really am very grateful. Friend was asking me if you could adapt the custom Slimrom rom for this device? because all the storage of this one takes the system, it would be of great help for all the users of this phone, I do not know if you can or are interested, but I thank you in advance

romish said:
We have the first port and root for this highly unpopular BLU phone.
DOWNLOAD from uploadfiles.io @ https://ufile.io/bj9kk​
Enjoy !​
Click to expand...
Click to collapse
Hi, can you provide a download link that doesn't require you to get a premium account to access the file. It's against XDA rules.​

kirito9 said:
Hi, can you provide a download link that doesn't require you to get a premium account to access the file. It's against XDA rules.
Click to expand...
Click to collapse
It is not premium, the file just expired so the site will keep it on line for a fee. I'll upload it again.

romish said:
It is not premium, the file just expired so the site will keep it on line for a fee. I'll upload it again.
Click to expand...
Click to collapse
Try this one.. if the host tries to replace it with the original let us know and one of the others who have the file will re upload it to another host. I don't feel like signing up anywhere so that is why I use this host.
https://ufile.io/8oc6k
https://ufile.io/8oc6k
https://ufile.io/8oc6k

kevoncrush said:
Thank you very much! You do not know how much I needed to be root! I thought that this device was impossible to root. I really am very grateful. Friend was asking me if you could adapt the custom Slimrom rom for this device? because all the storage of this one takes the system, it would be of great help for all the users of this phone, I do not know if you can or are interested, but I thank you in advance
Click to expand...
Click to collapse
All 'ya 'all are welcome . Unfortunately I can't go any further because there is no source for the kernel so TWRP won't work because there is no touch to get past the first screen. Otherwise if it. did slim rom would flash without any problems, its just these older recoveries don't support a few things that TWRP has to make flashing full roms successful. If someone has source files for the BLU Dash M2 let me know.
I'll just let you guys know, I managed to make a pretty good custom rom with root only by deleteing everything but the core OS. I don't recommend this for everyone but I did get rid of just about everything and made this 6.0 more like 4.4 .. I got it to the point where even the phone and SMS didn't work and the google framework was deleted, then slowly began adding my approved versions of apps. Now its totally de googled but again I realize this isn't for everyone. I just wanted a small rom with camera ad GPS and those are working fine for me.

Custom recovery link taken down again
Could someone please upload the custom recovery again?

[Port] [Recovery] BLU DASH M 2
I tried to fast boot as peryour instructions but I get the error: cannot load ' ctr_6.6.1 etc. :crying:

Please try this link, if you have a better locarion to store it please do so and reshare as this link is only valid for 2 days.
ctr_6.6.1_blu_dash_m2_d090u.img
---------- Post added at 05:08 AM ---------- Previous post was at 05:01 AM ----------
If that recovery does not work, try this one. I have two of different sizes and can't remember which one i used.
recovery.img

Download link
Please repost the download link

[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.