[GUIDE] Updating any ROM with Magisk installed on your device - Xiaomi Mi 8 Guides, News, & Discussion

So I was looking for an answer of being stuck in the bootanimation and I found the answer. I've gave this tip on some ROM threads and one guy has finally tried and the result was positive. And today, with Pixel Experience update, I was able to confirm that this method works so I wanted to tell you guys that you won't need to clear data anymore.
Before the ROM update, you will need to flash the stock boot.img in Magisk. Use "Uninstall" button and click on the "RESTORE IMAGES" button. This is supposed to keep your modules, but I haven't tried it since I was getting some sort of error that claims I don't have any backup, but I do.
Another way is to flashing the stock boot.img in the firmware update file of your current version, not the version that you are updating. It's supposed to work in theory and should keep the modules you have. Haven't tested it yet.
And lastly flashing the Uninstaller.zip. It'll remove your modules too, so get ready to install them all again, so keep a Screenshot of them if there are plenty of them.
After doing one of these three, you are good to go with installing the update. They will work on any ROM, including miui.
Ps: In latest magisk releases, after restoring the stock boot image and flashing something from recovery, it appears that magisk reflashes itself again after the flashing is done. This means if you are going to update system, you only need to restore boot.img and install the update, magisk will install itself after the update.
Please note that your kernel will need to be flashed again if you are using a different kernel.
Have a great day.
If this thread helped, hit the like button and if it didn't, you know what to do. For more of these threads, hit bell icon and don't forget to subscribe. PLEASE HIT THE BELL ICON OR I'M ****ED. PLEASE USE IT, MY FAMILY ID STARVING USE THE DAMN BELL ICON!!!

Thnks mate for the info, Ill try it soon and let you know.
Gesendet von meinem MI 8 mit Tapatalk

Eclipse1991 said:
Thnks mate for the info, Ill try it soon and let you know.
Gesendet von meinem MI 8 mit Tapatalk
Click to expand...
Click to collapse
You are welcome, I am trying to spread the information.

What I do when there is update (miui):
Download update, go to twrp
1. Flash update
2. Flash magisk
3. Flash disable dm force encrypt patch
done

lesharodin said:
What I do when there is update (miui):
Download update, go to twrp
1. Flash update
2. Flash magisk
3. Flash disable dm force encrypt patch
done
Click to expand...
Click to collapse
No. Just update and flash magisk. The dm verity patch is already included in a magisk package.

Related

[Recovery] Unofficial TWRP SM-G360T1

Quick fast post. Fix it up later.
Unofficial TWRP for the SM-G360T1
Step 1:
You should know how to flash twrp by now.
Step 2:
Profit
Download link:
https://www.androidfilehost.com/?fid=24052804347820600
Known issues:
Usb otg not working. Will fix later.
Enjoy. Hit thanks or donate and all that good crap [emoji14]
Mine
THANK YOU ONCE AGAIN @ShinySide!!! Not only for root, but now for a working custom recovery. Truly the 2 most important tools we could have for our phone.
FOR EVERYONE ELSE:
As usual, be sure to give @ShinySide your Thanks/Donations/etc.!!! He deserves it! Also, now that you have TWRP you might be wondering what to do next. Here are a couple of suggestions of things that I've already done and that I am quite happy with.
1) Theme it! - Here are some themes you can try out that will not only make TWRP more beautiful, but also provide a layout that is more intuitive and user friendly. These are listed in a Galaxy S2 thread yes, but I've attached a picture of the one that I'm currently running and I'm happy to say that it works on our phone like a charm. I've also used these themes on other phones in the past. Just follow the instructions in the OP of that thread and give the guy some thanks on that thread if you like them. There is no risk in this btw. Either it works or it doesn't and to get rid of it if you don't like it you just have to delete the theme folder that you placed in TWRP. (Try to use the files that say "480x800" as that's the resolution of our screen.) Here is the link: http://forum.xda-developers.com/galaxy-s2-plus/themes-apps/theme-materialised-t2933979
2) Add the Xposed Framework - Go to this link here: http://forum.xda-developers.com/showthread.php?p=62377731
Then, install the Xposed app from the link on that thread. After that, you're going to want to pick the file attached to the OP of that thread that is called "xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip" and save it to the root of your external SD card. (Do not download the one that says "ARM64" in it. Just the one I mentioned.) Then, just flash it via TWRP and reboot. You should now have the Xposed Framework installed. Once, again be sure to give the OP thanks on that thread too!
NOTE: After flashing Xposed it may hang on the MetroPCS screen on the next reboot for up to 15-20 mins or so while it's doing stuff. If it's any longer than that, then just pop the battery out and reboot. It will boot properly after that while it reoptimizes some apps.
OK something not right everytime I flash the twrp I keep getting the 2.8.70 instead of the version of This 2.8.1.0 one I need help cause everything is correct I keep getting that old version instead of this new version but twrp 2.8.7.0 still works good but I want the version right here
Deandre7452 said:
OK something not right everytime I flash the twrp I keep getting the 2.8.70 instead of the version of This 2.8.1.0 one I need help cause everything is correct I keep getting that old version instead of this new version but twrp 2.8.7.0 still works good but I want the version right here
Click to expand...
Click to collapse
2.8.7.0 is right. The picture I attached of my themed one I just downloaded from the theme thread because I couldn't take a screenshot from TWRP. Everything is good. No need to worry.
Thanks....glad to know that but everytime I reboot to system from twrp it keep going right back to the twrp instead of system that's what I worry about I have to keep flashing the kernel root cause the twrp not working right but ima get the theme to see what happens next
Deandre7452 said:
Thanks....glad to know that but everytime I reboot to system from twrp it keep going right back to the twrp instead of system that's what I worry about I have to keep flashing the kernel root cause the twrp not working right but ima get the theme to see what happens next
Click to expand...
Click to collapse
It shouldn't be doing that. Also, you should just make sure your TWRP is properly installed first before you do anything else to it. Maybe try rebooting your phone just by holding the power button once instead of selecting reboot system and see if it boots correctly then.
Sent from my SM-G360T1 using Tapatalk
I don't think it's right now I have the same picture frame u have in the picture but still not 2.8.1.0 at the top it have the 2.8.7.0 up there at the top of it and another thing is I can't flash anything everything else good but can't swipe to install so I need to get this right cause I don't be having problems with nothing else when I do stuff for my device
Deandre7452 said:
I don't think it's right now I have the same picture frame u have in the picture but still not 2.8.1.0 at the top it have the 2.8.7.0 up there at the top of it and another thing is I can't flash anything everything else good but can't swipe to install so I need to get this right cause I don't be having problems with nothing else when I do stuff for my device
Click to expand...
Click to collapse
Again, it is supposed to be 2.8.7.0 . Don't go by the picture I posted it was just a sample of what I had. Not a screenshot. Also, it doesn't need to look like mine to work. Theming it was just for fun and should only be done after you've successfully installed TWRP. Anyhow, try flashing this stock recovery file here. Then, boot into stock recovery and make sure you can still reboot to Android from there. If so, then go back and try flashing the TWRP recovery file again instead and see if that fixes the problem. No one else should flash this file by the way unless they are trying to go back to stock recovery for whatever reason. Thanks!
Sent from my SM-G360T1 using Tapatalk
Good job
Awesome! Goood job dude, can't wait till you write up the proper instructions. I'm a noob so don't want to do something wrong.
Another masterpiece By @shineside....
A great BIG Thank you @Bogarty For helping to bring this all together.
We have root, we have TWRP, and that's all thanks to @ShinySide! Great work!
Ok yall I just did a splash screen if anyone don't know but everyone have the color theme already go to the page here http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584 scroll down to the change the recovery splash screen download the AIK file First when it finish flash it before anything download the splash set zip when it finish unzip that file then u download the trap kernel root are if u already have it on the device use any root explore renamed the tar.md5 to .img now go to recovery flash that AIK before you start anything hit where u change your theme color but click on change splash then u put the trap kernel.img on the first slot then the second slot click inside the splash set folder choose what color u want then flash it then there u go a new splash screen set......this for anyone that don't know
bogarty said:
It shouldn't be doing that. Also, you should just make sure your TWRP is properly installed first before you do anything else to it. Maybe try rebooting your phone just by holding the power button once instead of selecting reboot system and see if it boots correctly then.
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
So, should this NOT work and it continues to reboot to TWRP what comes next? ? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
i am oblivion said:
So, should this NOT work and it continues to reboot to TWRP what comes next? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try flashing through ODIN again. Make sure you are in actual download mode (meaning don't use the option in TWRP, use the key combo), and flash it again.
Maybe we could get another youtube video? What do you say, "TheDerek"?
xRaZeR_FuZioNx said:
Try flashing through ODIN again. Make sure you are in actual download mode (meaning don't use the option in TWRP, use the key combo), and flash it again.
Click to expand...
Click to collapse
Ok, that's next on the agenda. Gonna take a walk and get myself calmed down before I resume troubleshooting. Thanks for the helpful and speedy response. And the bit about booting into Download Mode using the button combo over the TWRP option - I actually had no idea there was a difference there. I've gathered several boot/recovery zips and tars just in case and am tracking down the T-Mobile version of the g360t1 firmware as well (to cover all my bases, because when it rains it pours ?). Anyhow, I'll report back once I have something to report and thanks again guys ?
i am oblivion said:
Ok, that's next on the agenda. Gonna take a walk and get myself calmed down before I resume troubleshooting. Thanks for the helpful and speedy response. And the bit about booting into Download Mode using the button combo over the TWRP option - I actually had no idea there was a difference there. I've gathered several boot/recovery zips and tars just in case and am tracking down the T-Mobile version of the g360t1 firmware as well (to cover all my bases, because when it rains it pours ?). Anyhow, I'll report back once I have something to report and thanks again guys ?
Click to expand...
Click to collapse
i am oblivion said:
So, should this NOT work and it continues to reboot to TWRP what comes next? ? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
Click to expand...
Click to collapse
It has to be something you guys are doing during the flashing process that is causing it to boot into TWRP instead of Android. I would try flashing the Trapkernel again from download mode to see if that gives you boot, then if so, try flashing TWRP again. Both should be flashed in AP slot of ODIN. Make sure OEM Unlocking is checked in developer options, etc.
If that doesn't work and it still boots to TWRP, then you may have messed something up in there somehow. Try flashing back stock boot and stock recovery and make sure boot and stock recovery were restored. Once that's working, then you can try reflashing Trapkernel and TWRP. Use this link for more info on restoring your phone and for links to the stock files if you need them.
http://forum.xda-developers.com/showthread.php?p=62906680
Sent from my SM-G360T1 using Tapatalk
Theres a problem, I cant moutn system in Twrp and because of that i cant update SU binary and some apps dont work :/
cmurder61 said:
Theres a problem, I cant moutn system in Twrp and because of that i cant update SU binary and some apps dont work :/
Click to expand...
Click to collapse
Try reinjecting TWRP using the option in settings.

[DOWNLOAD] 6.0.1 update.zip

So my watch recently downloaded the latest 6.0.1 update.zip and I'm more than happy to report: WE CAN FLASH IT VIA TWRP!
This update.zip was grabbed from /cache, however seems to be completely identical with the one you can download from here: https://android.googleapis.com/pack...3ec3e78cb2a7d3.signed-platina-ota-2576000.zip
Exciting news, means we don't have to reset our watch back to stock for it to flash
Here are the download links:
Dropbox
Google Drive
OneDrive
Happy flashing!
loving the new update. its so smooth.
eraycetin said:
loving the new update. its so smooth.
Click to expand...
Click to collapse
That indeed Once the watch was updated it lagged for about 10 minutes still, probably due to it doing stuff in the background after the upgrade. But once that was done it's now working great, smooth and awesomely well!
thanks.
i still wiped out everything to have a more clean experience. and faster.
Yeah I would say the only reason we don't have to go back to stock is that the ota contains completely brand new system image and boot and recovery of course so it thosen't even verify system files as they all get replaced anyway
Can we flash this new stock and then flash a custom kernel? Idk anything sorry, this will be my one annoying question for the day
For 6.0.1 there is no kernel at the moment.
MihaiSG said:
For 6.0.1 there is no kernel at the moment.
Click to expand...
Click to collapse
No kernel for 6.0.1?? Really??
Go here :
http://forum.xda-developers.com/showthread.php?t=3082669
I haven't checked the topic today. Good that it was updated, can't wait to test it. Thanks for the heads up
Gohma Custom Rom
Hey guys,
My watch is currently running Gohma ROM. can i sideload the update and install right on top, or should i return it back to full stock before installing it?
it does have TWRP installed...
livinstyle said:
Hey guys,
My watch is currently running Gohma ROM. can i sideload the update and install right on top, or should i return it back to full stock before installing it?
it does have TWRP installed...
Click to expand...
Click to collapse
you might be able to but doubt it just flash the system image and boot from here
Is it compatible with invisiblek's kernel 6.1?
Edit: this rom is the same as before, MEC23G, theoretically, it should be compatible...
Edit1: It is compatible.
Jhon998 said:
Is it compatible with invisiblek's kernel 6.1?
Edit: this rom is the same as before, MEC23G, theoretically, it should be compatible...
Edit1: It is compatible.
Click to expand...
Click to collapse
Um dude what are you on about there haven't been any updates since. Invisibleks kernel was made for that build anyway you can also try the non stock 6 version on his builds it has smartmax eps instead of on demand
Xmaster24 said:
Um dude what are you on about there haven't been any updates since. Invisibleks kernel was made for that build anyway you can also try the non stock 6 version on his builds it has smartmax eps instead of on demand
Click to expand...
Click to collapse
Lol I was lost I thought that the update was released yesterday, because the xda page of g watch listed this post as 22nd april as for the last activity not the actual post date...
hi guy's.I have a problem with this version.
when I put my phone on silent mode,my watch goes to"don't disturb mode" and when I turn off the "don't disturb mode" in watch,my phone go back to ring mode.I don't like this.
I want put my phone on silent mode and watch doesn't go to don't disturb mode.do you have this problem? Any idea for this?
is there any way to update my lg g watch without using "system update" and without using "stock recovery" ? i have problems with both of them, looking for a third method...
Help
I Download ROM + I Install TWRP On My Watch But I Don't Know to How install with twrp PLEASE Help Me
help
helppp me pls
MehranAB said:
I Download ROM + I Install TWRP On My Watch But I Don't Know to How install with twrp PLEASE Help Me
Click to expand...
Click to collapse
Do you know how to use TWRP? Copy update zip to watch using adb, reboot to recovery then flash zip. As it's a smartwatch you have to touch and swipe screen in a certain way to activate recovery, please search the forum for more info.
lfom said:
Do you know how to use TWRP? Copy update zip to watch using adb, reboot to recovery then flash zip. As it's a smartwatch you have to touch and swipe screen in a certain way to activate recovery, please search the forum for more info.
Click to expand...
Click to collapse
Thank You! But What is the exact command to copy the update file.zip to LG G watch via ADB?
Regards

[SOLVED] Update .570 to .575 to .291 w/o losing root

Hi,
I currently have .570 fw installed with root, dualrecovery, xposed,... and wonder how to update to .575 w/o losing them. Can I just create flashable zip and that's it, or should I use the original guide that I used to update from LP to MM ([Stock][Z2(D6503) 6.0.1 Marshmallow][.570][Prerooted+ TWRP + Xposed][LB])?
//UPDATE: If you want to upgrade too, then grab files from this post and follow "nurps" guide here.
//UPDATE 2 (To avoid misunderstanding):
1. Make sure you download both files from here
2. In PRF Creator, insert your FTF as FTF File, dummy_flashable.zip as SuperSU and RecRootV4_combined.zip as Recovery.
3. Flash in recovery, if you want xposed, flash it separately afterwards.
4. Wipe cache
5. Reboot and that should be it.
//UPDATE 3
Also works for .291!
Well and without losing recovery would be important too. I'm ready with PRF Creator, but where do I get that TWRP Recovery zip from that works with MM?
nurps said:
Well and without losing recovery would be important too. I'm ready with PRF Creator, but where do I get that TWRP Recovery zip from that works with MM?
Click to expand...
Click to collapse
I'm not sure that we are having the same issue... I am already on MM, with recovery, etc. And want to update to newer version of MM.
btw if you just want dual recovery for MM you can visit the guide I mentioned earlier. You won't get .zip, since it's flashed by adb, but it works just the same.
Yes and when you reflash you have to reflash a rooted image and also recovery, or its gone.
nurps said:
Yes and when you reflash you have to reflash a rooted image and also recovery, or its gone.
Click to expand...
Click to collapse
I see.. Now I know what you mean... The thing is... I would assume that you would just flash it the same way you did from LP to MM.. flash ROM (w/o recovery), then flash SuperSU, boot Android and use the adb recovery flasher... But i don't really want to spend hours getting things to normal if that doesn't work. So I'm hoping someone braver already done this and will shed some light on how it really is...
Actually I dont remember how it went, but now that you mention it, than a prerooted firmware should be enough, maybe I'll try tomorrow. Of course a flashable backup would make it easier if anything happens.
nurps said:
Actually I dont remember how it went, but now that you mention it, than a prerooted firmware should be enough, maybe I'll try tomorrow.
Click to expand...
Click to collapse
Yeah... The problem was, after flashing MM and SuperSU, you had to pray that when Android boots up, you will have root permissions. If not, then it was game over, as you no longer had dual recovery...
Anyway... If you'll try, let me know how it went. I would really appreciate it!
Prerooted PRF creator file didn't work, root is lost.
nurps said:
Prerooted PRF creator file didn't work, root is lost.
Click to expand...
Click to collapse
That's what I was afraid of... Have you tried flashing SuperSU after flashing ROM? I know that you can insert it in the ROM, but just to be sure I find it "safer" to flash separately.
Because I got an error on supersu I actually did reflash it, but the same error message appeared. Should have stopped there and reflashed my backup....I didnt...
nurps said:
Because I got an error on supersu I actually did reflash it, but the same error message appeared.
Click to expand...
Click to collapse
And do you remember what error it was by any chance? We could probably find out why you lost root permissions that way...
No, sorry.
nurps said:
No, sorry.
Click to expand...
Click to collapse
That's a shame... Nevermind, what version of SuperSU were you flashing?
can u fetch me the ftf link ?
medalogii said:
can u fetch me the ftf link ?
Click to expand...
Click to collapse
Not sure what link you mean... Can you be more specific?
nurps said:
Because I got an error on supersu I actually did reflash it, but the same error message appeared. Should have stopped there and reflashed my backup....I didnt...
Click to expand...
Click to collapse
It's annoying, but at least you won't lose anything, as long as you have that backup... Now, you will have to downgrade to LP, root, flash back to MM, get recovery, flash your backup and done (if you want root back, that is of course, which I would strongly recommend for MM, as there are some things that would really bother me, if I didn't have root).
It's not the best solution, as it takes quite the time, but at least you have backup... could have been worse, take it that way...
Sorry my bad, I Was looking for the ftf now I'm downloading it with xperifirm,, now I'm looking for the recovery and supersu files to try,,
Sent from my D6503 using XDA-Developers mobile app
Thats a bit overcomplicated. I wasted some hours to find a rootable FTF though, 3rd I tried (D6503_17.1.A.2.69) worked, then it's just nuts dual recovery (with its own root exploit included) and restore.
For the other stuff I should have kept up, apparently for MM you include dummy_flashable for root not supersu and RecRootV4_combined is actually available as flashable recovery.
https://mega.nz/#!dtYQSYKa!V3cV1KUB2XPMn71wJHPPAwLrrVvB_hG7JPoun9WQ7AM
https://mega.nz/#!8woHjZyb!ksx9rXDSOnS_zUncNiYw0JbfUIt14YU61Fwc8Wrcjz8
nurps said:
Thats a bit overcomplicated. I wasted some hours to find a rootable FTF though, 3rd I tried (D6503_17.1.A.2.69) worked, then it's just nuts dual recovery (with its own root exploit included) and restore.
For the other stuff I should have kept up, apparently for MM you include dummy_flashable for root not supersu and RecRootV4_combined is actually available as flashable recovery.
https://mega.nz/#!dtYQSYKa!V3cV1KUB2XPMn71wJHPPAwLrrVvB_hG7JPoun9WQ7AM
https://mega.nz/#!8woHjZyb!ksx9rXDSOnS_zUncNiYw0JbfUIt14YU61Fwc8Wrcjz8
Click to expand...
Click to collapse
So, now you have .575 with root/recovery? And if, then you just create flashable.zip from your FTF and include dummy_flashable, flash in recovery and then flash RecRootV4_combined?
Nope not done yet. Trying now.

Note 4X Not updating to latest firmware

Hey,
I've tried multiple times to update to V8.2.5.0 via OTA. Download goes fine and installation seem to be fine also, but after rebooting it says "update failed, please download full ROM".
Same thing happened in the previous OTA update but when I pressed "update again" on the pop-up fail notification it switched to a larger ROM download. This time, however, it doesn't.
Can I force it to download the ROM via OTA? If not, is there an official ROM file somewhere that I can download and install manually?
Thanks.
possibly FULL ROM ?. Read "Flashig guide"
fx3000se said:
possibly FULL ROM ?. Read "Flashig guide"
Click to expand...
Click to collapse
Thank you very much. For some reason had trouble finding it.
Still having issues:
Downloaded full ROM from the site above, tried flashing it via the updater and still no go. Does everything right, goes through to reboot then fails and goes back to not letting me get the full ROM via OTA.
Any help?
Perhaps you have to do a factory reset.
Gesendet von meinem Redmi Note 4 mit Tapatalk
Are you rooted? If yes, updater app is just a waste of time.
Zephoro said:
Are you rooted? If yes, updater app is just a waste of time.
Click to expand...
Click to collapse
Nope, not yet... I know it is but I just don't really care for rooting atm since I don't have much time. Fiddled around plenty with my ZF2 but I'm alright with how the Note 4X is without root/custom rom and such.

[GUIDE] How I flashed TWRP, Xiaomi.eu rom and rooted with Magisk

Hey guys.
The below is my full experience of how I flashed TWRP, the Xiaomi.eu rom and rooted with Magisk. Whilst it essentially is a step-by-step, it also contains not only how I succeeded but also how I encountered issues and so...
*UPDATE!*
Here is a slightly condensed verison with thanks to @airwebber
Get the latest xiaomi.eu rom from here or here, just scroll down and find the "xiaomi.eu_multi_MI9..." version.
https://sourceforge.net/p/xiaomi-eu...ty/?page=0&limit=100#5cb9f96ee8ba7c44716e87ff
Get the latest magisk (magisk v19 works at the time of writing this post):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Some versions of twrp may not work on older builds other than the latest (9.4.25) and so use this one with:
https://mega.nz/#!CH5jgYTB!yNqOiVoo3cf0_15jIwZ-btO52cvpOG7iZrRCe19V2Nc
Once the waiting time elapses (usually 360 hours) use the MiFlash tool to unlock the bootloader. Warning: this wipes your phone entirely, so be sure to backup anything of importance.
Unlocking takes a few minutes and once 100% complete your Mi 9 will reboot. Your phone will say “unlocked” on the first splash screen while booting up.
Your Mi 9 will boot, and you will need to either perform/skip the initial setup stuff. Once ready, power off your device in order to flash TWRP.
Press both the volume down key and power key to boot into Fastboot Mode.
Once in Fastboot Mode, use the following command to install TWRP: “fastboot flash recovery XXXX” (XXXX = the pathway to your TWRP.img file). However, I find it best using Minimal ADB and copying the TWRP file and renaming it to “twrp.img” for ease) in the Minimal ADB folder location e.g. “C:\Program Files (x86)\Minimal ADB and Fastboot”.
Once flashed, disconnect the USB cable and boot to TWRP recovery by holding down both the volume up and the power buttons. This sometimes will bring you to the stock recovery and NOT TWRP! If it does, boot back to Fastboot and reflash TWRP.
Once you can boot to TWRP, push both the rom and magisk via CMD line:
adb push rom.zip /tmp/
adb push magisk.zip /tmp/
For ease, I suggest copying both files to the Minimal ADB folder location e.g. “C:\Program Files (x86)\Minimal ADB and Fastboot”. And renaming them to: “rom.zip” and “magisk.zip”.
This step is very important!! You must go to the Wipe menu and select: Format Data, then type “yes” to continue and then: do a Factory reset, which also wipes: Data, Caches and Format Data. If you skip this step you won’t be able to install a lot of important apps and will have to start over.
Now that you have pushed both the rom & magisk and wiped everything you needed to. Install the ROM immediately after install magisk.zip (in that order) both located in /tmp/.
The installation will take a couple of minutes (if your screen dims, don’t worry that’s just TWRP screen dimming, touch the screen to keep it awake!) once finished with no errors, then reboot and chose Do Not Install the TWRP app when prompted.
The phone will take a few seconds to reboot and show the first MI splash screen, but it should start booting. After a couple of minutes, you should see the initial boot screen! Perform the setup (connecting to Wi-Fi, adding my Google account etc.).
Once finished setting up, you may notice that magisk was not installed, if that happens, you can install the APK version and follow the prompts and reboot.
Once rebooted, confirm that magisk is now installed. If it is, I suggest installing SafetyNet and confirming your phone passes!
If it passes, you have successfully installed and rooted the Xiaomi.eu rom!
Also, when updating with each weekly I recommend the below as an alternative to using the built in Updater app. The reason being is I believe the updater app automatically reboots after it installs, which if you're rooted means you'll lose it. That then means you have to reboot back to twrp, reflash magisk, reboot, reinstall modules, reboot again etc.
Therefore to update a weekly:
Download the rom manually
Reboot to twrp
Wipe system and caches
Flash the rom and magisk
Reboot
Optional: I also disable my substratum theme too before updating and reapply afterwards. Whether it's needed or not I'm not too sure, so give it a try either way
Awesome, all files at the ready! BTW get the latest MIUI from HERE or HERE.
Make sure you download the xiaomi.eu_multi_MI9_xxx.zip.
The Dutchman said:
Awesome, all files at the ready! BTW get the latest MIUI from HERE or HERE.
Make sure you download the xiaomi.eu_multi_MI9_xxx.zip.
Click to expand...
Click to collapse
Thanks, first post updated!
cd993 said:
Thanks, first post updated!
Click to expand...
Click to collapse
You have used the Magisk Canary build I presume?
And great job for writing it down.... Now I remember the same culprits I had of flashing TWRP. [emoji23]
*justintime* said:
You have used the Magisk Canary build I presume?
And great job for writing it down.... Now I remember the same culprits I had of flashing TWRP. [emoji23]
Click to expand...
Click to collapse
That's right:
Magisk-v18.2-51110866(18116).zip
If I can find the link (of if someone can link me to it) I'll update the posy
cd993 said:
That's right:
Magisk-v18.2-51110866(18116).zip
If I can find the link (of if someone can link me to it) I'll update the posy
Click to expand...
Click to collapse
Here ya go.
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
*justintime* said:
Here ya go.
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Click to expand...
Click to collapse
Thanks, updated!
Rommco05 said:
Good stuff for early roots without not tested stuff like twrp and magisk but I would hide that middle part coz some people can get be confused. Or make a short version which working in order and another with your all step's but separately
edit: still 46h left
Click to expand...
Click to collapse
Yeah I agree it's kinda overkill, being a a full run down - when I get time I'll make a shorter condensed version
Thanks for the detailed write up. The EU roms are google approved correct? Does the side Ai button work with google assist? Do you need to install twrp to flash or can I just flash global/EU rom if I don't want to root yet?
I just got the bootloader unlocked (1h before than I tought ahahah). I had some issue that the unlocker was telling to me thaat I didn't use enought the phone and that so I had to try in few days I overtook the problem using an old version of the unlocker (2.3.803.10).
Reading your procedure it all logical and fine, thanks! Except one thing that I'm not sure... Is xiaomi.eu a 'full rom' (on all Xiaomi that I had I always jumped straight to something different than MIUI and so I never tried it ahahah )?
If so, I think it would be better to wipe the system too before installing the rom. That's because doing so it will do 100% 'clean' installation and not a an update on the normal global miui
perryano said:
Thanks for the detailed write up. The EU roms are google approved correct? Does the side Ai button work with google assist? Do you need to install twrp to flash or can I just flash global/EU rom if I don't want to root yet?
Click to expand...
Click to collapse
Hmm unsure about them being approved or not... The side button does work. As far as I understand, you'll need to install twrp in order to flash the new rom, but could always go back to stock recovery and of course no need to root if you don't want to
mr-mauro said:
I just got the bootloader unlocked (1h before than I tought ahahah). I had some issue that the unlocker was telling to me thaat I didn't use enought the phone and that so I had to try in few days I overtook the problem using an old version of the unlocker (2.3.803.10).
Reading your procedure it is more or less everything fine except one thing that I'm not sure. is xiaomi.eu a full rom? If so, I think it would be better to wipe the system too before installing the rom because instead it will try to to an update on the normal global miui rather than a 100% 'clean' installarion
Click to expand...
Click to collapse
That's a fair point - if you have some this successfully then perhaps I'll amend my post. Sometime soon I'll make a small set of instructions, rather than my essay
cd993 said:
That's a fair point - if you have some this successfully then perhaps I'll amend my post. Sometime soon I'll make a small set of instructions, rather than my essay
Click to expand...
Click to collapse
aahahha, yes, it looks like an essay. I'm trying it now... If it fail I'll scream ahahaha
mr-mauro said:
aahahha, yes, it looks like an essay. I'm trying it now... If it fail I'll scream ahahaha
Click to expand...
Click to collapse
Let us know
cd993 said:
Let us know
Click to expand...
Click to collapse
It just boot So, it is fine I just noticed TickTock as a default app installed by Xiaomi.eu
P.S. FYI I noticed that the devices is seen by Google as a Mi Mix 2S
mr-mauro said:
It just boot So, it is fine I just noticed TickTock as a default app installed by Xiaomi.eu
Click to expand...
Click to collapse
Great!
Ahh I did see 1 random app. But then I debloated a went away
cd993 said:
Great!
Ahh I did see 1 random app. But then I debloated a went away
Click to expand...
Click to collapse
Luckily in those two waiting-weeks I had time to test all the debloat that I wanted to come with a stable configuration today It's just a pity that we can't get rid completely of the Security app It is integrated too much in the system!
One quick question for who has installed Xiaomi EU with Magisk: does it pass SafetyNet to you? (to me no )
cd993 said:
Hmm unsure about them being approved or not... The side button does work. As far as I understand, you'll need to install twrp in order to flash the new rom, but could always go back to stock recovery and of course no need to root if you don't want to
Click to expand...
Click to collapse
So once bootloader is unlocked I can install TWRP and flash the EU rom without rooting?
mr-mauro said:
It just boot So, it is fine I just noticed TickTock as a default app installed by Xiaomi.eu
P.S. FYI I noticed that the devices is seen by Google as a Mi Mix 2S
Click to expand...
Click to collapse
Yeah, to change the device name back to mi 9, just install "Find my device" app from Google play store, sign in with google account, there's an option in the setting to rename the device (this device).
That's the only place you can change the name back, I did try all, but only this one worked.

Categories

Resources