Database Info

Great News!

Magisk Root now Works on Nokia 3 Device! You can flash it on Twrp recovery, and no errors comes up! (Like software update stopped working and cust manager) it requires stock boot image.
Link https://www.mediafire.com/folder/n2dmcnfjl7mz88h,4771ez9ddvccuim
In link, there is Magisk and Boot.img

RootingPro-18 said:
Magisk Root now Works on Nokia 3 Device! You can flash it on Twrp recovery, and no errors comes up! (Like software update stopped working and cust manager) it requires stock boot image.
Link https://www.mediafire.com/folder/n2dmcnfjl7mz88h,4771ez9ddvccuim
In link, there is Magisk and Boot.img
Click to expand...
Click to collapse
this is modified boot.img to work with magisk without errors, right? How to do this for SuperSU

SkaboXD said:
this is modified boot.img to work with magisk without errors, right? How to do this for SuperSU
Click to expand...
Click to collapse
No, this is clean boot img. Magisk you have to flash by yourself

[stupid question] OTA update when on magisk and xposed?

Hello XDA!
It's been a while since I did 'modding' on phones, I think I started with the OP1 back in 2014 but have not really been keeping up ever since. I am now on 5.1.5 and running official OOS with magisk and xposed for gravitybox.. Can I just disable magisk and xposed, do the OTA update and then re-enable or do I have to uninstall them fully? Or can I just do the OTA right now?
Sorry for what might be a really obvious answer.
Thank you!

You can do the OTA but if you want magisk (and then xposed systemless) i suggest you to install TWRP after update and you need in all cases to re-do root process

Hitman478™ said:
You can do the OTA but if you want magisk (and then xposed systemless) i suggest you to install TWRP after update and you need in all cases to re-do root process
Click to expand...
Click to collapse
Ahh I see. Because xposed is now systemless it doesn't matter if I leave it enabled right? Is the new official TWRP without any dangerous bugs?
Thanks for your swift reply!!

maybe to help you all
me: 5.1.5, unlocked bootloader, unofficial TWRP from thread by wuxianlin, magisk 16.4
my procedure was to change to official twrp which can be done easily by
downloading the twrp installer from official site, put to internal storage
flash twrp official installer
still in recovery, select reboot: recovery
flash magisk
boot system
now download full 5.1.6 signed flashable zip
recovery: flash 5.1.6
reflash recovery
reboot recovery
flash magisk
boot system
now you have rooted 5.1.6 with official twrp and magisk, no wipe needed

oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.

trivita said:
oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.
Click to expand...
Click to collapse
This will useful only if don't have TWRP, in other case you'll lose twrp in this way
---------- Post added at 15:21 ---------- Previous post was at 15:19 ----------
TheHighLife said:
Ahh I see. Because xposed is now systemless it doesn't matter if I leave it enabled right? Is the new official TWRP without any dangerous bugs?
Thanks for your swift reply!!
Click to expand...
Click to collapse
TWRP official has no bug, the only thing i don't know is if backup/restore is working fine, if you install ota via TWRP and then flash (without reboot) twrp.zip and magisk, after reboot you'll find out that system is exactly the same it was before updating

The only thing u need to disable before updates are overlays through substratum, I also remove any security like finger prints, face unlock and pin or patterns too just in case. Once u flash update u will have to reflash magisk and xposed too

trivita said:
oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.
Click to expand...
Click to collapse
Did anyone try this?

defsix said:
Did anyone try this?
Click to expand...
Click to collapse
i did this myself
idontcare abt the twrp at all
im perfectly fine with stock recovery

trivita said:
i did this myself
idontcare abt the twrp at all
im perfectly fine with stock recovery
Click to expand...
Click to collapse
Same as that. I'll give it a try next update.
Sent from my Brain using my Keyboard

How do you install to second partition? I only get install or uninstall Magisk (16.70) on the screen. i AM NEW TO MAGISK.

TWRP on Android 10

After recently bricking my Oneplus 6 by trying to flash the latest TWRP on the latest Android 10 OTA from Oxygen Updater, I found a post from official TWRP explaining how root with a10 will take a while to implement due to changes that Google has made to their partitions.
So I guess for anyone trying this out on their own, be warned. You will probably end up bricking your device like I did and will probably end up having a bad time.
Please correct me if i'm wrong though, peace!
Edit: can confirm fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img from the other popular post is working!

