[ROM][Developer] MIUI 11 xiaomi.eu - Xiaomi Poco X2 Guides, News, & Discussion

20.3.5
https://sourceforge.net/projects/xi...omi.eu_multi_HMK30_20.3.5_v11-10.zip/download
20.2.20 v2
https://sourceforge.net/projects/xi...mi.eu_multi_HMK30_20.2.20_v11-10.zip/download
https://androidfilehost.com/?fid=4349826312261729739
New links will be posted here.

It worked!!! Thanks.

Works without major bugs. Plus all the goodies and extra features are here. Thanks for the superb ROM. Love to the .eu team.

Camerado said:
20.1.21
https://sourceforge.net/projects/xi...mi.eu_multi_HMK30_20.1.21_v11-10.zip/download
https://androidfilehost.com/?fid=4349826312261718263
New links will be posted here.
Installation guide: https://xiaomi.eu/community/threads/guide-how-to-install-xiaomi-eu-rom-for-hmk30-hmk30-5g.54536/
Click to expand...
Click to collapse
when i tried to give windows command and press y, it only write boot and finished
what to do?

20.2.20 added in OP: https://xiaomi.eu/community/index.php?posts/529659

This time we have to install it by twrp. I am on developer eu rom only. So after installing by twrp is it mendetory to clean cache and dalvik cache??

20.2.20 v2 added in OP: https://miuipolska.pl/d/xiaomi.eu/updater/changelog/20.2.20.html

20.3.5 added in OP: https://miuipolska.pl/d/xiaomi.eu/updater/changelog/20.3.5.html

How to enable the "New gesture" from 20.2.20 changelog?
Edit : I updated system launcher via adb and it changed to new one.

Martensite said:
How to enable the "New gesture" from 20.2.20 changelog?
Click to expand...
Click to collapse
Are you using K30 or POCO X2?
How did you flash this ROM? Did you root it? Were you able to boot after flashing magisk?

kushal.purkar said:
Are you using K30 or POCO X2?
How did you flash this ROM? Did you root it? Were you able to boot after flashing magisk?
Click to expand...
Click to collapse
K30
Through twrp they provided. Wipe cache after flashing.
Yes. Don't flash magisk through twrp. It causes bootloop. You have to patch the kernel and manually flash it.
1. Extract boot.img from the rom.zip
2. Install magisk manager app. Connect to any working network and open magisk manager.
3. Patch the boot.img from 1. It will generate magisk_patched.img to /storage/emulated/0/Download
4. (If you have twrp installed, go to 4.1)
Copy the magisk_patched.img to your pc's adb and fastboot folder and flash it through fastboot.
4.1 Boot to twrp, flash magisk_patched.img to "Boot"
Sorry if my english is bad

Martensite said:
K30
Through twrp they provided. Wipe cache after flashing.
Yes. Don't flash magisk through twrp. It causes bootloop. You have to patch the kernel and manually flash it.
1. Extract boot.img from the rom.zip
2. Install magisk manager app. Connect to any working network and open magisk manager.
3. Patch the boot.img from 1. It will generate magisk_patched.img to /storage/emulated/0/Download
4. (If you have twrp installed, go to 4.1)
Copy the magisk_patched.img to your pc's adb and fastboot folder and flash it through fastboot.
4.1 Boot to twrp, flash magisk_patched.img to "Boot"
Sorry if my english is bad
Click to expand...
Click to collapse
Thanks for this. I was able to root with this method.

ddaggebi said:
Works without major bugs. Plus all the goodies and extra features are here. Thanks for the superb ROM. Love to the .eu team.
Click to expand...
Click to collapse
whats extra feature??

i cant seem to install miui eu, stuck at redmi logo for hours, any idea guys, already format data

Related

[RECOVERY] Hybrid Recovery v3 (Supports All MM Roms: OOS H2OS CM AOSPA)

