Is Xiaomi blocking my Phone from installing Custom Roms? - Xiaomi Mi Mix 2 Questions & Answers

Hi,
I'm trying to install this Custom ROM: https://forum.xda-developers.com/mi-mix-2/development/rom-havoc-os-t3883065
I've previously used the Custom ROM if xiaomi.eu.
Now that I'm trying to install an AOSP ROM it won't let me boot the system.
I've unbind my Mi Account and device from https://i.mi.com/ and unlocked bootloader in developer settings before wipe eveything and flash the havoc OS rom.
Is there something I'm missing? I've done that multiple times before with non-Xiaomi phones but never had such problems.
I tried to reinstall a xiaomi.eu ROM and it worked btw.

Is your bootloader really unlocked?

Raymino said:
Hi,
I'm trying to install this Custom ROM: https://forum.xda-developers.com/mi-mix-2/development/rom-havoc-os-t3883065
I've previously used the Custom ROM if xiaomi.eu.
Now that I'm trying to install an AOSP ROM it won't let me boot the system.
I've unbind my Mi Account and device from https://i.mi.com/ and unlocked bootloader in developer settings before wipe eveything and flash the havoc OS rom.
Is there something I'm missing? I've done that multiple times before with non-Xiaomi phones but never had such problems.
I tried to reinstall a xiaomi.eu ROM and it worked btw.
Click to expand...
Click to collapse
Strange. For me xiaomi.eu roms never worked for me. Have u tried flashing global stable 10.0.2.0 zip via TWRP first? Not the xiaomi.eu rom.
All you have to do is wipe system, caches, data, dalvik. Then flash havoc and gapps. Let it boot. Then reboot to recovery (before setting ur lockscreen password) and flash magisk if u want root

Format Data is required. Did you do that?

So what happened when u try to open ur mix2?
The mi screen forever? Or just black.

How come you have to keep doing Format Data after each update of any rom?

Related

Decryption my Phone in a endless loop, need help !

ive installed firstly the latest S.Team S4 Rom also HTC 10 Base, but it ended with a assistant to decrypt my phone so ive done the steps.
have do a factory reset, and nothing has do, it asks again for decrypt my phone, so i tested with other Roms
the same problem was with Leedroid, Skydragon ROM. before i never have encrypted my phone
and i have latest firmware 3.12.401 international
latest hboot bootloader 3.19.xxx sense international bootloader
latest twrp 3.0.2-0 recovery
Let say it's a typo error, your firmware is 6.12.401 and not 3.12.401
In TWRP, select wipe - format data - yes - reboot recovery
then reinstall ROM zip
not worked for me, reinstalled many rom zips like wolla and S.Team Rom and rebooted many times
and it ask for decrypt
I'm having the same issue. is there anyway to get around this on a verizon phone.
Smilex93 said:
not worked for me, reinstalled many rom zips like wolla and S.Team Rom and rebooted many times
and it ask for decrypt
Click to expand...
Click to collapse
ive got fixed but with only one i dont know if it works with other roms or othe rmodels
you must wipe data, system, cache and then reboot the recovery, install rom.zip (Wolla Sense worked, S.Team Rom not) and choose 'perform a ful wipe'
youre done !

Problems with flashing OOS

I've One Plus 5T, bought in China. It came to me with hydrogenOS. Then I flashed TWRP, Resurrection Remix, everything was fine.
But I want to use secondary camera and to that, as I understood, I need to have OOS or some ROM based on OOS.
I've tried everything, but it doesn't want to work. In most cases I ended in soft bricked phone, but today I couldn't even boot to fastboot (I tried flashing stock recovery first, because flashing OOS ended with Error 7), I don't know how, but it finally booted to fastboot and I flashed RR via command line.
What should I do to have OOS?
kubixmaster3009 said:
I've One Plus 5T, bought in China. It came to me with hydrogenOS. Then I flashed TWRP, Resurrection Remix, everything was fine.
But I want to use secondary camera and to that, as I understood, I need to have OOS or some ROM based on OOS.
I've tried everything, but it doesn't want to work. In most cases I ended in soft bricked phone, but today I couldn't even boot to fastboot (I tried flashing stock recovery first, because flashing OOS ended with Error 7), I don't know how, but it finally booted to fastboot and I flashed RR via command line.
What should I do to have OOS?
Click to expand...
Click to collapse
I'm pretty sure you would need to format data on twrp due to encryption differences between oos and custom ROMs.
Sent from my ONEPLUS A5010 using Tapatalk
You've gotta wipe /system & /data before you install a different rom. I usually do a full wipe when switching.
Couchment said:
You've gotta wipe /system & /data before you install a different rom. I usually do a full wipe when switching.
Click to expand...
Click to collapse
I've always done wipe of everything except internal storage.
jmtjr278 said:
I'm pretty sure you would need to format data on twrp due to encryption differences between oos and custom ROMs.
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I wiped data, but what are these encryption differences? Maybe that's the reason of my problems.
kubixmaster3009 said:
I've always done wipe of everything except internal storage.
Click to expand...
Click to collapse
Are you flashing just the system in twrp or have you tried the full unroot? I.E. flashing the stock recovery and locking the bootloader?
Also what TWRP are you running? I've had issues with it not booting, not decrypting etc. blu_spark twrp 3.2.1-x was the only version I could get to work properly last I tried.
Couchment said:
Are you flashing just the system in twrp or have you tried the full unroot? I.E. flashing the stock recovery and locking the bootloader?
Also what TWRP are you running? I've had issues with it not booting, not decrypting etc. blu_spark twrp 3.2.1-x was the only version I could get to work properly last I tried.
Click to expand...
Click to collapse
I tried flashing the stock recovery, but it wouldn't boot to recovery then, also I tried locking the bootloader via fastboot after flashing recovery, but still it wouldn't boot.
I'm running blu_spark twrp 3.2.2-x with support for treble.
Did you try flashing stock recovery and sideloading OOS?

Update Xiaomi.eu 8.8.9 to Global 10.2.1 best way?

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

Pie Firmware Rom?

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

Bootloop on every Magisk installation

Hi everyone,
I recently made a fresh install of the latest OOS ROM on my Onplus 5T (OOS 9.0.8). After reinstalling all the apps and data I tried to root the phone. My bootloader was already unlocked, so I just went on to flash TWRP (first tried the official TWRP 3.3.1 dumpling, and then the 3.3.1 blu_spark version). Then I tried to flash Magisk via TWRP (tried versions 19.2, 19.3, 19.4), and every time I try to reboot I get stuck on a black screen with the cyan led on, and I have to uninstall Magisk in order to reboot on the phone. Also the phone is encrypted, and I have a the Microsoft Intune Portal app installed to use some work apps, but I don't know if that can be the source of the problem.
If you have any idea on how to successfully flash Magisk, that would be amazing.
Thanks in advance :good:
I use the same version of ROM and magisk I use is canary build . Working fine. (even its not canary build I also can boot successfully)
you might need to check if some apps you install might cause this.
my recommendation is clear /data and starts fresh then root it before installing any apps. to see if it working fine or not.
also after you flash magisk do you try to wipe cache, dalvik-cache?
and how long are you waiting for its to boot? normally it would take more time than normal boot (without magisk)
Just connect to to ADB and delete vendor.. recovery.. rom.. radio.. antennaa.. ect everything. Get yourself a stock full rom and flash that through ADB. Then flash custom recovery, custom rom, gapps, custom kernel, magisk. thats it. find stock rom on manufacturers data server. I did this to a different phone I had but this is the way to 100% fix everything... by purging the phone to nothing. You can however do a twrp backup before doing so.
Thanks for the input, I will try first to reflash the ROM and root before installing any apps, and see if it works in order to avoid the long process of restoring all my data. I do wipe cache/dalvik cache before and after every flash. If that doesn't work I will try another time a clean flash and tell you if it worked.
I just reflashed the ROM and right after I flashed Magisk 19.3, then rebooted and it worked. Not sure what the issue was but the problem is now resolved. Thanks guys for the advice.

Categories

Resources