Database Develop

mobile iron after relocking and unrooting not working

I unrooted and relocked my nexus 6, but my mobile iron still says it is OS comprismised. I did uninstall supersu, doesn't look to be installed. What else does MDM or mobile iron flag for? I am the admin to our MI box, so I can see what's going on, and can retire/readd at whim. I just don't see what else it's flagging for, it just says OS compromised, like when I was rooted, and unlocked.

vivithemage said:
I unrooted and relocked my nexus 6, but my mobile iron still says it is OS comprismised. I did uninstall supersu, doesn't look to be installed. What else does MDM or mobile iron flag for? I am the admin to our MI box, so I can see what's going on, and can retire/readd at whim. I just don't see what else it's flagging for, it just says OS compromised, like when I was rooted, and unlocked.
Click to expand...
Click to collapse
Not sure but probably same as Google update. Just removing the SU app doesn't remove all the SU system files. Have to reflash back to stock.

It is a stock OS. Do I have to unlock wipe, flash, lock ,wipe?

vivithemage said:
It is a stock OS. Do I have to unlock wipe, flash, lock ,wipe?
Click to expand...
Click to collapse
no. you want to unlock your bootloader, flash a factory image, make sure that it boots fine, only then you want to relock your bootloader.

vivithemage said:
It is a stock OS. Do I have to unlock wipe, flash, lock ,wipe?
Click to expand...
Click to collapse
If you just removed SU app will have to unlock and reflash system to actually remove root. Do not relock till you sure it will boot and reset the unlock switch in developer options.

OK, doing that now. What's the correct way to relock once in the OS unlocked bootloader and fresh install?
I booted into the OS, went back to recovery, ran this: fastboot oem lock
Should be good, will set it up again, hopefully mobile iron thinks I am an compromised OS now.

vivithemage said:
OK, doing that now. What's the correct way to relock once in the OS unlocked bootloader and fresh install?
I booted into the OS, went back to recovery, ran this: fastboot oem lock
Should be good, will set it up again, hopefully mobile iron thinks I am an compromised OS now.
Click to expand...
Click to collapse
fastboot oem lock is the only way to lock the bootloader

ahhh man, after all that, it still says OS compromised. Is there another flag somewhere? It is not rooted, or unlocked!

vivithemage said:
ahhh man, after all that, it still says OS compromised. Is there another flag somewhere? It is not rooted, or unlocked!
Click to expand...
Click to collapse
You did fastboot flash the system.img and boot.img before locking your bootloader, right?

cam30era said:
You did fastboot flash the system.img and boot.img before locking your bootloader, right?
Click to expand...
Click to collapse
yeah, and everything else in the gz file, cache, system data, radio, boot, etc.
I am going to open a ticket with mobile iron, they have a root ident app that they can install, to tell me what is still flagging it.

vivithemage said:
yeah, and everything else in the gz file, cache, system data, radio, boot, etc.
I am going to open a ticket with mobile iron, they have a root ident app that they can install, to tell me what is still flagging it.
Click to expand...
Click to collapse
Let us know what you find out.

https://help.mobileiron.com/articles/MI_Article/Android-Compromised-Rooted-devices
Apparently they have a root checker app. I removed all of my root required applications and I am good. So greenify (flagged), root browser (flagged), total commander (not flagged), betterbattary stats, .
I also uploaded their root status tool if anyone wants to use it:
http://vivithemage.com/extra/RootCode.apk
If anyone else is having problems, but doesn't have support with MI. this should help you discover what's causing it to be listed as comprismised. I am sure some of the savvier folks will use it as a way to stay rooted, but find ways around MI MDM .

vivithemage said:
If anyone else is having problems, but doesn't have support with MI. this should help you discover what's causing it to be listed as comprismised. I am sure some of the savvier folks will use it as a way to stay rooted, but find ways around MI MDM .
Click to expand...
Click to collapse
Any chance you could re-upload the tool? I'm running into the exact same problem but don't have MI support available

Sorry, they asked me to remove it

Re locking boot loader.

Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!

H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.

Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?

H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.

you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.

simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.

danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.

Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6

Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.

H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.

cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.

-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.

Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6

Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?

H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.

Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?

alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.

Frp locked

I cant unlock frp as It is grayed out the option of oem unlocking in the dev options
pls I need help
Model : LLD-L21
OS : KangVIP Rom (EMUI 8.0.0)
Bootloader Status : Unlocked
In fastboot it says
Phone Unlocked
FRP Locked

did u try dload method?

yes I tried dload
It did not work

I can't upload zipI will send u the file to unlock frp or you can find that file in telegram group of our device

That wont work...
Go to terminal in root mode and do
Code:
Setprop sys.oem_unlock_allowed 1
Than you can change the value and its not longer greyed out.

