Database Users

Disable security warning at boot for MHC191

It seems to be from searching you can use a custom vendor image? I'm on stock with root. Everything went smooth as butter but i'm still unclear on this as i know custom roms dont have it i believe. Is there a thread i'm missing where these are listed or is there anything i can flash? It's not a big deal whatsoever but the ocd in me felt compelled to figure it out lol.

Download factory image for what build your on, unzip and flash vendor.img in twrp 3001 done.
Sent from my Nexus 6P using Tapatalk

SM210 said:
Download factory image for what build your on, unzip and flash vendor.img in twrp 3001 done.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks. I didn't realize that's all i had to do. I spent half the day setting everything up how i wanted and didn't want to mess it all up. Thank goodness for backups now.
Update: I flashed the vendor image in twrp in vendor and the corrupt message at boot is still there. Maybe i wasn't clear. I'm talking about the locked boot loader message

If you're running stock you have to re-lock the bootloader to get rid of that message on power on.

Zaphon said:
If you're running stock you have to re-lock the bootloader to get rid of that message on power on.
Click to expand...
Click to collapse
Ok. There seems to be a workaround for everything once your rooted so i thought maybe there was something for this also.

bckrupps said:
Thanks. I didn't realize that's all i had to do. I spent half the day setting everything up how i wanted and didn't want to mess it all up. Thank goodness for backups now.
Update: I flashed the vendor image in twrp in vendor and the corrupt message at boot is still there. Maybe i wasn't clear. I'm talking about the locked boot loader message
Click to expand...
Click to collapse
Are you talking about the orange "your device can't be checked for corruption" message or the red "your device is corrupt message"? The orange one is standard if you have an unlocked bootloader, there's nothing you can do about it apart from locking the bootloader. I'd advise dealing with it though, it's better to deal with that orange message than to deal with the potential consequences of having as locked bootloader when something goes wrong.

Heisenberg said:
Are you talking about the orange "your device can't be checked for corruption" message or the red "your device is corrupt message"? The orange one is standard if you have an unlocked bootloader, there's nothing you can do about it apart from locking the bootloader. I'd advise dealing with it though, it's better to deal with that orange message than to deal with the potential consequences of having as locked bootloader when something goes wrong.
Click to expand...
Click to collapse
yeah that's what i was talking about and i agree. i just thought maybe there was a work around i may be missing. Thanks everyone for the help. Been flashing for years. This one had me lost. Nexus 6p is one incredible phone. I always loaded custom roms right away on Samsung devices but with xposed and root this is more than enough running stock. I even skipped a toolkit for the first time and battled windows running on my mac. not fun lol.

All customs Roms also have this. Dirty unicorns, resurrection remix and cm. I understood in op what you meant. That message can also alert to if someone messed with your phone, it'll change to red and say your device is corrupt. I think when /system is modified. I got that once or so.

Phone won't boot

I have the Qualcomm version, XT1768. LOS 14 from squid as well as his TWRP. I was downloading movies when the screen had just turned off. I thought it was just screen timeout. I tried to turn it back on but it wouldn't. Turned it off, won't boot into LOS, or TWRP, only boot loader. Not ready to give up and go back to stock just yet. Any help would be appreciated, Thanks

codyalan said:
I have the Qualcomm version, XT1768. LOS 14 from squid as well as his TWRP. I was downloading movies when the screen had just turned off. I thought it was just screen timeout. I tried to turn it back on but it wouldn't. Turned it off, won't boot into LOS, or TWRP, only boot loader. Not ready to give up and go back to stock just yet. Any help would be appreciated, Thanks
Click to expand...
Click to collapse
Given the symptoms seems likely your device experienced a hardware failure. In your shoes the first thing I'd try is booting (not flashing/installing) a TWRP image assuming the bootloader is unlocked. If no joy it's probably game over. There is nothing in LOS (or any legitimate custom rom) that would cause this behavior.

Davey126 said:
Given the symptoms seems likely your device experienced a hardware failure. In your shoes the first thing I'd try is booting (not flashing/installing) a TWRP image assuming the bootloader is unlocked. If no joy it's probably game over. There is nothing in LOS (or any legitimate custom rom) that would cause this behavior.
Click to expand...
Click to collapse
Yeah, tried that this morning, didn't work. Just flashed stock and them back to LOS

codyalan said:
Yeah, tried that this morning, didn't work. Just flashed stock and them back to LOS
Click to expand...
Click to collapse
Whatever happened is likely to reoccur (unless you were doing something other than described). Good luck.

