Develop Bugs

Update to Android 10 on magisk & Edxposed?

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

rooting ( after unlocking bootloader)

So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums
1 ) Download the latest Android factory image for your device ("see this guide on where to find it.
2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.
Warning! Make absolutely sure the firmware is exactly the same as the installed one. If not, you might loose touch.
Be aware that LMSA will download the latest firmware, even if it is not yet installed. That might break your touchscreen
Click to expand...
Click to collapse
3 ) Download latest Magisk Manager application on your phone and install it :
Link
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update
5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"
if it boots fine you should have root for this single boot / magisk would show as installed.
9 ) When it's done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and check if everything is good, and it should be
extra info:
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.

Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?

testtubebaby said:
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
Click to expand...
Click to collapse
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed

pjottrr said:
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
Click to expand...
Click to collapse
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?

Sorry, no idea, i found the provided link via google,

testtubebaby said:
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiar/official/

zuggi_m said:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
@zuggi_m , how does posting the same url help?
i don't see a retgb here ....
Maybe someone with more dev experience can tell if you need the exact same firmware or if the version numbers are the same it is ok to use that file ?

No fastbootd?
One Hyper needs fastbootd in order to flash boot and root

mingkee said:
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
Click to expand...
Click to collapse
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.

pjottrr said:
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
Click to expand...
Click to collapse
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery

mingkee said:
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
Click to expand...
Click to collapse
maybe i'm missing your point here, my description is just so people who have to figure it out can just use my steps to get root, it is indeed based on fastboot flashing . so i'm not sure what you are trying to say, or am i misinterpreting something?

https://forum.xda-developers.com/motorola-one-hyper/development/rom-omnirom-t4044405
I did root on One Hyper (shipped with Android 10) using fastbootd method
Used old method soft brick my One Hyper
That's why I'd like to know

pjottrr said:
so after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root
you need to download the firmware for our device,
That can be found here;
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETEU/
after that, extract, patch, fastboot install patched version, done.
I did have some issues with the current magisk manager ( from highonandroid, i did find another source, installed version 7.5.1 of the magisk manager from this source
and that one was able to patch the boot.img
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Click to expand...
Click to collapse
There's a head up
US version: Sofia
The rest: Sofiar
I will buy US G Power in May and let's the fun begin
Check out One Hyper general to install Dolby Atmos and it can be toggle on/off.

Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.

CCivale said:
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
Click to expand...
Click to collapse
So you should know G Stylus ROM is Sofiap.
Be aware the way Android 10 flashing is different.
Download and install the latest ADB in order to access fastbootd (fastboot reboot fastboot) and flash boot, recovery, dtbo, vbmeta, and super

Hmmmm, I will have to read more about fastbootd in your other thread.
I did use the boot.img for the sofiap.

Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.

hazd said:
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
Click to expand...
Click to collapse
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

pjottrr said:
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
rsdsecure-cloud.motorola.com/download/SOFIA_RETAIL_QPM30.80-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.

hazd said:
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
Click to expand...
Click to collapse
I downloaded the kernel and waiting for the unit.
I can flash full ROM with fastboot and fastbootd, but just flashing kernel would be much faster.
Moreover, check One Hyper general to get Dolby Atmos because you can turn on and off anytime you want.

Has anyone successfully updated to Android 11 with Magisk?

I see "11.0.0 (RQ1A.201205.003, Dec 2020" is available for Crosshatch and Blueline.
I'm still on Android 9 with Magisk installed by patching the boot image.
Is the following process still valid and supported for applying an OTA update to Android 11, and then re-installing Magisk?
1) Magisk Manager → Uninstall → Restore Images
2) Apply the OTA update :
__a) Boot into factory recovery
__b) Choose Apply update from ADB
__c) From windows: adb sideload crosshatch-ota-rq1a.201205.003-4d6e609b.zip
__d) Reboot phone and let the update finish in Android
3) Separately download the corresponding Factory image: crosshatch-rq1a.201205.003-factory-d5cb2a93.zip. Extract the boot.img, move it into the Pixel 3 XL's download folder
4) Uninstall old Magisk manager and install the latest Magisk Manager (Direct Install Magisk Manager v8.0.4 from here, per Magisk installation instructions)
5 ) Open Magisk Manager and Press Install ==> Press Install again ==> Select Patch a File ==> Select the boot.img file in "Download". It will be patched.
6) Copy the magisk_patched.img file to your computer's Platform-tools folder
7) Boot Pixel 3 XL into fastboot mode by typing the commad: adb reboot bootloader
8) Once phone is on fastboot mode then type: fastboot flash boot magisk_patched.img
9) Once it's done then type the command : fastboot reboot
10) Open Magisk Manager and check if its rooted
This is based on the process from about a year ago. so please reply if anything has changed.

timg11 said:
I see "11.0.0 (RQ1A.201205.003, Dec 2020" is available for Crosshatch and Blueline.
I'm still on Android 9 with Magisk installed by patching the boot image.
Is the following process still valid and supported for applying an OTA update to Android 11, and then re-installing Magisk?
1) Magisk Manager → Uninstall → Restore Images
2) Apply the OTA update :
__a) Boot into factory recovery
__b) Choose Apply update from ADB
__c) From windows: adb sideload crosshatch-ota-rq1a.201205.003-4d6e609b.zip
__d) Reboot phone and let the update finish in Android
3) Separately download the corresponding Factory image: crosshatch-rq1a.201205.003-factory-d5cb2a93.zip. Extract the boot.img, move it into the Pixel 3 XL's download folder
4) Uninstall old Magisk manager and install the latest Magisk Manager (Direct Install Magisk Manager v8.0.4 from here, per Magisk installation instructions)
5 ) Open Magisk Manager and Press Install ==> Press Install again ==> Select Patch a File ==> Select the boot.img file in "Download". It will be patched.
6) Copy the magisk_patched.img file to your computer's Platform-tools folder
7) Boot Pixel 3 XL into fastboot mode by typing the commad: adb reboot bootloader
8) Once phone is on fastboot mode then type: fastboot flash boot magisk_patched.img
9) Once it's done then type the command : fastboot reboot
10) Open Magisk Manager and check if its rooted
This is based on the process from about a year ago. so please reply if anything has changed.
Click to expand...
Click to collapse
You might be able to skip all the step 2's and just check for update after unrooting and take the ota normally. That has worked for me for quite awhile.
Other than that, your steps are spot on and work with 11.

TonikJDK said:
You might be able to skip all the step 2's and just check for update after unrooting and take the ota normally. That has worked for me for quite awhile.
Other than that, your steps are spot on and work with 11.
Click to expand...
Click to collapse
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?

timg11 said:
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?
Click to expand...
Click to collapse
Best practice would be to do an actual update and reboot bootloader to flash your patched boot.img. If you are jumping android releases problems might arise that no one can account for and generally you should do a full wipe when switching releases. Google has by no means accounted for any contingencies in the ota process, read the disclaimer they give upon an ota (any data lost in the process is never their fault, so backup you stuff). Patching the boot image through the manager is the preferred method, anything else is very difficult to troubleshoot.

timg11 said:
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?
Click to expand...
Click to collapse
By boot method do you mean unroot, do not boot, update do not boot, then root the inactive slot?
Do not do that, on 11 it can go bad in fact if you have 11 it will not even be available in Magisk. He took it out for now due to problems.
What I was suggesting bead unroot, boot, take the OTA, boot. Then patch the boot img and flash it.

Fairphone 4 - Root

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.

Question Help!!!!!! Boot failure / stuck in fastboot

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 Failed​Device 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 Failed​Device 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)".