If you already have a working TWRP on OOS 9 you should be fine as long as you flash a working TWRP afterwards. Blu_spark TWRP 9.101 is compatible (please not 9.101 no earlier version will work).
Also don't use Magisk 20 only 20.1.
There is already a pre-patched version out there. You can fastboot flash it (as fastboot boot doesn't work). An easier way (without a pre-patched version) is currently being worked one as you pointed out already

just updated to a10
boot into twrp, flash new bluspark twrp
flash FULL ota a10 image
reflash twrp
reboot into twrp
boot into system
boot back to twrp
install magisk 20.1
a10, twrp and root working

Hi,
I am on 9.0.9 stable with root using magisk. Is it possible to update to android 10 without loosing data and root??

nightfury04 said:
Hi,
I am on 9.0.9 stable with root using magisk. Is it possible to update to android 10 without loosing data and root??
Click to expand...
Click to collapse
havent lost data and you can root again

Blu_spark twrp
could you please provide link for blu_spark twrp img, zip files that work with android 10?

akri1337 said:
havent lost data and you can root again
Click to expand...
Click to collapse
Did you uninstall Magisk in stable 9.0.9 before updating to andeoid 10?

nightfury04 said:
Did you uninstall Magisk in stable 9.0.9 before updating to andeoid 10?
Click to expand...
Click to collapse
nope

akri1337 said:
havent lost data and you can root again
Click to expand...
Click to collapse
akri1337 said:
nope
Click to expand...
Click to collapse
It would be of great help if you could provide link to working TWRP with android 10.

https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page222
i used this one

akri1337 said:
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page222
i used this one
Click to expand...
Click to collapse
Which build did u use mate? R108 is not working with android 9, I tried flashing it using my older installed twrp.
It says unsupported android version. And in github r108 says only for android 10.

r108 is the kernel not twrp
https://github.com/engstk/android_device_oneplus_enchilada/releases/tag/v9.107

akri1337 said:
r108 is the kernel not twrp
https://github.com/engstk/android_device_oneplus_enchilada/releases/tag/v9.107
Click to expand...
Click to collapse
Thanks again mate.. I will give this one a try.

there is a problem with Magisk 20.1, after all flashes the system is booting ok with Magisk working but after I give first program root access and rebooting its stuck on bootloader and not booting to system.

nightfury04 said:
Thanks again mate.. I will give this one a try.
Click to expand...
Click to collapse
I can confirm that this is working for me. I successfully upgraded from Android 9, Oxygen OS 9.0.9 to Android 10, Oxygen OS 10. Steps that I followed :
1) Flashed new twrp from link in the above post by akri1337 using my previously installed twrp : bluspark 9.85.
2) Flashed Oxygen OS 10 full update and added to queue latest bluspark twrp which I flashed in step one as it would be overwritten by flashing the full OTA update.
3) Rebooted into recovery again to switch to active slot.
4) Flashed Magisk 20.2 to regain root.
This process successfully upgraded my Oneplus 6 without any data loss.
Please note that I disabled all magisk modules just to be safe before starting the upgrade process but didn't uninstall magisk. I was on Magisk 20.2 earlier.
Hope this helps everyone.

nightfury04 said:
I can confirm that this is working for me. I successfully upgraded from Android 9, Oxygen OS 9.0.9 to Android 10, Oxygen OS 10. Steps that I followed :
1) Flashed new twrp from link in the above post by akri1337 using my previously installed twrp : bluspark 9.85.
2) Flashed Oxygen OS 10 full update and added to queue latest bluspark twrp which I flashed in step one as it would be overwritten by flashing the full OTA update.
3) Rebooted into recovery again to switch to active slot.
4) Flashed Magisk 20.2 to regain root.
This process successfully upgraded my Oneplus 6 without any data loss.
Please note that I disabled all magisk modules just to be safe before starting the upgrade process but didn't uninstall magisk. I was on Magisk 20.2 earlier.
Hope this helps everyone.
Click to expand...
Click to collapse
Which magisk? Ver 20.1 ?

Why is it that I get an error when trying to flash the full OTA update using TWRP? Something about error 7 and not have a digest file. Is there a full OTA update file that everyone is using? I tried the signed full zip from here on XDA and the one from Oxygen Updater. I get the same error with both.

GunFishin said:
Why is it that I get an error when trying to flash the full OTA update using TWRP? Something about error 7 and not have a digest file. Is there a full OTA update file that everyone is using? I tried the signed full zip from here on XDA and the one from Oxygen Updater. I get the same error with both.
Click to expand...
Click to collapse
Had this error too and couldn't flash it with twrp, flashed successfully OTA file from oxygen -> Local upgrade

chetbiz said:
Had this error too and couldn't flash it with twrp, flashed successfully OTA file from oxygen -> Local upgrade
Click to expand...
Click to collapse
Still confused as to how everyone else can flash these zip files through TWRP and I cannot.
I'm currently Magisk rooted and have TWRP installed. Will I lose root and TWRP when updating through the local upgrade method?

GunFishin said:
Still confused as to how everyone else can flash these zip files through TWRP and I cannot.
I'm currently Magisk rooted and have TWRP installed. Will I lose root and TWRP when updating through the local upgrade method?
Click to expand...
Click to collapse
Yes, you will need to flash twrp with adb and going through the hole process of installing twrp and magisk, but for me its not worked well, after first boot to Android Q with magisk 20.1 and granting some apps root access when I rebooted the phone its not booting to system and going to bootloader, I think its related to some problem with magisk 20.1.

CUstom ROM installation problem, please help

Hi to everyone. I have a european version of the op7 pro. The device produces an issue when using android auto, which I use daily (the bottom bar is rarely responsive to my touches whereas the rest of android auto works fine). So I wanted to try a custom ROM and see if the problem persists.
I tried multiple roms like havoc, aosip and lineage following the respective guides of installation, but regardless of the ROM, I always get stuck at the startup animation when I first try to reboot to system after installing twrp, magisk, gapps etc.
The only rom that seems to work is any version of OOS.
Any help would be greatly appreciated!

Exact what steps you do when installing a custom ROM?

U need to explain how you flash those OS; from my experience on OP6 -> flashing a third party rom need to update it' firmware to match the rom u try to flash, or else it cannot go into system definitely!

Steps :
Unlock bootloader
Boot twrp
Flash twrp
Flash rom
Flash twrp
Reboot to recovery
Once again flash rom
Once again flash twrp
Flash magisk
Flash gapps

Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system

pranacrockz said:
Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system
Click to expand...
Click to collapse
What oos do I flash? Would you mind linking me to it?:good:

Kama45 said:
What oos do I flash? Would you mind linking me to it?:good:
Click to expand...
Click to collapse
Latest android 10 stable rom available for your phone.

pranacrockz said:
Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system
Click to expand...
Click to collapse
I think this post is useful. But what is dm verity, where to find?
I flash the roms and manage to open them but sensors not working on any custom rom. I create a topic to help but nobody cared.

c3drik 67 said:
Latest android 10 stable rom available for your phone.
Click to expand...
Click to collapse
Is that the same as going back to stock with the MSM tool?
Like this one: https://androidfilehost.com/?fid=4349826312261732239

poulidis said:
Steps :
Unlock bootloader
Boot twrp
Flash twrp
Flash rom
Flash twrp
Reboot to recovery
Once again flash rom
Once again flash twrp
Flash magisk
Flash gapps
Click to expand...
Click to collapse
You must Format internal storage before booting into Custom ROM.
Also, when you flash a Custom Rom, when it's done flashing, reboot once more to recovery and then flash the rest like Gapps, Magisk, etc... (Keep in mind that some custom ROMs require once time boot before flashing Magisk).

Kama45 said:
What oos do I flash? Would you mind linking me to it?:good:
Click to expand...
Click to collapse
https://otafsg1.h2os.com/patch/amaz...P.26_OTA_026_all_2003222032_6893aca031668.zip
---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------
GöğüstekiDövme said:
I think this post is useful. But what is dm verity, where to find?
I flash the roms and manage to open them but sensors not working on any custom rom. I create a topic to help but nobody cared.
Click to expand...
Click to collapse
Dm Verity is to keep the phone unencrypted. I don't use dm Verity but I never faced such problems.
Which rom u using?

pranacrockz said:
https://otafsg1.h2os.com/patch/amaz...P.26_OTA_026_all_2003222032_6893aca031668.zip
---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------
Dm Verity is to keep the phone unencrypted. I don't use dm Verity but I never faced such problems.
Which rom u using?
Click to expand...
Click to collapse
Oos O2 Beta 11 now. Back when I try, it was oos beta 10. None of custom roms sensors were not working. Like Pixel exp, havoc, lineage
Sent from my OnePlus7Pro using XDA Labs

Never use beta. Always use stable

pranacrockz said:
Never use beta. Always use stable
Click to expand...
Click to collapse
I'll try one more time later. Thanks.

General Global 11.2.6.6 rooted!!!

First off I'm not responsible for anything that happens to your device
Attached below is the patched image for OnePlus 9 global 11.2.6.6
Flash via fastboot
For support and faster answer look here

Thank you for this! Since Magisk removed the option for OTA install, I was forced to do it the harder way... But you my friend made it much easier on me ! Thank you!!

Sorry for newbie's question, what's the difference between the two files? one is stock and one is patched?

Yes. Stock has to be flashed to take next ota. And patched is for root on current rom. Since op9 now uses google ota if any partitions are modified including the boot image ,it will fail.

Jg1234 said:
Thank you for this! Since Magisk removed the option for OTA install, I was forced to do it the harder way... But you my friend made it much easier on me ! Thank you!!
Click to expand...
Click to collapse
When did they remove OTA install? Mine still has it....

illusiveairforce said:
When did they remove OTA install? Mine still has it....
Click to expand...
Click to collapse
Mine still there as well. But I like to flash stock boot image back. Take ota. Then fastboot boot patched.img. Dump current boot image to sd through shell. Then direct install in magisk. I've seen many users have issues taking ota's using the other method. As in not even being able to boot or booting back into old build . So I prefer this way. Wanna avoid the msm tool and not loose data on device/have to factory reset.

mattie_49 said:
Mine still there as well. But I like to flash stock boot image back. Take ota. Then fastboot boot patched.img. Dump current boot image to sd through shell. Then direct install in magisk. I've seen many users have issues taking ota's using the other method. As in not even being able to boot or booting back into old build . So I prefer this way. Wanna avoid the msm tool and not loose data on device/have to factory reset.
Click to expand...
Click to collapse
What are the shell commands to extract the stock boot?

Amd4life said:
What are the shell commands to extract the stock boot?
Click to expand...
Click to collapse
we are making a group for global only and help can be found there

Amd4life said:
What are the shell commands to extract the stock boot?
Click to expand...
Click to collapse
'dd' command in Linux - GeeksforGeeks

Edit- I got it, I had to flash original images and then updates showed up. Thanks for posting these images.
Hi, thanks for posting the images. I assume global as in the US AA model since that is the only model with OTA from googles server right? The reason I was asking is I am on 11.0.4.4 and never received the notification for the update yet, but using oxygen updater, when I go in settings and check advanced mode, it shows a incremental update. My system under local file of course can't see it or will not show the update. I figured I could fastboot boot the stock image and then maybe it system could see the update, but when I try, the device just hangs on the fastboot screen(right before normally booting). I tried with my image and it booted. Do you have any suggestions? Thanks

Steps as follows if on rooted 11.2.5.5
1. flash stock 11.2.6.6.img
2. install OTA
3. flash patched 11.2.6.6.img
4. profit

TheBurgh said:
Steps as follows if on rooted 11.2.5.5
1. flash stock 11.2.6.6.img
2. install OTA
3. flash patched 11.2.6.6.img
4. profit
Click to expand...
Click to collapse
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?

netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
You are correct my friend. One needs stock untouched boot image to be able to take next update. If your on 11.2.5.5 you need that boot image to get ota to install correctly. This 11.2.6.6 img if for next round of updates. Here is 11.2.5.5 for anyone that might still be on older build.
Stock 11.2.5.5.img
drive.google.com

netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
mattie_49 said:
You are correct my friend. One needs stock untouched boot image to be able to take next update. If your on 11.2.5.5 you need that boot image to get ota to install correctly. This 11.2.6.6 img if for next round of updates. Here is 11.2.5.5 for anyone that might still be on older build.
Stock 11.2.5.5.img
drive.google.com
Click to expand...
Click to collapse
Appreciate the input. I have been out of the game since the 6t so I am still trying to catch up

UPDATED POST
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.*
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img**
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*this step presupposes that Magisk has a STOCK boot.img to restore for the unroot procedure. If it does not have that, you're obligated to use the process described in post #11.
**you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install

reaper000 said:
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img*
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
Click to expand...
Click to collapse
So doing it this method backs up stock untouched current boot image and reflashes during uninstall of magisk to allow ota to go through.? Since the op9 uses google ota all partitions have to be stock including boot image. Or it fails

reaper000 said:
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img*
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
Click to expand...
Click to collapse
this will fail

FizzyAps said:
this will fail
Click to expand...
Click to collapse
What's the command to flash the stock 11.2.5.5 boot.img? I tried renaming the boot_a.img the mattie_49 posted to boot.img but it would not flash.

TheBurgh said:
What's the command to flash the stock 11.2.5.5 boot.img? I tried renaming the boot_a.img the mattie_49 posted to boot.img but it would not flash.
Click to expand...
Click to collapse
Fastboot flash boot boot.img

mattie_49 said:
Fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks. Got the command to work this time. Tried a few times yesterday but had no luck