Well, it's hard bricked

I was able to root my 6T with no problem. Was even able to run the XXX No Limits OnePlus 6 rom with no issues. However overnight the pending software update installed itself. When I tried to reboot the phone got the screen that says "your device is corrupt". Went and tried to flash the official stock OOS rom and now its hard bricked. Phone won't even power on. Is there anyway to fix it, or am I just F'ed in the A?

For clarity, you were running a OP6 rom on the 6T?

Krunk_Kracker said:
For clarity, you were running a OP6 rom on the 6T?
Click to expand...
Click to collapse
XxX made a 6/6T rom.

The rom was made for the 6 and 6T. It flashed and booted with no problems. Multiple reboots no issues. Wasn't until the software update installed itself I had issues

Does a computer recognize it at all, even with any weird key combinations?

skinzy98 said:
Does a computer recognize it at all, even with any weird key combinations?
Click to expand...
Click to collapse
After messing with it some more was finally able to get it to boot. Had to hold down power+volume up for like 3 minutes. Now that I am able to get in fastboot going to try this: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516

blue5055 said:
After messing with it some more was finally able to get it to boot. Had to hold down power+volume up for like 3 minutes. Now that I am able to get in fastboot going to try this: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
I had pretty much the exact same issue Saturday, and I was t even rooted or unlocked bootloader so I know how you feel

There's an option to turn off automatic updates, for future reference.

blue5055 said:
I was able to root my 6T with no problem. Was even able to run the XXX No Limits OnePlus 6 rom with no issues. However overnight the pending software update installed itself. When I tried to reboot the phone got the screen that says "your device is corrupt". Went and tried to flash the official stock OOS rom and now its hard bricked. Phone won't even power on. Is there anyway to fix it, or am I just F'ed in the A?
Click to expand...
Click to collapse
Have you tried to flash the fastboot Rom in the xda thread?
Enviado desde mi ONEPLUS A6013 mediante Tapatalk

blue5055 said:
After messing with it some more was finally able to get it to boot. Had to hold down power+volume up for like 3 minutes. Now that I am able to get in fastboot going to try this: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
Using the tool above I was able to unbrick and return to stock. For anyone else bricked, that tool will help you

Your device is corrupted. It can't be trusted and ...

After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???

azzinder said:
After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
Click to expand...
Click to collapse
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724

azzinder said:
After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
Click to expand...
Click to collapse
You're not waiting long enough.
And by the way it tells you to press the power button to PAUSE booting.
It's only a few second wait (possibly one second longer than the default unlocked message on other devices). I just timed it. It's 8 seconds. A regular device will display that message for 3-4 seconds.
It just means that your bootloader is unlocked.
Sent from my ONEPLUS A6013 using Tapatalk

genbu said:
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
Click to expand...
Click to collapse
Had this issue on my op6. This solution fixed it for me. not sure if we have this tool for the 6t yet. If the message is orange then it's the unlocked bootloader message. If it's in red it's the corrupt message and you gotta hit the power button twice to boot.

The message i get is in RED color. Not in ORANGE.
And yes if you press twice the power button it boots normally.
My question is about how to get rid of this!!!
If for some reason the device is gonna reboot -like in Settings-> Utilities-> Scheduled power on/off- it wont boot until I get action...

Fear!!!
genbu said:
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
Click to expand...
Click to collapse
I am thinking to try this solution but i am scared...
This tool is gonna try to install Oxygen os Oreo for the OP6 as far as I understand.
But the OP6T never had this.
I wonder that maybe it wont boot after process and if it boots gonna refuse to upgrade to Oxygen OS Pie for OP6T
:confused
***Just found the OP6T version here***
As soon as i find a pc with Windows installed i'll try it!!!

I have the same issue and have a remote session booked with OP support today.
Hopefully I will be able to grab a copy of MSMTool for the 6T and share it.

azzinder said:
I am thinking to try this solution but i am scared...
This tool is gonna try to install Oxygen os Oreo for the OP6 as far as I understand.
But the OP6T never had this.
I wonder that maybe it wont boot after process and if it boots gonna refuse to upgrade to Oxygen OS Pie for OP6T
:confused
***Just found the OP6T version here***
As soon as i find a pc with Windows installed i'll try it!!!
Click to expand...
Click to collapse
And password

iaTa said:
I have the same issue and have a remote session booked with OP support today.
Hopefully I will be able to grab a copy of MSMTool for the 6T and share it.
Click to expand...
Click to collapse
Waiting patiently for news...

