Related
Have downloaded magisk APK and zip file but it's not working please help how to deal with this issue .
Anank54 said:
Have downloaded magisk APK and zip file but it's not working please help how to deal with this issue .
Click to expand...
Click to collapse
Common, search.
You need twrp if you want flash something.
Anank54 said:
Have downloaded magisk APK and zip file but it's not working please help how to deal with this issue .
Click to expand...
Click to collapse
Along with TWRP, you're best to get the bootloader unlocked from Xiaomi. I did this with my mi max, Xiaomi approved and I unlocked with their tool. Basically, miui may screw up with OTAs and TWRP in the future, so best to move from miui if you can.
From that point on, you're free to use the tools you wish. I'd recommend nigel's 7.1 unofficial ROM.
So the sequence would be :
1. Unlock bootloader with Xiaomi.
2. Download nigel's / other ROM and modem firmware, Gapps, and Magisk to the SD card.
3. Reboot to fastboot mode
4. Install TWRP with adb recovery command from your computer
5. Restart in bootloader / TWRP mode.
6. Wipe everything but the SD card.
7. Install the ROM, the firmware and gapps
8. Restart into regular system and setup the new ROM
9. Restart in bootloader / TWRP mode
10. Install Magisk
Boom...you now get regular OTA, have Magisk and substratum can be installed as well.
What are the steps to be able to update to Android 10?
Can't seem to find it anywhere. Coming from pie. Thank you.
It was said that Edxposed does not work on android 10. Will eye on this as I need Edxposed badly, currently on Pie.
bush911 said:
It was said that Edxposed does not work on android 10. Will eye on this as I need Edxposed badly, currently on Pie.
Click to expand...
Click to collapse
Edxposed I can remove it. But I know that magisk does work. And that's what I need. Maybe disabling it and updating it will work ?
You can update you Pixel downloading the ota and the factory image from Google repository. Sideload the ota, reboot your phone and wait for the "update optimization" (there is a notification), then you have to patch the boot image (get it from factory) with Magisk Manager. Finally, flash the patched boot image.
In details:
1. Download the full OTA image and the Factory image from Google
2. Keep Magisk and root, copy boot.img from Factory in the Pixel
3. Boot into factory recovery (go in bootloader, choose recovery, keep power and press volume up button).
4. Choose Apply update from ADB
5. From windows: adb sideload fullOTAimage.zip
6. The update will take awhile
7. Reboot and let the update finish in android
8. Load magisk and patch the boot.img, copy patch_boot.img to computer
9. Boot into the bootloader
10. Flash the patched boot image with: fastboot flash boot patch_boot.img
BUT in the Google repository there are 2 version of ota/factory images (.019 e .020). I don't know the difference.
Edit: you need the Magisk Manager canary version, see this post: https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359
Simone_ASR said:
BUT in the Google repository there are 2 version of ota/factory images (.019 e .020). I don't know the difference.
Click to expand...
Click to collapse
According to what I've read .019 is for those who were already on the betas and .020 is for those upgrading from Pie.
Simone_ASR said:
You can update you Pixel downloading the ota and the factory image from Google repository. Sideload the ota, reboot your phone and wait for the "update optimization" (there is a notification), then you have to patch the boot image (get it from factory) with Magisk Manager. Finally, flash the patched boot image.
In details:
1. Download the full OTA image and the Factory image from Google
2. Keep Magisk and root, copy boot.img from Factory in the Pixel
3. Boot into factory recovery (go in bootloader, choose recovery, keep power and press volume up button).
4. Choose Apply update from ADB
5. From windows: adb sideload fullOTAimage.zip
6. The update will take awhile
7. Reboot and let the update finish in android
8. Load magisk and patch the boot.img, copy patch_boot.img to computer
9. Boot into the bootloader
10. Flash the patched boot image with: fastboot flash boot patch_boot.img
BUT in the Google repository there are 2 version of ota/factory images (.019 e .020). I don't know the difference.
Edit: you need the Magisk Manager canary version, see this post: https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359
Click to expand...
Click to collapse
Awesome man, thank you !
i updated from pie and patched the boot.image so now i have root. i was trying to edit the build.prop for hotspot tethering, the old net.tethering.noprovisioning=true but it wont allow me to edit and save the changes to the build.prop, root explorer is not getting read write permissions or something, root explorer does have super user [permission though. can anyone shed some light on this please
This seems kind of dangerous. It would be great to hear some more people's experience.
Has anyone confirmed whether or not Xposed works on Android 10? Riru Core says that it's compatible with Android 10. As long as Riru core works then Xposed should work. But I would like some confirmation so that I can update.
Ariel_PR said:
Has anyone confirmed whether or not Xposed works on Android 10? Riru Core says that it's compatible with Android 10. As long as Riru core works then Xposed should work. But I would like some confirmation so that I can update.
Click to expand...
Click to collapse
I haven't yet. I've been busy with work. As soon as I get a moment I'll do the update and confirm if everything is working right.
GunToYoMouth123 said:
I haven't yet. I've been busy with work. As soon as I get a moment I'll do the update and confirm if everything is working right.
Click to expand...
Click to collapse
Awesome, let us know!
Ariel_PR said:
Awesome, let us know!
Click to expand...
Click to collapse
I finally updated through OTA while on magisk and disabled it to enable it again with a patch. But with steps. I'll upload it soon for people coming from Android 9 (rooted in magisk) and OTA updating to Q and rooting back with magisk. Xposed will come in next.
GunToYoMouth123 said:
I finally updated through OTA while on magisk and disabled it to enable it again with a patch. But with steps. I'll upload it soon for people coming from Android 9 (rooted in magisk) and OTA updating to Q and rooting back with magisk. Xposed will come in next.
Click to expand...
Click to collapse
I'm exactly the same situation as you, currently on Android 9 rooted with Magisk, and receiving 10 OTA notification, but I don't know how to move foward. Looking for your guide, thanks dude!
GunToYoMouth123 said:
I finally updated through OTA while on magisk and disabled it to enable it again with a patch. But with steps. I'll upload it soon for people coming from Android 9 (rooted in magisk) and OTA updating to Q and rooting back with magisk. Xposed will come in next.
Click to expand...
Click to collapse
Thanks for the update!
ngelee said:
I'm exactly the same situation as you, currently on Android 9 rooted with Magisk, and receiving 10 OTA notification, but I don't know how to move foward. Looking for your guide, thanks dude!
Click to expand...
Click to collapse
Sorry it's taking long. I'm gonna post it here now in a few.
Okay, I work at a fulltime job so please bear with me and sorry for my late responses. And acknowledge that I am not responsible for anything that happens to your device. This step-by-step guide was done on an unlocked Google Pixel 3 XL unlocked bought from the Google Play store. I haven't tested it out on other versions of Pixel 3's or any other phone that isn't the Pixel 3 models since I do not own them, so keep that in mind. My situation was to find out how to update my ALREADY ROOTED/MAGISK version of Android 9 PIE through OTA. Upon checking or looking around I couldn't find any tutorials that are easy for me so with all the info I gathered I decided to wing it and compile steps from a lot of sites,risk it all and used my knowledge to put together this guide. In hopes, this helps everyone else! anyways here we go...
First, PLEASE make sure if you have Edxposed or any other modules or anything that is similiar, uninstall it or remove it. (Applications or mods from magisk are fine, I did this while I had a few mods from magisk, like viperfx, youtube vanice etc..)
1. Disable Automatic system updates in developer options, so it won't install OTAs without your acknowledgment.
2. When an OTA is available, first go to Magisk Manager → Uninstall → Restore Images. Do not reboot or you will have Magisk uninstalled. This will restore your boot back to 100% untouched stock images in order to pass pre-OTA block verifications.
3. After restoring the stock boot image, apply the OTA update as you normally would (Settings → System → System Update).
Wait for the installation to be fully done then press the "Restart now"
Wait for the phone to reboot and let it sit for a few minutes. 10-15 minutes give or take.
Don't panic, let it do its thing.
Once you see the "G" with the loading under it, you should be fine.
let it boot up.
4. Now download the factory zip
download 10.0.0 (QP1A.190711.020, Sep 2019)
5. Once downloaded, open the zip using any zip/rar program. (I HIGHLY recommend WinRar) within THAT zip folder extract the image-crosshatch-qp1a.190711.020.zip somewhere on your desktop.
6. Now then open THAT zip file and from it, extract the boot.img file onto your desktop and move it into your Pixel 3 XL's download folder. (I did it this way, so I recommend it)
7. Now uninstall your old magisk manager and install the latest Magisk Manager (app-release.apk)from HERE
8. Open Magisk Manager and Press Install ==> Press Install again ==> Select Patch a File ==> Select the boot.img file you extracted from the latest factory image that you placed in your Pixel 3 XL.
9. Magisk Manager will patch the boot.img and store the patched boot.img in the download folder as "magisk_patched.img"
10. Copy the magisk_patched.img file to your computer's Platform-tools folder(The one you use to adb push files in etc.) or the folder that has fastboot.exe(your ADB folder should have the fastboot.exe in it normally lol ) in it.
11. Connect the phone to the Computer with USB type- c cord.
12. Open your platform-tools folder if you haven't, and on the search bar type in "cmd" and tap enter on your keyboard.
(the cmd promt should open already in your location)
13. Now boot your Pixel 3 XL into fastboot mode by typing the commad: adb reboot bootloader
14. Once your phone is on fastboot mode then type: fastboot flash boot magisk_patched.img
15. Once it's done then type the command : fastboot reboot
16. Google logo should show,but don't panic give it a few.
Open Magisk and check if its rooted on the manager
And congrats ! you have a Magisk root on Android Q ! :highfive:
Please let me know if it worked for you and let me know if you need any help! :fingers-crossed:
ngelee said:
I'm exactly the same situation as you, currently on Android 9 rooted with Magisk, and receiving 10 OTA notification, but I don't know how to move foward. Looking for your guide, thanks dude!
Click to expand...
Click to collapse
Just posted it above ! please let me know if it works!
does Dolby work on pixel 3 xl? can anyone confirm?
I installed the OTA update the other day, but did anyone figure out if Edxposed Is working on Android 10?
This also works on Pixel 2 XL going from Android 9.0 July image with xposed 19.3.
Here's a simpler guide:
1. Go to Magisk Manager → Uninstall → Restore Images
2. Apply the OTA update and reboot
3. Download factory ZIP for 10.0 (In this case for taimen: Pixel 2 XL Android 10.0 Image)
4. From ZIP extract "taimen-qp1a.190711.020/image-taimen-qp1a.190711.020.zip/boot.img" and put it somewhere in the phone
5. Update Magisk with this version: Link
6. Open Magisk Manager and press: Install -> Install -> Patch a File and then select boot.img extracted before
7. Copy magisk_patched.img that Magisk has made to PC
8. Reboot phone to bootloader: adb reboot bootloader
9. Flash patched boot image: fastboot flash boot magisk_patched.img
10. Reboot phone: fastboot reboot
TL;DR:
Disable Magisk, update 10.0 OTA, upgrade Magisk, patch factory boot image with Magisk and flash boot image.
btw: I recommend Easy 7zip: http://www.e7z.org/ for handling the ZIP in a ZIP
Hello, I would need help to root my device, if someone could bring me advice I'm taking, I own remote control software if it tempts someone to help me I'm up for it
Have you unlocked the bootloader and install TWRP first?
The bootloader is unlocked, TWRP is not installed, I had to read the forums to try to install TWRP but my phone is stuck on fastboot impossible to do anything
You can root very easily:
1. start the phone in fastboot mode
2. from a PC type command "fastboot boot twrp.img"
3. once in TWRP, install magisk.zip file (don't forget to follow new instructions for Magisk v22)
4. once Magisk has been installed, reboot to system
5. congrats, your phone is rooted now (without TWRP permanently installed)
hello
after updating to android 11, euxm version, I have problems rooting with magisk 22, I change the apk extension to zip, I install it from twrp, but on reboot it crashes and returns to twrp.
also i no longer see the internal memory folders in android - data
carabot said:
hello
after updating to android 11, euxm version, I have problems rooting with magisk 22, I change the apk extension to zip, I install it from twrp, but on reboot it crashes and returns to twrp.
also i no longer see the internal memory folders in android - data
Click to expand...
Click to collapse
You might have incompatible module installed (for example SafetyNet fix) - disable all modules temporarily, install Magisk and see if the phone starts.
I disabled all the modules before installing the recovery rom, however there is the uninstall of magisk 22.0 and safetynet fix?
carabot said:
I disabled all the modules before installing the recovery rom, however there is the uninstall of magisk 22.0 and safetynet fix?
Click to expand...
Click to collapse
Can you start the phone without Magisk installed?
yes
I solved by disabling modules from orange fox recovery,
how can i do to see the contents of the android folder, that is scoped storage?
carabot said:
yes
I solved by disabling modules from orange fox recovery,
how can i do to see the contents of the android folder, that is scoped storage?
Click to expand...
Click to collapse
You are contradicting yourself a little, you said that you disabled all modules before recovery ROM installation, now that you disabled them from Orange recovery. It might help to describe steps which you did and current status of your phone.
I had disabled them from magisk, but in the twrp they were active, and when I realized it I disabled them from twrp and I solved them.
p. s.
safetynet fix is compatible with android 11 and magisk 22?
i wouldn't ruin it again
carabot said:
I had disabled them from magisk, but in the twrp they were active, and when I realized it I disabled them from twrp and I solved them.
p. s.
safetynet fix is compatible with android 11 and magisk 22?
i wouldn't ruin it again
Click to expand...
Click to collapse
Yeah just hide magisk from all google apps and it will work fine, mine passes
Jooan92 said:
Hello, I would need help to root my device, if someone could bring me advice I'm taking, I own remote control software if it tempts someone to help me I'm up for it
Click to expand...
Click to collapse
Unlock bootloader
Flash a recovery (fastboot flash recovery nameofrecovery.img)
Reboot into recovery (fastboot reboot and hold power and volume up)
Load magisk zip on an EXTERNAL SD find it and flash
Boom
for scoped storage is there a solution?
carabot said:
I had disabled them from magisk, but in the twrp they were active, and when I realized it I disabled them from twrp and I solved them.
p. s.
safetynet fix is compatible with android 11 and magisk 22?
i wouldn't ruin it again
Click to expand...
Click to collapse
You need to reinstall safetynet fix after Android upgrade, installation script uses different files for different Android versions.
What issue exactly do you have with storage?
after the update open file manager and if I click on android - date I no longer see the folders
i tried to install safetynetfix from twrp but it gives me error
carabot said:
i tried to install safetynetfix from twrp but it gives me error
Click to expand...
Click to collapse
Install from magisk under the modules section, then install from storage
gave me mistake because i had wrong files
Just for notification. If safety net is important with you. Install latest stable xiaomi.eu rom v12.0.11.0. Safety net is passed and implement in rom. I 've installed it...Developers continue playing cat and mouse with Google
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
I just flashed Lineage, rebooted, set up the phone, rebooted into recovery and then flashed Magisk.apk after renaming it to Magisk.zip. After a reboot I opened the Magisk app (which was automatically installed when flashing Magisk) for the first time and it prompted me to do some additional operations. It survived an OTA update so it should keep working in the future.
The firts mentioned method does not seem to work with the new Magisk 24.1
Does anyone have a solution to this?
(Never mind ..you need to uninstall the earlier version,then it will work)
sburry said:
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
Click to expand...
Click to collapse
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
ldm21 said:
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
Click to expand...
Click to collapse
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Rstment ^m^ said:
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Click to expand...
Click to collapse
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
ldm21 said:
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
Click to expand...
Click to collapse
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
I think this is the equivalent of flashing the apk as zip in custom recovery, which is deprecated.
I compared the official one with the first post and I think the following is missing in the first post:
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
From:
Installation
The Magic Mask for Android
topjohnwu.github.io
Poco has a vbmeta but i never executed this step. The instructions say that it is optional but they don't specify it.
I used the first post since LOS18.1 and no problems. Since LOS19.1 updates give me bootloops so after some repair tries (and failed twrp restore) I did a fresh install and did not take the updates anymore. No idea if it has something to do with magisk or patching vbmeta. Soon gonna try to update LOS with magisk disabled.
Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
Does this still apply to LOS20 and Magisk 25.2? After doing this, do I still need to extract the patched image?
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
[deleted]
johnr64 said:
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
Click to expand...
Click to collapse
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
dangerousnerdrays said:
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
Click to expand...
Click to collapse
lol... flashing patched image is all you need to do
Either via adb sideloading magisk.apk or manually flashing image both will suffice.
Just look at magisk app, if it doesn't say not installed then it is working
Hi, guys. The patched imaged failed, and the detail is as follows. I am really confused and any comments are welcomed.
device: Redmi K40
Magisk version: v22.0, v22.1, v23.0 report the same behavior
MIUI: xiaomi.eu_multi_HMK40_POCOF3_21.12.8_v12-12-fastboot
Here's what I have done (following the docs)
1. unlock bootloader, turn usb debug on.
2. flush the brand-new MIUI rom as above.
3. installmagisk version xfrom the official github apk, where x represents v22.0, v22.1 or v23.0, withinstalled: N/A, A/B: yes, Ramdisk: Yes, SAR: yes
4. copy theboot.imgto the phone and patch it in magisk. The los is available here.
5. use.\platform-tools-windows\fastboot.exe flash boot patched_img.imgand.\platform-tools-windows\fastboot.exe flash vbmeta --disable-verity --disable-verification .\images\vbmeta.img, then reboot.
6. when I enter the magisk app again, it is the same as before, i.e.,installed: n/awithinstallbutton still showingselect and patch a file, nothing changed.
I wonder if anyone met the same problem when installing magisk on redmi K40, or could you give some suggestions on how to install it? I tried many available tutorials but all ended with the above problem.
i believe you need twrp or other custom recovery installed to install magisk. you haven't mentioned twrp at all so i'm assuming you don't have it? i mean, yes, you can patch the boot.img but i think you still need twrp installed - someone will correct if i'm wrong.
boot your device into fastboot mode, plug in to pc and open adb fastboot cmd box, type 'fastboot devices' and hit enter. if a serial key shows up, you're connected.
Download lastest official twrp from here (alioth is the name or our device).
Download lastest magisk manager from here and rename the .apk file extension to .zip, for example: Magisk-v24.1.apk → Magisk-v24.1.zip
1. the simplest way is to boot to twrp using cmd 'fastboot boot twrp.img' [or whatever your twrp.img is named to] with the twrp.img in adb fastboot folder (usually on C drive root)
2. install twrp 'Preferred Installation Method: Once booted, navigate to the Advanced > Flash Current TWRP option. This will install the TWRP image you just booted permanently to the device.'
3. flash magisk zip in twrp and DESELECT 'Inject twrp after install' if you have that option (sorry to be vague but i haven't updated in a while and it may now be different.
4. boot to system, you'll find a link in apps for magisk app to finish installing magisk manager.
Hope this makes sense, it's 4.50am and i'm about to go bed!! sorry if it's not correct at all...
may be you can use "fastboot reboot fastboot" at first
flash your magisk.apk as zip in recovery (rename it to .zip and flash using recovery)
Hi, guys. @SamantaSync, @eee625, @reg66, thanks for the reply!
I followed your suggestions to use TWRP to install magisk, but I met another problem. Here is what I have done.
1. I boot from TWRP: fastboot boot twrp.img.
2. After entering into TWRP, I found that the "internal storage 0mb", thus I found another method to make it readable. In short, I first change the "data" partition to "ext2" format and then change back to "ext4". This makes the internal storage readblae (around 200gb).
3. After this step, I tried to make TWRP permanent, thus I use "advance" section's "flush current TWRP".
4. Finally, I reboot the device. But found that my device keep reboot into the recovery.
Though I could still boot externally from TWRP, in normal mode, it just boot into the main recovery forever. Is my device becoming brick in this case?
You probably had a kind of encryption (fingerprint + PIN/or Password). Removing those would allow memory to be read.
Also, Twrp has to be kkk's. Not Vasi, Not any other. Kkk's TWRP supports a12 but still doesn't decrypt, and that's why we remove lock.
You should've asked dude before doing anything that might lead to making a brand know flash again.
I think now you should flash from scratch and go one by one. TWRP will root your rom just fine.
AreuMiFan said:
Hi, guys. @SamantaSync, @eee625, @reg66, thanks for the reply!
I followed your suggestions to use TWRP to install magisk, but I met another problem. Here is what I have done.
1. I boot from TWRP: fastboot boot twrp.img.
2. After entering into TWRP, I found that the "internal storage 0mb", thus I found another method to make it readable. In short, I first change the "data" partition to "ext2" format and then change back to "ext4". This makes the internal storage readblae (around 200gb).
3. After this step, I tried to make TWRP permanent, thus I use "advance" section's "flush current TWRP".
4. Finally, I reboot the device. But found that my device keep reboot into the recovery.
Though I could still boot externally from TWRP, in normal mode, it just boot into the main recovery forever. Is my device becoming brick in this case?
Click to expand...
Click to collapse
To solve this,just format you data and reflash boot.img
Hi, @laid1995 ,@eee625, thanks for the reply. Following your guide, I made it.
I succesffully flashed magisk in, and I found the problem is that I am using android 12, and I need magisk >= v24.0.
btw, I found two weird problems and want to share with you guys. In magisk>=24, we need safetynet-fix module to pass the safetynet-check. I finished this following the official guide (1. enable Zygisk 2.enforce denylist, where the denylist contains google-play Store & google-play service 3.install safetynet-fix module). I validate this in the YASNAC app, which shows that I passed all the checks.
Howvever, I found that
1. Everytime I added Google-play service to denylist, after reboot, it escapes from the denylist. But the google-play Store will not escape.
2. I could not install google-native apps in Google-play, like Chrome, but I can still install other non-native apps.
I wonder if you guys have ever met this problem?
AreuMiFan said:
Hi, @laid1995 ,@eee625, thanks for the reply. Following your guide, I made it.
I succesffully flashed magisk in, and I found the problem is that I am using android 12, and I need magisk >= v24.0.
btw, I found two weird problems and want to share with you guys. In magisk>=24, we need safetynet-fix module to pass the safetynet-check. I finished this following the official guide (1. enable Zygisk 2.enforce denylist, where the denylist contains google-play Store & google-play service 3.install safetynet-fix module). I validate this in the YASNAC app, which shows that I passed all the checks.
Howvever, I found that
1. Everytime I added Google-play service to denylist, after reboot, it escapes from the denylist. But the google-play Store will not escape.
2. I could not install google-native apps in Google-play, like Chrome, but I can still install other non-native apps.
I wonder if you guys have ever met this problem?
Click to expand...
Click to collapse
I havent met this yet
eee625 said:
I havent met this yet
Click to expand...
Click to collapse
Hi reuMiFan.
Neither did I :/ since I don't really need for safetynet to pass. I hope you find a solution bud. You just need to dig a little more about it. I'm sure you'll work it out.