Darkest-Dark said:
That wont work...
Go to terminal in root mode and do
Code:
Setprop sys.oem_unlock_allowed 1
Than you can change the value and its not longer greyed out.
Click to expand...
Click to collapse
If that dosent work you can also follow the below procedure.
Relock your bootloader. Your phone will factory reset and boot. Then head to developer options and you will see oem unlock is not greyed out. Then just enable oem unlocking and unlock the bootloader. When you boot up again you will see that oem is greyed out but it'll be enabled. So you'll have unlocked fastboot and unlocked frp now.

Fredin_ said:
That wont work...
Go to terminal in root mode and do
If that dosent work you can also follow the below procedure.
Relock your bootloader. Your phone will factory reset and boot. Then head to developer options and you will see oem unlock is not greyed out. Then just enable oem unlocking and unlock the bootloader. When you boot up again you will see that oem is greyed out but it'll be enabled. So you'll have unlocked fastboot and unlocked frp now.
Click to expand...
Click to collapse
This will just brick the device.

Fredin_ said:
If that dosent work you can also follow the below procedure.
Relock your bootloader. Your phone will factory reset and boot. .....<snip>.
Click to expand...
Click to collapse
Never Ever a good idea to try and relock the bootloader.

viratbansal001 said:
This will just brick the device.
Click to expand...
Click to collapse
Sparkrite said:
Never Ever a good idea to try and relock the bootloader.
Click to expand...
Click to collapse
Umm why? Its working pretty fine for me. ?

Fredin_ said:
Umm why? Its working pretty fine for me.
Click to expand...
Click to collapse
Have you Unlocked, Relocked and then Unlocked again ?

[/COLOR]
Sparkrite said:
Have you Unlocked, Relocked and then Unlocked again ?
Click to expand...
Click to collapse
I haven't gone that far. I've unlocked and then relocked.
Everything fine. I believe it's completely safe if you have complete stock firmware installed ie, stock rom, stock recovery, stock Kernal and all that stuff. Otherwise you'll end up in a loop. Guess I forgot that part sorry.
So I know this is someone else's thread but can you tell me if I relocked bootloader will the service center be able to know I'd unlocked before? I don't have the phone unlocked warning at boot. Just curious.

Fredin_ said:
[/COLOR]
I haven't gone that far. I've unlocked and then relocked.
Everything fine. I believe it's completely safe if you have complete stock firmware installed ie, stock rom, stock recovery, stock Kernal and all that stuff. Otherwise you'll end up in a loop. Guess I forgot that part sorry.
So I know this is someone else's thread but can you tell me if I relocked bootloader will the service center be able to know I'd unlocked before? I don't have the phone unlocked warning at boot. Just curious.
Click to expand...
Click to collapse
Hey will it work if I have complete stock firmware like you said? I want to take my device to service centre but my bootloader is unlocked and I have L OS installed. Will relockeing bootloader get me back my waranty?
PS. I have already asked in question and answers section but no reply yet. ?I

Fredin_ said:
[/COLOR]
I haven't gone that far. I've unlocked and then relocked.
Everything fine. I believe it's completely safe if you have complete stock firmware installed ie, stock rom, stock recovery, stock Kernal and all that stuff. Otherwise you'll end up in a loop. Guess I forgot that part sorry.
So I know this is someone else's thread but can you tell me if I relocked bootloader will the service center be able to know I'd unlocked before? I don't have the phone unlocked warning at boot. Just curious.
Click to expand...
Click to collapse
Some if not all bootloaders nowadays are not "locked" by the manufacturer using a code but are usually "locked" by employing a digital signature and/or a CID (carrier Id) hard coded into the OS. When we "unlock" a bootloader with a code we are simply using a routine written into the loader by the manufacturer to now ignore signatures and/or CIDs of the OS and this allows us to flash whatever we wish.
Sometimes upon unlocking using a code the DS/CID is erased/altered and cannot be retrieved, so not a good idea to relock an altered bootloader.
At least, that is my understanding of it.

Krazydon said:
Hey will it work if I have complete stock firmware like you said? I want to take my device to service centre but my bootloader is unlocked and I have L OS installed. Will relockeing bootloader get me back my waranty?
PS. I have already asked in question and answers section but no reply yet. I
Click to expand...
Click to collapse
Sparkrite said:
Some if not all bootloaders nowadays are not "locked" by the manufacturer using a code but are usually "locked" by employing a digital signature and/or a CID (carrier Id) hard coded into the OS. When we "unlock" a bootloader with a code we are simply using a routine written into the loader by the manufacturer to now ignore signatures and/or CIDs of the OS and this allows us to flash whatever we wish.
Sometimes upon unlocking using a code the DS/CID is erased/altered and cannot be retrieved, so not a good idea to relock an altered bootloader.
At least, that is my understanding of it.
Click to expand...
Click to collapse
That's too bad. Means we won't get back our waranty if we relock it ?. So thanks for the heads up . I'll be careful while unlocking it again (if ever).?

Fredin_ said:
That's too bad. Means we won't get back our waranty if we relock it . So thanks for the heads up . I'll be careful while unlocking it again (if ever).
Click to expand...
Click to collapse
Not necessarily, I doubt if most service centres would bother delving that deep, but maybe some would.
I don't know...........