Here you go with Hybrid Recovery v3.x , which supports all available ROMs/ OSs for our beloved OnePlus2.
#One Recovery for All
1. Oxygen OS
2. Hydrogen OS
3. CM 13
4. Paranoid ROM
5. Ressurection Remix
6. Vanilla Unicorn
7. Dirty Unicorn
Download: Hybrid Recovery v3.2
Download: Hybrid Recovery v3.3
Download: Hybrid Recovery v3.4
Changelog : Hybrid Recovery v3.4
Code:
1. Added Option to Rename a backup package.
2. Added missing Timezone tab.
3. Combined modemst1 & modemst2 as "EFS" partition.
4. UI Enhancements.
Changelog : Hybrid Recovery v3.3
Code:
1. Install Section Optimized
2. Added New Partitions
a.Modemst1
b.Modemst2
c.OEM
d.Misc
e.Persist
f.Firmware
3. Fixed missing Strings & Optimized UI
Changelog : Hybrid Recovery v3.2
Code:
1. Hybrid UI, Simple and Beautiful.
2. Optimized Animation and Speed
3. Added SysLog and SysInfo in Advance Section.
4. Added Missing EFS and Recovery Partitions
5. OTG Support
6. Added ViewLog Option in Install Section
7. OnePlus Logo is now the back button (on demand)
Thanks! Been waiting for this. Downloading now.
Update:
My phone is encrypted and on OOS 3.0. Was able to use fastboot method to flash the new recovery. Unfortunately still can't get TWRP to decrypt the phone. Anyone have luck?
Update 2:
Tried TWRP 3.0.2 Hybrid v2 and decrypt still not working. Thanks for the attempted fix WhyOrean!
Just a FYI, flashing your recovery form TWRP prevented me from getting back into recovery. Had to load the previous twrp (3.0.2) via fastboot.
Could you please share the steps to Install it?
Do they depend on our current TWRP?
Best Regards
marpe said:
Could you please share the steps to Install it?
Do they depend on our current TWRP?
Best Regards
Click to expand...
Click to collapse
+1
marpe said:
Could you please share the steps to Install it?
Do they depend on our current TWRP?
Best Regards
Click to expand...
Click to collapse
https://twrp.me/devices/oneplustwo.html
The easiest way is to flash it within TWRP if you have TWRP 2.8.4 or higher already installed. Otherwise use Fastboot Install Method. Check the link above.
madferretx said:
https://twrp.me/devices/oneplustwo.html
The easiest way is to flash it within TWRP if you have TWRP 2.8.4 or higher already installed. Otherwise use Fastboot Install Method. Check the link above.
Click to expand...
Click to collapse
Yes but if do i flash via twrp..?
isoladisegnata said:
Yes but if do i flash via twrp..?
Click to expand...
Click to collapse
If you have TWRP already just select install images, flash this file and reboot.
this hybrid firmware not work for me while using CM13.
I flashed the official TWRP 3.0.2.0 via fastboot then its okay now.
Some users have reported many problems flashing this TWRP, so, please add the steps depending your current TWRP.
Can we flash it directly if we are using the modified H20 and OOS3 TWRP?Is it necessary to flash "Revert2Lollipop" before flashing this?
Thank you
I'm on OS3.0 and flash this recovery img file directly from my previous TWRP, and it worked as expected.
From OOS3.0 beta and TWRP 3.0.1-0 modified I've flash'd this hybrid recovery and no problem at all.
It works fine.
Thanks for the job.
WhyOrean said:
Download required Firmware Zip and Run Update script.
Click to expand...
Click to collapse
@WhyOrean - It might be worth including the backup partitions in the Update.bat too so users running Oxygen OS can flash OTA updates (these are checked before being patched).
Code:
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hypbak hyp.mbn
fastboot flash pmicbak pmic.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tzbak tz.mbn
Finally thanks for this
Verstuurd van mijn ONE A2003 met xda Forums PRO
So..if i am on h2os or oos3 and want to flash a cm13 ROM i flash old modem so oos2/cm13/ first...if i am on cm13 and i want to flash oos3 or h2os mm i have to flash new modem firmware ..right?
isoladisegnata said:
So..if i am on h2os or oos3 and want to flash a cm13 ROM i flash old modem so oos2/cm13/ first...if i am on cm13 and i want to flash oos3 or h2os mm i have to flash new modem firmware ..right?
Click to expand...
Click to collapse
Yep, but fastboot flash rather than recovery flash.
If you're on OOS3 or H2MM and want to move to CM13, fastboot flash the contents of the Oxy2_CM13_Firmware.zip first.
If you're on CM13 and want to move to OOS3 or H2MM, fastboot flash the contents of the OOS3_H2MM_Firmware.zip first.
Spannaa said:
@WhyOrean - It might be worth including the backup partitions in the Update.bat too so users running Oxygen OS can flash OTA updates (these are checked before being patched).
Click to expand...
Click to collapse
Sure I will add up that too, soon.
madferretx said:
Thanks! Been waiting for this. Downloading now.
Update:
My phone is encrypted and on OOS 3.0. Was able to use fastboot method to flash the new recovery. Unfortunately still can't get TWRP to decrypt the phone. Anyone have luck?
Click to expand...
Click to collapse
Sad to here that it didnt help, but remember patching encrypt fix from TWRP 3.0.2.
Yeah I never checked it on Encrypyed OP2, I dont Encrypt my phone nor I can encrypt it now to check.
Anyhow thanks for reporting, I will unto that in next build soon.
lockmunk said:
this hybrid firmware not work for me while using CM13.
I flashed the official TWRP 3.0.2.0 via fastboot then its okay now.
Click to expand...
Click to collapse
Thanks for reporting, I will look unto it.
But its working fine with my OPT Mokee OS(CM13 based)
marpe said:
Could you please share the steps to Install it?
Do they depend on our current TWRP?
Best Regards
Click to expand...
Click to collapse
1) Install it via your Current TWRP
Got to Install Section
Select Flash Image
Select TWRP Hybrid n Flash
2) Install via fastboot
Put your phone in fastboot
And flash via following command:
fastboot flash recovery twrp.img
fastboot boot twrp.img

