I am on official 12.5.1 stock rom, TWRP installed, rooted.
I wanna know how can I flash the weekly Xiaomi EU without issues of bootloops or anything, so that later I can just download weekly updates and flash them using updater (Through TWRP)
Could anybody tell me about how to do it from scratch step by step, please?
as far as i'm aware, xiaomiEU weekly roms are twrp flashable. no need to reflash twrp after either, twrp is flashed along with rom. just flash directly over 12.5.1 (although i would do a factory reset first)
No factory reset need it. Just flash latest weekly and do a Format data (yes) before rebooting to system.
Alin45 said:
No factory reset need it. Just flash latest weekly and do a Format data (yes) before rebooting to system.
Click to expand...
Click to collapse
Thanks. I'll try that.
Alin45 said:
No factory reset need it. Just flash latest weekly and do a Format data (yes) before rebooting to system.
Click to expand...
Click to collapse
I was successfully able to flash it. Everything went smooth. But when I tried to flash the latest weekly. The updater ( after saying that my phone is encrypted which wasn't, I cancelled then did it again) took me to TWRP where I manually selected the lastest weekly. when the flashing was done, I tried to Reboot to system. It took me back to TWRP. Am I supposed to "Format Data" every time ?!!!
Is losing data necessary for every update !
laid1995 said:
I was successfully able to flash it. Everything went smooth. But when I tried to flash the latest weekly. The updater ( after saying that my phone is encrypted which wasn't, I cancelled then didn't it again) took me to TWRP where I manually selected the lastest weekly. when the flashing was done, I tried to Reboot to system. It took me back to TWRP. Am I supposed to "Format Data" every time ?!!!
Is losing data necessary for every update !
Click to expand...
Click to collapse
When switch from stable to weekly, or weekly to stable, you need to format data.
Stable to stable, or weekly to weekly does not necessary need to format data.
Your case seems to be 12.5.1.0 stable stock to Xiaomi.eu weekly Rom, so need to format data.
Alin45 did told you to format data.
pl1992aw said:
When switch from stable to weekly, or weekly to stable, you need to format data.
Stable to stable, or weekly to weekly does not necessary need to format data.
Your case seems to be 12.5.1.0 stable stock to Xiaomi.eu weekly Rom, so need to format data.
Alin45 did told you to format data.
Click to expand...
Click to collapse
I think I can't really tell which is which. Well. initially I flashed "xiaomi.eu_multi_HMK40_POCOF3_V12.5.3.0.RKHCNXM_v12-11.zip" over the official 12.5.1. Which required Data format. Fine with that. But now when I tried to dirty flash "xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip" which was released yesterday. I had to Format Data to boot to system. I don't get it!
Is the weekly one with the date being part of the zip name ?
So this one is the stable one, not the weekly. Right !
laid1995 said:
I think I can't really tell which is which. Well. initially I flashed "xiaomi.eu_multi_HMK40_POCOF3_V12.5.3.0.RKHCNXM_v12-11.zip" over the official 12.5.1. Which required Data format. Fine with that. But now when I tried to dirty flash "xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip" which was released yesterday. I had to Format Data to boot to system. I don't get it!
Is the weekly one with the date being part of the zip name ?
Click to expand...
Click to collapse
Then complain to Xiaomi.eu
https://xiaomi.eu/community/threads/56191/
They release the ROM, so they have to deal with your issue.
Those information written earlier were from here: https://forum.xda-developers.com/t/4267741/post-85199911
https://forum.xda-developers.com/t/4267741/post-85178383
Only passing the info to you, so ask him Alin45, or ask Xiaomi.eu.
laid1995 said:
So this one is the stable one, not the weekly. Right !
Click to expand...
Click to collapse
Yes
laid1995 said:
I think I can't really tell which is which. Well. initially I flashed "xiaomi.eu_multi_HMK40_POCOF3_V12.5.3.0.RKHCNXM_v12-11.zip" over the official 12.5.1. Which required Data format. Fine with that. But now when I tried to dirty flash "xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip" which was released yesterday. I had to Format Data to boot to system. I don't get it!
Is the weekly one with the date being part of the zip name ?
Click to expand...
Click to collapse
You did something wrong. I was in 12.5.3 and I just flashed 12.5.4 and I didn't had to format data.
If you keep flashing firmware something will go wrong... unless you're a developer or have good reasons to be constantly flashing I wouldn't take it so lightly. It's a sure fire way to instantly destroy a device and it opens you to the worst kinds of malware attacks.
I was successfully able to flash it. The whole thing went smooth. But after I tried to flash the latest weekly. The updater ( after saying that my phone is encrypted which wasn't, I cancelled then did it once more) took me to TWRP wherein I manually selected the lastest weekly. Whilst the flashing changed into done, I attempted to Reboot to machine. It took me back to TWRP. Am I imagined to "layout facts" each time ?!!!
Is losing records important for every update !192.168.100.1 192.168.1.1
Updating weekly updates without loosing your Data is now very simple with TWRP:
1. Download the new weekly update (xxx.zip)
2. Reboot to TWRP recovery and enter the same graphic scheme used to unlock your lockscreen.
3. In TWRP Install (flash) the downloaded weekly update with TWRP
4. If you want to (keep) root, flash last Magisk.zip
5. Wipe Dalvik (and nothing else)
6. Reboot to System
Done
I hope it helps.
michelD said:
Updating weekly updates without loosing your Data is now very simple with TWRP:
1. Download the new weekly update (xxx.zip)
2. Reboot to TWRP recovery and enter the same graphic scheme used to unlock your lockscreen.
3. In TWRP Install (flash) the downloaded weekly update with TWRP
4. If you want to (keep) root, flash last Magisk.zip
5. Wipe Dalvik (and nothing else)
6. Reboot to System
Done
I hope it helps.
Click to expand...
Click to collapse
Thanks. Now, I believe I'll have to do a clean flash since I'm on stable. I don't wanna lose data though. I'll try to back it up and recover it when finished flashing weekly.
Indeed, if you go from weekly developer to stable and vice-versa or to any custom ROM, you will have the wipe the Data.
The simplest way to restore your applications and associated data is to backup (and restore) all with Titanium (root) backup app.
I flashed eu weekly rom in my mi 11x but noting changes .
Right now i am on xiomi.eu 12.5.4 STABLE.
Please guide me how to flash eu weekly rom in my mi 11x.
Related
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
savvymatthew said:
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
Click to expand...
Click to collapse
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
LS.xD said:
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
Click to expand...
Click to collapse
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
savvymatthew said:
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
Click to expand...
Click to collapse
OnePlus.net offers the rom files as download:
OOS 3.2.6 (capable for OTA 3.2.8)
Open Beta 7
I'm using the Open Beta at the moment and it runs without any issues
OOS roms can be flashed with custom TWRP
For a clean installation just wipe partitions (System; Data; Cache; Int. Storage) with TWRP before flashing the new rom
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Hw4ng3r said:
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Click to expand...
Click to collapse
Thank you for pointing on that I backup all my stuff on my computer once a week but others may not.
By never wiping your internal or manually deleting folders you will collect garbage over time when you change android installations.
I have a back up from when i first set it up, so its very old. After i Flash and set everything up again think im gonna start making weekly back ups, with all the roms and stuff for this phone probably be smart.
Thanks guys
I'm running Android Oreo on the Beta line. I've felt that Camera quality used to be better in Nougat, and occassionally phone heats up with Oreo. So I'd like to switch back to Nougat. But I've seen a couple of threads mentioning about a potential data loss(whole internal storage getting wiped) and needing to install a rollback build before installing a stable Nougat ROM. Could someone shed some light into this? Is flashing the rollback build really necessary if I can flash the stable OOS 4.5.1 via TWRP? And, would I lose data in internal storage during the procedure? Thanks in advance.
wHiTeWoLf007 said:
I'm running Android Oreo on the Beta line. I've felt that Camera quality used to be better in Nougat, and occassionally phone heats up with Oreo. So I'd like to switch back to Nougat. But I've seen a couple of threads mentioning about a potential data loss(whole internal storage getting wiped) and needing to install a rollback build before installing a stable Nougat ROM. Could someone shed some light into this? Is flashing the rollback build really necessary if I can flash the stable OOS 4.5.1 via TWRP? And, would I lose data in internal storage during the procedure? Thanks in advance.
Click to expand...
Click to collapse
The info you asked for and the steps with links everything is available here: https://forums.oneplus.com/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
tnsmani said:
The info you asked for and the steps with links everything is available here: https://forums.oneplus.com/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
Click to expand...
Click to collapse
I checked the thread and noticed that it's all about installing via the stock recovery. My phone's bootloader is unlocked and I have TWRP installed. So my question is, do I really need to install the rollback build? Can I not directly flash the 4.5.1 zip file via TWRP and be done with it? Or is there a purpose to installing the rollback version? I mean I read in that thread that after installing the rollback version via stock recovery, a factory reset should be done(which would erase the whole internal storage I assume?) and then the 4.5.1 zip file should be flashed. If I could use the advanced wipe option in TWRP to wipe the cache, data and system partitions and install the 4.5.1 zip file, do I need to go through the tedious procedure of installing via stock recovery, which would potentially erase my whole internal storage?
wHiTeWoLf007 said:
I checked the thread and noticed that it's all about installing via the stock recovery. My phone's bootloader is unlocked and I have TWRP installed. So my question is, do I really need to install the rollback build? Can I not directly flash the 4.5.1 zip file via TWRP and be done with it? Or is there a purpose to installing the rollback version? I mean I read in that thread that after installing the rollback version via stock recovery, a factory reset should be done(which would erase the whole internal storage I assume?) and then the 4.5.1 zip file should be flashed. If I could use the advanced wipe option in TWRP to wipe the cache, data and system partitions and install the 4.5.1 zip file, do I need to go through the tedious procedure of installing via stock recovery, which would potentially erase my whole internal storage?
Click to expand...
Click to collapse
Why would OnePlus provide the rollback build if there are other reliable methods of downgrading?
I think rollback version is for stock recovery users and data loss + . And if you decrypted your data already downgrading is just flash zip in twrp and no data loss but you keep decrypt.
drmuruga said:
I think rollback version is for stock recovery users and data loss + . And if you decrypted your data already downgrading is just flash zip in twrp and no data loss but you keep decrypt.
Click to expand...
Click to collapse
You mean the dm-verity thing? So it will be fine if I flash the Nougat zip file and install SuperSU binaries via TWRP to fix the dm-verity issue? That's what I've been waiting for as an answer. Thanks.
I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?
msafiri said:
I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?
Click to expand...
Click to collapse
Since you are on OOS (though beta), flashing 5.0.8 should not affect your encryption status. Your plan is ok.
Encryption is related to security. Decrypted means lesser security though I have no idea by how much. It is your call.
Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.
abhibnl said:
Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.
Click to expand...
Click to collapse
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?
msafiri said:
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?
Click to expand...
Click to collapse
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
Yep, i understand the difference in the operations on the data partition now. Thank you once again for the clarification.
abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
One small addl. info. After flashing TWRP, there is no need to reboot to recovery. Simply flash Magisk right after TWRP and then boot to system. Flashing Magisk at that stage prevents TWRP being overwritten by stock recovery.
EDIT: or you can skip flashing TWRP and boot back to recovery after flashing the ROM and then flash Magisk alone before booting into system. Either way, you save one step.
abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
I always download the full OTA zip and flash it manually wiping only system and cache/dalvik partitions, and I never had any issues whatsoever. Sure you will need to reflash magisk since your kernel and firmware will be flashed again.
msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.
tnsmani said:
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.
Click to expand...
Click to collapse
Thanks. That clears my doubts.
Girlfriend had one of the earlier Mi Max 3 with the 'fake' global ROM. Using some of Omer919 info I updated it to the Xiaomi.eu 8.8.9 and left it at that as most things worked. Due to one annoying bug she wants to update to Global 10.2.1.
Is this just a case of flashing a fastboot ROM and making sure 'lock bootloader' is NOT ticked or is it easier (safer) to do it via Recovery?
Wam7 said:
Girlfriend had one of the earlier Mi Max 3 with the 'fake' global ROM. Using some of Omer919 info I updated it to the Xiaomi.eu 8.8.9 and left it at that as most things worked. Due to one annoying bug she wants to update to Global 10.2.1.
Is this just a case of flashing a fastboot ROM and making sure 'lock bootloader' is NOT ticked or is it easier (safer) to do it via Recovery?
Click to expand...
Click to collapse
Hi, On MiMax 3 unlocked bootloader, region is not a problem. But why you want to flash a global rom on a chinese one (fake global) ? It's more interesting to flash eu. 10.2.1
As you already are on xiaomi.eu, 8.8.9 (oreo) and 10.2.1 eu (oreo) you can only follow instructions on the Xiaomi.eu thread, wipe dalvik, cache and flash 10.2.1 eu. If it don't boot only wipe data partition and it'll boot fine.
If you want a cleaner install, you can factory reset. Or like me, I use a method which is not very recommended. (Wipe all axcept external storage and flash eu 10.2.1).
I recommend you to update your recovery to latest nigel8 one, whatever the method you want to use. Specially if you still have an encrypted partition. (On my side no more encrypted - did a format data to avoid problems)
Regards
Skyllery said:
Hi, On MiMax 3 unlocked bootloader, region is not a problem. But why you want to flash a global rom on a chinese one (fake global) ? It's more interesting to flash eu. 10.2.1
As you already are on xiaomi.eu, 8.8.9 (oreo) and 10.2.1 eu (oreo) you can only follow instructions on the Xiaomi.eu thread, wipe dalvik, cache and flash 10.2.1 eu. If it don't boot only wipe data partition and it'll boot fine.
If you want a cleaner install, you can factory reset. Or like me, I use a method which is not very recommended. (Wipe all axcept external storage and flash eu 10.2.1).
I recommend you to update your recovery to latest nigel8 one, whatever the method you want to use. Specially if you still have an encrypted partition. (On my side no more encrypted - did a format data to avoid problems)
Regards
Click to expand...
Click to collapse
Many thanks for the info. I think I will definitely update the recovery as I remember having issues booting the 8.8.9 and had to wipe data partition to fix it. Will try the Xiaomi.eu10.2.1 , let's hope the poor audio in video calls is fixed.
Skyllery said:
.... Or like me, I use a method which is not very recommended. (Wipe all axcept external storage and flash eu 10.2.1).
Click to expand...
Click to collapse
I did not feel as brave as you though I was tempted to wipe system as well (I'm used to doing this when updating my old Note 4) but I played it safe and just did the normal cache, data etc.
All done and working well and the girlfriend is really impressed with how much faster it is - just in time for Valentine's day.
Better flash fastboot rom to start clean if you previously had a fake rom.
Because you don't wipe everything when you flash Xiaomi.eu rom.
Wam7 said:
I did not feel as brave as you though I was tempted to wipe system as well (I'm used to doing this when updating my old Note 4) but I played it safe and just did the normal cache, data etc.
All done and working well and the girlfriend is really impressed with how much faster it is - just in time for Valentine's day.
Click to expand...
Click to collapse
What did you do ? Steps
Happy to read this btw
Sent from my MI MAX 3 using XDA Labs
mierlo420 said:
Better flash fastboot rom to start clean if you previously had a fake rom.
Because you don't wipe everything when you flash Xiaomi.eu rom.
Click to expand...
Click to collapse
It should be fine as I did the whole realign partition thing etc back when I originally flashed Xiaomi.eu. 8.8.9
Skyllery said:
What did you do ? Steps
Happy to read this btw
Click to expand...
Click to collapse
First I downloaded Nigel8's recovery, though took a little digging around to locate it.
I then booted into recovery and flashed the new recovery.
Then I just mounted all partitions and wiped cache, etc all except system. Then just flashed the 10.2.1 Xiaomi.eu ROM and after wiped cache and dalvik.
I'm liking the look of the Xiaomi.eu 10.2.1, at some later state I might put it on my own official Global MiMax3 when I can be bothered to unlock the bootloader.
Did updating to Global or Xiaomi.eu 10.2.1 also update your baseband on Chinese phone? I'm currently on 10.2.1.0(OEDMIFK) Model name: M1804E4A Baseband version: AT31c7-00014-1218_1225_71f61ca for an OTA update from Global 10.0.XX
The reception in North America is not good. I keep getting stuck on E edge 2G. Phone came with unlocked bootloader. I'd like to try the Xiaomi.eu ROM but am having issues updating recovery to TWRP
I just unlocked my Mix 2, but doing some looking before rooting. Is there any Roms that will work on Miui Beta Global 9.5.16? If all custom Roms are using 8.0 firmware, i guess i will wait to root this phone. If there is a Rom i can flash being on 9.0 firmware please let me know where to find it. Thank you.
Use the xiaomi.eu Roms, they are original Chinese MIUI Roms, but without any Bloatware Apps
https://xiaomi.eu/community/forums/miui-rom-releases.103/
If you browse through the forum you will find that most pie rom's have moved or are moving to pie firmware.
jkotte said:
Use the xiaomi.eu Roms, they are original Chinese MIUI Roms, but without any Bloatware Apps
https://xiaomi.eu/community/forums/miui-rom-releases.103/
Click to expand...
Click to collapse
How do I flash this rom? I never had luck with Xiaomi.eu roms but this time Imma do it again if I find someone who has working instructions.
Which recovery do I need? I'm currently on TWRP 3.2.3.0 (the official one from TWRP website)
What I do is
Wipe Data, Cache, System, Internal Storage everything. Even format data. Then copy the rom over into internal storage and flash it. Wipe cache again. Reboot system.
It always is stuck in loading.
Edit: I'm on Havoc OS-Pie currently.
dark_prince said:
How do I flash this rom? I never had luck with Xiaomi.eu roms but this time Imma do it again if I find someone who has working instructions.
Which recovery do I need? I'm currently on TWRP 3.2.3.0 (the official one from TWRP website)
What I do is
Wipe Data, Cache, System, Internal Storage everything. Even format data. Then copy the rom over into internal storage and flash it. Wipe cache again. Reboot system.
It always is stuck in loading.
Edit: I'm on Havoc OS-Pie currently.
Click to expand...
Click to collapse
Im on 9.5.23 eu, just wipe data caches system. If you are encrypted format data(im decrypted so i dont format sata) if you format sata reboot recovery and just install the zip. First boot may take longer than usual.
Sent from my Xiaomi MIX 2 using XDA Labs
dark_prince said:
How do I flash this rom? I never had luck with Xiaomi.eu roms but this time Imma do it again if I find someone who has working instructions.
Which recovery do I need? I'm currently on TWRP 3.2.3.0 (the official one from TWRP website)
What I do is
Wipe Data, Cache, System, Internal Storage everything. Even format data. Then copy the rom over into internal storage and flash it. Wipe cache again. Reboot system.
It always is stuck in loading.
Edit: I'm on Havoc OS-Pie currently.
Click to expand...
Click to collapse
Sorry for late response, i had this Problem too, bootlooping...
NEVER wipe System or Persist! Just FORMAT Data and install the Rom, i did it via ADB Sideload, worked perfectly