Database Develop

Is it possible for me to have this root combo?

Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?

Ulti2x said:
Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Click to expand...
Click to collapse
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Sent from my ONEPLUS A3000 using Tapatalk

uudruid74 said:
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Click to expand...
Click to collapse
What's CE?

Ulti2x said:
What's CE?
Click to expand...
Click to collapse
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk

To simplify this question, could I disable dm-verify and unlock the bootloader on OOS 3.5.4 and boot back into a wiped phone without any problems? After unlocking the bootloader and disabling dm verify, will I able to just update to 4.0.3 using the OTAs in settings?
Or does booting into the phone with an unlocked bootloader and no dm verify cause me to get stuck at boot? Thanks in advance.

Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.

Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
Click to expand...
Click to collapse
Thanks so much. I don't need to wipe cache after I flash Magisk right? And what's the big deal if the play store detects my device as uncertified?

Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.

Just a small note but you should be able to root without modifying system. They modify boot image now and don't touch system.
Sent from my ONEPLUS A3000 using Tapatalk

Anova's Origin said:
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Click to expand...
Click to collapse
Can I use fastboot commands just by opening command prompt right?
EDIT: This link okay? https://forum.xda-developers.com/showthread.php?t=2588979

That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.

Anova's Origin said:
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Click to expand...
Click to collapse
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799

Ulti2x said:
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Click to expand...
Click to collapse
Yep

uudruid74 said:
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
CE stands for community edition

Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Click to expand...
Click to collapse
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?

Ulti2x said:
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Click to expand...
Click to collapse
Go into settings, find Play Store and wipe cache. Then reboot.

Anova's Origin said:
Go into settings, find Play Store and wipe cache. Then reboot.
Click to expand...
Click to collapse
Still says it. Maybe I need to wait?

Forgot, I actually had to delete Play Store's app data last time before rebooting. Then it worked.

Thanks a lot everybody! I have never used fast boot before (have only flash w/ sammy phones) and now I know. Thanks again all for helping me.

[Solved] Magisk?

Solved: See this post.
After the recent SuperSU 2.81 update sent my Z3C into a boot-loop I came across a few comments on this XDA article saying that MagiskSU is the way to go these days.
Now, I gather from this thread that the best way to root is to just install stock Marshmallow and run the provided installer then flash a root binary via TWRP.
However, the FAQ in the official Magisk post states:
Sony Devices: If you're using stock kernel, it is using Sony's special ELF format. Magisk will repack it to standard AOSP format, which requires your device to be unlocked.
Click to expand...
Click to collapse
So, if the bootloader needs to be unlocked to install Magisk, does that mean you can't have the phone's DRM features active? Or is it possible to restore the DRM stuff after Magisk has been installed (assuming you've backed up the DRM keys)?
Also, does the fact that Magisk repacks the kernel mean SafetyNet will always fail on a Sony device, regardless of Magisk Hide being enabled?

I'm on latest MM and no problems with new SuperSU. All latest updates installed and 2.81 and 2.82 are working well.

Chamelleon said:
I'm on latest MM and no problems with new SuperSU. All latest updates installed and 2.81 and 2.82 are working well.
Click to expand...
Click to collapse
I guess you must be lucky then since Chainfire has advised Xperia users to stay on 2.79, as per the news article I linked.
Still, regardless of whether SuperSU works for some people or not, I'd still like to find out if MagiskSU is a viable alternative for Sony devices and what the correct procedure is to install it and retain all the phone's features.

Did Your SuperSU app was converted to system app? Mine wasn't, maybe thats an answer.

Chamelleon said:
Did Your SuperSU app was converted to system app? Mine wasn't, maybe thats an answer.
Click to expand...
Click to collapse
Possibly; can't remember to be honest. Anyway, flashing back to 2.79 fixed the boot loop and I've disabled auto-update until Chainfire says otherwise.
I still want to learn about Magisk though; not keep discussing SuperSU
I found a few bits of info on the subject:
RootKernel can apparently repack the stock kernel with a DRM fix so that all the DRM features can be restored with an unlocked bootloader.
BootBridge can install Magisk without repacking the ELF kernel in AOSP format, which the author says is preferable. However, BootBridge itself requires an unlocked bootloader so the DRM is still an issue I guess... <-- This is only meant for specific older devices; not the Z3C.
Magisk Patch claims Magisk won't work without disabling Sony RIC and provides a fix if you haven't used RootKernel already.
Trying to piece it all together is a little confusing so if anyone has actually done it, I'd be interested to hear from you.

Do we even need the SuperSU updates? 2.79 works fine for me without any issues plus the new versions are maintained by the Chinese company (I'm using some different version compiled by Chainfire himself). The only problem is the update notification in Play Store tho....

nogaff said:
After the recent SuperSU 2.81 update sent my Z3C into a boot-loop I came across a few comments on this XDA article saying that MagiskSU is the way to go these days.
Now, I gather from this thread that the best way to root is to just install stock Marshmallow and run the provided installer then flash a root binary via TWRP.
However, the FAQ in the official Magisk post states:
So, if the bootloader needs to be unlocked to install Magisk, does that mean you can't have the phone's DRM features active? Or is it possible to restore the DRM stuff after Magisk has been installed (assuming you've backed up the DRM keys)?
Also, does the fact that Magisk repacks the kernel mean SafetyNet will always fail on a Sony device, regardless of Magisk Hide being enabled?
Click to expand...
Click to collapse
actually, i have my DRM partition and Magisk on my z3c UB. Here is what i did, first i did patch boot.img with magisk and then used ta-poc tool to restore my TA-backed up partition. oh! magisk hide works properly as well giving me full access to SafetyNet.

espaciosalter20 said:
first i did patch boot.img with magisk and then used ta-poc tool to restore my TA-backed up partition
Click to expand...
Click to collapse
I finally got a chance to try this out and I'm not having much success to be honest.
I'm starting off with an unlocked bootloader and flashing stock MM 23.5.A.1.291, then flashing TWRP.
In TWRP, the current version of Magisk (v14.0) refuses to install; it just complains about Sony ELF32 format and instructs me to use BootBridge, which is only supposed to be required for older devices like the Z2.
Anyway, I tried installing Magisk via BootBridge and it claims to have installed successfully, but then Magisk Manager says Magisk is not installed when I boot into Android (yes, I've rebooted a couple of times as well).
Next, I started over from the beginning and tried Magisk v13.3 instead, which at least begins to install, but then fails to patch the boot image.
Does anyone have a working method they could describe here?

Solution
I figured it all out by myself in the end. For anyone else having trouble, here's what I did:
Made sure I had a backup of my DRM keys!!! I already had one from when I first rooted my phone on KitKat, but I decided to make another backup using Universal TA Backup v2, just in case anything was wrong with the original.
Obtained the official Marshmallow 23.5.A.1.291 firmware from XperiFirm, created a .ftf file with Flashtool, unlocked the bootloader on my device and flashed the .ftf file via Flashtool.
Flashed TWRP custom recovery via fastboot.
Extracted the stock kernel.elf boot image from the .ftf file using Flashtool.
Ran ta_poc on the kernel.elf file, answering "Y" when prompted to disable Sony RIC*. This produced a repacked boot.img with the DRM features added back in.
Copied the boot.img to my SD card.
Booted to Android and installed the Magisk Manager apk.
Used the "Install" button in Magisk Manager and selected the boot.img on my SD card.
Noted the location of the patched_boot.img that Magisk Manager created, then booted into TWRP and flashed patched_boot.img.
Booted back into Android and checked Magisk Manager status.
My device is now fully rooted, has all the DRM features intact and is passing all SafetyNet checks.
As an alternative to steps 7-9, you could simply flash the boot.img from step 6 via TWRP and then also flash the Magisk zip file via TWRP. You'd end up with exactly the same result at step 10.
I believe you could even complete the installation without TWRP or any custom recovery at all, by using Magisk Manager to create a patched_boot.img, then copying it to your PC and flashing it via fastboot.
* Disabling Sony RIC in my boot.img was what solved all my problems. This thread suggests you don't need to do that any more, but I couldn't get it to work without doing so.

Hi, I recently installed magisk 14, I get it to work. However, somehow it broke my wifi and LTE functionality. DNS NOT FOUND. I have a m4 aqua with 6.0.1 ver.1.33. Do you have any idea what could be the cause of this problem?
Enviado desde mi E2306 mediante Tapatalk

any know magisk for Z3 Compact Docomo MM 6.1 Bootloader Lock ?

Hi nogaff,
I tried your solution but there are two difficulties I can't resolve:
1) Where can I download a valid TWRP image for the Sony Xperia Z4 Tablet? My search in the internet was without success, and TWRP doesn't seem to support this device.
2) I used the same procedure to patch the kernel:
TA_POC'd the kernel with disabling DM-verity and disabling Sony-RIC
copied this image to a SD-card
put the SD-card into my SGP771
patched this image with Magisk 22.1 (this version of Magisk supports officially my Android 7.1.1)
flashed this image using FlashTool (because I don't have a TWRP recovery for the SGP771) - flashing ended without error!
BUT​​The SGP771 stucks in a boot loop!!!​​Can you tell me if I forgot something?​
Regards
Ansgar

Relock bootloader (with magisk) on the Oneplus 5?

Hello everyone, I've tried to search on the web about this issue since the OTA for Android O is finally out for the Oneplus 5 and couldn't get a satisfying solution. I rooted my OP5 a while ago with Magisk and now that this update is out and tried to install it, It just wouldn´t let me, searching I found that my locked swich to relock the bootloader was because I had to enable it on Magisk, so I opened magisk and couldn´t find that option, and now that I searched on how to enable the "Lock bootloader option" in the Magisk app and found nothing, I'm just out of ideas, so guys, could you help a (noob) brother out with this?
Ps.: If you could attach some screenshots about where to click or what to do, I'll apreciate it a lot (yeah, I'm that stupid when I freak out and don't find how to undo mi mess)

No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the full OTA zip, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.

Didgeridoohan said:
No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the update, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.
Click to expand...
Click to collapse
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?

Fosko Stock said:
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?
Click to expand...
Click to collapse
Yes.

Root MI 8 in MIUI keeping OTA updates

Is it possible to root MI 8 in MIUI keeping OTA updates with Magisk?
And keeping bootloader locked? (I guess the answer for this is no right now, since there is no bug found already)
I've found this guide for Note 4 (https://forum.xda-developers.com/redmi-note-4/how-to/guide-root-using-magisk-stock-recovery-t3718203) which, in a unlocked bootloader phone can root keeping OTA updates. It keeps the original recovery to achieve it.
Has anyone done something like it in the MI 8?

enable dm verity and everytime your phone boot it will replace recovery with original recovery, then ota updates will work. But everytime u update via ota, boot gets rewritten and your magisk will not survive. u have to fastboot flash via pc recovery rom then flash magisk again. U cant root a phone and keep bootloader locked, it doesnt work that way i dont think. Magisk modifys boot partition and relocking it will either softbrick or just not lock. Correct me if i am wrong

OTA update on rooted device with MagiskProps -> 3a

Hi all,
TLDR QUESTION: do I have to "fastboot flash boot magisk_patched_boot.img" every time after "adb sideload ota_file.zip" ?
-------------------------------------------------------------------------------------------------------------------------------------------------
I'm coming over from only using samsung galaxy series to Pixel 5.
I've always used custom roms with root and whenever there was an update available, the usual process was:
1. Flash updated rom.zip
2. Flash magisk.zip
Done.
I assume it's a similar process for pixel phones and I intend to stay on stock rom with root.
I need to pass safetynet for google pay so I have to change the device fingerprint to Pixel 3a to bypass hardware attestation (as written on this forum guides).
1. Does changing the fingerprint to 3a break the on-device OTA updates?
2. Does changing the fingerprint to 3a break updates for Pixel 5 apps?
3. After an OTA update, (either by on-device or sideload), do I have to re-flash the magisk patched boot.img to retain root?
4. Also, if I decide to un-root, does bootloader re-locking also require a device wipe?
Thank you.

swangjang said:
Hi all,
TLDR QUESTION: do I have to "fastboot flash boot magisk_patched_boot.img" every time after "adb sideload ota_file.zip" ?
-------------------------------------------------------------------------------------------------------------------------------------------------
I'm coming over from only using samsung galaxy series to Pixel 5.
I've always used custom roms with root and whenever there was an update available, the usual process was:
1. Flash updated rom.zip
2. Flash magisk.zip
Done.
I assume it's a similar process for pixel phones and I intend to stay on stock rom with root.
I need to pass safetynet for google pay so I have to change the device fingerprint to Pixel 3a to bypass hardware attestation (as written on this forum guides).
1. Does changing the fingerprint to 3a break the on-device OTA updates?
2. Does changing the fingerprint to 3a break updates for Pixel 5 apps?
3. After an OTA update, (either by on-device or sideload), do I have to re-flash the magisk patched boot.img to retain root?
4. Also, if I decide to un-root, does bootloader re-locking also require a device wipe?
Thank you.
Click to expand...
Click to collapse
This may help. https://forum.xda-developers.com/pixel-5/how-to/tutorial-unlock-bootloader-root-valid-t4178673/page1
For bootloader, I'm pretty sure that relocking would wipe the device. I think unlocking it wipes the device.
Though, it's not entirely necessary, I think, to relock the bootloader after unrooting. I think, for preference of complete security over device. I believe it disallows device modification.

dirtyreturn said:
This may help. https://forum.xda-developers.com/pixel-5/how-to/tutorial-unlock-bootloader-root-valid-t4178673/page1
For bootloader, I'm pretty sure that relocking would wipe the device. I think unlocking it wipes the device.
Though, it's not entirely necessary, I think, to relock the bootloader after unrooting. I think, for preference of complete security over device. I believe it disallows device modification.
Click to expand...
Click to collapse
Hi, thanks for your response however I have already read that guide but it does not answer any of my questions.

swangjang said:
Hi, thanks for your response however I have already read that guide but it does not answer any of my questions.
Click to expand...
Click to collapse
Oh, sorry.
1) I think it changes a build.prop entry for device manufacturer or model.
2) Pixel 5 apps? Do you mean specifically designed for this device? I have a 3xl also, and I think and it seems, that stock apps are the same. Ah, for example, the Google stock camera app - I am not sure if a Pixel 5 specific feature would disappear or not work or something.
3) I THINK you will need to. Like, at least with elementalx and kirisakura kernel the (?)script(?) looks to see if Magisk is installed and retains it. I am assuming the Google stock kernel does not .
4) unlocking the bootloader wipes the device, I believe. I would assume relocking the bootloader would. Personally, I've never relocked the bootloader on any device after unrooting . If you do relock, back up your internal storage as an incase , failsafe, or general rule or something.
Hopefully, there will be someone to chime in in case I am wrong.