Grab Flashable 7.0 OFFICIAL OTA from Here

http://www.pocketables.com/2016/08/official-android-nougat-released.html
Pulled directly from my device and uploaded to my AFH site.
https://drive.google.com/open?id=0B0OpOqUNqeKkb19UbGxBV2NPc28
Stock, decrypted boot image, w. Verity disabled.
What version of android where you coming from?
spunks3 said:
What version of android where you coming from?
Click to expand...
Click to collapse
I had the MM version installed. However, this has system.transfer.list and vendor.transfer.list - meaning - it *should* be the FULL ROM.
digitalhigh said:
I had the MM version installed. However, this has system.transfer.list and vendor.transfer.list - meaning - it *should* be the FULL ROM.
Click to expand...
Click to collapse
So we should be good to wipe all in twrp, flash the update zip, then seperately flash the boot.img and maybe supersu?
Deadlights said:
So we should be good to wipe all in twrp, flash the update zip, then seperately flash the boot.img and maybe supersu?
Click to expand...
Click to collapse
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
digitalhigh said:
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
Click to expand...
Click to collapse
What steps did you follow to get TWRP and root ?
So how is OTA different from full image?
digitalhigh said:
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
Click to expand...
Click to collapse
Nice! Thanks man :good:.. I guess it'll handle vendor for us?
MRL3GS said:
What steps did you follow to get TWRP and root ?
Click to expand...
Click to collapse
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
kolyan said:
So how is OTA different from full image?
Click to expand...
Click to collapse
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Deadlights said:
Nice! Thanks man :good:.. I guess it'll handle vendor for us?
Click to expand...
Click to collapse
Yep, /vendor is included, as well as updates to bootloader, etc.
kolyan said:
So how is OTA different from full image?
Click to expand...
Click to collapse
It does not encrypt if you were not previously encrypted, this is the biggest difference
digitalhigh said:
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Click to expand...
Click to collapse
When i try to setup pay I get "android pay cant be used" :S
MRL3GS said:
When i try to setup pay I get "android pay cant be used" :S
Click to expand...
Click to collapse
Ahaha! Sorry. Magisk requires you have Magisk manager installed, and then you use the manager to disable root when you want to use Pay. My bad.
http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
digitalhigh said:
Ahaha! Sorry. Magisk requires you have Magisk manager installed, and then you use the manager to disable root when you want to use Pay. My bad.
http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
Click to expand...
Click to collapse
Thanks all working now
digitalhigh said:
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Click to expand...
Click to collapse
Working great for me! Thanks again man!
Working great thanks !
Just to confirm for others :
1. Flash ROM don't reboot system !
2. Flash TWRP don't reboot system !
3. Flash the modified boot image, now reboot system !
4. Let it boot fully and make any app updates
5. Reboot into recovery
6. Flash SU
7. Wipe caches
8. Reboot and away you go !
I came from the latest MM security update and dirty flashed so be warned mileage may vary !
Worked for me Thank you!!!! Still kept super su and twrp!!!
Is anyone getting E:unknown command for patching system and vendor when flashing
Is that normal
hutzdani said:
Working great thanks !
Just to confirm for others :
1. Flash ROM don't reboot system !
2. Flash TWRP don't reboot system !
3. Flash the modified boot image, now reboot system !
4. Let it boot fully and make any app updates
5. Reboot into recovery
6. Flash SU
7. Wipe caches
8. Reboot and away you go !
I came from the latest MM security update and dirty flashed so be warned mileage may vary !
Click to expand...
Click to collapse
Flash the TWRP image file from TWRP? And what is the modified boot image?
Sent from my Nexus 6P using Tapatalk
Batfink33 said:
Is anyone getting E:unknown command for patching system and vendor when flashing
Is that normal
Click to expand...
Click to collapse
Me everything works fine tho just i cant get root to wrk the app keeps freezing on me can't grant root?
Sent from my Nexus 6P using Tapatalk

[Guide] How to install Magisk on MIUI and How to install GSI roms

Hello everyone, firstly, i'm not a dev. I'm just someone who really enjoying tweaking phones, Windows... So, in this post i'll show you how to install Magisk and GSI rom. Most of resources i took from 4PDA forum. Redmi 8A section on their forum is very active. My phone is Chinese variant (4-64), using MIUI 11 Xiaomi.eu rom / Havoc OS 3.1 GSI
Backup your data before doing anything!!!
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
#1. Install TWRP
- First, you must unlock phone with Mi Unlock tool. Which can be download from http://en.miui.com/unlock/download_en.html The unlocking process normally will take about 14 days.
- After unlock the phone, flash twrp from @milankragujevic thread. https://forum.xda-developers.com/xiaomi-redmi-8a/help/twrp-redmi-8a-olivelite-global-miui-10-t4006827
Now you'll have a working twrp.
#2 Install Magisk
1. Download lastest Magisk Flashable Zip from @topjohnwu thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Download patcher tool (thanks to @YaAlex3): http://files.yaalex.tk/patcher.7z
3. Reboot the phone to TWRP, on the computer, open adb and type command:
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
This'll pull your current boot image to sdcard
4. Unpack patcher.7z, copy boot.img to this folder. Open boot-patch.exe.
5. You'll have new_boot.img, flash this to boot partition using TWRP.
6. Flash Magisk you download at step 1
Caution: If bootloop happens, you may have to WIPE DATA.
7. Now you should have Magisk installed and working
If you can't patch the boot image file for some reasons, you can download here, choose the correct version, unzip and flash. If bootloop happens, wipe data in TWRP.
GLOBAL 11.0.3.0. PCPMIXM_20191219: Here
GLOBAL 11.0.1.0. PCPMIXM_20191121: Here
INDIA 11.0.3.0 .PCPINXM_20191119: Here
INDIA 11.0.1.0 .PCPINXM_20191105: Here
XIAOMI.EU 11.0.4.0 .PCPCNXM: Here
XIAOMI.EU 11.0.7.0. PCPCNXM: Here
#3 Install GSI Roms
Our phone is arm32binder64, so we'll download A64 A/B GSI rom to flash. In github of @phhusson, there is a list of GSI roms: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list
After you choose a rom, we'll follow these steps to flash a GSI rom:
1. Unzip the rom you choose and you'll have image file (.img)
2. Copy to your phone, Flash Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip to stay encrypted (optional, you can backup the /data but you can't setup password)
3. Make a factory reset and flash your unpacked image to system partition using TWRP or Orange Fox.
4. If you like Gapps, you can download Bitgapps or Opengapps (Arm) and flash (optional). But you must resize system partition first (advanced wipe -> repair or change file system -> resize system partition)
5. Flash Permissiver_v5.zip and Certification+Patch.zip
6. Go to Reboot and reboot to bootloader. Flash vbmeta using command:
Code:
fastboot flash vbmeta vbmeta.img
fastboot reboot
Otherwise, you can flash vbmeta.img directly to vbmeta partition, no difference though.
7. Now your phone should be reboot.
After trying some GSI rom like Pixel, RR, Lineage OS, AOSP... There're some bug like:
- D2TW is present in phhusson setting but not working. Use Magisk module: magisk_force-d2tw.zip to fix
- Auto brightness
- Brightness Slider: Can be fixed using adb:
Code:
adb shell su -c setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
or using Terminal:
Code:
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
- Camera Recording: You can use 3rd camera apps if bug occurs.
- When set password (pattern, etc...), next time you enter password, password will be wrong. (if you flash disable_dm... above), temp fix: boot to TWRP and remove some files in /data/system then reboot, password will be removed
Code:
locksettings.db-wal
locksettings.db-shm
locksettings.db
- Fix auto brightness, power consumtion... : copy treble-overlay-xiaomi-redmi8a.apk to /system/overlay then set permission 644, reboot.
- No Mac, IP address? Install the correct boot image.
- Some rom specific bugs...
UPDATE: On Havoc OS 3.1 from ExpressLuke, all the bugs are fixed, if any still present, just follow instructions above.
That is. I don't know why our device development is so slow after 2 months... So i decided to write this post. My main language is Vietnamese so if there's a grammar error, feel free to comment below. Thanks.
I get an error
C:\aaa\patcher>boot-patch.exe
Developer: YaAlex (yaalex.tk)
Thanks to:
acdev for zimage packer concept
And_PDA for AndImgTool
Igor Pavlov for 7zip
topjohnwu for magisk and all it's parts used here
Report any issues to t.me/yaalex3
UPDATER: Latest version is: 0.4
UPDATER: Current version is: 0.4
UPDATER: You have latest version!
INFO: Unpacking boot image....
ERROR: Can't find file: kernel.img
Press any key to continue . . .
Traceback (most recent call last):
File "C:\aaa\patcher\boot-patch.py", line 244, in <module>
File "C:\aaa\patcher\boot-patch.py", line 68, in die
NameError: global name 'quit' is not defined
Click to expand...
Click to collapse
arana1 said:
I get an error
Click to expand...
Click to collapse
The boot image you pulled from your phone, is it 64mb? Did you follow the instruction correctly? I have tried patching boot image again and it worked fine.
arana1 said:
I get an error
Click to expand...
Click to collapse
I am fixing patched boot.img from different firmware on 4pd, but if you want I will do it for you. Just take a screenshot of the phone settings where the firmware version is indicated and post your boot.img
Отправлено с моего Redmi 8A через Tapatalk
dmitrypershin2015 said:
I am fixing patched boot.img from different firmware on 4pd, but if you want I will do it for you. Just take a screenshot of the phone settings where the firmware version is indicated and post your boot.img
Отправлено с моего Redmi 8A через Tapatalk
Click to expand...
Click to collapse
Can i add your patched boot.img from your post on 4PDA to my thread? Thanks.
Ga_hap_la_chanh said:
Can i add your patched boot.img from your post on 4PDA to my thread? Thanks.
Click to expand...
Click to collapse
of course yes
Ga_hap_la_chanh said:
Hello everyone, firstly, i'm not a dev. I'm just someone who really enjoying tweaking phones, Windows... So, in this post i'll show you how to install Magisk and GSI rom. Most of resources i took from 4PDA forum. Redmi 8A section on their forum is very active. My phone is Chinese variant (4-64), using MIUI 11 Xiaomi.eu rom.
Backup your data before doing anything!!!
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
#1. Install TWRP
- First, you must unlock phone with Mi Unlock tool. Which can be download from http://en.miui.com/unlock/download_en.html The unlocking process normally will take about 14 days.
- After unlock the phone, flash twrp from @milankragujevic thread. https://forum.xda-developers.com/xiaomi-redmi-8a/help/twrp-redmi-8a-olivelite-global-miui-10-t4006827
Now you'll have a working twrp.
#2 Install Magisk
1. Download lastest Magisk Flashable Zip from @topjohnwu thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Download patcher tool (thanks to @YaAlex3): http://files.yaalex.tk/patcher.7z
3. Reboot the phone to TWRP, on the computer, open adb and type command:
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
This'll pull your current boot image to sdcard
4. Unpack patcher.7z, copy boot.img to this folder. Open boot-patch.exe.
5. You'll have new_boot.img, flash this to boot partition using TWRP.
6. Flash Magisk you download at step 1
Caution: If bootloop happens, you may have to WIPE DATA.
7. Now you should have Magisk installed and working
If you can't patch the boot image file for some reasons, you can download here, choose the correct version, unzip and flash. If bootloop happens, wipe data in TWRP.
GLOBAL 11.0.3.0. PCPMIXM_20191219: Here
GLOBAL 11.0.1.0. PCPMIXM_20191121: Here
INDIA 11.0.3.0 .PCPINXM_20191119: Here
INDIA 11.0.1.0 .PCPINXM_20191105: Here
XIAOMI.EU 11.0.4.0 .PCPCNXM: Here
#3 Install GSI Roms
Our phone is arm32binder64, so we'll download A64 A/B GSI rom to flash. In github of @phhusson, there is a list of GSI roms: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list
After you choose a rom, we'll follow these steps to flash a GSI rom:
1. Unzip the rom you choose and you'll have image file (.img)
2. Copy to your phone, Flash Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip to stay encrypted (optional)
3. Make a factory reset and flash your unpacked image to system partition using TWRP.
4. If you like Gapps, you can download Bitgapps or Opengapps (Arm) and flash (optional)
5. Flash Permissiver_v4.zip and Certification+Patch.zip
6. Go to Reboot and reboot to bootloader. Flash vbmeta using command:
Code:
fastboot flash vbmeta vbmeta.img
fastboot reboot
7. Now your phone should be reboot.
After trying some GSI rom like Pixel, RR, Lineage OS, AOSP... There're some bug like:
- Auto brightness
- Brightness Slider: Can be fixed using adb:
Code:
adb shell su -c setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
or using Terminal:
Code:
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
- Camera Recording: You can use 3rd camera apps if bug occurs.
- When set password (pattern, etc...), next time you enter password, password will be wrong. (some case), temp fix: boot to TWRP and remove some files in /data/system then reboot, password will be removed
Code:
locksettings.db-wal
locksettings.db-shm
locksettings.db
- Some rom specific bugs...
That is. I don't know why our device development is so slow after 2 months... So i decided to write this post. My main language is Vietnamese so if there's a grammar error, feel free to comment below. Thanks.
Click to expand...
Click to collapse
Thanks!
Edit: was having problems at first and ended up in a bootloop but eventually got Magisk and Root working finally. Thanks a lot for your help!
Hello everyone, I send you my best regards.
I comment. -
I have a global 8th redmi (olivelite), I unlocked the bootloader and continued to install the unofficial TWRP, but there is a problem, my touch screen does not work.
That's why I tried Orangefox and the touch panel worked without problems, I could erase everything except the micro SD, and continued to install Mi Globe 11.0.7, the most recent.
But at the time of finishing and restarting, restart only in recovery, no more, again and again.
Try once installed the rom my globe, flash twrp and force start by fastboor reboot, but it didn't work either.
Also install by fastboot, boot.img of the rom eu, of the global and also the patched by magysk and it didn't work either.
I am NOT looking for root, I am NOT looking for magysk, just install rom MY GLOBE clean, as in all my xiaomis, then I ask.
Has anyone been able to install Xiaomi.eu successfully on your device? With orangefox what was your process? With TWRP and the OTG, do you think I can start?
I would greatly appreciate your response. ):
marcachas said:
Hello everyone, I send you my best regards.
I comment. -
I have a global 8th redmi (olivelite), I unlocked the bootloader and continued to install the unofficial TWRP, but there is a problem, my touch screen does not work.
That's why I tried Orangefox and the touch panel worked without problems, I could erase everything except the micro SD, and continued to install Mi Globe 11.0.7, the most recent.
But at the time of finishing and restarting, restart only in recovery, no more, again and again.
Try once installed the rom my globe, flash twrp and force start by fastboor reboot, but it didn't work either.
Also install by fastboot, boot.img of the rom eu, of the global and also the patched by magysk and it didn't work either.
I am NOT looking for root, I am NOT looking for magysk, just install rom MY GLOBE clean, as in all my xiaomis, then I ask.
Has anyone been able to install Xiaomi.eu successfully on your device? With orangefox what was your process? With TWRP and the OTG, do you think I can start?
I would greatly appreciate your response. ):
Click to expand...
Click to collapse
Hi, have you try to wipe yet? Or try to wipe internal storage? I don't use miglobe but i'm using xiaomi.eu rom and this rom works great for me. And don't flash boot.img because each version is different.
Ga_hap_la_chanh said:
Hi, have you try to wipe yet? Or try to wipe internal storage? I don't use miglobe but i'm using xiaomi.eu rom and this rom works great for me. And don't flash boot.img because each version is different.
Click to expand...
Click to collapse
Miui 11.0.7 is not global, it apparently flashed either Chinese, or xiaomi.eu .
I posted the patched boot.img for xiaomi.ue 11.0.7 on 4pda
Sorry for my bad english. I am not literate and in Russian )))
dmitrypershin2015 said:
Miui 11.0.7 is not global, it apparently flashed either Chinese, or xiaomi.eu .
I posted the patched boot.img for xiaomi.ue 11.0.7 on 4pda
Sorry for my bad english. I am not literate and in Russian )))
Click to expand...
Click to collapse
He wrote mi-globe which is a rom modified from xiaomi.eu rom. I haven't updated the post yet. By the way i feel somehow MIUI is bad at wifi compare to GSIs. But GSIs have many bug, sometimes they won't boot at all. I noticed that you installed havoc os before, does it have double tab to wake device?
Ga_hap_la_chanh said:
He wrote mi-globe which is a rom modified from xiaomi.eu rom. I haven't updated the post yet. By the way i feel somehow MIUI is bad at wifi compare to GSIs. But GSIs have many bug, sometimes they won't boot at all. I noticed that you installed havoc os before, does it have double tab to wake device?
Click to expand...
Click to collapse
I have all the gsi loaded which I tried. Double tap does not work
Sorry for my bad english. I am not literate and in Russian )))
Just this
Sorry for my bad english. I am not literate and in Russian )))
dmitrypershin2015 said:
Just thisView attachment 4931295
Sorry for my bad english. I am not literate and in Russian )))
Click to expand...
Click to collapse
Yeah, the same as mine. I'm just waiting for a device specific rom so that we have a more stable rom, full-features, not miui. I hate the thing that after update i have to re-patch boot image to install magisk, if bootloop then wipe all. That's inconvenient.
Ga_hap_la_chanh said:
Yeah, the same as mine. I'm just waiting for a device specific rom so that we have a more stable rom, full-features, not miui. I hate the thing that after update i have to re-patch boot image to install magisk, if bootloop then wipe all. That's inconvenient.
Click to expand...
Click to collapse
Only check for rom updates
Sorry for my bad english. I am not literate and in Russian )))
I've been using havoc os 10 for the past day and so far I really like it. MIUI is really sluggish compared to havoc. So far I have not really noticed any bugs besides the brightness which was easily fixed using the command in the original post and not being able to apply a screenlock.
ways2 said:
I've been using havoc os 10 for the past day and so far I really like it. MIUI is really sluggish compared to havoc. So far I have not really noticed any bugs besides the brightness which was easily fixed using the command in the original post and not being able to apply a screenlock.
Click to expand...
Click to collapse
I have a dialer for havoc os with recording calls (but it doesn’t work very loudly) and a patch for increasing the volume in the headphones + libraries from the Samsung. I can give
Sorry for my bad english. I am not literate and in Russian )))
View attachment 4931461
Ga_hap_la_chanh said:
Hi, have you try to wipe yet? Or try to wipe internal storage? I don't use miglobe but i'm using xiaomi.eu rom and this rom works great for me. And don't flash boot.img because each version is different.
Click to expand...
Click to collapse
Excellent, thanks for your reply.
Could you be a little more specific about the steps you took?
Formatting before installing the ROM, or after?
For example, I followed these steps.
Unlock the bootloader.
Fastboot, install the vbmeta first (or something like that).
install the Orange fox recovery, then the orangefox zip.
Clean EVERYTHING (dalvik cache, intertnal storage, etc), except SD.
Install MY GLobe ROm Olivelite.
Start in recovery, restart again, without changes, continue to start in recovery, and so, for eternity.
I did not do the formatting, and I do not use TWRP because the touch panel does not work with that, so I only have Orangefox as an alternative, could you try to install the MI Globe ROM please? https://mi-globe.com/miui-firmware-rom-builder-features/41/
Thanks for everything.
dmitrypershin2015 said:
I have a dialer for havoc os with recording calls (but it doesn’t work very loudly) and a patch for increasing the volume in the headphones + libraries from the Samsung. I can give
Sorry for my bad english. I am not literate and in Russian )))
View attachment 4931461
Click to expand...
Click to collapse
Sure, I'll check those out. Go ahead and send them my way

