Related
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Tom403 said:
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Click to expand...
Click to collapse
Why don't you install Magisk by patching Boot image from Magisk Manager and flashing the patched image from Fastboot.
Just for Magisk, you don't need (to bother with) TWRP
zgfg said:
Why don't you install Magisk by patching Boot image from Magisk Manager and flashing the patched image from Fastboot.
Just for Magisk, you don't need (to bother with) TWRP
Click to expand...
Click to collapse
Won't that replace my recovery with the stock one?
I'd like to keep twrp
Tom403 said:
Won't that replace my recovery with the stock one?
I'd like to keep twrp
Click to expand...
Click to collapse
You flash the patched Boot image from Fastboot, so Recovery (and other partitions) remains the one you have currently installed.
Also, just patching in Magisk Manager does not affect either Recovery, Boot (Vendor, etc)
When patching Boot image by Magisk Manager make sure you take the options:
-Preserve ADM dm-verity: YES
-Preserve force encryption: YES
-Recovery mode: NO
zgfg said:
You flash the patched Boot image from Fastboot, so Recovery (and other partitions) remains the one you have currently installed.
Also, just patching in Magisk Manager does not affect either Recovery, Boot (Vendor, etc)
When patching Boot image by Magisk Manager make sure you take the options:
-Preserve ADM dm-verity: YES
-Preserve force encryption: YES
-Recovery mode: NO
Click to expand...
Click to collapse
Ok, I'll do that then
Thanks for the help ?
Tom403 said:
Ok, I'll do that then
Thanks for the help ?
Click to expand...
Click to collapse
For the Boot image you have to patch boot.img extracted from zip/recovery package of your stock ROM
But you can also backup Boot partition by TWRP and then let Magisk Manager patch the backup boot.emmc.win file
Is it safe to assume that Tom403 didn't find any love at the end of the encrypted rainblow? I JUST WANT to verify, This IS the same situation that used to be remedied by deleting locksettings.db and a files with .key extension?? No such luck for anymore, wow, what a setup for future-screwing your users Google!! Dicks
goo. said:
Is it safe to assume that Tom403 didn't find any love at the end of the encrypted rainblow? I JUST WANT to verify, This IS the same situation that used to be remedied by deleting locksettings.db and a files with .key extension?? No such luck for anymore, wow, what a setup for future-screwing your users Google!! Dicks
Click to expand...
Click to collapse
Okay, I may have found a lightbulb somewhere in the tunnel that may be whats required for others as well to unencrypt when deleting .keyfiles is no longer an option having version greater than PIE. It's in the form of in a recovery log from a recent, perhaps backup attempt, that states the version of Orange Fox recovery I had (11.0) and also says fbe encryption in use and info like the following that looks very promising... I'd really appreciate if someone that knows more than me to let me know if I'm on the right path and guide me in if so... heres part of the LOG that gives me hope --
ased Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using SoftwareWrappedKeymaster1Device from Google for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
Added key 90117251 (ext4:72f7ca8ad834ad5d) to keyring 322439018 in process 546
Added key 866183642 (f2fs:72f7ca8ad834ad5d) to keyring 322439018 in process 546
Added key 321684719 (fscrypt:72f7ca8ad834ad5d) to keyring 322439018 in process 546
contents mode 'aes-256-xts' filenames 'aes-256-heh'
Wrote system DE key reference to:/data/unencrypted/ref
e4crypt_ini
Thanks in advance for any help with this
Tom403 said:
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Click to expand...
Click to collapse
thanks for the terminal command
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
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.
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
jcp2 said:
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
Click to expand...
Click to collapse
Try using Android Flash Tool to get back to stock.
I tried. it failed.
Flash FailedDevice failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
jcp2 said:
I tried. it failed.
Flash FailedDevice failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
Click to expand...
Click to collapse
Then just manually flash ROM files in fastboot
jamescable said:
Then just manually flash ROM files in fastboot
Click to expand...
Click to collapse
is there a write up somewhere with adb commands?
Use PixelFlasher and the latest full update.
AlDollaz said:
Use PixelFlasher and the latest full update.
Click to expand...
Click to collapse
tried that as well
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I'm not sure of the commands. Fastboot flash recovery "recovery.img" , same with the other files inside the zip inside the stock rom zip file
If i ran into this issue I'd try fastboot -w and fastboot update a custom rom.
jcp2 said:
is there a write up somewhere with adb commands?
Click to expand...
Click to collapse
Most need to be flashed in fastbootd I think. So to get there, fastboot reboot fastboot. You can flash recovery( boot, dtbo and vendor boot) in regular fastboot. That should fix everything because it will fully get rid of magisk
I used AFT and forced flashed partitions / wiped (kept bootloader unlock) and it's alive again!
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
StanWiz said:
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
Click to expand...
Click to collapse
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Strephon Alkhalikoi said:
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Click to expand...
Click to collapse
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
StanWiz said:
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
Click to expand...
Click to collapse
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Strephon Alkhalikoi said:
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Click to expand...
Click to collapse
It's not a question of knowledge but rather the things that are beyond ones control - possibility of bugs in the code. For example look what happened recently with platform tools.
@jcp2 With all the things you flash, you should also know what that is. Then it would be much easier for you to figure it out why your device is in an unbootable state.
Magisk, Kernel, fastbootd... have one thing in common: your boot.img!
It doesn't make sense to let Magisk patch your boot.img and installing a custom kernel without Magisk installed afterwards. In that case Magisk gets overwritten.
Your fastbootd is only a binary and located in the recovery's /sbin folder. Due to the fact that your P6P is an A/B slot device, your recovery is part of the boot.img.
Flash your stock boot.img from the image-raven-BUILD_NO.zip that you'll find inside your firmware download.
I had already tried flashing stock boot image to both slots. I had to use AFT and force flash all partions. I'm up and running/ rooted. I just have to reinstall apps .
Android flash tool is by far the easiest way to go for sure. Happy you got it fixed
{Mod edit: Quoted post has been deleted. Oswald Boelcke}
6. fast boot flash
That ADB Command does nothing.
The correct command is:
fastboot flash boot boot.img if you want to flash the boot.img
{Mod edit: Quoted post has been deleted. Oswald Boelcke}
You should give us the correct command. The syntax is (see fastboot -h):
Code:
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.
you can't use "fast boot" for a binary that's called "fastboot(.exe)".