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.
Related
Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
MAGISK modules are HERE
Magisk MANAGER is available on PLAYSTORE
BEFORE making a twrp backup... (after data format ect.)...
you may want to FIX the huawei theme manager not working problem for some of us... the FIX is HERE
Thanks to Henkate
Youll need a good file system manager...i'm using ROOT EXPLORER and theres that new FX file explorer
does it work with android 7?
tanlikar1 said:
does it work with android 7?
Click to expand...
Click to collapse
Yes. In fact, this was meant for Android 7, but it should work on Android 6 too.
Absolutely...Im on Nougat emui5
does anyone have stock rom for MLA-L12C636B340 ?
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
virusdunil said:
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
Click to expand...
Click to collapse
ya
Working on Nova?
Does it work in the non plus Nova as well? Any experiences?
Worked on Can-L11. Tested. No need format data, in twrp tree, i add img, that work with encrypted data.
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Cooks_08 said:
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Click to expand...
Click to collapse
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
virusdunil said:
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
Click to expand...
Click to collapse
Got the flash working. Used Garak's Twrp and now i got. Thanks.
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Mezo21 said:
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Click to expand...
Click to collapse
Hi there,
I have Nova 2s, carefully follow this thread's instructions, it will 100% works : https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
Thanks for the guidance, Magisk is doing very well.
Only TWRP is missing, but later.
Huawei Nova
CAN-L01C432B382
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
meskafonas said:
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
Click to expand...
Click to collapse
did you format data as f2fs? If yes, magisk doesn't go well along with it. If no, then you would get better support at magisk thread
virusdunil said:
Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
Click to expand...
Click to collapse
Do you have this problem with fingerprint? [emoji853] https://r.tapatalk.com/shareLink?ur...share_tid=3907398&share_fid=3793&share_type=t
Enviado desde mi HUAWEI CAN-L11 mediante Tapatalk
I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me
IO13 said:
I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me
Click to expand...
Click to collapse
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
marstonpear said:
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
I assure you that if I would have preferred to find the information myself rather than wait for some kind user to answer me. Unfortunately it is not so simple, there are many double posts with information missing (you imagine a new user who wants to try to install the GCam, there are several posts on the subject with redundant or sometimes opposite information, there are two posts on how to install Magisk without losing the OTA, they are almost identical but in one there is written that with Pie no longer works, in the other no ..). Look for an info here with the search function is anything but simple so thank you for answering me so exhaustively!
marstonpear said:
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)
bla.tiga said:
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)
Click to expand...
Click to collapse
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:
marstonpear said:
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:
Click to expand...
Click to collapse
Oh i see.. thanks for the explanation... Gathering information in xda is bit confusing lol
Okay one more thing to be clear, right now im on oreo august security patch V 9.6.6.0 ODLMIFF
I want to install twrp and flash magisk (do i need downgrade to 9.6.4.0?) , if i succeed install both of that, and i want upgrade rom to pie or upper version via fastbot flash, i need to remove twrp and magisk, or just directly flash with mi flash??
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
Here's a quick guide for rooting your Fairphone 4.
DISCLAIMER
I'm not the author of this method, merely sharing the informations that can be found on fairphone community forums.
All credit goes to hirnsushi from fairphone community forum.
I will not be held responsible for any damage caused by this operation, flashing your device always implies a risk of manufacturing your very own plastic brick.
PREREQUISITES
- Unlocked bootloader
- Computer with adb & fastboot
- Magisk app installed on your device
- FP4's official stock boot.img
HOW TO ROOT
1. Copy the boot.img file on your device's internal memory
2. Patch the boot.img file using Magisk -> Installation -> Patch a file
3. Transfer the patched boot.img back to your computer
4. Reboot to fastboot: Power + vol up from off device OR adb reboot bootloader
5. Boot from the patched img by running: fastboot boot patched_boot.img where patched_boot.img is actually replaced with the path and name of your patched file
DO NOT FLASH THE PATCHED IMG. BOOT ONLY.
6. Your device will take much much more time to boot than usual, be patient.
7. Once booted, open Magisk, run a direct Install and reboot.
You are now rooted.
This will break your ability to use Google Pay. Though a workaround is described below.
[OPTIONAL]- PASS SAFETYNET AND GPAY CERTIFICATION
1. Download and enable the following Magisk mod:
- Riru module
- Riru’s universal SafetyNet’s fix 2.1.2
- SQLLite for ARM aarch64 devices
- GPay SQLLite Fix 2.5
2. Enable Magisk hide and hide Magisk from the following packages:
- Google Play Store
- Google Pay
- Google Play Services
3. Now the part that is very important to follow otherwise it will not work :
- Put your phone in Airplane mode
- Clear all data from:
Google Play
Google Pay
Google Play Service: remember, clear ALL data, not just cache, even for this one
- Reboot
- Toggle Airplane mode off
You should now have a rooted device that can be used to pay for groceries. How cool is that.
If Pay app states device is not certified, there is high chances you did not follow exactly the described steps.
I really like a rooted phone as always. I will wait till there is a way to reinstall the standard ROM. Then it will be safe for me to try.
I'm on the latest update and not able to unlock the bootloader. I enabled OEM unlocking in developer options and rebooted to bootloader. On the first screen it says "Device status: Locked" and doesn't react on any fastboot command. When I enter recovery and start fastboot, each command will fail (command not present in this implementation). Any hints?
Finally managed to unlock the bootloader. The trick was to use an USB2.0 port on my PC.
I live in US so don't have one in my hands yet. Has anyone done a .QCN dump of the phone yet? Do you program the phone with Firehose EDL? Are there qualcomm drivers? I have so many questions.
I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems
Generally speaking I can only but encourage you to register and browse the fairphone forum as there are much much more resources, guides and activity around the fairphone 4 than on xda.
I'm using latest magisk 24.1 and todays OTA fails. I tried with Zygisk on and off. In the magisk app under install there is a install to new slot thing but I feel like that's supposed to be used if it don't fail. will I brick my phone if i click it?
edit:
found this on fp forum
Fixing OTA after rooting
Because my FP is rooted, I couldn’t install the update right away. Message: Couldn't update, installation problem The problem is that the boot partition gets modified when you root your phone and this prevents the OTA package from installing. It’s described well on Quora. This is how I was...
forum.fairphone.com
citroniais said:
I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems
Click to expand...
Click to collapse
My Build-Number say I am on:
FP4.FP3R.A.099.20220112
So it seems my Bootloader version should be A.099 but there is no file like this:
https://storage.googleapis.com/fairphone-source/FP4/A.099-boot.img
Is it okay to take a older boot img or another?
Latest seems to be
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
and before that:
https://storage.googleapis.com/fairphone-source/FP4/A.091-boot.img
yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.
I'm using latest magisk and safetynet-fix-v2.2.1, GPay.SQLite.Fix.v2.5, SQLite for ARM aarch64 devices.
Thomas.swe said:
yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.
Click to expand...
Click to collapse
okay, so you are on a magisk-boot-v-A.094? I thought Magisk, run a direct Install then is only able to patch your current running patched-A.094 boot.
Am I wrong?
I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.
Thomas.swe said:
I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.
Click to expand...
Click to collapse
Yes that it true, you are have root now.
But I think you are on the bootloader version A.094.
the 099 came from OTA so why whould bootloader be 094?
Thomas.swe said:
the 099 came from OTA so why whould bootloader be 094?
Click to expand...
Click to collapse
I am just thinking that you are on 094. Perhaps I am wrong.
But in step 5 you boot the patched 094 img and with this 094 boot image you run the direct magisk install on step 7. If I a not wrong magisk used the current running boot-image. So magisk patched your 094.
Perhaps I am wrong, I am not sure.
EDIT:
You are right @Thomas.swe Sorry for confusing.
See here: https://forum.fairphone.com/t/fp4-root-access-is-possible-maybe-a-bit-risky/76839/144
EDIT2:
@Eznaa does "our device will take much much more time to boot than usual, be patient." mean more than 20 minutes?
EDIT3:
No I used the wrong bootloader. Iode OS has its own bootloader-image upsi
I had root working using this method on A.116-boot.img. I then uninstalled Magisk, did an OTA (to A.128), did "Install Magisk to inactive Slot" (as I successfully did in older OTA updates), but it bootloops. If I `fastboot flash boot A.128-boot.img` it boots normally, but as expected, without root.
I tried an `adb wait-for-device shell magisk --remove-modules` to make sure no Magisk modules are causing the bootloop. I am on Magisk 25.1, btw.
Do you have any idea what could cause the Magisk-patched image to bootloop?
Hi,
Did you try to patch A.128 and boot on it ?
fastboot boot [image]
Please note : the best way to find an answer about any issue related to Fairphone is in the "Fairphone Community Forum" : forum.fairphone.com - The Fairphone users are not using that much XDA
I am thinking of buying Fairphone 4 and need magisk. Can anyone answer a question about the installation instructions above? Magisk website says to flash the magisk patched boot image but here the instruction is to first boot from the magisk patched image, not flash it, and then once booted run a direct install from the magisk app. What is the reason for this extra step?
Just a heads up. Root/Unlock voids FairPhone warranty unfortunately. Only reason I haven't bought this phone.
I am trying to Unlock my bootloader, Install TWRP then install Magisk for the customizations. I connected my Mi Account on my phone, and I have to wait 5 more days from the 7 days wait period. Meanwhile I was wondering If there were any simple tutorials for Installing TWRP out here, or any specific channel/video you guys would recommend for my phone. which I can watch and prepare myself, while I wait.
I checked YouTube, there are a few good tutorials there, but they each do a slightly different method, or they mention that all the Xiaomi phones will have the same method but go on to mention that "for this specific X phone you will have to do slightly differently" and that's where It gets confusing.
I don't want to end up bricking my phone in the process, that's why I was looking to ask directly in the forums so I can get more relevant suggestions, rather than just watching a YouTube follow along video which the channel owner doesn't check comments on.
Any suggestions, recommendations welcome
Suggestion before flashing the ROM you need to read the whole page of the ROM because it's the number one thing that people missed up and bricking their phone because they don't read the whole post. Also backup your data.
percharnel said:
Suggestion before flashing the ROM you need to read the whole page of the ROM because it's the number one thing that people missed up and bricking their phone because they don't read the whole post. Also backup your data.
Click to expand...
Click to collapse
I'm just tryna install Magisk as the end goal. No plans for ROM currently. But thanks for the suggestion nontheless. Something to keep in mind in case I change my mind later
My advice for you is as follows:
Let TWRP go and don't use OpenGApps.
Use the things that are working flawlessly.
Take LOS Recovery instead of mighty, but outdated TWRP,
Take MindTheGApps instead of highly customizable OpenGApps.
(Think about LOS as your custom ROM).
I used to use both together with my Mi 8. But installing LOS, the recovery and GApps on my Poco F3 was possible within round about an hour. All this went well, while I watched Netflix and cuddled a beautiful woman on her Sofa. By the way - I had to install ADB and divers on her Surface Laptop at first.
Hi,
You could check out My Beginners guide post:
Also a Very important Note, "NEVER RE-LOCK YOUR BOOLOADER" with a custom recovery or Custom Rom installed, as this will BRICK your device and you will have to pay to get it unbricked.
The Re-lock could happen when you use the MIFlash Tool and select "Clean all and Lock".
.
SDK Platform Tools (ADB & Fastboot): https://developer.android.com/tools/releases/platform-tools
Xiaomi USB Driver: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
(link source: https://developer.android.com/studio/run/oem-usb)
OrangeFox Recovery: https://orangefox.download/device/alioth
Notes:
-During BL-Unlock, your phone will auto. factory reset.
-Unlike on many AOSP-ROMs, using a Custom Recovery on MIUI will cause OTAs to not work anymore as the MIUI Update relies on MIUI Recovery. Instead you have to manually flash each MIUI-update in your Custom Recovery.
-I'm suggesting OrangeFox Recovery, because it never failed me personally, and because it's simply much more modern than TWRP.
-On MIUI, Magisk (by default) will cause you to fail Google SafetyNet, which means Banking Apps, Netflix, and many other apps won't work. You will have to spoof Attestation to "Basic" by using a Magisk Module that changes the fingerprint. And you'll have to hide Magisk from Play Services (.gms and .gms.unstable specifically) and user-apps that check for Magisk/Root.
Boot to Fastboot Mode (Power + Vol Down),
extract "recovery.img" from OrangeFox.zip,
Open Terminal inside Platform-Tools folder and do "fastboot boot <path_to_recovery.img>"
To install OrangeFox, go to its Menu and tap "Install current Recovery" (something along those lines)
To install Magisk, you can rename Magisk.apk to Magisk.zip and flash it in Custom Recovery (only TWRP or OrangeFox!, other recoveries may not be able to install anything other than the ROM ZIP file). It's the easy method of getting Magisk, however flashing Magisk.zip in Recovery isn't supported anymore by TopJohnWu.
Recommended way is to obtain the boot.img and patch it with the Magisk App. I personally do a Boot Backup with OrangeFox Recovery, patch the backup file, and restore the magisk-patched Boot file with OFox.
My break is over, so I'll have to cut here, but I think I have my socials linked in my profile. if you need more help you can message me privately on TG
cyanGalaxy said:
SDK Platform Tools (ADB & Fastboot): https://developer.android.com/tools/releases/platform-tools
Xiaomi USB Driver: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
(link source: https://developer.android.com/studio/run/oem-usb)
OrangeFox Recovery: https://orangefox.download/device/alioth
Notes:
-During BL-Unlock, your phone will auto. factory reset.
-Unlike on many AOSP-ROMs, using a Custom Recovery on MIUI will cause OTAs to not work anymore as the MIUI Update relies on MIUI Recovery. Instead you have to manually flash each MIUI-update in your Custom Recovery.
-I'm suggesting OrangeFox Recovery, because it never failed me personally, and because it's simply much more modern than TWRP.
-On MIUI, Magisk (by default) will cause you to fail Google SafetyNet, which means Banking Apps, Netflix, and many other apps won't work. You will have to spoof Attestation to "Basic" by using a Magisk Module that changes the fingerprint. And you'll have to hide Magisk from Play Services (.gms and .gms.unstable specifically) and user-apps that check for Magisk/Root.
Boot to Fastboot Mode (Power + Vol Down),
extract "recovery.img" from OrangeFox.zip,
Open Terminal inside Platform-Tools folder and do "fastboot boot <path_to_recovery.img>"
To install OrangeFox, go to its Menu and tap "Install current Recovery" (something along those lines)
To install Magisk, you can rename Magisk.apk to Magisk.zip and flash it in Custom Recovery (only TWRP or OrangeFox!, other recoveries may not be able to install anything other than the ROM ZIP file). It's the easy method of getting Magisk, however flashing Magisk.zip in Recovery isn't supported anymore by TopJohnWu.
Recommended way is to obtain the boot.img and patch it with the Magisk App. I personally do a Boot Backup with OrangeFox Recovery, patch the backup file, and restore the magisk-patched Boot file with OFox.
My break is over, so I'll have to cut here, but I think I have my socials linked in my profile. if you need more help you can message me privately on TG
Click to expand...
Click to collapse
I'm considering to switch from latest TWRP 3.7.0_9-0 to OFR R11.1_3_A12 on my old dipper. But that dosn't play a role here, because I have some general questions about it that are the same for alioth.
Just want to try it out and see, if it's really so much better than TWRP like lots of people tried to tell me in the last years...
So may I ask you some vital questions?
1. From what I understood, it should be possible to flash OFR easily through my already installed TWRP on the device, right?
2. Which decryption methods does the A12-Branch of OFR support? A12 only or A11+A12 so that it's possible to dirty flash from A11 to 12?
3. In OFR there's an inbuild (and easy to handle?) direct management of the preinstalled Apps, right? This could be avery interesting feature for me, especially with regards to the slowly dying OpenGApps-Project that was imho the best way to customize GApps over the last few years...
If you are a visual learner just watch them carefully, watch the suggestions above they work great, works perfectly on OFOX too