Will I get security patch updates if my bootloader is unlocked?
if not, is it a good idea to relock bootloader?
my device is samsung galaxy a 32 4g (sm-a325f)
jiglex said:
Will I get security patch updates if my bootloader is unlocked?
if not, is it a good idea to relock bootloader?
my device is samsung galaxy a 32 4g (sm-a325f)
Click to expand...
Click to collapse
no once your boot loader is unlocked you will not be able to do firmware upgrades. while it is possible to trick the phone into thinking everything is normal it will always fail while trying to install the update. i have tried and it never worked. Although once you relock the boot loader even with knox tripped you will start recieving updates normally again.
Captain_cookie_200 said:
no once your boot loader is unlocked you will not be able to do firmware upgrades. while it is possible to trick the phone into thinking everything is normal it will always fail while trying to install the update. i have tried and it never worked. Although once you relock the boot loader even with knox tripped you will start recieving updates normally again.
Click to expand...
Click to collapse
Thanks for your reply mate.Can you help me with another thing which is, can I downgrade my stock firmware(flashing older stock firmware with odin) if my bootloader is locked?
jiglex said:
Thanks for your reply mate.Can you help me with another thing which is, can I downgrade my stock firmware(flashing older stock firmware with odin) if my bootloader is locked?
Click to expand...
Click to collapse
yes you can downgrade your firmware as long as the bit number is the same. e.g. there is a number ln each firmware's name like U1, U2
these may be found in the middle of the firmware's name. if the firmware you are downgrading to has a lower bit than of the firmware currently installed it will not work. you will have to choose a firmware with the same bit version. thats why always be on the lookout when upgrading to newer firmwares. for me with SM-A325F the highest bit js U2 and most of the resources are for that firmware so im fine.
Captain_cookie_200 said:
yes you can downgrade your firmware as long as the bit number is the same. e.g. there is a number ln each firmware's name like U1, U2
these may be found in the middle of the firmware's name. if the firmware you are downgrading to has a lower bit than of the firmware currently installed it will not work. you will have to choose a firmware with the same bit version. thats why always be on the lookout when upgrading to newer firmwares. for me with SM-A325F the highest bit js U2 and most of the resources are for that firmware so im fine.
Click to expand...
Click to collapse
That was a lot of help for me brother.
Thanks a lot.
jiglex said:
That was a lot of help for me brother.
Thanks a lot.
Click to expand...
Click to collapse
your welcome
Related
Hi all,
I've searched and searched but haven't been able to find anyone else with the same issue I have with my S9, so i'm hoping somebody might be able to help me out!
Basically i installed twrp and then installed Lineageos with Odin. But after a while decided i wanted to go back to stock (there were a few things i was missing, dolby atmos, the stock camera, wi-fi calling and google pay.)
I downloaded a stock firmware from updato and installed with Odin. I used the BTU version, although my phone would have come with the XEU version as standard. I used the HOME_CSC (not sure if that is important?)
So now my phone has stock firmware and got an OTA update yesterday. But when i go into dev settings OEM unlock is greyed out and says 'Bootloader is already unlocked' and my phone is also uncertified in the play store and failed safetynet.
So i'm hoping to be able to get my phone back to the boot loader locked state and to get it certified and passing safetynet. I've waited 7 days as some people have suggested, phone was up for 170 hours but OEM unlock is the same and phone is still uncertified. My next thought is to install the XEU firmware and see if that makes any difference, but i'm not convinced it will.
Does anyone have any idea on how i can fix this please??
evjohns said:
Hi all,
I've searched and searched but haven't been able to find anyone else with the same issue I have with my S9, so i'm hoping somebody might be able to help me out!
Basically i installed twrp and then installed Lineageos with Odin. But after a while decided i wanted to go back to stock (there were a few things i was missing, dolby atmos, the stock camera, wi-fi calling and google pay.)
I downloaded a stock firmware from updato and installed with Odin. I used the BTU version, although my phone would have come with the XEU version as standard. I used the HOME_CSC (not sure if that is important?)
So now my phone has stock firmware and got an OTA update yesterday. But when i go into dev settings OEM unlock is greyed out and says 'Bootloader is already unlocked' and my phone is also uncertified in the play store and failed safetynet.
So i'm hoping to be able to get my phone back to the boot loader locked state and to get it certified and passing safetynet. I've waited 7 days as some people have suggested, phone was up for 170 hours but OEM unlock is the same and phone is still uncertified. My next thought is to install the XEU firmware and see if that makes any difference, but i'm not convinced it will.
Does anyone have any idea on how i can fix this please??
Click to expand...
Click to collapse
HOME_CSC does not reset the device, CSC does, chances are some of the root stuff / system modified files are still present causing these problems
Factory reset, if that doesn't work, flash again but use CSC this time
*Detection* said:
HOME_CSC does not reset the device, CSC does, chances are some of the root stuff / system modified files are still present causing these problems
Factory reset, if that doesn't work, flash again but use CSC this time
Click to expand...
Click to collapse
Thanks, I'll try that again later. Any idea whether it matters if i use the XEU or BTU firmware?
evjohns said:
Thanks, I'll try that again later. Any idea whether it matters if i use the XEU or BTU firmware?
Click to expand...
Click to collapse
Probably won't be able to switch to BTU if you were originally on XEU, BTU is multiCSC and contains XEU so the phone will default to it's original CSC
The firmware will flash fine, but if you check the CSC it will likely still be on XEU unless you managed to change it when you were custom
*Detection* said:
Probably won't be able to switch to BTU if you were originally on XEU, BTU is multiCSC and contains XEU so the phone will default to it's original CSC
The firmware will flash fine, but if you check the CSC it will likely still be on XEU unless you managed to change it when you were custom
Click to expand...
Click to collapse
Yep you're right, it's still XEU. I'll try a factory reset. I'm hoping the OTA update may have fixed a few things.
Can you lock the bootloader back?
parnunu said:
Can you lock the bootloader back?
Click to expand...
Click to collapse
I did a factory reset, then flashed the stock ROM again and used CSC, but the boot loader is still unlocked. I don't have the option to re-lock it, so seems like maybe you can't
Just in case this helps anyone else, I did a complete reset of the stock ROM using @rifek4 instructions from https://forum.xda-developers.com/galaxy-s7/how-to/guide-onelatest-stock-fw-csc-root-t3702963
But i'm still not able to re-lock the boot loader. So going to leave it now and hope the option comes back after 7 days.
rifek4 said:
https://forum.xda-developers.com/showpost.php?p=76388485&postcount=51
Click to expand...
Click to collapse
Thanks for replying. Do you think that method would help me to re-lock the boot loader?
When I go to the settings the OEM unlock says "boot loader is already unlocked"
Basically all I want to do is get safety net to pass again, and it seems that having an unlocked boot loader makes it fail.
Just in case this helps anyone else.
I downloaded magisk 16.7 beta, 16.6 caused my OS (lineage 15.1) to crash, but 16.7 was fine. I installed universal safety net fix for magisk, beta version. Installation said it failed, but when I rebooted it had worked!
Safety net now passes, device is certified in play store and Google pay is working fine. As @rifek4 said, bootloader lock has nothing to do with safety net (although I've seen a lot of people claiming it does).
I waited 7 days then disabled oem unlock in the developer option.
DONE.
None of skip wait time method work for me.
Hello all. My 935f came with firmware XSG for United Arabic Emirates but I am in the UK and would like to flash VOD instead. I tried as soon as I got the phone with odin but got some error (don't remember exactly but f.w. 2 expected 1?). Anyways, 7 days have since passed and I have access to OEM unlock. 2 questions:
1) does the firmware (XSG vs VOD) changes anything at all?
2) if so, how could I flash this without losing OEM unlock.
Thanks a lot!
Flashing firmwares doesn't effect OEM unlock and I'll install Vodafone bloat, go for btu if you're in the uk
ASHLEY117 said:
Flashing firmwares doesn't effect OEM unlock and I'll install Vodafone bloat, go for btu if you're in the uk
Click to expand...
Click to collapse
Thanks for this. Do you just flash using Odin? It won't let me gives some kind of SW Rev error . Can it be because of the baseband? I am on BRG8 with build number BRH1 trying to flash BRF8...
batpoil said:
Thanks for this. Do you just flash using Odin? It won't let me gives some kind of SW Rev error . Can it be because of the baseband? I am on BRG8 with build number BRH1 trying to flash BRF8...
Click to expand...
Click to collapse
G960FXXU2BRGA
Check you'e not trying to downgrade the bootloader as shown highlighted here, check yours in download mode (B:1 or B:2)
*Detection* said:
G960FXXU2BRGA
Check you'e not trying to downgrade the bootloader as shown highlighted here, check yours in download mode (B:1 or B:2)
Click to expand...
Click to collapse
Working fine now, thanks so much for this!!
batpoil said:
Working fine now, thanks so much for this!!
Click to expand...
Click to collapse
:good:
Been trying to unlock my bootloader to no avail, but on the other hand, I can't seem to find a stock Nougat rom that I can install on stock recovery. Should I just return this phone, get a new one and obtain unlock code before updating to Oreo? Or is there any way to downgrade back to Nougat on locked bootloader?
Thanks.
I think it's possible with hisuite.
Trecoolius said:
Been trying to unlock my bootloader to no avail, but on the other hand, I can't seem to find a stock Nougat rom that I can install on stock recovery. Should I just return this phone, get a new one and obtain unlock code before updating to Oreo? Or is there any way to downgrade back to Nougat on locked bootloader?
Thanks.
Click to expand...
Click to collapse
Yes it is possible,connect device to pc with usb ,internet is on and open Hisuite and connect device after connected click on update so
you got option to downgrade OREO to Naught.
anilsrj said:
Yes it is possible,connect device to pc with usb ,internet is on and open Hisuite and connect device after connected click on update so
you got option to downgrade OREO to Naught.
Click to expand...
Click to collapse
well that method doesnt work, atleast not for me.
once you click update there no option to downgrade, all mine says is that ive got the newest version
cdmanproductions said:
well that method doesnt work, atleast not for me.
once you click update there no option to downgrade, all mine says is that ive got the newest version
Click to expand...
Click to collapse
what is your current version..
anilsrj said:
what is your current version..
Click to expand...
Click to collapse
8.0.0.341 on the phone
8.xxxx on hisuite, but I also tried 5.xxx and still no option
Trecoolius said:
Been trying to unlock my bootloader to no avail, but on the other hand, I can't seem to find a stock Nougat rom that I can install on stock recovery. Should I just return this phone, get a new one and obtain unlock code before updating to Oreo? Or is there any way to downgrade back to Nougat on locked bootloader?
Thanks.
Click to expand...
Click to collapse
There is service rom that will flash with locked boooader, and one that is nougat. But it will leave you with strange build number. But should allow for dc-unlocker to read your code.
I was unaware that some trouble with reading the code in Oreo existed. But just got confirmation in other thread that service rom roll back helped
Thanks everyone, I ended up returning the phone and getting a new one. Read bootloader code from nougat, updated to oreo and unlocked everything no probs.
Trecoolius said:
Thanks everyone, I ended up returning the phone and getting a new one. Read bootloader code from nougat, updated to oreo and unlocked everything no probs.
Click to expand...
Click to collapse
Bro.. How could u downgrade ur phone?? Mine is Indian variant bnd Al10c675
Question for those of you on L29 model w/ C636 region.
I purchased a bootloader unlocked EVR-L29 from a forum member here but don't want to bother him with more questions.
QUESTIONS:
-I am on version 9.0.0.7 I have tried manually updating within the phone itself but it says I am on latest version.
I downloaded latest HiSuite program on laptop and connected the phone to it using usb debug in dev mode. Still says on latest version. I have attempted to go into erecovery & force searching for an update. Which sorta worked but it just downloads the current version I am already on.
So I am guessing I am having these issues because it is bootloader unlocked?
I am guessing you bootloader unlocked guys have an alternate method of forcing an update?
If there is an alternate method I can use I am guessing it is best to incrementally update instead of pushing the latest build?
-Once fully updated to the latest build will the old root method still work on EMUI 9.1? Where we flash a recovery ramdisk as shown HERE?
If the answer is yes do you all flash a stock recovery ramdisk for L29 or a patched recovery ramdisk? What is the difference?
I unlocked the bootloader on my L29 and was on 9.0.0.208 and couldn't get the 9.1.0.300 OTA update until I used e-recovery to download and install 9.0.0.207. Once I did that the phone immediately received the 9.1.0.300 OTA update and then patch #1. I haven't rooted yet so I don't know if root survives the update. It might because the update didn't wipe anything.
frcraig said:
I unlocked the bootloader on my L29 and was on 9.0.0.208 and couldn't get the 9.1.0.300 OTA update until I used e-recovery to download and install 9.0.0.207. Once I did that the phone immediately received the 9.1.0.300 OTA update and then patch #1. I haven't rooted yet so I don't know if root survives the update. It might because the update didn't wipe anything.
Click to expand...
Click to collapse
Yup erecovery just keeps downloading and installing 9.0.0.207 and when the phone reboots I get no OTA. Odd. I'll try putting the sim card in to see if that helps since I'm using wifi
Update for any people in the future that have this problem.
NO METHODS WORKED except Dload method. Finally on .310 update.
CCJ22 said:
Update for any people in the future that have this problem.
NO METHODS WORKED except Dload method. Finally on .310 update.
Click to expand...
Click to collapse
Where did you get the unlock code from? thanks
magare said:
Where did you get the unlock code from? thanks
Click to expand...
Click to collapse
I bought the phone already unlocked from a forum member that unlocked it back when the unlock codes were available.
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
Unlocked the device's bootloader.
Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
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.
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
binary**# said:
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
Unlocked the device's bootloader.
Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
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.
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
Click to expand...
Click to collapse
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.
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?
binary**# said:
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?
Click to expand...
Click to collapse
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.
tys0n said:
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.
Click to expand...
Click to collapse
tys0n said:
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.
Click to expand...
Click to collapse
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.....
binary**# said:
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.....
Click to expand...
Click to collapse
Oh I see. I don't know then.
You could ask here:
https://forums.lenovo.com/t5/motorola-one-action/bd-p/motorola_one_action_en
They should be able to give a proper answer.
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
If you are on Stock Firmware, unrooted but your Bootloader is Unlocked, you'll not get any OTA despite the Motorola Support page you've posted (It might be old information, just look the phone they used on the top).
Is it possible to relock it?
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.
binary**# said:
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.
Click to expand...
Click to collapse
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
tys0n said:
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
Click to expand...
Click to collapse
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**# said:
No, my device isn't rooted. The only modification is the unlocked bootloader.
Click to expand...
Click to collapse
Ok, thanks. That's intresting.
tys0n said:
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
Click to expand...
Click to collapse
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.
It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..
aditya7286 said:
It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..
Click to expand...
Click to collapse
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
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.
arsradu said:
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.
Click to expand...
Click to collapse
binary**# said:
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
Click to expand...
Click to collapse
I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.
methuselah said:
I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.
Click to expand...
Click to collapse
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
arsradu said:
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
Click to expand...
Click to collapse
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.