Root Redmi 9 without twrp and data lost

VERY IMPORTANT:
Please make sure your boot.img version matches the ROM version . that's mean if you update your device then you have to use patch boot.img from new recovery rom.never use the old one. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.(link in this post)
Then run this command
fastboot flash vbmeta vbmeta.img
fastboot flash boot patch-boot.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Shas45558 said:
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.
https://forum.hovatek.com/thread-32719.html
Go to method 3....log in to download vbmeta.img file.
Then run this command
fastboot flash boot patch-boot.img
fastboot flash vbmeta vbmeta.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Click to expand...
Click to collapse
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
nielsync said:
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
Click to expand...
Click to collapse
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Shas45558 said:
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Click to expand...
Click to collapse
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
nielsync said:
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
Click to expand...
Click to collapse
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Shas45558 said:
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Click to expand...
Click to collapse
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
nielsync said:
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
Click to expand...
Click to collapse
I use this version of magisk manager and it always work
Shas45558 said:
I use this version of magisk manager and it always work
Click to expand...
Click to collapse
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Thanks for the post. It helped me to root my redmi note 9.
nielsync said:
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Click to expand...
Click to collapse
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Shas45558 said:
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Click to expand...
Click to collapse
My issues was patching using the canary version of Magisk Manager which isn't stable enough and was probably not patching the boot image properly as opposed to Magisk Manager 7.5.1 which is the stable version. Nice explanation on the vbmeta.img file.
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
I guess this still doesn't unlock the bootloader, and what about system updates?
Kiwironic said:
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
Click to expand...
Click to collapse
Ok i do ir on top and bottom of the post and thanks for your advice:good::good:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
rizelgeorgel said:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
Click to expand...
Click to collapse
Download pbrp from official website.then extract it and you will get a .img file.flash it via fastboot mood and the cmd is
fastboot flash recovery pbrp.img
*Change pbrb.img according to your file name.
One big question..did you unlock your bootloader and root your device?
Thank you very much! I succeeded according to your advice!
shas hows pbrp?
regarding flashing?
mhark.moby said:
shas hows pbrp?
regarding flashing?
Click to expand...
Click to collapse
Pbrp is in beta testing....so it has some bug and there's no use to install..
Buenas tardes tengo problemas al cargar el parche de magisk en redmi 9. Cuando cargo el boot.img parchado de magisk el tlfn queda en bootloop estoy en la version 11.0.8 global.

