Related
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
Code:
- Device platform: arm64-v8a
- Existing zip found
- Copying image to cache
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
maretodoric said:
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
Click to expand...
Click to collapse
I'm also getting same error how did you managed to find the solution...
maretodoric said:
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager.
[...]
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Click to expand...
Click to collapse
Similar problem here, but with Magisk 19.3.
Could you pass a link to patched boot image,you used? Can´t find it...
Thanks
I didn't download boot.img, it's best that you extract it yourself by using ADB.
Download adb software, there should be some tutorial here on forums how to find and get it (possibly https://forum.xda-developers.com/mi-a1/how-to/computer-setup-rooting-gcam-setup-t3731526) , but Windows 10 SHOULD natively have it (at least i did, i didn't have to install anything, already had ADB).
Now here comes the tricky part. I didn't remember this and i didn't write it down. When this happens again to me, i will be in huge .......
I'm sorry i can't help you, but try to google for info on how to extract boot.img from current installation using fastboot or adb.. not sure which, possibly fastboot.
Then you will have clean untouched boot.img from official repo. No need to wait for it to appear on xiaomi site.
If i find a tutorial, i will post it here. Please do the same if you find it before me.
GOT IT!!!
- Follow the previous tutorial if you do not have adb and fastboot, so you can install them. There should be plenty of tutorials how to install both of them
- After you installed it, download this version of TWRP https://dl.twrp.me/tissot/twrp-3.3.0-2-tissot.img.html to your desktop
- Connect your phone to your PC via USB cable
- Open command prompt (in Windows, hit CTRL+R then type in cmd)
- Change directory to desktop, for example type cd C:\Users\<username>\Desktop - replace "<username>" with your username ofcourse.
- Type adb reboot bootloader - it will boot to fastboot mode
- Once the phone is in fastboot mode, type fastboot boot twrp-3.3.0-2-tissot.img (keep cmd prompt open)
- It will boot into recovery, click on "Backup"
- Select "Boot"
- Click on Select Storage and there choose Internal Storage, click on OK
- Then on the bottom part of the screen, just swipe to right to extract boot.img (It should literally say "Swipe to Backup"). Pay attention to messages, it will display the directory where it will place the boot.img, but it will not be strictly named boot.img
- In my case, it's in Internal Storage/TWRP/BACKUPS/00bf23cc0904/2019-06-20-14-25-3_PKQ1/boot.emmc.win
You can either rename it to boot.img or just leave that name. But either way, open new magisk manager, select "Install" next to Magisk (not magisk manager), click on "Select and Patch a file", point to your new boot.img or boot.emmc.win.
Magisk will patch that image and show you the new location. Just download that file to your PC, on desktop, cmd again "adb reboot bootloader", and when it gets to fastboot mode, type "fastboot flash boot magisk_patched.img".
You should be good to go!
Well, a lot of people wanting to root global miui 11.0.7 and not being able to... So I did it on my Global redmi 7a - MIUI 11.0.7 Global.
Simple though. Apart from whats being said, u can update Magisk to v20.+ after flashing
the 19 version, through the app Magisk Manager automatically installed after flashing.
Prerequisites & Downloads:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- ADB and Fastboot -> I did on windows version, maybe can be done on linux...
- patched boot.img for miui 11.0.7 global
- vbmeta.img
- Magisk v19.3 zip -> place it on the root of your external sdcard
This is basically copied from cg730620's post [Guide][Redmi 7A] TWRP, Root with Magisk, Custom ROM [GSI][Pie] and Avedroid's vid
1 - Unlock bootloader and flash stock miui 11.0.7 recovery rom, using miflash 2017
CAREFUL! On the lower right corner check the first option, "clean all", or you may end up with a locked bootloader.
-> exactly the same from the quoted post from now on, what differs is the files and we are only flashing magisk v19.3
"2. Install Minimal ADB and Fastboot
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in Program Files (x86)/Minimal ADB and Fastboot/ folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
Code:
fastboot flash boot boot.img
Code:
Code:
fastboot flash vbmeta vbmeta.img
Code:
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
Reboot to system, open Magisk, update and there u go.
Same steps of the beginning of Avedroid's video, only with modified boot.img and Magisk Version
https://www.youtube.com/watch?v=NSs08O6uGVI&t=324s
After 16:30 of the video he flashes a custom gsi rom which is not of the interest of this thread, just flash magisk.
Thanks to all who made it possible, especially Avedroid and cg730620
Post questions and answers here, please, NOT in PM.
Good luck!
Thank's it's work fine on custom gsi too, i just flash patch boot, vbmeta, finally install magisk success
I did everything right, however, when it came to installing Magisk, the following error occurred: "Updater process ended with ERROR: 1".
So I redid the whole process, but before installing Magisk I did the following: I went to Mount, I deselected the System partition and after that the installation proceeded normally.
Well, I don’t know if this is the best way to fix this problem, I don’t understand much of these things, but it ended up working for me.
Thanks for the post
I will do some tests to see if everything is working.
Can I just do this on MIUI 11.0.5 Global?
Omborkar said:
Can I just do this on MIUI 11.0.5 Global?
Click to expand...
Click to collapse
Download patched boot.img for ur rom instead of 11.0.7 boot.img I uploaded. Or patch it yourself.
I have a problem. Everytime I do the wipe it says only: "Failed to mount "vendor"(invalid argument)"
What to do?
Google play not certified... after flashing and installed magisk... Got solution??? Thanks
I've rooted my MoKee OS Android 10 rom. Can somebody help me change the system font? The font changer module in Magisk is not appearing in the search bar.
vincecabalan said:
I've rooted my MoKee OS Android 10 rom. Can somebody help me change the system font? The font changer module in Magisk is not appearing in the search bar.
Click to expand...
Click to collapse
I Tried To Root Mokee But Failed. Can You Please Tell Me How You Root Mokee
Hello, what files do I need to rename to boot.img and recovery.img? I'm lost
3. Rename the patched boot file to boot.img
4. Rename the custom recovery to recovery.img
RsAbubokor4 said:
I Tried To Root Mokee But Failed. Can You Please Tell Me How You Root Mokee
Click to expand...
Click to collapse
Extract boot.img of installer mokee.zip Patch boot image https://patcher.yaalex.xyz/ select include magisk Expect to do uploud after downloading rename boot.img sdcard Go twrp flash boot install magisk manager apk
Credit to @idcamper
vincecabalan said:
Extract boot.img of installer mokee.zip Patch boot image https://patcher.yaalex.xyz/ select include magisk Expect to do uploud after downloading rename boot.img sdcard Go twrp flash boot install magisk manager apk
Credit to @idcamper
Click to expand...
Click to collapse
I did according to this advice, uploaded boot.img to this site. Magisk works, but Wifi won't work . When I uploaded boot.img, Wifi works, then it shows that Magisk is not installed, but it was installed.
speed_cars said:
I did according to this advice, uploaded boot.img to this site. Magisk works, but Wifi won't work . When I uploaded boot.img, Wifi works, then it shows that Magisk is not installed, but it was installed.
Click to expand...
Click to collapse
try this process after flash zip of the last magisk from reset factory
Can i do this on miui 11.0.3.0 indian rom based on Android 10. If yes then i need recovery.img pls help.
4. Rename custom recovery file to recovery.img
- where i can download this?, or this is the outcome of step 1?
Everything works fine, exept password. When i set new password, let's say it is 1234, i set the password in the setting, then i press the power button for lock screen, i put the password in as usual, but it just says try again over and over, im pretty sure that it is not my fault. Thanks for reply.
Anyone have patched boot 11.0.4?
jurubebaamarga said:
Well, a lot of people wanting to root global miui 11.0.7 and not being able to... So I did it on my Global redmi 7a - MIUI 11.0.7 Global.
Simple though. Apart from whats being said, u can update Magisk to v20.+ after flashing
the 19 version, through the app Magisk Manager automatically installed after flashing.
Prerequisites & Downloads:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- ADB and Fastboot -> I did on windows version, maybe can be done on linux...
- patched boot.img for miui 11.0.7 global
- vbmeta.img
- Magisk v19.3 zip -> place it on the root of your external sdcard
This is basically copied from cg730620's post [Guide][Redmi 7A] TWRP, Root with Magisk, Custom ROM [GSI][Pie] and Avedroid's vid
1 - Unlock bootloader and flash stock miui 11.0.7 recovery rom, using miflash 2017
CAREFUL! On the lower right corner check the first option, "clean all", or you may end up with a locked bootloader.
-> exactly the same from the quoted post from now on, what differs is the files and we are only flashing magisk v19.3
"2. Install Minimal ADB and Fastboot
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in Program Files (x86)/Minimal ADB and Fastboot/ folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
Code:
fastboot flash boot boot.img
Code:
Code:
fastboot flash vbmeta vbmeta.img
Code:
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
Reboot to system, open Magisk, update and there u go.
Same steps of the beginning of Avedroid's video, only with modified boot.img and Magisk Version
After 16:30 of the video he flashes a custom gsi rom which is not of the interest of this thread, just flash magisk.
Thanks to all who made it possible, especially Avedroid and cg730620
Post questions and answers here, please, NOT in PM.
Good luck!
Click to expand...
Click to collapse
I wish to obtain root / access to magisk,
Wanting to know if I can do this without losing data (having to delete system data)
Thank you
Hello.
So I was trying to root my Redmi 7A - v10.2.1 with TWRP 3.3.1 but now I am stuck in a bootloop.
What I did:
1. Flash boot.img
2. Flash recovery.img
3. Flash vbmeta.img
4. reboot
Phone rebooted to system and TWRP was installed.
Then I booted to TWRP to install Magisk-v23.0.zip,
I went to Advanced Wipe, then wiped 'Dalvik / ART cache', 'System', 'Data', 'Cache'.
When I rebooted, it went into a bootloop, when I go to TWRP it says 'No OS INSTALLED".
What did I do wrong? And how to recover?
Thanks.
Cinox said:
I did everything right, however, when it came to installing Magisk, the following error occurred: "Updater process ended with ERROR: 1".
So I redid the whole process, but before installing Magisk I did the following: I went to Mount, I deselected the System partition and after that the installation proceeded normally.
Well, I don’t know if this is the best way to fix this problem, I don’t understand much of these things, but it ended up working for me.
Thanks for the post
I will do some tests to see if everything is working.
Click to expand...
Click to collapse
Im also getting the same error,, but what do you mean by "deselected the System partition". I see "system_root" in Mount but not "System"
WARNING:
You need to backup your data before installing. I am not responsible for any damage or loss that might occur. Proceed at your own risk.
Tested with MIUI version 10.2.5.0 Global.
Bootloader must be unlocked (https://en.miui.com/unlock/)
1. Unpack Minimal ADB and Fastboot to C:\ drive of your PC
2. Rename patched boot to boot.img. Rename recovery file to recovery.img. Place boot.img, recovery.img, vbmeta.img in ADB folder.
3. Enable USB-debugging in developer options on your phone.
4. Connect phone with PC via USB. Reboot phone to fastboot mode (Volume-down + Power).
5. On your PC open command prompt and nagivate to ADB folder.
6. Enter the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot flash vbmeta vbmeta.img
Code:
fastboot flash recovery recovery.img
7. Reboot to recovery (Volume-Up + Power; release Power when phone turns on, keep holding Volume-Up until you see screen of TWRP). If TWRP asks for PIN, enter the PIN of your unlock screen.
8. Wipe Dalvik / ART cache, System, Data, Cache. Format Data > Yes
Do not wipe Internal Storage!
9. Unpack the downloaded GSI Rom and move it to your phone.
10. Flash the Rom (Install image).
11. Reboot to Recovery.
12. Move files Magisk, Permissiver, FM-Radio fix, GApps to your phone.
13. Flash Magisk (optional)
14. Flash Permissiver
15. Flash GApps (optional).
If you get 'insufficient space' error, first resize System partition.
16. Flash FM-Radio fix:
In TWRP, Mount System. Then flash fix.
17. Reboot system and enjoy.
-----------------------
Downloads:
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
GSI Rom:
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
You need to get a64_bvN version from folder lineage-17.x.
Patched boot img file:
http://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
Check your MIUI version in System, so that you download the correct boot img file.
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
vbmeta file
http://www.mediafire.com/file/bgpn9b87b4t8yye/vbmeta.img/file
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Permissiver
https://androidfilehost.com/?fid=6006931924117940902
GApps (choose 'ARM' & '10.0')
https://opengapps.org/
FM Radio fix:
https://androidfilehost.com/?fid=8889791610682885147
After installing Gsi
After installing Gsi, can I get the fast boot mode later
Ts40 said:
After installing Gsi, can I get the fast boot mode later
Click to expand...
Click to collapse
Yes, you can still get into fastboot mode.
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?
Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?
kra_ppo said:
Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?
Click to expand...
Click to collapse
i would recommend you to flash MIUI global first, because if somethings goes wrong you can't say whats the reason for the error.
and the encrypted folders can be deleted in twrp by format data -->yes
raijinlee said:
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?
Click to expand...
Click to collapse
thats the one i'm using and never had problems with this, so yes
Reposting here (from the Magisk forum) on the advice of a Senior Moderator.
I have a Pixel 5 and two days ago now I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version), i.e. from the October version to the November version.
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW (1): I'm still using the canary channel, is this still necessary?
BTW (2): I also posted in the github Magisk issues page and that issue was promptly closed with the comment "format data". Really?!
Help.
Curiouser and curiouser: this works
adb reboot bootloader
fastboot boot redfin-2111_boot_magisk_patched.img
gone_bush said:
Reposting here (from the Magisk forum) on the advice of a Senior Moderator.
I have a Pixel 5 and two days ago now I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version), i.e. from the October version to the November version.
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW (1): I'm still using the canary channel, is this still necessary?
BTW (2): I also posted in the github Magisk issues page and that issue was promptly closed with the comment "format data". Really?!
Help.
Click to expand...
Click to collapse
Sorry, but you are going to have to wipe your phone here. On the next updates you won't have to following these instructions.
Get the vbmeta.img from the factory image (the same place you got the boot.img) and put it into your fastboot folder.
In bootloader/fastboot enter:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Then enter:
fastboot -w (<---this wipes your phone)
Then flash the patched boot image as you normally would and reboot.
In the future for updates, download both the ota.zip and the factory image. Pull the boot.img from the factory image and patch it. Pull the vbmeta.img and put it into your fastboot folder with the patched boot.img. Sideload the OTA and when the flash is done, boot to bootloader using the volume/power buttons on your phone from recovery (you'll be there to sideload the ota.zip) IF YOU BOOT TO /SYSTEM YOU'LL HAVE TO WIPE AGAIN!
Flash the vbmeta.img with fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, then flash the patched boot.img and reboot. You won't have to wipe again as long as you don't boot to /system and don't forget to flash the vbmeta.img with disabling verity and verification.
xunholyx said:
Sorry, but you are going to have to wipe your phone here. On the next updates you won't have to following these instructions.
Get the vbmeta.img from the factory image (the same place you got the boot.img) and put it into your fastboot folder.
In bootloader/fastboot enter:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Then enter:
fastboot -w (<---this wipes your phone)
Then flash the patched boot image as you normally would and reboot.
In the future for updates, download both the ota.zip and the factory image. Pull the boot.img from the factory image and patch it. Pull the vbmeta.img and put it into your fastboot folder with the patched boot.img. Sideload the OTA and when the flash is done, boot to bootloader using the volume/power buttons on your phone from recovery (you'll be there to sideload the ota.zip) IF YOU BOOT TO /SYSTEM YOU'LL HAVE TO WIPE AGAIN!
Flash the vbmeta.img with fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, then flash the patched boot.img and reboot. You won't have to wipe again as long as you don't boot to /system and don't forget to flash the vbmeta.img with disabling verity and verification.
Click to expand...
Click to collapse
Thank you for your reply. Some questions:
1) What's changed that required a wipe? (Let's face it, it's a MAJOR PITA! Thankfully, I do use TitaniumBackup )
2) You state "download both the ota.zip and the factory image" - what's the difference?
3) Re "Pull the vbmeta.img" - in the current instance, is that from the November file (SP1A.211105.004), if not, from where?
4) Do I have this right for future updates?
* Unpack the downloaded file and put the boot.img and vbmeta.img files in a safe place
* Sideload the update by
adb reboot recovery
Apply update from ADB
adb sideload <ota-update.zip>
* Use volume buttons to boot into bootloader (booting into system will mean I'll have to do another wipe!)
* fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
* flash patched boot.img
* boot
5) Re using Magisk to patch the boot.img: can, say, the November boot.img be patched whilst the phone is running the October update?
Yeah, I know, answering my questions is all you've got to do with your life
1: verified boot is needed in Android 12. Patching the boot.img breaks the signature from Google
2: after flashing the factory image in fastboot you're promoted to press any key to continue, which boots the phone to system iirc (I could be mistaken ~ it's been over a year since I flashed a factory image). You can boot to bootloader from recovery after you sideload the OTA.
3: yes. From the update you are applying.
4: I guess.... Place the vbmeta.img in your fastboot folder the same as the patched boot.img (at least that's where I always put the patched boot.img). Put the pulled boot.img wherever you like to transfer it to your phone from to patch. The rest after that part is correct.
5: yes
EDIT: (Sorry I forgot to use the reply button)
xunholyx said:
1: verified boot is needed in Android 12. Patching the boot.img breaks the signature from Google
2: after flashing the factory image in fastboot you're promoted to press any key to continue, which boots the phone to system iirc (I could be mistaken ~ it's been over a year since I flashed a factory image). You can boot to bootloader from recovery after you sideload the OTA.
3: yes. From the update you are applying.
4: I guess.... Place the vbmeta.img in your fastboot folder the same as the patched boot.img (at least that's where I always put the patched boot.img). Put the pulled boot.img wherever you like to transfer it to your phone from to patch. The rest after that part is correct.
5: yes
EDIT: (Sorry I forgot to use the reply button)
Click to expand...
Click to collapse
Thank you for yor replies and time - much appreciated!
First things first. What you need:
Platform tools
MIUI 14 Beta Stable Stock ROM
Android OTA Extractor
Device updated to MIUI 14 Beta
Magisk app installed on the phone
Step 1
Extract MIUI 14 zip on your PC. Move payload.bin to Android OTA extractor folder.
Open terminal in the same folder.
Enter following command:
Android-ota-extractor.exe payload.bin
Let it extract.
Step 2
Root your phone via Magisk app.
Move the boot.img extracted from payload.bin to you phone's internal storage.
Open Magisk app.
Click install, select file and patch.
Once done, move your patched boot image to your PC and put it in platform-tools folder.
Reboot device into bootloader.
Open terminal in platform-tools folder.
Enter the following:
cmd
Press ENTER
fastboot flash boot patched_magisk_(press TAB to autocomplete).img
Let it finish. Reboot. Check if device is rooted.
Step 3
Download a GSI of your choice. I personally tested Pixel Experience Base/Plus and Evolution X by ponces. Extract and put the img file in platform-tools.
Reboot to fastboot.
Enter the following:
fastboot reboot fastboot
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system yourgsiname.img
fastboot -w
If you want root just enter (you might actually need it, check footnotes)
fastboot reboot
If you don't, then flash the stock unpatched boot.img and reboot.
The process is done. Footnotes:
Set up the device offline. Go to phh treble settings. Select Misc.
Install ims package check both:
Request IMS
Force 4G Calling....
Reboot
Now continue setting up and logging in with your google account. SMS verification should work now.
The problems:
Incoming calls will go through on the callers side but won't pop up on your phone. Some say it might be fixed by using the Truecaller app as default phone app but I haven't tested.
Refresh rate is finicky. You need root for this. Do the following:
Download the Dfps magisk module. While you're at it download the Universal SafetyNet bypass module as well. Enable Zygisk in Magisk app and install both modules. Reboot. Should mostly be fixed now.
That's all folks.
rorkeanathema said:
First things first. What you need:
Platform tools
MIUI 14 Beta Stable Stock ROM
Android OTA Extractor
Device updated to MIUI 14 Beta
Magisk app installed on the phone
Step 1
Extract MIUI 14 zip on your PC. Move payload.bin to Android OTA extractor folder.
Open terminal in the same folder.
Enter following command:
Android-ota-extractor.exe payload.bin
Let it extract.
Step 2
Root your phone via Magisk app.
Move the boot.img extracted from payload.bin to you phone's internal storage.
Open Magisk app.
Click install, select file and patch.
Once done, move your patched boot image to your PC and put it in platform-tools folder.
Reboot device into bootloader.
Open terminal in platform-tools folder.
Enter the following:
cmd
Press ENTER
fastboot flash boot patched_magisk_(press TAB to autocomplete).img
Let it finish. Reboot. Check if device is rooted.
Step 3
Download a GSI of your choice. I personally tested Pixel Experience Base/Plus and Evolution X by ponces. Extract and put the img file in platform-tools.
Reboot to fastboot.
Enter the following:
fastboot reboot fastboot
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system yourgsiname.img
fastboot -w
If you want root just enter (you might actually need it, check footnotes)
fastboot reboot
If you don't, then flash the stock unpatched boot.img and reboot.
The process is done. Footnotes:
Set up the device offline. Go to phh treble settings. Select Misc.
Install ims package check both:
Request IMS
Force 4G Calling....
Reboot
Now continue setting up and logging in with your google account. SMS verification should work now.
The problems:
Incoming calls will go through on the callers side but won't pop up on your phone. Some say it might be fixed by using the Truecaller app as default phone app but I haven't tested.
Refresh rate is finicky. You need root for this. Do the following:
Download the Dfps magisk module. While you're at it download the Universal SafetyNet bypass module as well. Enable Zygisk in Magisk app and install both modules. Reboot. Should mostly be fixed now.
That's all folks.
Click to expand...
Click to collapse
I tried to flash the pixel experience hsi on my redmi 11 prime 5g using above method
I have successfully rooted my phone but while giving the command.
fastboot flash system yourgsiname.img
It says no such file found..
I tried for almost 4 to 5 times please help us
To install gsi also it's very sad that we cannot flash any twrp on redmi 11 prime 5g....
coolagori said:
I have successfully rooted my phone but while giving the command.
fastboot flash system yourgsiname.img
It says no such file found..
Click to expand...
Click to collapse
yourgsiname.img is given as example, you should put instead your GSI image filename in the command
Thanks for reminding me sir
I have done the same I have entered the name of rom only but then also it got the problem
Please help light users to get custom roms
And I forgot to tell that I didn't had miui 14 beta but I tried on both miui 14 India and miui 14 china but I failed
coolagori said:
And I forgot to tell that I didn't had miui 14 beta but I tried on both miui 14 India and miui 14 china but I failed
Click to expand...
Click to collapse
I am working on RisingOS (formerly know as RiceDroid) for the phone. It might take a while though.
Thank you so much for your efforts sir..
please tell me if you need any help regarding
testing