[Tut][Jan-update]Fix DTBO message "There's an internal problem with your device"
Warning: I'm not responsible for any bricks or abnormalities, this tutorial is based on my personal trial, I DONT OWN MAGISK It's developed by @topjohnwu and this tutorial is only for the full 8.1 (api27) December 05
Disclaimer: on recent updates topjohnwu released magisk boot scripts that clears avb-verity to allow modifications on the vendor partitions and all of that was possible by patching dtbo automatically using magisk manager and google developers assigned any unclear vendor modifications will indicate a message "There's an internal problem with your device. Contact your manufacturer for details"
make sure you have the latest magisk 14.5 installed using topjohnwu's tutorial
- uninstall magisk manager from your phone
- extract original dtbo.img from google's factory image 8.1 - 05 december's release
-reboot to bootloader using key combination vol- power or using adb command
-install dtbo using fastboot commands
-reboot the system
-the message is gone
- install magisk-manager 5.4.0
- open the magisk manager and go to settings and turn-off update notification option
Reminder: If you are going to update magisk manager to 5.4.2 or later then dtbo will be automatically patched and you will see the message again the next reboot, please be aware that this is a temporairly fix until topjohnwu makes dtbo patch optional, so far modules , su and scripts are working like charm
-------------------------------------------------------------------------------------------------------------------------------------------------------
Jan Update
Hello Pixel Team, There have been some changes done recently
"there seems to be some sort of confusion about a/b slots, but Google made this method in order to avoid a catastrophic failure during an OTA update.
so for example: partitions like "radio, vendor, boot, bootloader and system" are occupied twice, so if boot.img is 50MB then it will be 50*2 = 100 which is installed on both slots (A/B).
DTBO slots dilemma solution:
Simply if your system is running on slot A which it is by default, then flash the DTBO to slot A.
Now let's wrap this up by saying we're glad that topjohnwu added new preserve option but since he updated magisk to 15.2 there seems to be a problem with that ,The flashable magisk triggers a script noticed in patchDTBO() script to automatically patch the DTBO.
Therefore I advise you to install Magisk 15.1 for the moment with the latest magisk manager if you want, that's also temporarily until the OP fix the issue ,definitely make sure you tick Preserve AVB option.
Make sure you also follow the same instructions in flashing the stock DTBO from Jan+ factory images
Bonus tip : to avoid notifications about updating, change the channel to custom and leave it blank in the magisk manager settings : download link
Cheers
Warning: I'm not responsible for any bricks or abnormalities, this tutorial is based on my personal trial, I DONT OWN MAGISK It's developed by @topjohnwu and this tutorial is only for the full 8.1 (api27) December 05
Disclaimer: on recent updates topjohnwu released magisk boot scripts that clears avb-verity to allow modifications on the vendor partitions and all of that was possible by patching dtbo automatically using magisk manager and google developers assigned any unclear vendor modifications will indicate a message "There's an internal problem with your device. Contact your manufacturer for details"
make sure you have the latest magisk 14.5 installed using topjohnwu's tutorial
- uninstall magisk manager from your phone
- extract original dtbo.img from google's factory image 8.1 - 05 december's release
-reboot to bootloader using key combination vol- power or using adb command
Code:
adb reboot bootloader
Code:
fastboot flash dtbo dtbo.img-the message is gone
- install magisk-manager 5.4.0
- open the magisk manager and go to settings and turn-off update notification option
Reminder: If you are going to update magisk manager to 5.4.2 or later then dtbo will be automatically patched and you will see the message again the next reboot, please be aware that this is a temporairly fix until topjohnwu makes dtbo patch optional, so far modules , su and scripts are working like charm
-------------------------------------------------------------------------------------------------------------------------------------------------------
Jan Update
Hello Pixel Team, There have been some changes done recently
"there seems to be some sort of confusion about a/b slots, but Google made this method in order to avoid a catastrophic failure during an OTA update.
so for example: partitions like "radio, vendor, boot, bootloader and system" are occupied twice, so if boot.img is 50MB then it will be 50*2 = 100 which is installed on both slots (A/B).
DTBO slots dilemma solution:
Simply if your system is running on slot A which it is by default, then flash the DTBO to slot A.
Now let's wrap this up by saying we're glad that topjohnwu added new preserve option but since he updated magisk to 15.2 there seems to be a problem with that ,The flashable magisk triggers a script noticed in patchDTBO() script to automatically patch the DTBO.
Therefore I advise you to install Magisk 15.1 for the moment with the latest magisk manager if you want, that's also temporarily until the OP fix the issue ,definitely make sure you tick Preserve AVB option.
Make sure you also follow the same instructions in flashing the stock DTBO from Jan+ factory images
Bonus tip : to avoid notifications about updating, change the channel to custom and leave it blank in the magisk manager settings : download link
Cheers
Last edited:
