Database Info

January Patch

Latest update is out on the developer page of Google.

Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?

chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
?
I did not have to use a "patched" boot image thirty days ago . . . Normal old boot image did the trick.
.
You have to boot twrp but what do we gain by loading the twrp zip ? . nandroid backups ?

chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
Have no idea haven't even tried. Didn't know where to get started since I haven't seen anyone say anything about rooting with the January patch.

Rooting is the same as it always has been. Boot to TWRP and install the Magisk zip from TWRP.

The update is good, I see no new features but I noticed big improvements in performances and RAM management

chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
Just have to put twrp on and flash through that all good and tested even with swift installer for themes

TonikJDK said:
Rooting is the same as it always has been. Boot to TWRP and install the Magisk zip from TWRP.
Click to expand...
Click to collapse
OK, yes, Magisk v18 worked fine by flashing it on TWRP

Link to download?
Sent from my Pixel 3 XL using Tapatalk

chakra said:
Link to download?
Click to expand...
Click to collapse
January 2019 Update (for Pixel 3 XL aka "crosshatch"):
Factory Image -- https://dl.google.com/dl/android/aosp/crosshatch-pq1a.190105.004-factory-7165155c.zip
Full OTA Image -- https://dl.google.com/dl/android/aosp/crosshatch-ota-pq1a.190105.004-5f23d043.zip

Can you flash via TWRP?

virtyx said:
Can you flash via TWRP?
Click to expand...
Click to collapse
Installing OTA via TWRP (I assume you are referring to than and not the Magisk flash) has never worked on the Pixel 3 or 3XL. Sideload the OTA or flash-all with the -w removed.

Just came across this bit of vague information but thought some might be interested. Apologies if it's old info, but seems to indicate the upcoming Feb 2019 update.
Feb 19 Various bug fixes as well as support for Optus VoWIFI + EVS codec activation.
Security updates for Android 9.0
Status: Complete
Click to expand...
Click to collapse
https://yescrowd.optus.com.au/t5/Blog/Android-Software-Updates-07-01-2019/ba-p/522497

sliding_billy said:
Installing OTA via TWRP (I assume you are referring to than and not the Magisk flash) has never worked on the Pixel 3 or 3XL. Sideload the OTA or flash-all with the -w removed.
Click to expand...
Click to collapse
Never side loaded an OTA before. Does it wip TWRP and root? I'd assume so but just checking.
Fire Hound 8.1

Shaftamle said:
Never side loaded an OTA before. Does it wip TWRP and root? I'd assume so but just checking.
Fire Hound 8.1
Click to expand...
Click to collapse
It does. Effectively, it does the same thing as the factory image without the -w. It just loads les files. I have been doing the factory image way for years on the OG Pixel XL and now the 3XL. I have done a sideload once just to see the process as well as an OG TWRP sideload once (when it was working) for the same reason. The factory method is the easiest and most reliable IMO. You just need to remember to remove the -w, LOL.

anyone have any idea why i can get twrp to install but when i install any version of magisk it boots to the g with a line under it for a few minutes then it just reboots to twrp

DrUnkeN_TiGeR said:
anyone have any idea why i can get twrp to install but when i install any version of magisk it boots to the g with a line under it for a few minutes then it just reboots to twrp
Click to expand...
Click to collapse
Could be a few things. Make sure you have the current fastboot/adb files, flash boot.img to both slots, make sure you have the most recent TWRP and stable Magisk files, verify all of your downloads and start over.

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.

OnePlus6 fastboot boot twrp not possible after OTA

Hey guys,
got a OP6 for years. Stay on Stock OS with root. Never flashed any CustomRom or OS.
Bootet with fastboot boot twrp-version.img and flashed Magisk in twrp.
Works absolut fine until now. I installed the OTA and now i cant enter any twrp.
Information about my device:
Device: OnePlus6 A6003
OSS: 10.3.3
Android: 10
Build-Number: A6003_22_200414
USB-Debuggin: Enabled
OEM-Unlock: active
I tried all .img files from here:
eu.dl.twrp.me/enchilada/
and
twrp-3.2.3-x_blu_spark_v9.91_op.img
twrp-3.2.3-x_blu_spark_v9.86_op.img
No version working.
After flashing the 3.2.x versions i get a screen with
"qualcom crashdum mode
-------------"
With the newer 3.3x versions the screen just switch to "fastboot mode" and stay there forever.
How can i just boot into twrp with the new version? I wont twrp forever (flash). Just need to flash root after every OTA.
Thx for help!

