Related
MODS: Please move this question to the HELP section - incorrectly posted. Thanks.
Hello,
I am trying to root the Global MIUI _V10.2.1.0.PECMIXM ROM using Magisk. I want my phone to remain encrypted, and having spent all day today trying to achieve this, I am turning here for help.
I have tried flashing via Fastboot and TWRP, have tried flashing Disable DMVerity (without disabling the force encryption) before, and after flashing Magisk. I hava managed to get Magisk 18 flashed and able to boot to the ROM, but when I open Magisk Manager (Installed by the flash) it updates itself and says it needs to install Magisk, proposing to download it - or patch boot img.
Every time I try to flash the downloaded zip, or try fastboot flashing the modified boot.img, the phone won't boot - it just ends up in TWRP recovery.
I have wiped data 100s of times to try to fix this, to no avail.
I have tried to boot into TWRP without flashing it, but this just hands on the TWRP flash screen every time.
Any help / tips would be appreciated.
Were you following any tutorial post? Recent xiaomi phones come with more strict policy on bootload locks. I'm not familiar with it, but if I didn't misunderstand, without BL unlock it's kinda dangerous to flash anything on the phone.
msg7086 said:
Were you following any tutorial post? Recent xiaomi phones come with more strict policy on bootload locks. I'm not familiar with it, but if I didn't misunderstand, without BL unlock it's kinda dangerous to flash anything on the phone.
Click to expand...
Click to collapse
Thanks for replying. Yes, following tutorials, have unlocked my bootloader and can flash ROMs, just cannot get the latest MIUI 10 Global Stable rooted, without decrypting the phone. I have managed it on the Xiaomi.eu global stable, but not with the original Stock ROM.
Has anyone succeeded?
hello bro, u can try my way.
NEED:
unlock bootloader.
folder ADB / u can download all in my GG driver or internet from other source if u scare virus (^o^)
twrp / u can download all in my GG driver or internet from other source if u scare virus (^o^)
diver ADB / u can download all in my GG driver or internet from other source if u scare virus (^o^)
PREPARING:
download and copy to phone store and folder ADB
u should rename file TWRP with short name, any name u can remember. (ex: twrp.img or aaa.img, etc....)
install diver for PC/ LAP, u can try to plug mi phone in case FASTBOOT and check in DEVICE MANAFER of PC/ LAP.
remember ENABLE USB debugging on phone
OK, ACTION:
open CMD/ command window in folder ADB (u can put this folder at any diver on PC / LAP) with right click at this folder.
type all commands, follow with contrucs:
adb reboot bootloader (past this if u are in BL)
choose 1 in 2 ways:
1.
fastboot flash recovery twrp.img (do it to install recovery cook replace recovery stock)
fastboot flash misc misc.bin (do this line if u use stock folder china - TWRP-3.2.3-1202-XIAOMI8UD-CN-wzsx150-fastboot.7z)
fastboot boot twrp.img (do it for reboot to recover cook)
2.
fastboot boot twrp.img (do it, u use recovery temporary recovery cook and very easy, find file recovery, install it)
(test again by to use temporary reovery, reboot to recovery again)
note: i like second way, very easy and fast with pro person (^o^)
i tested in all miui stock (china, global)
HAVE FUN \(^o^)/
this link for all
https://drive.google.com/open?id=1uT8g1oOOkD27P2fylNzlAlXrT8PbCJEs
do note use it if u scare virus, malware, etc........ \(^o^)/
reply me if u can not apply all or do not dowload my GG driver.
u can read and do all with this stock link in miui en (http://en.miui.com/thread-3671565-1-1.html)
t4manh198E said:
hello bro, u can try my way.
NEED:
unlock bootloader.
folder ADB / u can download all in my GG driver or internet from other source if u scare virus (^o^)
twrp / u can download all in my GG driver or internet from other source if u scare virus (^o^)
diver ADB / u can download all in my GG driver or internet from other source if u scare virus (^o^)
PREPARING:
download and copy to phone store and folder ADB
u should rename file TWRP with short name, any name u can remember. (ex: twrp.img or aaa.img, etc....)
install diver for PC/ LAP, u can try to plug mi phone in case FASTBOOT and check in DEVICE MANAFER of PC/ LAP.
remember ENABLE USB debugging on phone
OK, ACTION:
open CMD/ command window in folder ADB (u can put this folder at any diver on PC / LAP) with right click at this folder.
type all commands, follow with contrucs:
adb reboot bootloader (past this if u are in BL)
choose 1 in 2 ways:
1.
fastboot flash recovery twrp.img (do it to install recovery cook replace recovery stock)
fastboot flash misc misc.bin (do this line if u use stock folder china - TWRP-3.2.3-1202-XIAOMI8UD-CN-wzsx150-fastboot.7z)
fastboot boot twrp.img (do it for reboot to recover cook)
2.
fastboot boot twrp.img (do it, u use recovery temporary recovery cook and very easy, find file recovery, install it)
(test again by to use temporary reovery, reboot to recovery again)
note: i like second way, very easy and fast with pro person (^o^)
i tested in all miui stock (china, global)
HAVE FUN \(^o^)/
this link for all
https://drive.google.com/open?id=1uT8g1oOOkD27P2fylNzlAlXrT8PbCJEs
do note use it if u scare virus, malware, etc........ \(^o^)/
reply me if u can not apply all or do not dowload my GG driver.
u can read and do all with this stock link in miui en (http://en.miui.com/thread-3671565-1-1.html)
Click to expand...
Click to collapse
Thanks for replying. However, this tells me how to flash TWRP, how to boot to TWRP - I have no problem doing that whatsoever. I can successfully do that again and again.
What I have not been able to do is flash Magisk v18 on v10 stock ROM and be able to boot successfully. It bootloops into TWRP.
My post help u to install twrp or flash twrp
I do not know your mean what is flash twrp !?
Reboot to recov cook by press volumn +/- and power button
Use magisk 17.1 stanle, u can find it in my gg driver or download in miui eu 's page
---------- Post added at 05:03 AM ---------- Previous post was at 05:02 AM ----------
nealed said:
Thanks for replying. However, this tells me how to flash TWRP, how to boot to TWRP - I have no problem doing that whatsoever. I can successfully do that again and again.
What I have not been able to do is flash Magisk v18 on v10 stock ROM and be able to boot successfully. It bootloops into TWRP.
Click to expand...
Click to collapse
1 in 2 ways is certainly successful
nealed said:
Thanks for replying. However, this tells me how to flash TWRP, how to boot to TWRP - I have no problem doing that whatsoever. I can successfully do that again and again.
What I have not been able to do is flash Magisk v18 on v10 stock ROM and be able to boot successfully. It bootloops into TWRP.
Click to expand...
Click to collapse
Hey, I'm success root my mi 8 pro (Android 9 V10.2.1.0.PECMIXM - MIUI 10)
If you know how to use TWRP, now just reboot your mi 8 pro to TWRP
and then choose Mount > check system & vendor.
Then flash the Latest Version of magisk (v18.1)
REMEMBER : TO MOUNT >> CHECK SYSTEM & VENDOR. AFTER THAT JUST FLASH MAGISK. ONLY MAGISK !!!
And then reboot to your system.
After that, download the latest versio of Magisk Manager, install it and open it.
And BOOOOM~
Your Mi 8 Pro just rooted.
nfadrizp said:
Hey, I'm success root my mi 8 pro (Android 9 V10.2.1.0.PECMIXM - MIUI 10)
If you know how to use TWRP, now just reboot your mi 8 pro to TWRP
and then choose Mount > check system & vendor.
Then flash the Latest Version of magisk (v18.1)
REMEMBER : TO MOUNT >> CHECK SYSTEM & VENDOR. AFTER THAT JUST FLASH MAGISK. ONLY MAGISK !!!
And then reboot to your system.
After that, download the latest versio of Magisk Manager, install it and open it.
And BOOOOM~
Your Mi 8 Pro just rooted.
Click to expand...
Click to collapse
I rooted firsr u
nd now i am using mi mix 3 ???
Hello
I am trying to update for a while now, but I just cannot get it installed.
I already have TRWP 3.3.0.0 running on a rooted Pocophone F1.
I am still kind of newbie using LOS, sorry. Some stuff I still don't understand even though spending lots of time reading and googling and reading...
What I do:
I start TRWP and wipe: WIPE ADVANCE Dalvik,Cache,System,Data
I install in the following order:
beryllium-V10.3.6.0.PEJMIXM-9.0-vendor-firmware
lineage-16.0-20191003-nightly-beryllium-signed
Disable_Dm-Verity_ForceEncrypt_02.04.2019
Magisk-v19.4
open_gapps-arm64-9.0-mini-20191003
then I reboot, stare a while on the working LOS-installing-log and...
boot to TRWP
I am experiencing problems while installation for some time, so I already tried:
- wiping dalvik after each zip during installation
- Magisk-v19.3
- leave out open-gapps
- beryllium-9.6.27-9.0-vendor-firmware
- lineage-16.0-20190807-nightly-beryllium-signed
- lineage-16.0-20190929-nightly-beryllium-signed
Where do I find information on which corresponding vendor/firmware to be used for LOS16?
Looking at the screen while installation of lineage-16.0-20191003-nightly-beryllium-signed, I read: "... Target: ...V10.2.3.0.PEJMIXM..."
So I guess I should flash that mentioned vendor/firmware version for that mentioned LOS version, but I just don't know where to download that vendor/firmware. It is not available on the server of akhilnarang...
Maybe I'm wrong and there might be another problem, I just do not know what to do.
Best regards
what rom your using before you installed los?
Clean flash would be needed ..you should wipe internal too to get it working , dont forget to remove all you password , fingerprint and face unlock.
Boot to recovery wipe system/dalvik/data/cache/internal before doing this you need to do a nandrioid back up..
do this:
download the lastest vendor:
beryllium-V10.3.8.0.PEJMIXM-9.0-vendor-firmware
next the LOS rom:
lineage-16.0-20191003-nightly-beryllium-signed
open_gapps-arm64-9.0-mini-20191003
and then
download the latest DFE version 19.3:
you can download it in telegram pocof1 group chat
and then wipe dalvik cache after that reboot system
first boot reboot to twrp recovery and the flash magisk v19.3 the reboot system....
i hope this method will help you..goodluck!!!
Prior to now, I had a 6 month old LOS working up to now.
My last attempt:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
says: "If you plan to install custom kernels, flash the zip AFTER installing Magisk".
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Zackptg5 says:"If you're not encrypted: flash all of your stuff, then FLASH THIS ZIP LAST"
I use the most recent DFE Disable_Dm-Verity_ForceEncrypt_10.01.2019 from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/page64
most actual vendor/firmware i find here: https://xiaomifirmwareupdater.com/firmware/beryllium/
is: fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
I have not found a trustworthy source for the very new 10.3.8.0, but this should not be an issue...
So then, my new order is:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- Magisk-v19.4
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
Done that and REBOOT SYSTEM and....
Pocophone boots into FASTBOOT...
I am really pissed off at this point.
I can still enter TRWP 3.3.0.0 by pressing ON+VOLUP
I don't know any further.
So then, my new order is:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- Magisk-v19.4
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
Done that and REBOOT SYSTEM and....
Pocophone boots into FASTBOOT...
Why you didn't follow my instructions? clearly you dont understand ...
Oh...
I read your reply again, so is it correct you want me to:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT to RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
? ok in this order?
Sorry, found another mistake in my last description, now I tried:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT SYSTEM
-> after REBOOT SYSTEM, Poco F1 instantly starts into FASTBOOT. I then press ON+VOLUP to enter RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
-> still, Poco F1 instantly starts into FASTBOOT again.
That is where I am stuck now.
Andi900rr said:
Sorry, found another mistake in my last description, now I tried:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT SYSTEM
-> after REBOOT SYSTEM, Poco F1 instantly starts into FASTBOOT. I then press ON+VOLUP to enter RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
-> still, Poco F1 instantly starts into FASTBOOT again.
That is where I am stuck now.
Click to expand...
Click to collapse
install a global rom via twrp the latest one with 10.3.8.0 recovery flashable
go to twrp
flash the miui stable ..and then flash magisk 19.3 ..format data then reboot ... and then follow the steps i already given..
watch this for your reference https://www.google.com/url?sa=t&sou...BMAF6BAgFEAk&usg=AOvVaw09B7QXYvADkv7ZyNQtvH1K
Ok, will do that next day, thank you for your help and patience!!
In Recovery, I cannot "Swipe to unlock" anymore...
The touchscreen is not working. I had that issue several times in the past already. Rebooting to Recovery sometimes helps, but not now.
Andi900rr said:
In Recovery, I cannot "Swipe to unlock" anymore...
The touchscreen is not working. I had that issue several times in the past already. Rebooting to Recovery sometimes helps, but not now.
Click to expand...
Click to collapse
ok so its time to flash rom via fastboot ..just download the latest stable 10.3.8 fastboot rom after you install back up everthing first before flashing so you can restore if anything happens..back up only Boot , Recovery , System image , Vendor image , Efs and your good to go.. watch these and download are already included in this video https://www.google.com/url?sa=t&sou...BMAJ6BAgFEA4&usg=AOvVaw2naYU5q2jUaE5qUeskrBed[/url]
Before anything else ..use the twrp 3.2.3.0 recovery
Man, flash MIUI 10.3.8.0 on fastboot. ONLY MIUI. then boot... if it boot, tell us
Success flashing:
miui_POCOF1Global_V10.3.8.0.
recovery-20181211
Magisk-v19.3
rebootet to recovery, now into TWRP 3.2.3-0
I still wonder what was the problem and what was the solution...
Maybe formatting data was the solution?
From here, I backed up:
Boot
Recovery
System.image
Vendor.image
Efs
Backup created successfully; also copied to PC.
I wonder when installing LOS again from here on, if I should...
- update to TWRP 3.3.0-0
- update to Magisk-v19.4
or not.
bamz1117 said:
what rom your using before you installed los?
Clean flash would be needed ..you should wipe internal too to get it working , dont forget to remove all you password , fingerprint and face unlock.
Boot to recovery wipe system/dalvik/data/cache/internal before doing this you need to do a nandrioid back up..
do this:
download the lastest vendor:
beryllium-V10.3.8.0.PEJMIXM-9.0-vendor-firmware
next the LOS rom:
lineage-16.0-20191003-nightly-beryllium-signed
open_gapps-arm64-9.0-mini-20191003
and then
download the latest DFE version 19.3:
you can download it in telegram pocof1 group chat
and then wipe dalvik cache after that reboot system
first boot reboot to twrp recovery and the flash magisk v19.3 the reboot system....
i hope this method will help you..goodluck!!!
Click to expand...
Click to collapse
you can download it in telegram pocof1 group chat
Click to expand...
Click to collapse
please guide me to the group
****
I did the exact order bamz1117 wrote:
flashed:
-beryllium-V10.3.7.0.PEJMIXM
-lineage-16.0-20191003-nightly-beryllium-signed
-open_gapps-arm64-9.0-mini-20191003
-DFE 19.3
wipe dalvik
reboot system
and back into FASTBOOT...
Seems I am back where a was coming from? I am confused.
I have the suspicion that one of my zips is corrupted/defective/unproper version, but I have no idea which one.
When I flash
- beryllium-V10.3.6.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- Disable_Dm-Verity_ForceEncrypt_02.04.2019
wipe dalvik
reboot
- Magisk-v19.3
at least I see the LOS install logo working for quite a long time, but after that it reboots to TWRP recovery.
I noticed the following things:
concerning FW/vendor:
- beryllium-V10.3.6.0.PEJMIXM
I downloaded from https://mirror.akhilnarang.me/MIUI/beryllium/
is 451MB in size
- the newer ones:
fw_beryllium_miui_POCOF1Global_V10.2.3.0.PEJMIXM_a0319918c1_9.0
fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM_aa86bd1d08_9.0
are 91 MB each, I downloaded from https://xiaomifirmwareupdater.com/firmware/beryllium/
are those files fake?
Where to download V10.3.8.0 from a trustworthy source?
Would someone please explain me the proper order for a clean re-install (while rooted and TWRP recovery already installed) AND explain the reason behind that particular order?
My current understanding, which might be wrong:
1. Firmware/vendor first (obvioulsy this is giving hardware support to the operating system like with a PC), then
2. Lineage OS (this is the operating system) and
3. openGapps third (this modifies the operating system and includes google apps)
4. DFE (a kind of a script? which modifies the operating system by disabling verity/encryption/quota when setting the filename of the zip accordingly)
5. Magisk (offers services in order to hide rooting etc. to prevent apps with higher security e.g. online banking to detect security nonconformity and thus stop working)
Please correct me where and why I am wrong in that order - I want to understand it.
Thank you.
I dont know why but I lost TWRP meanwhile.
My Pocophone only starts into fastboot mode, I cannot invoke TWRP Recovery anymore.
I tried to flash the latest stock rom with "Tool all in one", which tells me bootloader is still unlocked.
But when I try to flash, a command window opens and closes immediately and nothing happens.
I try to run "Tool all in one" as admin, but it does not start.
I dont know what to do.
Was able to flash twrp 3.3.0-0 via fastboot... If I enter Recovery, it shows twrp 3.2.3-0 .... idk,wtf
I am able to restore Miui10 from backup! It runs!
But flashing vendor/LOS/DFE/Magisk is not working! WTF! No idea why.
Still have THE SAME fastboot-loop issue after flashing vendor/LOS/DFE/Magisk I STARTED WITH the first post.
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
64-bit Base Package For GSI Redmi 7A
Flashing instructions ?
• Boot to recovery
• Flash given zip file (Downloads section)
• Wipe system
• Flash any arm64 GSI of your choice to system image
• Format data, wipe cache
• Flash gapps, magisk, etc...
• Boot to system, congrats you're on arm64.
Changelog:
- Fixed camera service crashing.
- Gcams can now run on Enforcing mode.
- Swap is disabled by default in favor of ZRAM.
- Fixed more services crashing that just filled up the logcat.
- Changed to Global for better overlay compatibility
- ViperFX now works in Enforcing mode where as before it would be unstable.
- Camera doesn't take as long to launch now.
Old Changes (from previous vendor/post):
• Fix bt audio, cleanup audio configs
• Add exfat fix
• Fix headphones
• Fix video recording
• Enable pseudo-gyro (emulated gyroscope from miui)
Downloads :
Base
mirror link
Bugs ?
• VoLTE doesn't work (fix: https://t.me/Redmi7AUpdates/98)
Things to point out:
- As mentioned on the previous release, Pie and Amber/Erfan based GSIs can't boot on Enforcing mode, in which case the Permissiver v5 zip from #permissiver is necessary.
- The FM Radio fix found in notes doesn't work anymore, use this instead (http://www.mediafire.com/file/wgnysvjo362yuco/FM_Radio-Fix.zip/file) and flash through Magisk.
- If you are having any camera related issues then switch to Permissive mode.
-Fixed some stuff and made a new one.
-Sadly, upgrading directly from the old one isn't possible and formatting data is required, I tried to make it upgradable but with no success.
*Currently using Havoc os 3.8"
And credits to telegram redmi 7a team and for the developers who work so hard for this project I do not own this work
Join here need telegram app on windows and android and dont forget to like my post https://t.me/PineOfficial
just flash permissiver to make wired headphone work
for me blissrom arm64 is smooth with face unlock unless u use android 9 as base firmware to have encryption or else u cant add password
daizu said:
just flash permissiver to make wired headphone work
for me blissrom arm64 is smooth with face unlock unless u use android 9 as base firmware to have encryption or else u cant add password
Click to expand...
Click to collapse
True, use MIUI A9 base to get encryption working on TWRP.
No chance to get this working on MIUI?
iagm12 said:
No chance to get this working on MIUI?
Click to expand...
Click to collapse
theres no way and also memeUI sucks
Custom Roms GSIs are better
edit:
there is new a update bluetooth already fix and other bugs..
iagm12 said:
No chance to get this working on MIUI?
Click to expand...
Click to collapse
You could try to use this on a MIUI GSI ported from the Redmi 8 maybe, but I don't know if it would work completely.
Maybe Erfan's GSI builds? https://mirrors.lolinet.com/firmware/gsi/MIUI/
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
Also, not to nitpick, but my username is different in XDA.
https://forum.xda-developers.com/redmi-7a/how-to/redmi-7a-arm64-kernel-t4134381
I'm the kernel dev.
---------- Post added at 03:29 PM ---------- Previous post was at 03:24 PM ----------
Also, I'm going to try out Ubports if I can. It would be interesing to see if it would work because of the Q vendor.
Great Work, congrats <3
i have ask helios developer (maintainer of helios gsi) to resize the gsi of redmi 8 (redmi 8 has 3.5 gb raw image that cant be flash easy to our phone which has only 3gb)
"Flash any arm64 GSI of your choice to system image" i dont know what is this, but can u give me yours?
all using just twrp to flash?
How did you root your device? Im currently on MIUI 11.0.3 Q and there's no TWRP or any magisk rooting files/guide that is updated.
Good work btw. If you can share your rooting method and TWRP this can be an ALL IN ONE guide. Many thanks!
EDIT: Its working right now, but thing is I cant flash anything from internal storage, it shows weird letters (encrypted). Its Pitch Black Recovery 3.0. How did you solve this?
regularfanb0y said:
EDIT: Its working right now, but thing is I cant flash anything from internal storage, it shows weird letters (encrypted). Its Pitch Black Recovery 3.0. How did you solve this?
Click to expand...
Click to collapse
Had the same situation here on my 7A with TWRP, i also couldn't transfer the files via file Explorer from Windows to the 7A
because of the encryption (the copy and paste window doesn't do anything and disapears after a while).
Solution to this is:
Format Data > Yes
[Warning - outdated - OP has replaced the fw+vendor file 11.0.3 to 11.0.11]
Explaning some stuff about GSI basics
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i had all the needed files to give it a try.
Instructions how to get from some sort of a corrupt status xy --> StockRom
Because i did some testing with Rom's i needed a "starting point" = this means unlocked Bootloader, Stock Rom V11.0.3, recovery installed
This was necessary for me to find out what step causes problems and also to "reset" the boot.img if i used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status "xy" back to "starting point":
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
go to recovery by holding Vol-Up & Power
-->my starting point to testing different settings...
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section [Warning - outdated - OP has removed this file]
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead [EDIT: app doesnt work because of errormessage]
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
As already mentioned the FM Radio fix doesn't work, if you skip it LOS boots perfectly
another bug: No other color of the Notification LED than white
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
mYXiao said:
I had some troubles getting this running, but finally i made it
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i theoretically had all the files to give it a try.
But i had to flash Stock Rom for many times because i wanted to start from the same starting point so i could find out what step causes the problem
and also to "reset" the boot.img if i had used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status back to "my starting point" = this means unlocked Bootloader, Stock Rom V11.0.3 and recovery installed
[ beginning of loop
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
] end of loop -> my starting point to testing different settings...
go to recovery by holding Vol-Up & Power
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
I found out that the FM Radio fix doesn't work here, if you skip it LOS boots perfectly
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
Click to expand...
Click to collapse
Whats the FM radio GSI zip for?
List of GSIs I've tried on 11.0.3 64 bit
Boots:
Havoc OS (Camera and Screenrecording bug)
Bliss Q (Camera and Weird cutted corners)
Bootleggers (Camera, Weird cutted corners and Brightness cant adjust)
Evolution X (Camera and Brightness cant adjust)
LOS 17 (Camera)
Dont boot:
N/A
Anyone here have a fix for camera, Brightness, Screenrecording and weird cut corners?
regularfanb0y said:
Whats the FM radio GSI zip for?
Click to expand...
Click to collapse
If i boot LOS 17 without the FM radio GSI zip the default FM Radio App which should be preinstalled isn't. flashing the zip fixed that.
regularfanb0y said:
Anyone here have a fix for camera, Brightness, Screenrecording and weird cut corners?
Click to expand...
Click to collapse
All i can say is that i tested Camera, Weird cutted corners and Brightness and Screenrecording on LOS 17 based on 11.0.3 64 bit . Everything works so far
PS: Can you please edit your quote so only the lines you refer to getting repeated? thx
does it work with the feature ： wireless fm radio？
so you can play sky children of light with this or games 64 bit based?
mYXiao said:
I had some troubles getting this running, but finally i made it
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i theoretically had all the files to give it a try.
But i had to flash Stock Rom for many times because i wanted to start from the same starting point so i could find out what step causes the problem
and also to "reset" the boot.img if i had used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status back to "my starting point" = this means unlocked Bootloader, Stock Rom V11.0.3 and recovery installed
[ beginning of loop
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305] end of loop -> my starting point to testing different settings...
go to recovery by holding Vol-Up & Power
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
I found out that the FM Radio fix doesn't work here, if you skip it LOS boots perfectly
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
Click to expand...
Click to collapse
I have two redmi 7a phones, and I tried both. The first one worked the first try, but the second one does not let me install the gapps, I get error code 70 don't have enough space, I tried to resize system but I get an error and if I try again it works but when starting the phone it stuck in the logo (I already installed FM radio gsi). I don't understand why that happens
Jak08 said:
so you can play sky children of light with this or games 64 bit based?
Click to expand...
Click to collapse
I would also wish to know this, will this allow arm64 apps to run? this is a new one to me ? didn't know this was even possible
This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )Support Project TrebleSupport System as root
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_Patch.zip: (at the attachment)Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)most rooms with AB partition will be supportedMagisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
[Update#1]
Today I have managed to install the Android Beta 3.1 [ is beta software and I don't recommend using it as your daily os]
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel4a_SBeta3.1%20-%20TBO42ZZ8IF/Pixel4a_SBeta3.1-AB-12-20210727-nippongsi.img.gz/download
you can download the ROM file from Nippon's Sourceforge
every step is the same and you just have to change the rom as this
there's a bug that developer setting crash the settings app and it is working but it does have some lots of bugs, and screen lock is not working but I'll try to fix it and upload the method
if your device get boot looped, press Bixby + power + vol down to boot into download mode and flash the stock AP file using Odin
[I was supposed to edit the upper one but accidentally created as a reply ]
Just go to UPDATE#2
Skuld Norniern said:
Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)
Click to expand...
Click to collapse
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
thongass000 said:
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
Click to expand...
Click to collapse
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Skuld Norniern said:
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Click to expand...
Click to collapse
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
thongass000 said:
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
Click to expand...
Click to collapse
Sorry for being late!!
for me, I do have the same issue with wired audio and I have not been able to find a way to fix it yet
if I manage to fix the issue I will fix the main article
Skuld Norniern said:
Skuld Norniern said:
This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )Support Project TrebleSupport System as root
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_Patch.zip: (at the attachment)Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)most rooms with AB partition will be supportedMagisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
Click to expand...
Click to collapse
Hello sir i can't find havoc os 4.5 in:https://download.havoc-os.com/?dir=arm64-ab
Click to expand...
Click to collapse
After flashing twrp on my sm g885f, cant get into terp,
mine shows volume down + power to restart, not to enter turn off
how can i enter into twrp
Skuld Norniern said:
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
Click to expand...
Click to collapse
'os.img file' where
, guess i fixed it
when installing Certification_Patch.zip, it shows command error
what i found- this patch is for G885FDXS5CUL1, mine is
G885FDXU5CUG1