Sparkrite said:
Not necessarily, I doubt if most service centres would bother delving that deep, but maybe some would.
I don't know...........
Click to expand...
Click to collapse
Thanks for your quick reply but do you know any way to get back CID/DS

No, but I haven't delved that deeply into Huaweis bootloaders, but I NEVER attempt to re-lock them.

Sparkrite said:
No, but I haven't delved that deeply into Huaweis bootloaders, but I NEVER attempt to re-lock them.
Click to expand...
Click to collapse
Anyways thanks for your replies. Means a lot ?

problem with booting my x4

i have bough a x4 from ebay without warranty or anyting, the problem that i have. my phone says at the begining your device has loaded another operating system and then just a line of code says verity mode is set to disabled.
but after that the device starts normally, i have tried to lock the device again, but it doesn't work , maybe you have a solution for this problem :the model is XT1900-1 Type:M2997

the bootloader has been unlocked and to be honest relocking has no real benefits. leave it like it is, flash the latest stock image or a custom rom and ignore the bootscreen message.

cango123 said:
the bootloader has been unlocked and to be honest relocking has no real benefits. leave it like it is, flash the latest stock image or a custom rom and ignore the bootscreen message.
Click to expand...
Click to collapse
first, thank you for your response.
do you think, is that a motorola specific issue with corrupt bootloader ?
i guess the firmware of my device is a nougat, will it really help to get rid of a such blemish if i flash it??

doksch84 said:
first, thank you for your response.
do you think, is that a motorola specific issue with corrupt bootloader ?
i guess the firmware of my device is a nougat, will it really help to get rid of a such blemish if i flash it??
Click to expand...
Click to collapse
The message is normal for an unlocked bootloader - it is not corrupt. You cannot get rid of the message when the bootloader has been unlocked, even if it is relocked. Well, you can replace the boot image, but the ”verity" message will remain.

another problem
jhedfors said:
The message is normal for an unlocked bootloader - it is not corrupt. You cannot get rid of the message when the bootloader has been unlocked, even if it is relocked. Well, you can replace the boot image, but the ”verity" message will remain.
Click to expand...
Click to collapse
thank you guys, i just try to flash TWRP image, but it hangs with bootloader logs
getvar is-logical recove
getvar:has-slot:recovery
getvar_maxdown
Sending ....... in the command line? did anyone faces that problem ?

Unlocking bootloader: definitive bye-bye to automatic updates?

With the Moto Z, after I returned the phone to stock (flashed stock firmware and locked the bootloader), I'd be able to flash stock firmware with the flashing locked.
Not so with the Motorola One Zoom. In other words, flashing stock and re-locking didn't return the phone to its pristine state. Even when flashing stock firmware over stock firmware, I have to unlock the bootloader.
Differences I observed: on the bootloader screen, when re-locked the Z would show "oem_locked" again. On the One Zoom, it shows "flashing_locked" instead. I'm pretty sure it showed "oem_locked" before unlocking.
WIth the Z, every time I wanted to unlock the bootloader, I had to issue "fastboot oem unlock" followed by the unlock code. The code isn't necessary with the re-locked One Zoom.
In other words, maybe it was a one-way trip. It seems that the phone won't return to its original state, it looks it's modified for good. And I'm afraid this means bye-bye to automatic updates.
Am I missing something here?

My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.

rafikowy said:
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
Click to expand...
Click to collapse
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.

Whammamoosha said:
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Click to expand...
Click to collapse
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.

rafikowy said:
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
Click to expand...
Click to collapse
Don't bother, I have mine. Thanks.

I would like the flash script if someone would share it

Help with unlocking bootloader
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.

Bodeman12345 said:
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Click to expand...
Click to collapse
In the settings for developers you gave permission for Factory Unlock?

ilia3367 said:
In the settings for developers you gave permission for Factory Unlock?
Click to expand...
Click to collapse
I enabled the setting to unlock oem bootloader is that the same?

Bodeman12345 said:
I enabled the setting to unlock oem bootloader is that the same?
Click to expand...
Click to collapse
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
Code:
fastboot devices
If the device is detected, enter the command:
Code:
fastboot getvar all
And copy the result here.

ilia3367 said:
yes.
Click to expand...
Click to collapse
Yes I did that

Bodeman12345 said:
Yes I did that
Click to expand...
Click to collapse
Answer the other questions, please!

diculpe por que mi pc no ve el fastboot de mi one zoom?

ilia3367 said:
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
If the device is detected, enter the command:
And copy the result here.
Click to expand...
Click to collapse
I used this youtube video
I dont know where it is manifactured but I live in the netherlands.
I dont get the 3th question
I will do the commands in a couple minutes

Hey all,
I have the Moto One Zoom running on Android 9.
Also, It's Rooted with Magisk and have Riru EdXposed installed, can I install my OTA updates without bootloop or do I have to Uninstall Magisk, relock bootloader and factory reset/flash stock firmware to get latest OTA updates?
Any feedback is appreciated.
Thanks