Hilzerak said:
Just need to flash root after every OTA.
Click to expand...
Click to collapse
You could do that without TWRP. You just need to use Magisk's "Install to inactive slot" feature after installing OTA but before rebooting.

Hilzerak said:
Hey guys,
got a OP6 for years. Stay on Stock OS with root. Never flashed any CustomRom or OS.
Bootet with fastboot boot twrp-version.img and flashed Magisk in twrp.
Works absolut fine until now. I installed the OTA and now i cant enter any twrp.
Information about my device:
Device: OnePlus6 A6003
OSS: 10.3.3
Android: 10
Build-Number: A6003_22_200414
USB-Debuggin: Enabled
OEM-Unlock: active
I tried all .img files from here:
eu.dl.twrp.me/enchilada/
and
twrp-3.2.3-x_blu_spark_v9.91_op.img
twrp-3.2.3-x_blu_spark_v9.86_op.img
No version working.
After flashing the 3.2.x versions i get a screen with
"qualcom crashdum mode
-------------"
With the newer 3.3x versions the screen just switch to "fastboot mode" and stay there forever.
How can i just boot into twrp with the new version? I wont twrp forever (flash). Just need to flash root after every OTA.
Thx for help!
Click to expand...
Click to collapse
You should you twrp by
remewer said:
You could do that without TWRP. You just need to use Magisk's "Install to inactive slot" feature after installing OTA but before rebooting.
Click to expand...
Click to collapse
Try to in to recovery mode,if not,you try to flash twrp by mau.....

remewer said:
You could do that without TWRP. You just need to use Magisk's "Install to inactive slot" feature after installing OTA but before rebooting.
Click to expand...
Click to collapse
Thx for the info, helps for future.
But know i rebootet.
soihuvuontrang said:
You should you twrp by
Try to in to recovery mode,if not,you try to flash twrp by mau.....
Click to expand...
Click to collapse
Thx for reply but i dont know what excactly do you try to say me.
"You should you twrp by"? What should i try in recovery mode? And im looking forward for an solution without permanent flash, as i sayn above.

Hilzerak said:
Hey guys,
got a OP6 for years. Stay on Stock OS with root. Never flashed any CustomRom or OS.
Bootet with fastboot boot twrp-version.img and flashed Magisk in twrp.
Works absolut fine until now. I installed the OTA and now i cant enter any twrp.
Information about my device:
Device: OnePlus6 A6003
OSS: 10.3.3
Android: 10
Build-Number: A6003_22_200414
USB-Debuggin: Enabled
OEM-Unlock: active
I tried all .img files from here:
eu.dl.twrp.me/enchilada/
and
twrp-3.2.3-x_blu_spark_v9.91_op.img
twrp-3.2.3-x_blu_spark_v9.86_op.img
No version working.
After flashing the 3.2.x versions i get a screen with
"qualcom crashdum mode
-------------"
With the newer 3.3x versions the screen just switch to "fastboot mode" and stay there forever.
How can i just boot into twrp with the new version? I wont twrp forever (flash). Just need to flash root after every OTA.
Thx for help!
Click to expand...
Click to collapse
The version you tried to boot is not for android 10.
Versions for android 10 are blu_spark 9.108 and 9.109. Unfortunately, i think @eng.stk stopped providing img, but you can download lastest @mauronofrio TWRP and then flash @mauronofrio or blu_spark TWRP

Hilzerak said:
Thx for the info, helps for future.
But know i rebootet.
Thx for reply but i dont know what excactly do you try to say me.
"You should you twrp by"? What should i try in recovery mode? And im looking forward for an solution without permanent flash, as i sayn above.
Click to expand...
Click to collapse
After fashing twrp.img you boot into recovery and flash the file twrp.zip(the same series and name with file twrp.img)then reboot recovery.

TWRP 3.5.2 not working / Root trough magisk patched boot.img

Hey guys
I need your help to be happy having my phone rooted....
After update to android 11 I try to install TWRP 3.5.2 but the phone stuck on fastboot screen and TWRP not opens. So, I found an another way to root the device patching boot.img trough magisk, even it not pass on SafetyNet validation.
The root works but after reboot the phone lose it.
Some one have a solution for root on android 11?
Thanks for your help.

At the moment the TWRP in android 11 is giving problems when the mobile is encrypted does not work, you would have to make a backup and decrypt the phone to be able to use it. Any questions let me know

You need to decrypt your data and stay decrypted to get twrp working in A11.
And for the magisk part (assuming you don't wanna use twrp and stay encrypted), after booting using the patched boot image, open Magisk app, then select the Install option, then Direct Install. And that's it. You won't lose root access after reboot.

dewri21 said:
You need to decrypt your data and stay decrypted to get twrp working in A11.
And for the magisk part (assuming you don't wanna use twrp and stay encrypted), after booting using the patched boot image, open Magisk app, then select the Install option, then Direct Install. And that's it. You won't lose root access after reboot.
Click to expand...
Click to collapse
Are you referring to the patched boot.img you make yourself using Magisk? I've tried that myself, but the phone keeps being stuck at the boot logo (not a boot loop). I'm always forced to flash the original boot.img file to make the phone operational again.

Skyrider said:
Are you referring to the patched boot.img you make yourself using Magisk? I've tried that myself, but the phone keeps being stuck at the boot logo (not a boot loop). I'm always forced to flash the original boot.img file to make the phone operational again.
Click to expand...
Click to collapse
You patched the boot.img yourself? I mean did you get the proper image using payload dumper? It should have booted. Check it again and try. If that doesn't help you still, decryption is the way to go. I have been decrypted since a long time, with a working twrp.

dewri21 said:
You patched the boot.img yourself? I mean did you get the proper image using payload dumper? It should have booted. Check it again and try. If that doesn't help you still, decryption is the way to go. I have been decrypted since a long time, with a working twrp.
Click to expand...
Click to collapse
I thought TWRP wasn't/isn't fully supported on Android 11?
And yes, I used the proper proper image as I grabbed the entire package using Oxygen Updater, while using the patched version to update the OS. And if I didn't get the proper image, I would assume reverting back to the original boot.img (from the full package) wouldn't have worked.

Skyrider said:
I thought TWRP wasn't/isn't fully supported on Android 11?
And yes, I used the proper proper image as I grabbed the entire package using Oxygen Updater, while using the patched version to update the OS. And if I didn't get the proper image, I would assume reverting back to the original boot.img (from the full package) wouldn't have worked.
Click to expand...
Click to collapse
I found working patched boot at OnePlus forum, I guess it was patched with canary version of magisk. Maybe you can try.

Skyrider said:
I thought TWRP wasn't/isn't fully supported on Android 11?
Click to expand...
Click to collapse
It is, if and only if you're decrypted. TWRP doesn't support encryption on A11.

Updated to OOS 11.05.1.GM21AA, Magisk not working, TWRP too

Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?

¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Than
Click to expand...
Click to collapse
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
Click to expand...
Click to collapse
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there

hammered58 said:
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
Click to expand...
Click to collapse
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?

¿GotJazz? said:
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
Click to expand...
Click to collapse
1. Yes that is the app Iam talking about.
2. Will you lose data? I always do a format (after the down grade) so I lost data but I never tried it with out formating, it might work, you could try it and see what happens .If it acts strange then it will need a format.
3. Yes you install 11.04 via twrp
4. Yes you will get root but if you want twrp you will have to reinstall
Once you down grade install the oxygen updater, let it download the update , don't let it install it, you can then grab the update from your root directory as it doesn't hide it, then your good to go, you can extract the boot.img by using payload dumper, then take the boot.img and patch that with the magisk app . ( Just install the magisk app on your downgraded 11.04 you don't need root to run the app ) ,,Then after your thru upgrading to 11.05 and after setup just reboot to bootloader and run the magisk patched boot.img, ( fastboot flash boot boot.img) reboot and wait a minute for the magisk app to appear ,it will want to install and do a reboot . Then you can install twrp if you want.
This is how I did it and it worked, you may find a simpler way once you start doing it ,, hth

I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.

¿GotJazz? said:
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
Click to expand...
Click to collapse
Right now I have 11.05 installed and Iam rooted, tomorrow I will unroot and downgrade to 11.04 without wiping and let you know what happens iam curious myself

I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.

¿GotJazz? said:
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
Click to expand...
Click to collapse
I guess that's possible , I never thought of that, the only way to know is to do a fresh install only this time setup encryption then try to install magisk . But for now your rooted,, until the bug hits you or me to try another rom then we can start the whole thing over again,,