Unlocked Bootloader leads to System Integrity being Compromised?

Search This thread

binary**#

Senior Member
Mar 20, 2014
52
43
new delhi
So Moto One Action keeps on surprising every now and then. The latest addition to it is the System Integrity is Compromised message. This is how I end up doing so:

https://photos.app.goo.gl/8Q5xZXTzGWGVMZX48

  1. Unlocked the device's bootloader.
  2. Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
  3. Then I had to unroot my device (for some reason), so flashed the stock firmware using Moto Smart Assistant Tool. But kept the device's bootloader in an unlocked state.
  4. Now I have a stock ROM on my device, unrooted without any modification to the /system partition. The only modification is the unlocked bootloader.

Then I went to System > Advanced > System Updates and then got greeted with the message that I am no longer eligible for software updates. Although not an issue as I could still flash the stock firmware by one way or the other, I am just curious to know whether it is indeed a result of an unlocked bootloader or not. All the users who have unlocked their bootloader kindly let me know in the comments whether they have the same message or not. Thanks in advance :)
 

Attachments

  • Screenshot_20191127-224913.png
    Screenshot_20191127-224913.png
    103 KB · Views: 424
Last edited:

tys0n

Senior Member
Nov 29, 2010
3,110
2,044
Stockholm
So Moto One Action keeps on surprising every now and then. The latest addition to it is the System Integrity is Compromised message. This is how I end up doing so:

https://photos.app.goo.gl/8Q5xZXTzGWGVMZX48

  1. Unlocked the device's bootloader.
  2. Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
  3. Then I had to unroot my device (for some reason), so flashed the stock firmware using Moto Smart Assistant Tool. But kept the device's bootloader in an unlocked state.
  4. Now I have a stock ROM on my device, unrooted without any modification to the /system partition. The only modification is the unlocked bootloader.

Then I went to System > Advanced > System Updates and then got greeted with the message that I am no longer eligible for software updates. Although not an issue as I could still flash the stock firmware by one way or the other, I am just curious to know whether it is indeed a result of an unlocked bootloader or not. All the users who have unlocked their bootloader kindly let me know in the comments whether they have the same message or not. Thanks in advance :)

Yeah you need locked bootloader for OTA. Same on One Vision.
Magisk will hide the unlocked status while you're rooted so that you can check for OTA, but I believe it will fail to install during update. Never tyried but that's how it is on Motorola One and One Power.
fastboot flash if you're unlocked and want to update.
 

binary**#

Senior Member
Mar 20, 2014
52
43
new delhi
Hey, sorry if I am wrong but I highly doubt this claim of yours: "you need a locked bootloader for OTA". True to my knowledge, I don't think any OEM really blocks OTA on an unlocked bootloader device. Until we modify system files, we are safe to get OTA updates. That's what I always knew and every time it stood correct. Isn't it?
 

tys0n

Senior Member
Nov 29, 2010
3,110
2,044
Stockholm
Hey, sorry if I am wrong but I highly doubt this claim of yours: "you need a locked bootloader for OTA". True to my knowledge, I don't think any OEM really blocks OTA on an unlocked bootloader device. Until we modify system files, we are safe to get OTA updates. That's what I always knew and every time it stood correct. Isn't it?

I don't know about all oem's but I believe samsung blocks ota if bootloader is unlocked.
I read somewhere in G7 forum that Moto support had told that OTA is disabled on that device if you're on unlocked bootloader, so I guess Moto changed their policy about that too.
 

binary**#

Senior Member
Mar 20, 2014
52
43
new delhi
Yeah you need locked bootloader for OTA. Same on One Vision.
Magisk will hide the unlocked status while you're rooted so that you can check for OTA, but I believe it will fail to install during update. Never tyried but that's how it is on Motorola One and One Power.
fastboot flash if you're unlocked and want to update.

I don't know about all oem's but I believe samsung blocks ota if bootloader is unlocked.
I read somewhere in G7 forum that Moto support had told that OTA is disabled on that device if you're on unlocked bootloader, so I guess Moto changed their policy about that too.

Not sure about Samsung, but was going through Motorola's official blog, and this is what they have to say:

"Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola."

Anyways, thanks for your inputs.....
 

tys0n

Senior Member
Nov 29, 2010
3,110
2,044
Stockholm

drtweak

Senior Member
May 4, 2010
177
31
I got a XT2013-4 US - Unlocked boot loader, but the root method doesn't work for the US Firmware (Hear the EU Firmware works for someone in Canada) but I am unable to check for updates being fully stock, unrooted, and only an unlocked bootloader so yes if the OS can read that the bootloader is unlocked then it won't let you check for updates (At least on the US Firmware) but then we aren't Android One though on the XT2013-4
 

binary**#

Senior Member
Mar 20, 2014
52
43
new delhi
ReConfirmed: Official OTA Updates is possible after Unlocked Bootloader.

Just to reiterate the facts (in response to #2 and #8), I guess my assumption was well and truly correct. This is because I did end up receiving an OFFICIAL OTA update from Motorola, a few days back. And at this point, my BOOTLOADER IS STILL UNLOCKED! The first image attached below shows the OTA update notification as well as the proof that my Bootloader is unlocked. The second one provides details about that OTA.
 

Attachments

  • Screenshot_20191211-171434.png
    Screenshot_20191211-171434.png
    159.7 KB · Views: 230
  • Screenshot_20191211-171450.png
    Screenshot_20191211-171450.png
    138.1 KB · Views: 232

tys0n

Senior Member
Nov 29, 2010
3,110
2,044
Stockholm
Just to reiterate the facts (in response to #2 and #8), I guess my assumption was well and truly correct. This is because I did end up receiving an OFFICIAL OTA update from Motorola, a few days back. And at this point, my BOOTLOADER IS STILL UNLOCKED! The first image attached below shows the OTA update notification as well as the proof that my Bootloader is unlocked. The second one provides details about that OTA.
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
 
  • Like
Reactions: Gypsy

binary**#

Senior Member
Mar 20, 2014
52
43
new delhi
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.

No, my device isn't rooted. The only modification is the unlocked bootloader. I did this when I saw enrolled users getting beta Android 10 updates for Moto One Power. Since One Action has released almost a year after Power, I thought the soak test would just be around the corner for our device as well. But here we are with One Power receiving Stable Android 10 update, and there is no news of the same for our device. I have got myself enrolled in the MFN and just keeping my fingers crossed.
 

binary**#

Senior Member
Mar 20, 2014
52
43
new delhi
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.

One more doubt. I tried the root hide via Magisk for some apps like Google Pay or Pokemon Go and it worked pretty well. But could it trick OEMs as well into thinking the device is unrooted, so that the device may receive OTA updates? I guess probably not, but need some more weight on this opinion.
 

aditya7286

New member
Aug 14, 2019
2
0
It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..
 

binary**#

Senior Member
Mar 20, 2014
52
43
new delhi
It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..

Bootloader Locking/Unlocking has nothing to do while receiving OTAs. As I have mentioned in my other post, I have already received Android 10 OTA on an unlocked bootloader. And as far as the response to my own question goes, it was regarding whether one could hide root from the system as we do for Google Pay and get OTAs. The answer is nopes. I tried hiding root from all the necessary files related to Motorola's system OTA via Magisk but didn't get the update. As soon as I unrooted, BOOM the Android 10 update was right there!
Anyways thanks for your response ;)
 

arsradu

Senior Member
Apr 28, 2011
3,241
3,302
Unlocking bootloader on its own does not lead to that message. So I'm guessing it's probably something specific to that ROM, or....something else entirely.
 

methuselah

Senior Member
Aug 25, 2011
3,856
2,133
Unlocking bootloader on its own does not lead to that message. So I'm guessing it's probably something specific to that ROM, or....something else entirely.
Bootloader Locking/Unlocking has nothing to do while receiving OTAs. As I have mentioned in my other post, I have already received Android 10 OTA on an unlocked bootloader. And as far as the response to my own question goes, it was regarding whether one could hide root from the system as we do for Google Pay and get OTAs. The answer is nopes. I tried hiding root from all the necessary files related to Motorola's system OTA via Magisk but didn't get the update. As soon as I unrooted, BOOM the Android 10 update was right there!
Anyways thanks for your response ;)

I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.
 

arsradu

Senior Member
Apr 28, 2011
3,241
3,302






I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.
You mean "System Integrity Compromised" or something else?

Omni, if we're talking about OmniROM, is a custom, pre-rooted ROM, right? So...maybe that's why.

Interesting though that people with stock ROM, who only unlocked the bootloader (no root) are getting the same message.

Personally, I never rooted this phone and I'm not planning to. Also never seen that message on my phone. However, it was bootloader unlocked and now it's back to locked again.

So... For custom ROMs I can understand why it would show you this. For stock ROM with no root, that doesn't make much sense to me. But maybe I'm missing something.

Sent from my motorola one action using Tapatalk
 

methuselah

Senior Member
Aug 25, 2011
3,856
2,133
You mean "System Integrity Compromised" or something else?

Omni, if we're talking about OmniROM, is a custom, pre-rooted ROM, right? So...maybe that's why.

Interesting though that people with stock ROM, who only unlocked the bootloader (no root) are getting the same message.

Personally, I never rooted this phone and I'm not planning to. Also never seen that message on my phone. However, it was bootloader unlocked and now it's back to locked again.

So... For custom ROMs I can understand why it would show you this. For stock ROM with no root, that doesn't make much sense to me. But maybe I'm missing something.

Sent from my motorola one action using Tapatalk
The issue in brief.
Well the thing is i have again flashed back stock that with blankflash file. Before april update i had locked bootloader. But now nothing is happening. As soon as i flash stock ROM(clean stock) and relock the bootloader, the phone just says it is corrupted. But at the same time when i unlock the boot loader it boots.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Just to reiterate the facts (in response to #2 and #8), I guess my assumption was well and truly correct. This is because I did end up receiving an OFFICIAL OTA update from Motorola, a few days back. And at this point, my BOOTLOADER IS STILL UNLOCKED! The first image attached below shows the OTA update notification as well as the proof that my Bootloader is unlocked. The second one provides details about that OTA.
    Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
    1

    The issue in brief.
    Well the thing is i have again flashed back stock that with blankflash file. Before april update i had locked bootloader. But now nothing is happening. As soon as i flash stock ROM(clean stock) and relock the bootloader, the phone just says it is corrupted. But at the same time when i unlock the boot loader it boots.

    I'm not familiar with G series Moto phones. It could be very different to the Moto One series.

    One thing I can tell you is that, more often than not, the rollback protections are not implemented by Motorola. They're from Google.
    And, if you had a newer security patch installed and then try to go to anything other than that same security patch version or newer, you won't be able to boot with locked bootloader. I can tell you that from my own experience. So, basically, the problem on downgrades doesn't seem to be the ROM itself, but the security patch.

    Now, personally I never encountered that specific error. But also, I've had my bootloader in a locked state for the past couple of months. So...it could be something new with the April 1 security patch. Also, I never rooted this phone or installed a custom ROM.

    Now, my thought is that, if you flashed the stock ROM (clean flash), then it's probably not something left from the custom ROM you had before. I could be wrong though. So...it's probably still caused by the rollback protection put in place by Google.

    So, if your stock ROM has a lower security patch than what you had before (for example downgrading from April to March security patch), that could be why you're experiencing that issue. The only solution I found was to keep the bootloader unlocked so I can boot, until there's an official stock ROM with the same security patch level, or newer. Then lock the bootloader back.
    1
    I'm not familiar with G series Moto phones. It could be very different to the Moto One series.

    One thing I can tell you is that, more often than not, the rollback protections are not implemented by Motorola. They're from Google.
    And, if you had a newer security patch installed and then try to go to anything other than that same security patch version or newer, you won't be able to boot with locked bootloader. I can tell you that from my own experience. So, basically, the problem on downgrades doesn't seem to be the ROM itself, but the security patch.

    Now, personally I never encountered that specific error. But also, I've had my bootloader in a locked state for the past couple of months. So...it could be something new with the April 1 security patch. Also, I never rooted this phone or installed a custom ROM.

    Now, my thought is that, if you flashed the stock ROM (clean flash), then it's probably not something left from the custom ROM you had before. I could be wrong though. So...it's probably still caused by the rollback protection put in place by Google.

    So, if your stock ROM has a lower security patch than what you had before (for example downgrading from April to March security patch), that could be why you're experiencing that issue. The only solution I found was to keep the bootloader unlocked so I can boot, until there's an official stock ROM with the same security patch level, or newer. Then lock the bootloader back.
    Somehow i used moto recovery tool and it flashed a different version of ROM on my phone instead of what came with my phone. Lol I was worried but i let it go. But somehow. The flash was successful and now the bootloader is relocked. Strange.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone