[Tut][Jan-update]Fix DTBO message "There's an internal problem with your device"

[edjanx]

Yep, I knew about the second zip file and that's where I didn't find it unless I was just hallucinating LOL! I could dig around and try to find a screenshot later

Thanks,
Janx

Well I have to do it again so I can start with January, and per attached image I do not see a dtbo.img file in the January image extract.

 

[Badger50]

Well I have to do it again so I can start with January, and per attached image I do not see a dtbo.img file in the January image extract.

Oh that's weird! Maybe download it again and check

 

[samteeee]

Well I have to do it again so I can start with January, and per attached image I do not see a dtbo.img file in the January image extract.

Those files are for a Pixel 1 XL (Marlin) device!

 

[edjanx]

Those files are for a Pixel 1 XL (Marlin) device!

Right, that's what I have. I assume based upon your reaction that it only applies to pixel 2? I thought it was just a A/B boot thing.

 

[elliwigy]

Well I have to do it again so I can start with January, and per attached image I do not see a dtbo.img file in the January image extract.

u kno thats for marlin right lol

 

[elliwigy]

Right, that's what I have. I assume based upon your reaction that it only applies to pixel 2? I thought it was just a A/B boot thing.

lol seein as how its a pixel 2 xl thread and u dont have a dtbo id say unfortunately ur outta luck

 

[edjanx]

lol seein as how its a pixel 2 xl thread and u dont have a dtbo id say unfortunately ur outta luck

Okay, sorry I was paying too close attention to try to solve the issue with the screen warning to contact your manufacturer, as that impacts pixels as well as pixel 2s

 

[elliwigy]

Okay, sorry I was paying too close attention to try to solve the issue with the screen warning to contact your manufacturer, as that impacts pixels as well as pixel 2s

np.. i understand lol its annoying but not really impacting

 

[Neverendingxsin]

I currently have magisk manager 5.5.5 on my 2XL and still get the message, version 5.5.4 was supposed to fix the on boot dtbo detection that triggers the message.

Should I still do this? Would I need to uninstall magisk manager since my version fixed it? Also do I just flash by default to slot A? I'm on January ota and stock rooted.

I'm using magisk 15.2 and not 15.3 if that makes a difference.

 

[DrSeussFreak]

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

Just rooted today, and running Magisk 5.5.5, so it auto-patched dtbo and had me reboot, and the error is back. I read through this thread, and I may have missed it, but is there a solution for this?

 

[Badger50]

Just rooted today, and running Magisk 5.5.5, so it auto-patched dtbo and had me reboot, and the error is back. I read through this thread, and I may have missed it, but is there a solution for this?

Although the message does not cause any harm, many find it annoying. What type of device and OS do you have? You may have to flash your stock dtbo and boot images to make it go away.

 

[DrSeussFreak]

Although the message does not cause any harm, many find it annoying. What type of device and OS do you have? You may have to flash your stock dtbo and boot images to make it go away.

Yea, it is only for my OCD that I care. Pixel 2 XL with 8.1.

I flashed the stock dtbo but magisk modified it automatically

---------- Post added at 02:12 PM ---------- Previous post was at 01:41 PM ----------

I'm actually running into a new issue now, which is after I flash the stock dtbo, everything works, but once Magisk updates it and has me reboot (which I cannot stop from happening), my Project Fi eSim continually loses connection (I see it connect and drop signal non-stop). If I flash to stock again, everything is fine.

 

[Badger50]

Yea, it is only for my OCD that I care. Pixel 2 XL with 8.1.

I flashed the stock dtbo but magisk modified it automatically

Then maybe try Flash kernel. I'm running the same device as you, with magisk 5.5.5 app, and 15.3 zip. And I never get the message anymore on any custom kernel.

 

[DrSeussFreak]

Then maybe try Flash kernel. I'm running the same device as you, with magisk 5.5.5 app, and 15.3 zip. And I never get the message anymore on any custom kernel.

Which *.img file do I need for the kernel? Is it "fastboot flash kernel *.img"?

 

[Badger50]

Which *.img file do I need for the kernel? Is it "fastboot flash kernel *.img"?

If your talking the stock kernel, then it's fastboot flash boot boot.img

If your talking custom kernel, then just flash the kernel zip in twrp ?

 

[DrSeussFreak]

Running stock, reflashed boot.img, grabbed the updated patched_boot.img, flashed it, and no luck, same issue. As soon as dtbo is updated by magisk, eSim breaks

 

[Badger50]

Running stock, reflashed boot.img, grabbed the updated patched_boot.img, flashed it, and no luck, same issue. As soon as dtbo is updated by magisk, eSim breaks

Are you using twrp at all?

 

[DrSeussFreak]

I went without it, didn't see a need. That said, if needed, I can install it

 

[Badger50]

I went without it, didn't see a need. That said, if needed, I can install it

I think it'll be much easier in my opinion.
Fastboot the twrp.img
That'll take you to temporary twrp
Once there, flash the twrp.zip, if you want it to stick.
Then flash the custom kernel zip(so much better than stock)
Then flash the magisk 15.3 zip
Reboot, done.

 

[DrSeussFreak]

Let me ask though, what is it I would be getting from doing this? Wouldn't magisk just patch dtbo once I am done with all that?