How Can I Flash the December security update in my magisk rooted device? If I tray the "normal" way it gives me an error.
Hi. I had the same problem. Tried with restoring stock rom without wipe, but no go. Still error.
I ended up backing up my stuff and flashed stock with wipe, and then everything went well.
After your procedure what boot.img you use to reinstall magisk?
Usually when the bootloader is unlock is impossible to install any official update.
In that case I have the same problem, and I think the solution is to lock the bootloader, try to apply the update and to see if root still works. ( I am sure not).
In other case is, unlock the bootloader again, to wait the official ROM with December patch, extract boot.img, rebuild it with magisk and install it with fastboot and wait the final result.
Is crazy but while there is not another solution is a good way to have root on this Moto One.
skia16 said:
After your procedure what boot.img you use to reinstall magisk?
Click to expand...
Click to collapse
I booted up twrp and made a backup of boot.img, then patched it and flashed with fastboot.
tys0n said:
I booted up twrp and made a backup of boot.img, then patched it and flashed with fastboot.
Click to expand...
Click to collapse
I follow this way but magisk manager tells me that magisk Is not installed
skia16 said:
I follow this way but magisk manager tells me that magisk Is not installed
Click to expand...
Click to collapse
skia16 said:
I follow this way but magisk manager tells me that magisk Is not installed
Click to expand...
Click to collapse
Make a backup of boot in twrp.
Go to backup folder and make a copy of it somewhere. Rename the copy from "boot.emmc.win" to "boot.img".
Open Magisk manager, select install, choose "patch boot image file" and select the boot.img-file to patch.
It will unpack, patch and repack the boot.img for magisk functionality.
Move the patched_boot.img to pc and flash it with fastboot. "fastboot flash boot patched_boot.img".
Reboot, open Magisk manager. It should now ask to continue with environmental setup.
Or if you have the firmware package, you could just extract boot.img from it, put it on phone and patch it instead of using boot from twrp back up.
Related
I want to root my poco f1 ....
But i have some questions regarding it
1. Will my data be format while rooting and installing twrp
2. How i will get ota update
3. Will installing ota update also format my data?
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
roxor101 said:
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
Click to expand...
Click to collapse
Does the twrp with working decryption also need to format my data?
You can root your device in two ways.
First, with twrp (OTA won't work afterwards)
Second, without twrp (OTA will work)
First method, unlock the bootloader (device will be wiped)>Grab the twrp with working decryption>Boot your device into fastboot and type fastboot flash recovery twrp.img (or whatever the recovery image name is)>Now type fastboot boot twrp.img (or whatever the recovery image name is)>Once booted into twrp, swipe to allow modification>Now download Magisk installer and copy into the device>Flash it?Reboot to system>Profit.
N.B. After flashing twrp, make sure to first boot into twrp before booting into system or else device will restore stock recovery. If you need to update in future, just grab the twrp flashable update package and flash it. That's it. No need for OTA.
Second method, this will also require an unlocked bootloader. Once the bootloader is unlocked, get the stock boot image of your current software (e.g. if you are on miui 10 with October security patch, make sure to grab the stock boot image for miui 10 october). Now install Magisk manager apk in your device. Now open magisk manager and go to install. You will find an option for patching stock boot image. Click on it and select the stock boot image. Magisk will patch the boot image and will place it in your internal memory. Now boot into fastboot mode and type fastboot boot patched_boot.img (or whatever the name is). Once device is booted into system, go to Magisk and click on Install>Direct install (recommended).Magisk will get flashed by itself and reboot. Once rebooted, go to Magisk manager and check. If you do everything correctly, you are rooted.
N.B. When you get an OTA update, open Magisk and go to Unsinatll and click on "Complete uninstall". It will uninstall magisk and revert your stock boot image back. Note that, if you play witgh system partition like modifying build.prop or change host file or bootanimantion or any such thing, you won't be able to get any further OTA update. In that case, you need to flash the complete fastboot rom through MiFlash tool.
For more information, please go to Magisk thread or search online.
Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
fajniejest said:
Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
Click to expand...
Click to collapse
You have an old version of TWRP... You need to install a newer version - 3.2.3.2 - which you will find by doing a search for it here on XDA...
Just load img file on INTERNAL storage of phone, choose install>install image file> and click on recovery partition. After install go to home menu and restart recovery...
If you still have issues then download magisk again, it may be corrupt...
Cheers....
ultramag69 said:
You have an old version of TWRP... You need to install a newer version - 3.2.3.2 - which you will find by doing a search for it here on XDA...
Just load img file on INTERNAL storage of phone, choose install>install image file> and click on recovery partition. After install go to home menu and restart recovery...
If you still have issues then download magisk again, it may be corrupt...
Cheers....
Click to expand...
Click to collapse
First of all, I'm not going to install TWRP - I want only to boot into TWRP once for flashing Magisk's ZIP.
Second - in this guide OP says that Unofficial TWRP should be used. I've tried v1 and v2 TWRP from the guide. So which other TWRP should I try to boot into? This? https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-x-t3836241
fajniejest said:
First of all, I'm not going to install TWRP - I want only to boot into TWRP once for flashing Magisk's ZIP.
Second - in this guide OP says that Unofficial TWRP should be used. I've tried v1 and v2 TWRP from the guide. So which other TWRP should I try to boot into? This? https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-x-t3836241
Click to expand...
Click to collapse
I am new on this forum (pocophone) and i seee how messed up it is. You should definitly use official twrp
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
fajniejest said:
Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
Click to expand...
Click to collapse
what are you trying to flash? If it is Magisk Manager, it is in apk format and you just click it to install. No TWRP.
If it is Magisk, which version are you trying to flash? Try 18.1. And preferably download any file from its source.
EDIT: If Magisk v18.1 is also not flashing, try Magisk Canary version. Some phones need that.
tnsmani said:
what are you trying to flash? If it is Magisk Manager, it is in apk format and you just click it to install. No TWRP.
If it is Magisk, which version are you trying to flash? Try 18.1. And preferably download any file from its source.
EDIT: If Magisk v18.1 is also not flashing, try Magisk Canary version. Some phones need that.
Click to expand...
Click to collapse
I'm trying to flash zip with Magisk Manager, as it is said in guide. I know that I can have an apk, but is it enough to just install apk without having custom recovery (but having bootloader unlocked)?
GrecoNeoV said:
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
Click to expand...
Click to collapse
I will try it if nothing from "my" guide will work, because I really don't want to lose my storage (I see that in this guide installing Magisk needs it)
fajniejest said:
I'm trying to flash zip with Magisk Manager, as it is said in guide. I know that I can have an apk, but is it enough to just install apk without having custom recovery (but having bootloader unlocked)?
I will try it if nothing from "my" guide will work, because I really don't want to lose my storage (I see that in this guide installing Magisk needs it)
Click to expand...
Click to collapse
Well Here is how i managed it to work. After i unlocked my bootloader i launched twrp and flashed beta magisk 19.0 (not latest anymore because 19.1 just today showed up) then i reminded that i forgot about DisableForceEncryption_Treble_v18.0.zip so i flashed iit and after it flashed again magisk 19.0, after reboot it everything was fine
GrecoNeoV said:
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
Click to expand...
Click to collapse
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'fastboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
guhvanoh said:
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'flashboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
Click to expand...
Click to collapse
The command is 'fastboot boot twrp-<version>.img'
tnsmani said:
The command is 'fastboot boot twrp-<version>.img'
Click to expand...
Click to collapse
Thanks for the correction. I really don't know where I got flashboot from.
Cheers!
guhvanoh said:
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'fastboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
Click to expand...
Click to collapse
So, to make it clear (and to not brick my poco... ):
1. I should use TWRP image from this link --> https://twrp.me/xiaomi/xiaomipocophonef1.html...
2. ...and I don't need to replace my recovery - just booting it once (as You described) is enough.
3. I should flash Magisk's ZIP, not MagiskManager's ZIP or Magisk.apk
4. No more flashing, clearing data and other operations needed.
Am I right?
1 - Yes.
2 - That's down to you. I have TWRP recovery installed and I have the app as well.
3 - You need to flash Magisk and install the apk. See this link for instructions on installing Magisk.
4 - Yes, you need to clear data, wipe dalvik and cache when installing a new ROM. If updating a current rom, I just wipe dalvik & cache.
HTH
Hey I know its not a thread related but if u install magisk can u tell me if you have 60fps screen recoding option? Because I already Dirty flashed rom once and nothing changed still cant unlock it :/
guhvanoh said:
1 - Yes.
2 - That's down to you. I have TWRP recovery installed and I have the app as well.
3 - You need to flash Magisk and install the apk. See this link for instructions on installing Magisk.
4 - Yes, you need to clear data, wipe dalvik and cache when installing a new ROM. If updating a current rom, I just wipe dalvik & cache.
HTH
Click to expand...
Click to collapse
Big thanks! Finally dealt with it. So grateful for Your help. :victory:
Dearminder said:
Hey I know its not a thread related but if u install magisk can u tell me if you have 60fps screen recoding option? Because I already Dirty flashed rom once and nothing changed still cant unlock it :/
Click to expand...
Click to collapse
Yes, I do. I've not tried it though...
Hi, I'm having trouble with Magisk re-installation.
First I installed Magisk using the flashing boot.img method, it was working correctly but I tried to remove the youtube vanced module, when it asked for a reboot it went straight to the bootloader, I just re-flashed the original boot.img to the phone and got it working again. the issue came when I tried to reinstall Magisk from scratch again. Whenever I tried to install it the process would go without any issue but when I tried to start the system it is going to the bootloader again.
I tried installing twrp using this guide and got the custom recovery working on both slots, then I tried to flash magisk using the zip file, the installer ran without throwing any issues but when I tried to reboot again to the system it still goes to fastboot, this time not only corrupting the system start but also the twrp recovery. I haded to reflash the stock boot.img image on slot A and the twrp image on slot B to re install twrp on both slots.
Also using the TWRP tried running the uninstall magisk zip but whenever I try to run it it just fails because it cannot find the magisk.img file and exits by telling that I have not installed magisk.
Tried erasing the folders inside of /data/adb but its the same issue all over again.
Does anyone has any idea or suggestion on what could I try to fix the issue?
Thanks
Try flashing patched boot image (the same version as your system) and boot into the system, go into magisk manager and do complete uninstall. Or download the latest Magisk uninstaller and try from TWRP again. Recent versions of Magisk ditched magisk.img, so you might be using old version of the uninstaller.
_mysiak_ said:
Try flashing patched boot image (the same version as your system) and boot into the system, go into magisk manager and do complete uninstall. Or download the latest Magisk uninstaller and try from TWRP again. Recent versions of Magisk ditched magisk.img, so you might be using old version of the uninstaller.
Click to expand...
Click to collapse
Tried using the lastest uninstaller found on the topjohnwu/Magisk repository, which did not show any error but after installing magisk the phone still goes to bootloader, then tried to run the uninstaller again but it only works on the b slot and to run it on the a slot I have to reflash boot.img and then install twrp on both slots.
But thanks for the sugestion.
jtcp2703 said:
Tried using the lastest uninstaller found on the topjohnwu/Magisk repository, which did not show any error but after installing magisk the phone still goes to bootloader, then tried to run the uninstaller again but it only works on the b slot and to run it on the a slot I have to reflash boot.img and then install twrp on both slots.
But thanks for the sugestion.
Click to expand...
Click to collapse
I would restore stock ROM, skip TWRP installation and flash just correct patched boot image.
_mysiak_ said:
I would restore stock ROM, skip TWRP installation and flash just correct patched boot image.
Click to expand...
Click to collapse
Do you know where can I find the lastest stock rom? Right now I'm on 10.3.9.0 PFQEUXM, or if the lastest is not possible, could I flash a older version of the rom without any trouble?
jtcp2703 said:
Do you know where can I find the lastest stock rom? Right now I'm on 10.3.9.0 PFQEUXM, or if the lastest is not possible, could I flash a older version of the rom without any trouble?
Click to expand...
Click to collapse
Try to find the full OTA zip for the latest version (or at least the same you have) and extract it with this tool https://github.com/cyxx/extract_android_ota_payload
Xiaomi hasn't released the fastboot rom for the recent updates yet.
So far I was able to find only global links here (they should work too, but rather backup your data first). http://4pda.ru/forum/index.php?showtopic=962154
You might have luck installing older fastboot EU ROM, but again, backup your data first.
If you did not enable "allow system modifications" in TWRP, it should be enough to flash only stock boot image (there are links to them somewhere on this forum).
Also I would avoid installing TWRP.
Sapper Morton said:
The complete firmware images, can only be found in .tgz archives, payload.bin OTAs only contains incremental firmware updates; thus you won't be able to successfully restore, system, vendor, boot, critical partitions and etc; the recommended method is to restore to either 10.3.4.0 PFQMIXM or 10.3.7.0 PFQEUXM, both .tgz archives, complete firmware inside. @_mysiak_
Click to expand...
Click to collapse
There are usually two types of OTA zip files, small incremental ones (which you described) - for monthly updates and full OTA (1-2gb in size) - for direct update across several versions. You can create all needed fastboot images from the full OTA payload.bin with before mentioned python extractor script.
Sapper Morton said:
You can try for yourself, I wasn't able to restore using this images (assuming of course you have a corrupt, system, vendor, boot, ... partition): https://bigota.d.miui.com/V10.3.6.0...UTGlobal_V10.3.6.0.PFQMIXM_00713c5a1d_9.0.zip
I was only able to return to global channel, by using 10.3.4.0 PFQMIXM firmware, .tgz archive.
Click to expand...
Click to collapse
By wasn't able to restore you mean that you couldn't convert payload.bin to fastboot images, or that converted fastboot images were not working?
I've just extracted these files from payload.bin from the link you provided (with this app). I don't have a phone to test them though (I did the same thing a few times on Mi A1 and flashing, phone and OTA worked afterwards).
Code:
abl.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
hyp.img
imagefv.img
keymaster.img
modem.img
product.img
qupfw.img
rpm.img
storsec.img
system.img
tz.img
uefisecapp.img
vbmeta.img
vendor.img
xbl.img
xbl_config.img
Hi there,
i'm rooted and i installed the latest OTA (oxygen os 10.3.7.hd01AA - india rom maybe because i used a patched boot.img in the first time months ago) right now and just like all the times before i made the usual steps:
1) Restored Original Image via Magisk Manager
2) Downloaded and installed OTA
3) Didn't reboot and tried to Install Magisk to inactive slot
Unfortunately 3 didn't work. More than that - Magisk Manager doesn't even recognized Magisk was uninstalled. So there is no Installation option.
Tried to Uninstall it again (Restore Original Image) but that didn't change anything.
a) Was the 2nd "Restore Original Image" after installing the OTA a bad idea?
b) How can i install Magisk now?
I don't reboot the phone as i think it could be bricked after that.
Dacoco said:
Hi there,
i'm rooted and i installed the latest OTA (oxygen os 10.3.7.hd01AA - india rom maybe because i used a patched boot.img in the first time months ago) right now and just like all the times before i made the usual steps:
1) Restored Original Image via Magisk Manager
2) Downloaded and installed OTA
3) Didn't reboot and tried to Install Magisk to inactive slot
Unfortunately 3 didn't work. More than that - Magisk Manager doesn't even recognized Magisk was uninstalled. So there is no Installation option.
Tried to Uninstall it again (Restore Original Image) but that didn't change anything.
a) Was the 2nd "Restore Original Image" after installing the OTA a bad idea?
b) How can i install Magisk now?
I don't reboot the phone as i think it could be bricked after that.
Click to expand...
Click to collapse
Well the procedure is disable all magisk modules. Reboot. Take the update don't reboot when the updater says to. Go to magisk select patch to inactive slot let it do it's thing then reboot
for now make a new patched one based on your current is to obtain root like you did initially
Ex pull your current non root boot img patch it in magisk then flash in fastboot
If you need I can grab the India ROM from Updater and make you a patched boot image?
I've already done it for HD01AA EU and HD01BA
Hey, i could manage to install Magisk into inactive slot after updating Magisk manager to the latest version. I would try to reboot now?
If I would like to patch my current boot.img - how can I do so?
digidude512 said:
If you need I can grab the India ROM from Updater and make you a patched boot image?
I've already done it for HD01AA EU and HD01BA
Click to expand...
Click to collapse
Thanks. I think I'll try to reboot and then - if it doesn't Boot - I will come back to you.
Dacoco said:
Thanks. I think I'll try to reboot and then - if it doesn't Boot - I will come back to you.
Click to expand...
Click to collapse
Any luck?
digidude512 said:
Any luck?
Click to expand...
Click to collapse
Booted up and root is working! Thanks a ton!
Dacoco said:
Booted up and root is working! Thanks a ton!
Click to expand...
Click to collapse
Well the ROM is already downloading, Might as well do the boot and recovery images anyway lol
When I'm done I'll update this thread to include HD01AA India
https://forum.xda-developers.com/7t-pro/how-to/oos-10-0-13-hd01aa-t4195159
I'm looking for help getting Magisk installed on MIUI 12.1.1. If I use the boot.img and pass it to Magisk manager and flash it, the system just reboots to recovery after a few minutes.
Does anyone have it working or a recovery that works with 12.1.1 global?
moffa~ said:
I'm looking for help getting Magisk installed on MIUI 12.1.1. If I use the boot.img and pass it to Magisk manager and flash it, the system just reboots to recovery after a few minutes.
Does anyone have it working or a recovery that works with 12.1.1 global?
Click to expand...
Click to collapse
By "passing it to magisk", do you mean patching the boot.img and getting a magisk_patched.img? Do you have the latest magisk app? It's no longer called magisk manager (v22).
Edit: You probably just hot the patched boot from the wrong boot.img
Tulsadiver said:
By "passing it to magisk", do you mean patching the boot.img and getting a magisk_patched.img? Do you have the latest magisk app? It's no longer called magisk manager (v22).
Edit: You probably just hot the patched boot from the wrong boot.img
Click to expand...
Click to collapse
Hi, thanks for responding.
Yes, I mean I take the boot.img from the MIUI fastboot package and select it in Magisk (no longer manager). I then reboot to bootloader mode, then run "fastboot flash boot magisk_patched_sLsab.img " but after running fastboot reboot it just ends up in recovery mode.
The only way to recover is to use fastboot to flash the original boot.img back over
I finally figured out that I had magisk modules left over before the upgrade which broke everything. A factory reset wiping all data has fixed it.