Database Info

Error message after update (OOS 5.1.9)

Hi guys,
I downloaded the latest OTA 5.1.9 (full zip), booted to TWRP, flashed the OTA, flashed TWRP 3.2.2.0, rebooted to recovery and flashed Magisk ... same procedure as the last OTA's, but know I get the message "There's an internal problem with your device contact your device manufacturer" on entering the ROM where I have to enter my PIN.
Redownloaded the ROM and flashed again, but the same message occurs. The phone seems to be working but I am a little bit worried.
I appreciate every help oder idea

dre-z said:
Hi guys,
I downloaded the latest OTA 5.1.9 (full zip), booted to TWRP, flashed the OTA, flashed TWRP 3.2.2.0, rebooted to recovery and flashed Magisk ... same procedure as the last OTA's, but know I get the message "There's an internal problem with your device contact your device manufacturer" on entering the ROM where I have to enter my PIN.
Redownloaded the ROM and flashed again, but the same message occurs. The phone seems to be working but I am a little bit worried.
I appreciate every help oder idea
Click to expand...
Click to collapse
It did that to me too. It is a pain but this worked for me to get rid of it.
1. Used a fastboot rom to install 5.1.8 (back to factory)
2. Completed setup
3. Did the whole thing to install TWRP.
4. Flashed Magisk
5. Restored by TWRP backup from before all this started
6. Let everything boot up and downloaded the full download for 5.1.9
7. Flashed the full 5.1.9 in TWRP, and flashed TWRP.
8. Reboot recovery
9. Flashed Magisk 16.4 (not the newer 16.6)
10. Boot to system
11. Use Magisk manager app to update Magisk to 16.6
Every time I have ever flashed Magisk 16.6 I get that same notice you get. Whenever I flash 16.4 and let it update Magisk from there everything is perfect.

tabletalker7 said:
It did that to me too. It is a pain but this worked for me to get rid of it.
1. Used a fastboot rom to install 5.1.8 (back to factory)
2. Completed setup
3. Did the whole thing to install TWRP.
4. Flashed Magisk
5. Restored by TWRP backup from before all this started
6. Let everything boot up and downloaded the full download for 5.1.9
7. Flashed the full 5.1.9 in TWRP, and flashed TWRP.
8. Reboot recovery
9. Flashed Magisk 16.4 (not the newer 16.6)
10. Boot to system
11. Use Magisk manager app to update Magisk to 16.6
Every time I have ever flashed Magisk 16.6 I get that same notice you get. Whenever I flash 16.4 and let it update Magisk from there everything is perfect.
Click to expand...
Click to collapse
Thank you very much, the tip with flashing magisk 16.4 worked! I didn't need to go back, I just reflashed 5.1.9 without magisk and the error was gone.

Hi, I got the same problem.
Until I flashed my custom kernel ElementalX the messege disapeared

Will it work only to flash 16.4 over 16.6 or uninstall 16.6 and then flash 16.4?

why dont you guys stick with stabe 16.0?

I did uninstall of 16.6 and then install 16.4, no error message anymore. Didn't flash directly over it.

Tried as you said but still got that message.

Deacon-Frost said:
Will it work only to flash 16.4 over 16.6 or uninstall 16.6 and then flash 16.4?
Click to expand...
Click to collapse
When you install the update to 5.1.9 you have to reflash Magisk. I just used Magisk 16.4 when I did it.

I can confirm completely uninstalling magisk and then installing 16.0 with an upgrade to 16.6 solves the error

Try this.
https://forum.xda-developers.com/sho...&postcount=386
I had the same problem and this fixed it for me.

The easiest way is explained by XDA user "airtower", read his response at:
https://forum.xda-developers.com/on...-oneplus-6-t3794232/post77104551#post77104551
Thanks!

This hint was really helpful and is highly appreciated. The message is gone. :thumbup:

Uninstall in Magisk app, select restore images. Do not reboot and install it via app again and now you can reboot that's it. very simple

Guys just flash magisk 16.6. It will work without the error message. Just after you flash, boot into system. Then go into magisk manager and click on Uninstall and then Restore Images. Then right away, without rebooting, install using the Direct Install method and making sure that both of the "preserve" options are checked in Advanced Settings before installing it.

How to upgrade rooted/unlocked OOS 9 to latest without losing anything?

I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3

https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
Post #3 has the instructions you need
Long story short you need to flash the update via TWRP.

unknown00 said:
I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3
Click to expand...
Click to collapse
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system

tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk

RASTAVIPER said:
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?

unknown00 said:
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?
Click to expand...
Click to collapse
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.

Like above.
Flashing ROM Will also flash stock recovery so after ROM you need to flash twrp again,if you reboot without it it's lost.
Also why magisk isn't flashed right away is because: when you choose to reboot to twrp after the twrp flash it Will change slot, this way you Will get magisk on the correct slot.
All this can be done from the OS.
Install the ROM upgrade as usual,don't reboot.
Open magisk app
Search for a module a/b twrp (you Will only find one module) and install it.ndont reboot just yet.
Go to main screen of magisk
Press install, install, install to inactive slot (after OTA). After this install you can reboot.
Both works, I find the twrp way to be more convenient

I don't about stable i am on open beta 10 i root every beta without twrp using patch boot image i got update every time around 1.5 GB because i am rooted after update i just lose root everything same before update phone not wipe anything

I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).

akxak said:
I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).
Click to expand...
Click to collapse
No need to reinstall TWRP in the first method?

unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
I do not have TWRP installed, it is basically not necessary as OOS can be updated with the settings/manual update tool and Magisk can be reinstalled via Magisk manager.
I had to use TWRP solely to downgrade to Magisk 17.2 from Magisk 18 as this cannot be done with Magisk Manager. But for that purpose, it's enough to temporarly make TWRP available via fastboot boot command without permanently installing it.
If you have TWRP and want to keep it, that easy process doesn't work to upgrade the OS.

unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
If you wanna keep TWRP you do the way I described few posts up.....

tabletalker7 said:
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.
Click to expand...
Click to collapse
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.

thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.

tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.

thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
thejase said:
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.
Click to expand...
Click to collapse
As promised, I'm writing back with my findings. I believe some enabled module in magisk was the issue. What I did was uninstall magisk 18 with the latest uninstaller. Thinking it was V18 itself that was the problem, I then proceeded to install v17.3 on both slots (reboot to recovery in betweene). This worked and booted! It started to occur to me that I had not disabled any of my modules before installation of the rom/magisk. This is a big mistake as a lot of magisk modules are still using old formatting and cause new installations to fail if left enabled. Since an uninstall also disables all modules, I believe using 17.3 was not necessarily the solution but rather either disabling modules before an install, or uninstalling whatever version magisk was installed to begin with (which essentially disables/uninstalls those modules anyway). After installing 17.3 and getting it to boot, I just updated via magisk manager to v18 with no issues to speak of! Now comes the part where I need to remember all the installed modules I had and test them one by one.
For uninstallation of modules in twrp, you can use https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165 Or https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
I hope this helps someone!

URGENT: disabling magisk made OP6 stuck on bootloader, How to recover from it?

I had latest magisk (stable version) installed and tried to disable it from magisk manager->uninstall->restore images.
when i restarted the phone it stuck on bootloader screen.
I tried to got to twrp recovery mode and it's stuck on the flash screen.
Why would magisk manager put a button which is not working at all and bricks the phone? Please guide me what to do.

JerryGoyal said:
I had latest magisk (stable version) installed and tried to disable it from magisk manager->uninstall->restore images.
when i restarted the phone it stuck on bootloader screen.
I tried to got to twrp recovery mode and it's stuck on the flash screen.
Why would magisk manager put a button which is not working at all and bricks the phone? Please guide me what to do.
Click to expand...
Click to collapse
Maybe you did something wrong and this isn't Magisk fault ?

Go to twrp and wipe system and vendor DO NOT REBOOT, flash OOS zip and twrp again, and it shall work,
NOTE: you will NOT lose any files or data

J0nhy said:
Go to twrp and wipe system and vendor DO NOT REBOOT, flash OOS zip and twrp again, and it shall work,
NOTE: you will NOT lose any files or data
Click to expand...
Click to collapse
too late for me i wiped all data. Thanks though, it shall help future readers.

next time, before wipe, try to flash magisk uninstaller first

Try to flash stock boot image.

Updating OOS Ota and loosing Root

Phone currently rooted and using xxxNolimits rom and Smurf kernel
Update available and getting below warning.
So if I update do I have to start from scratch again and re root.
So download update and then don't reboot system but reboot to twrp and flash Magisk again or do I flash updates and then Magisk
Confused dot com

Come on man, any amount of threads and answers to this throughout the forum via the search box.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368

hallo dare said:
Come on man, any amount of threads and answers to this throughout the forum via the search box.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
Click to expand...
Click to collapse
Fair cop on my behalf?
Just was not sure what to remove in Magisk as have few modules installed including substratum, you tube vanced theme, systemless hosts and xxxNolimits.
Take it just first 2 I remove

I always flash TWRP as a magisk module before rebooting, reboot into recovery, flash TWRP again, reboot into recovery again (unnecessary I'm sure, but i'm paranoid), then flash magisk, reboot into system and good to go.

funkyirishman said:
Fair cop on my behalf
Just was not sure what to remove in Magisk as have few modules installed including substratum, you tube vanced theme, systemless hosts and xxxNolimits.
Take it just first 2 I remove
Click to expand...
Click to collapse
To be sure to be sure i always remove all modules and reboot phone before doing any updates.

aNGERY said:
I always flash TWRP as a magisk module before rebooting, reboot into recovery, flash TWRP again, reboot into recovery again (unnecessary I'm sure, but i'm paranoid), then flash magisk, reboot into system and good to go.
Click to expand...
Click to collapse
That's what I've done wrong and lose twrp after updates. I need to reboot to recovery with adb commands and install twrp.

sportytony said:
That's what I've done wrong and lose twrp after updates. I need to reboot to recovery with adb commands and install twrp.
Click to expand...
Click to collapse
TWRP is installed to boot partition on this device (no discrete recovery partition). So anytime you update, the boot partition is overwritten with a new stock boot partition (therefore, no TWRP). To update and stay rooted and with TWRP, simply OTA update, do NOT reboot. Go to Magisk Manager. Flash TWRP installer zip as if it were a Magisk module. It will say you are unrooted, so (again, in Magisk Manager) install Magisk again, picking the option "Install to inactive slot (after OTA)". Reboot, and you should be updated and still rooted.

That's how I update everytime. But sometimes just for hahas, I've rebooted to recovery, just because, and it would reboot to factory recovery , and twrp wasn't there. I was rooted, just no twrp. ( I know weird)

[SOLVED] Magisk install methods suddenly no longer work

Hi all,
Yesterday I was messing around with V4A and following the final installation steps my phone got stuck in fastboot. To fix it I did the following:
1. I extracted the stock boot.img from my current OS version (10.3.12) and flashed it to boot_a and boot_b using fastboot. This restored the phone's ability to boot.
2. I booted the phone and went into the Magisk app to disable/unhide as much as possible and uninstalled the V4A app.
3. Rebooted into fastboot and booted into TWRP to remove Magisk, V4A and Vanced stuff from data/adb with the file manager.
4. Booted and flashed various combinations of TWRP versions (Mauronofrio, Bluspark) and Magisk (from 19.4 to 23.0). TWRP flashes fine and allows system to boot, but as soon as Magisk is flashed and a reboot is tried into system, it gets stuck on bootloader again and I have to repeat step 1.
(5. Tried patching stock boot.img file with the Magisk app. Same results as step 4.)
Does anyone here know what might be wrong? Is there another method I can try to regain Magisk without losing data?
Thanks in advance!
EDIT: really at a loss here. Idk why but as soon as magisk is flashed, the system refuses to boot. Without flashing magisk, system boots fine – am typing from it now. I figured at first that it had to do with remnants of AML, V4A and other Magisk modules not being properly removed, but I've removed those through TWRP file manager.
Really hoping one of you can point out something I've missed or think of something else I can try.
EDIT: solved! See update below.

UPDATE: solved it by forcing a local upgrade of the full OTA through phone settings (same version as mentioned above), causing it to switch slots. On the other slot, the system managed to boot after flashing TWRP and Magisk (latest versions).