azzinder said:
Waiting patiently for news...
Click to expand...
Click to collapse
Rescheduled to tomorrow

https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Done

Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter

This works! It is a lot easier than the MSM download tool solution. However, I wonder if it just mutes the notification, or solves the problem indeed?
I flashed a TWRP backup afterwards and that did not go well. I wonder if that could be caused bij the corrupt problem?
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Doesnt working for me. after reboot also i can see same error. however i can boot after twice pressing on power. i do not want to use Msm tool as it will format data. seems no other way as of now

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Hey that's amazing! I think this has finally solved this for me on my OnePlus 6. I was perfectly content to just put up with that warning forever, but this seems to have cured it ... And simple too! Thanks ?

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Thanks, this worked.

That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.

vikram.mohal said:
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
Click to expand...
Click to collapse
i had this happen when i went to update to 9.0.13. ended up backing up to usb otg, reflashing the full update via msm tool, and having to unlock bl again, reflash twrp again, installing magisk again, etc. then, and only then was my device no longer corrupt. i tried many things prior to that, but this was my only fix long term.
ive heard its die to A/B having different security patches, but reflashing both A/B with stock full 9.0.13 did not stop the issue. only msm tool reflashing to 9.0.12 did. and i then did the same on my second partition for good measure.
as far as trying to run decrypted, unless im remembering wrong, unlike the op6, the op6t will not abide that without the corrupted message unless i missed progress. id love that personally, but last i had read here it made op6t unstable. which sucks bonkey dalls.

vikram.mohal said:
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
Click to expand...
Click to collapse
No the device is not corrupted. Unlocked bootloader warning vs the device is corrupt are 2 different things. My bootloader ia unlocked since the day 1 and never had the corrupt warning until I flashed OOS 9.0.5. The step above resolved the device is corrupt issue.
---------- Post added at 07:26 AM ---------- Previous post was at 07:22 AM ----------
kitcostantino said:
i had this happen when i went to update to 9.0.13. ended up backing up to usb otg, reflashing the full update via msm tool, and having to unlock bl again, reflash twrp again, installing magisk again, etc. then, and only then was my device no longer corrupt. i tried many things prior to that, but this was my only fix long term.
ive heard its die to A/B having different security patches, but reflashing both A/B with stock full 9.0.13 did not stop the issue. only msm tool reflashing to 9.0.12 did. and i then did the same on my second partition for good measure.
as far as trying to run decrypted, unless im remembering wrong, unlike the op6, the op6t will not abide that without the corrupted message unless i missed progress. id love that personally, but last i had read here it made op6t unstable. which sucks bonkey dalls.
Click to expand...
Click to collapse
Yeah I agree its something to do with the slot A and B. I was running the phone with unlocked bootloader since day 1 and had flashed multiple twrp updates, kernels etc and never had the issue. It's when i recently flashed OOS 9.0.5 and then twrp on it is when this started.
Not sure about OP6T but on my OP6 the terminal commands helped.

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
This worked on my 6T ! Thanks !

Didn't realize I was upgrading to Android 11, magisk_patched.img bootloops, need help

When I downloaded the lasted OTA update for my OnePlus 8 Pro I thought it was just another hotfix and didn't realize it was a Big Deal Android 11 update. I tried using the normal OTA upgrade processed and kinda screwed myself.
After trying to install in the inactive slot the way I normally upgrade OTA, I ended up bootlooping. So I downloaded the recovery image and tried patching Magisk the long adb way. It wasn't until later that I realized I had to be on the beta channel. I didn't know you needed to disable modules when you upgrade to Android 11, so they might still be in play, but I don't know how to check. I've tried a bunch of stuff without much luck. Here's where I'm at now:
1) Bootloader is unlocked
2) I can get into Recovery Mode fine
3) I can flash the default/unpatched boot.img for my build and boot up fine, but there's no root, and wifi doesn't work and cellular data is really flakey (even though I normally have fine reception here).
4) From an unpatched boot.img I switched Magisk Manager to the beta channel and installed v21.1. Then I patched boot.img to make a new magisk_patched.img from the beta channel.
5) When I try to fastboot flash magisk_patched.img to slot A I bootloop.
6) When I try to fastboot boot magisk_patched.img I get stuck on the red dot with 2 white dots orbiting it for seemingly forever.
7) I think something is wrong in my slot B because I mostly just get stuck in fastboot. This might be an unrelated problem from a while back though.
8) When I try to run adb wait-for-device shell magisk --remove-modules, I just get an error message about magisk not being found.
What can I do to get back to a rooted working patched magisk without wiping all my data and starting from scratch?