Question Info about root/ota/debloat

Hi all and sorry for my bad english in first!!
i live in italy and i've buyed(but still not recieved) one oneplus 9r from china whit oxygenos rom on board..
When it comes i want to root & debloat it, but i've some queustion cause in last year i've used only device with custom rom!.
first of all i wan't to root the phone, but preserve the possibility to update the OS with ota. if i understand right it's possible with magisk, can please someone tell me the correct step to make?
after root i vant to uninstall not necessary app for my utilization (facebook/instagram/netflix, red cable and oneplus account, google app, gdrive, google photo and most of BigG apps cause i'm using only gmail/yt/maps/ an store!).
the question is.... if i uninstall this app it will be re installed in future ota?
Thanks in advice!
Step1 : unlock bootloader, this will wipe the storage, then setup the device once again then enable usb debugging in developer options.
You can use this
Tool to make (tool all in one) your life easier : https://sourceforge.net/projects/tool-all-in-one/files/TOOL_ALL_IN_ONE_1.0.6.1.zip/download
you should select 8t as 9r is not supported officially
at the moment.
Step2: update the phone to latest version , right now it's 11.2.5.5
Step 3: download the same version of the oxygen is ota wether from xda, OnePlus official site , oxygen updater ( make sure it is full version).
Step4: on pc now extract only the payload.bin file in the input of the payload extracter ,
Now use the payload extracter ,
Run .exe and get boot.img .
payload_dumper_tool_by_ius.zip
drive.google.com
(MAKE SURE THE PHONE OS VERSION AND BOOT IMG VERSION IS SAME)
Step 5: install magisk manager on phone, now patch the boot.img that you extracted earlier. Copy this patched boot.img in platforms tool folder(I hope that u have installed the platform tools and adb & fastboot ).
Step 6: open terminal there in platform tools , use the tool all in one to boot your phone in fast boot mode,then flash patched boot.img using.
Fastboot devices
Fastboot flash boot_a patched.img
Fastboot flash boot_b patched.img
Bingo got rooted.
Step 7( optional) : now properly restart the phone by opening magisk , then install universal safety net fix, debloat modules in magisk.
You can use lucky patcher to debloat unnecessary things (which don't exist as it is oxygen os)
Now in future if your phone gets ota make sure you disable all magisk modules then download the full version of ota from oxygen updater & update it locally & do not restart.
go to magisk ,
flash magisk to inactive slot.
restart now,
REnable the modules. (Tip don't enable the lucky patcher module this will put you in bootloop)
enjoy the ota .
@Rajveer chauhan
Do you have instructions to install TWRP?
I even tried to read the thread on the 8t forum, but I didn't understand it very well.
So, 1st of all make sure u are on oos , then simply boot in to bootloader then flash this ofox img file , using the command
fastboot flash recovery name.img then boot into recovery it will ask u your screen lock, then flash this ofox zip file .
this or any recovery are in beta phase , everything works but not 100/100 times.
unzip this and flash the img cuz the img could not be uploaded
this will only work on oos not on any custom rom, uwill not require to format data
& trust me i am not a hacker
Rajveer chauhan said:
So, 1st of all make sure u are on oos , then simply boot in to bootloader then flash this ofox img file , using the command
fastboot flash recovery name.img then boot into recovery it will ask u your screen lock, then flash this ofox zip file .
this or any recovery are in beta phase , everything works but not 100/100 times.
unzip this and flash the img cuz the img could not be uploaded
this will only work on oos not on any custom rom, uwill not require to format data
& trust me i am not a hacker
Click to expand...
Click to collapse
Is Orange Fox easy to use as TWRP?
Just flash via fastboot? Because I want to keep magisk/root.
lvints said:
@Rajveer chauhan
Do you have instructions to install TWRP?
I even tried to read the thread on the 8t forum, but I didn't understand it very well.
Click to expand...
Click to collapse
lvints said:
Is Orange Fox easy to use as TWRP?
Just flash via fastboot? Because I want to keep magisk/root.
Click to expand...
Click to collapse
Way better than twrp just follow the steps u won't lose anything
lvints said:
Is Orange Fox easy to use as TWRP?
Just flash via fastboot? Because I want to keep magisk/root.
Click to expand...
Click to collapse
So how did it go?
Rajveer chauhan said:
So how did it go?
Click to expand...
Click to collapse
I've already downloaded the files, but I haven't tested them yet.
I'll leave it for the weekend, if there's a problem I can solve it with peace of mind.
Sir have you tried changing the font of your 9R?
I've been looking on the magisk forums or some app but I haven't had success.
Yeah I actually use the Einstein font the font manager by androidacy seems to work for me.
Rajveer chauhan said:
Yeah I actually use the Einstein font the font manager by androidacy seems to work for me.
Click to expand...
Click to collapse
I tried this module too, only with Komika font, my favorite.
What version of the module do you use? I tried with the last one (5.5.6) and the font doesn't seem to have been applied.
I'm on OOS 11.2.7.7.
Same version
lvints said:
I tried this module too, only with Komika font, my favorite.
What version of the module do you use? I tried with the last one (5.5.6) and the font doesn't seem to have been applied.
I'm on OOS 11.2.7.7.
Click to expand...
Click to collapse
.
Rajveer chauhan said:
So, 1st of all make sure u are on oos , then simply boot in to bootloader then flash this ofox img file , using the command
fastboot flash recovery name.img then boot into recovery it will ask u your screen lock, then flash this ofox zip file .
this or any recovery are in beta phase , everything works but not 100/100 times.
unzip this and flash the img cuz the img could not be uploaded
this will only work on oos not on any custom rom, uwill not require to format data
& trust me i am not a hacker
Click to expand...
Click to collapse
I flashed the img file and it booted to OrangeFox but I cannot press anything as the screen does not react. What is the solution for it?
It's is compatible with oos 11
Not with oos 12, any custom roms
Rajveer chauhan said:
It's is compatible with oos 11
Not with oos 12, any custom roms
Click to expand...
Click to collapse
I was on OOS 11. The 11.2.8.8.LE28DA.
Flashed it, boot up but cannot press anything. How can I go back to the original boot?
U can unzip the payload.bin and extract the recovery file and flash it in the bootloader and everything goes normal
Rajveer chauhan said:
U can unzip the payload.bin and extract the recovery file and flash it in the bootloader and everything goes normal
Click to expand...
Click to collapse
Thanks I got back to the original boot, but now how can I root with Magisk?
@Rajveer chauhan
Hello sr
Have you updated your 9r for A12 ? If yes, how did you do it? Would it be possible to go from A11 (11.2.8.8) to A12 (C.33)?

Categories

Resources