Hi, i don't use OTA but full image for update but no, it don't break change props on pixel 5 but yes you need to flash magisk again.
Good update. No issues for november update

As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use

cescman said:
As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use
Click to expand...
Click to collapse
That's typically the way I've always do it except you do not unhide MM. I also modify the batch file named ‘flash-all.bat’ and remove the ‘-w' so it doesn't wipe my device.

cescman said:
As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use
Click to expand...
Click to collapse
With the Pixel 2 my process was
1. fastboot flash stock boot and dtbo images for your current build version. (Not sure if dtbo is really needed)
2. Apply OTA via ADB
3. Allow phone to boot and finish update
4. Use magisk to patch the boot image from the new build version
5. fastboot flash patched boot image.
I have used this method for three years with the Pixel 2 and only had one issue. I used smalipatcher to make mock GPS look like real GPS and apparently the magisk module needs to be re-created for each build.

j0nnyd said:
That's typically the way I've always do it except you do not unhide MM. I also modify the batch file named ‘flash-all.bat’ and remove the ‘-w' so it doesn't wipe my device.
Click to expand...
Click to collapse
I do this as well, but couldn't get the boot image patched through magisk for some reason. Anyone have a patched boot image they can share?

I hope to get a more streamlined solution eventually, but this is what I did to upgrade my Unlocked Pixel 5:
Download factory image
Unzip
Edit "flash-all.bat" to remove the "-w", save as "flash-nowipe.bat"
plug in phone and enable debugging
adb reboot bootloader
flash-nowipe.bat
unzip "image-redfin*" into a temp folder
cd into the temp folder
adb push boot.img /sdcard/Download/boot.img
on phone run Magisk Manager and patch /sdcard/Download/boot.img
adb pull /sdcard/Download/magisk_patched.img
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
I didn't need to uninstall / reinstall any modules, they were all there after the final reboot. I did have to uninstall / reinstall vanced using vanced manager to get it working.
Next time I will try patching the boot image and repacking so I need fewer reboots.

*deleted*

TonyApuzzo said:
I hope to get a more streamlined solution eventually, but this is what I did to upgrade my Unlocked Pixel 5:
Download factory image
Unzip
Edit "flash-all.bat" to remove the "-w", save as "flash-nowipe.bat"
plug in phone and enable debugging
adb reboot bootloader
flash-nowipe.bat
unzip "image-redfin*" into a temp folder
cd into the temp folder
adb push boot.img /sdcard/Download/boot.img
on phone run Magisk Manager and patch /sdcard/Download/boot.img
adb pull /sdcard/Download/magisk_patched.img
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
I didn't need to uninstall / reinstall any modules, they were all there after the final reboot. I did have to uninstall / reinstall vanced using vanced manager to get it working.
Next time I will try patching the boot image and repacking so I need fewer reboots.
Click to expand...
Click to collapse
1. What's your build.prop before upgrade?
2. Did you uninstall Magisk (restore/complete) before upgrade?
3. If #2 is 'NO', did your 'Restore Magisk Manager' and disable 'MagiskHide' before upgrade?
Thank you very much!