I've honestly never seen anyone do this before so I'm curious as to how you'll recover from this
My thought are MSM but you may be able to boot. Problem is the magisk modules are still in play.
The adb command may not work for removal as you may not get that far.
Did the installation go through ok? It was just booting that failed?
Could maybe try to wipe system via recovery and go from there.
I'm not too sure buddy.
Keep us posted how u get on.
Edit: Try to boot the boot img.
What model are you on? BA ? I have the boot images in my guides in the guides section. Feel free to take what you need.

dladz said:
My thought are MSM but you may be able to boot. Problem is the magisk modules are still in play.
Click to expand...
Click to collapse
What is MSM?
dladz said:
Did the installation go through ok? It was just booting that failed?
Click to expand...
Click to collapse
You mean the result of fastboot flash magisk_patched.img? Yeah, that has finished fine every time. I'm either stuck bootlooping or booting up never finishes.
dladz said:
Could maybe try to wipe system via recovery and go from there.
Click to expand...
Click to collapse
Doesn't that delete all my data? I've only tried wiping the cache so far.
dladz said:
Edit: Try to boot the boot img.
Click to expand...
Click to collapse
Do you mean fastboot boot magisk_patched.img? That just spins forever and never finishes booting.
Flashing back to the unpatched boot.img boots up fine, but my wifi won't turn on and my cellular data is flakey (even though I usually have fine reception here).
dladz said:
What model are you on? BA ? I have the boot images in my guides in the guides section. Feel free to take what you need.
Click to expand...
Click to collapse
I have the US hardware, so I extracted the boot.img from 11.IN21AA, which was the same number that showed up after the OTA was applied.

I dunno, I tried a bunch of different stuff, ended up bricking it. Restored it with MSM to Android 11, then unlocked the bootloader, and tried to flash a fresh magisk_patched.img and it refused to boot in the same way, even though everything was completely fresh.
Are we sure the Magisk beta channel is working right now?

Ecna said:
I dunno, I tried a bunch of different stuff, ended up bricking it. Restored it with MSM to Android 11, then unlocked the bootloader, and tried to flash a fresh magisk_patched.img and it refused to boot in the same way, even though everything was completely fresh.
Are we sure the Magisk beta channel is working right now?
Click to expand...
Click to collapse
There hasn't been anyone stating issues.
Are you using lucky patcher?

dladz said:
There hasn't been anyone stating issues.
Are you using lucky patcher?
Click to expand...
Click to collapse
I don't know what lucky patcher is, so I guess not?
Turns out the wifi problem was happening on stock anyway. And EdXposed doesn't support 11 yet either. So I flashed back to 10.5.13 before bothering to set up all my apps. I'm gonna wait a bit longer for until 11 is more ripe.

Ecna said:
I don't know what lucky patcher is, so I guess not?
Turns out the wifi problem was happening on stock anyway. And EdXposed doesn't support 11 yet either. So I flashed back to 10.5.13 before bothering to set up all my apps. I'm gonna wait a bit longer for until 11 is more ripe.
Click to expand...
Click to collapse
Ah ok, that's fine if you don't know what lucky patcher is then that's a good thing

Yes, that patched boot image failed me. Can't boot. Can't find stock to flash. Bumbed.

dladz said:
Ah ok, that's fine if you don't know what lucky patcher is then that's a good thing
Click to expand...
Click to collapse
Hi dladz, can you please give me more info on lucky patcher and how it could affect things. I'm an avid lucky patcher user, and recently had issues with phone not booting, had to do a factory reset. (I wonder if lucky patcher was some how the culprit)

hbhorat said:
Hi dladz, can you please give me more info on lucky patcher and how it could affect things. I'm an avid lucky patcher user, and recently had issues with phone not booting, had to do a factory reset. (I wonder if lucky patcher was some how the culprit)
Click to expand...
Click to collapse
Don't know if you know this or not but you can't even discuss LP on XDA so I'm afraid I can't..
All I know is that it's dodgier than Donald trump's hair and should be avoided like an old woman's waffle.
If you've had problems and lucky patcher was installed that would be top of my list of culprits.
Bootloops, corruption, force closes to name but a few issues, it probably mines for coin using your phone's processor when it's not in use and god only knows what it does with your data, if that's the price of free apps? Id rather pay for them, my data is with more than any app.
Soz mate, that's all I can offer.
Just avoid it.. :good: