Develop Bugs

Should i check OEM unlocking option in the Developer settings ?

Ok so i have read many posts on XDA about bricked nexus 5x's and many others, sometimes the main probelm is the oem isnt unlocked. I myself have a Nexus 5x that is completely stock no custom recovery no root no nothing, i just update the phone, right now on Nougat 7.0 sep security update.
So my question is, should i check the OEM unlocking in the settings ? i will never install any recovery or root but i think by reading the posts, it seems like its a major problem if this is not checked, should i check it just to be safe ?

U_Midrar said:
Ok so i have read many posts on XDA about bricked nexus 5x's and many others, sometimes the main probelm is the oem isnt unlocked. I myself have a Nexus 5x that is completely stock no custom recovery no root no nothing, i just update the phone, right now on Nougat 7.0 sep security update.
So my question is, should i check the OEM unlocking in the settings ? i will never install any recovery or root but i think by reading the posts, it seems like its a major problem if this is not checked, should i check it just to be safe ?
Click to expand...
Click to collapse
If you have issues in your current state they will most likely be hardware related and unfixable via software. But even locked you can completely reinstall the OS via sideloading an OTA or using the TOT method.
Enabling OEM unlock disables Factory Reset Protection (FRP). FRP is a security feature that prevents a stolen device from being activated. There is allot of info about it online if you wish to learn more.
So you need to decide if you want FRP or the ability to flash the factory images.
Sent from my XT1650 using Tapatalk

PiousInquisitor said:
If you have issues in your current state they will most likely be hardware related and unfixable via software. But even locked you can completely reinstall the OS via sideloading an OTA or using the TOT method.
Enabling OEM unlock disables Factory Reset Protection (FRP). FRP is a security feature that prevents a stolen device from being activated. There is allot of info about it online if you wish to learn more.
So you need to decide if you want FRP or the ability to flash the factory images.
Click to expand...
Click to collapse
ok thx dude for the reply, nah i dont care about the FRP. so flashing factory images is easier right ? rather than sideloading or whatever this TOT method is...., and do most mobiles have a oem locked or unlocked ?

U_Midrar said:
ok thx dude for the reply, nah i dont care about the FRP. so flashing factory images is easier right ? rather than sideloading or whatever this TOT method is...., and do most mobiles have a oem locked or unlocked ?
Click to expand...
Click to collapse
Sure, flashing the factory images is probably slightly easier than the other methods. Note that in your case you would need to actually unlock the bootloader to flash the images. With those added steps it's probably faster to sideload.
The Allow OEM unlock toggle has been around since LP I think. An pretty sure it's in phones that shipped with LP. It didn't automagically mean that the phones bootloader can be unlocked though. It should stop disable FRP though.
Sent from my XT1650 using Tapatalk

Yes, most, I think all OEMs leave the possibility to unlock the bootloader.
By default the bootloader is locked on most OEMs (Sony, Samsung, HTC, Motorola, even Nexus devices).
For Nexus devices it's a simple one liner to unlock/lock the bootloader which will also trigger a data wipe but. On Nexus devices it doesn't void your warranty.
For most other OEMs phones you have to follow some steps and usually get some kind of code in order to unlock the bootloader the first time. This will void your warranty!
If you don't know whether or not you should unlock/lock the bootloader, the answer is: NO!
It seems you're not modifying your phones software (Custom Kernel, Custom Rom, Root etc) and you seem to have no intention doing so. So it's not needed and even less "secure" than with locked bootloader. If you do, you should know that you have to unlock the bootloader in order to change the phones software.
Why would you want to unlock the bootloader when the only reason to do so is to modify the software and you do not plan to do this?
On a stock nexus there is no need to unlock the bootloader, you can even reflash your phone with locked bootloader with the stock software image.

creambyemute said:
Yes, most, I think all OEMs leave the possibility to unlock the bootloader.
By default the bootloader is locked on most OEMs (Sony, Samsung, HTC, Motorola, even Nexus devices).
For Nexus devices it's a simple one liner to unlock/lock the bootloader which will also trigger a data wipe but. On Nexus devices it doesn't void your warranty.
For most other OEMs phones you have to follow some steps and usually get some kind of code in order to unlock the bootloader the first time. This will void your warranty!
If you don't know whether or not you should unlock/lock the bootloader, the answer is: NO!
It seems you're not modifying your phones software (Custom Kernel, Custom Rom, Root etc) and you seem to have no intention doing so. So it's not needed and even less "secure" than with locked bootloader. If you do, you should know that you have to unlock the bootloader in order to change the phones software.
Why would you want to unlock the bootloader when the only reason to do so is to modify the software and you do not plan to do this?
On a stock nexus there is no need to unlock the bootloader, you can even reflash your phone with locked bootloader with the stock software image.
Click to expand...
Click to collapse
yo dude thx for the reply, as i said in my first post, i saw some bricked nexus 5x (they didnt mod anything i think) that couldnt be repaired cause he had the option unchecked about OEM, that is why i was asking for like a safety precaution that if something goes wrong it would be okay cause oem could be unlocked then... what do u say now ? (and yea im not gonna ever mod anything in the phone, learned fom my last phone which i somehow bricked and a man fixed it for for 5$ )

U_Midrar said:
yo dude thx for the reply, as i said in my first post, i saw some bricked nexus 5x (they didnt mod anything i think) that couldnt be repaired cause he had the option unchecked about OEM, that is why i was asking for like a safety precaution that if something goes wrong it would be okay cause oem could be unlocked then... what do u say now ? (and yea im not gonna ever mod anything in the phone, learned fom my last phone which i somehow bricked and a man fixed it for for 5$ )
Click to expand...
Click to collapse
That catch is if if you checked OEM unloking and chose to not perform oem unlock command now.
When something did went wrong afterward, you are able to perform oem unlock but it will wipe your data.
There is no point for doing it.

HebeGuess said:
That catch is if if you checked OEM unloking and chose to not perform oem unlock command now.
When something did went wrong afterward, you are able to perform oem unlock but it will wipe your data.
There is no point for doing it.
Click to expand...
Click to collapse
so i shouldnt do it like just leave it be ?

F IT I DID IT
i just read this site and also got to know a bootloop can occur with OTA update so yea i have done it.
Site: http://android.wonderhowto.com/news...ting-before-modding-anything-android-0167840/

14 day wait for bootloader unlock?

Is this possible to skip? Can we unlock with adb / fastboot or is that not going to work / likely to brick the device?

Unlock Resposibly
adb or fastboot unlock will only work after 14 days of waiting. It is to allow you to rethink your decision. OEM unlock will obviously void your warranty and applications like Android pay will stop working. Trust me, relocking will not be easy as unlocking. Even if you somehow get it relocked, Android pay will still not work for you. So, unlock responsibly.

Thanks for the reply . I'm really doing it for root access, modifying the hosts file, changing fonts and boot animation, but the latter two aren't necessities.
I don't use Android pay (don't use contactless) but I am a little concerned that online banking will cease to function when the phone is on a stock firmware and rooted. If there's an effective system wide ad blocker I may use that instead.

For hosts file, I recommend dns66, available through fdroid, no root required.

i have found that many banking apps will continue to work with root provided you also have a hide root app installed but android pay is a no go.

jk77 said:
For hosts file, I recommend dns66, available through fdroid, no root required.
Click to expand...
Click to collapse
Thanks! First I've heard of fdroid, looks very useful, and dns66 does exactly what I was planning on doing.

Need to put Android 10 so only way is custom ROM. How to put custom rom without OEM unlock?

cutom rom
Albert612103 said:
Need to put Android 10 so only way is custom ROM. How to put custom rom without OEM unlock?
Click to expand...
Click to collapse
there is no way. Should be rooted
CHEERS

Hello guys.
For those having bootloader unlock server issue (normally everybody), there's a post on the Lenovo forum that gives the origin of the issue:
https://forums.lenovo.com/t5/P2-P2a...-bootloader/m-p/4574568/highlight/true#M12457
In fact, the problem seems coming from an non renewed SSL Certificate in the Lenevo server tracking the OEM Unlocking requests.
The suggestion given by fls2 is to change the date of the P2 phone to a previous date than the 10 July 2019 and the Bootloader Unlocking process should be launched.
That's what I've done with a second P2 I bought that has its bootloader locked.
I set the date to 10th of April 2019 and the phone is now waiting for 14 complete days to engage the OEM Bootloader unlock instead of the usual Lenovo ID error pop-up.
I'll wait for the process to end and see if everything went fine, but it seems that it should be OK as it was with my first P2 phone.
I'll keep you informed if there are some trouble in the process but I stay confident.
In case of success, we should address a very big "thank you" to fls2 for pointing out the issue with Lenovo server.

20 days have passed since registered. Always shows error.
Unable to unlock OEM.
Don't know what to do...

Hello everyone,
As I have written in my last post, I've used the suggested method of manually changing the date to one before the 10th July 2019.
So, as I've said, the 14 days counter has been correctly launched and I was able to see the counter evolving from 14 to 2 days.
Then I was a little bit busy and I haven't followed my P2 phone until last week-end.
When I tried to consult the status of the bootloader unlocking request, I had the same annoying pop-up telling me there's a problem with my account.
The date was fixed to 10th of April 2019 manually, but still had connection error pop-up.
I then tried to switch to current day date of the week-end (29/02/2020), and tried to check again the bootloader unlock status: Annoying pop-up again.
Before giving up, I've tried putting another date manually but at least 14 days after the one I've put when I made my first request and still before the 10th of July 2019, so I switched to 10th of June 2019.
This time, when I checked the bootloader unlock request, I've got no error and had a positive bootloader unlock message that told me the phone is going to reboot and erase all user data that are present.
The phone has rebooted in Fastboot mode and I was able to send the awaited "fastboot oem unlock" command from my laptop.
I didn't try to reboot the system and see if the fastboot command will work if I go in fastboot mode by myself, because I didn't want to miss the opportunity to succeed in unlocking the bootloader of this phone.
I let the people brave enough to try if they feel comfortable with that.
Now this phone is working with an AICP Android Q ROM that seems very stable.
@ Albert612103
20 days have passed since registered. Always shows error.
Unable to unlock OEM.
Don't know what to do...
Click to expand...
Click to collapse
Try to follow my steps.
There's no reason I've succeded and you cannot.
I'm sure you'll be able to unlock your bootloader as I've done.
If you have some question, just feel free to ask.

I'm trying to unlock the bootloader too. Is there any way to avoi waiting 15 days? I'm still using the Stock Rom by default (Android 6).
According to the last comment in the Lenovo forum, the changing date no longer works.
Thanks

xavicosco said:
I'm trying to unlock the bootloader too. Is there any way to avoi waiting 15 days? I'm still using the Stock Rom by default (Android 6).
According to the last comment in the Lenovo forum, the changing date no longer works.
Thanks
Click to expand...
Click to collapse
AFAIK, no. You need to wait that. Also there is bigger problem than that which its the unlocking bootloader (server problem). Just you can read above, for no reason you cannot unlock bootloader.

mahmutpekkara said:
AFAIK, no. You need to wait that. Also there is bigger problem than that which its the unlocking bootloader (server problem). Just you can read above, for no reason you cannot unlock bootloader.
Click to expand...
Click to collapse
@mahmutpekkara somehow I managed to unlock the OEM. It took me few attempts tho, so I'm guessing their servers are not always operating. No needed to change the date in my case.
Only 3 days remaining, so hopefully everything goes well.

So, after 15 days waiting I was getting the message ''Server sync data success'. I managed to get thru by signing off and signing in again with another account. Flashed properly and enjoying Syberia OS

[CLOSED]Force Unlocking Bootloader on Nokia 6.1

Hey,
I have been searching for an answer to this for quite a while, and I've found some information. Before you start bashing me in the comments, I do know that Nokia has disabled unlocking bootloaders on certain devices. My question is, is there 100% no (free) way of unlocking the bootloader on my phone, or just in general to get root. I am running Android 9, and I do have adb (of course).
Thank!

Also interested in this ... Don't want to let someone mess around with my phone .. used to do it myself

Short answer, no. By the looks of it there are currently no free tools, etc.
Long answer, yes but not accessible for us currently. There are ways to gain root access/unlock the bootloader on every device. Currently there are some unpatched exploits (that sometimes cannot even be fixed) in the Linux and Android system that are able to root devices, etc. The last few years showed that Baseband (proprietary Qualcomm code), the RAM (Rowhammer, Rampage) and other device features are attackable. Maybe KingoRoot or someone else might implement these exploits in the following years, and we get a free utility to root devices.

Bootloader unlock for Nokia phones!
​
_xNyx_ said:
Hey,
I have been searching for an answer to this for quite a while, and I've found some information. Before you start bashing me in the comments, I do know that Nokia has disabled unlocking bootloaders on certain devices. My question is, is there 100% no (free) way of unlocking the bootloader on my phone, or just in general to get root. I am running Android 9, and I do have adb (of course).
Thank!
Click to expand...
Click to collapse
Visit the link below
https://www.nokia.com/phones/en_int/bootloader/

I'm quite new to this rooting stuff, therefore a few stupid questions:
I read that with old security patches, before Aug 2018 (was that still Android Pie?) it was possible to unlock the bootloader. Isn't there some way to downgrade the security patch to a version allowing to unlock?
Is it at all required to unlock the bootloader in order to be able to install LineageOS as provided by this link?
many thanks!
EDIT: Can you recommend any working alternative way to unlock the bootloader?
Frozen_Duck said:
Short answer, no. By the looks of it there are currently no free tools, etc.
Long answer, yes but not accessible for us currently. There are ways to gain root access/unlock the bootloader on every device. Currently there are some unpatched exploits (that sometimes cannot even be fixed) in the Linux and Android system that are able to root devices, etc. The last few years showed that Baseband (proprietary Qualcomm code), the RAM (Rowhammer, Rampage) and other device features are attackable. Maybe KingoRoot or someone else might implement these exploits in the following years, and we get a free utility to root devices.
Click to expand...
Click to collapse

belzebubi said:
I'm quite new to this rooting stuff, therefore a few stupid questions:
I read that with old security patches, before Aug 2018 (was that still Android Pie?) it was possible to unlock the bootloader. Isn't there some way to downgrade the security patch to a version allowing to unlock?
Is it at all required to unlock the bootloader in order to be able to install LineageOS as provided by this link?
many thanks!
EDIT: Can you recommend any working alternative way to unlock the bootloader?
Click to expand...
Click to collapse
August 2018 would have been Oreo and YES currently you have to roll back to unlock bootloader. It's a PAID service to have this done. @singhnsk can aid you in doing this service. I as well as many others have used him to unlock our devices. You will have to use Team Viewer and let him remotely do his work.
Good luck!!

And actually, the main question is how to unlock? Bootloaderunlocker.apk dont work, it say me "google service error" help me please

OEM unlocked for Nokia 7.1 and for all nokia
Hi guys I am new here also searching for unlocking the bootloader for Nokia I read this method somewhere tried my self with some tweaks it worked
1. Open the developer option and turn it off.
2. Again turn it on but skip the on screen option for ok and cancle again turn the developer option off.
3.now trim developer option again click ok and as soon as you do it click on oem unlocking it will show a message to reboot the mob do it.
4. After rebooting you will see the oem unlock is still off just step 1,2and 3 vola bootloader is unlocked now
Comment if it works
Thanx

Sourabh22kori said:
OEM unlocked for Nokia 7.1 and for all nokia
Hi guys I am new here also searching for unlocking the bootloader for Nokia I read this method somewhere tried my self with some tweaks it worked
1. Open the developer option and turn it off.
2. Again turn it on but skip the on screen option for ok and cancle again turn the developer option off.
3.now trim developer option again click ok and as soon as you do it click on oem unlocking it will show a message to reboot the mob do it.
4. After rebooting you will see the oem unlock is still off just step 1,2and 3 vola bootloader is unlocked now
Comment if it works
Thanx
Click to expand...
Click to collapse
You da Man! I had to try it a few times, but it worked.
Just to clarify point 3.
3. Now turn developer option on again click OK and as soon as you do you will be returned to previous menu. Immediately click "OEM unlocking", it will show a message and ask your password, (if set), and work.

Thread closed as a subject matter related thread already exists:
How to Unlock Bootloader & Root Nokia 6.1?
Hello Guys! anybody know how to unlock this phone TA-1089 and root? currently it's running on latest software update Android 9 ( January Patch) kindly help please.
forum.xda-developers.com
Regards
Oswald Boelcke
Senior Moderator

Unlocked Bootloader leads to System Integrity being Compromised?

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.

Question Unable to unlock bootloader Samsung Galaxy S22 SM-S901B/DS

Hello everyone.
I recently bought a Samsung Galaxy S22 SM-S901B/DS 256MB in the UK. I'm trying to unlock the bootloader to get root with Magisk.
First, I updated the operating system to the latest version available. After that I managed to toggle the OEM unlocking in the Developer Options but when I restart to Download mode I don't get the option to long press the volume up key to finish the process. There's a line that says "OEM UNLOCK: ON(U1)". That very line read "OEM UNLOCK: ON(L1)" before I toggled the option in the Developer section.
I tried to install an AP file modified by Magisk with Odin 3.14 but at the end of the process I get the error "Custom binary (VBMETA) blocked due to remaining installment balance" and I have to flash the original OS from scratch to be able to use the phone again.
Could anyone please help me here?

AFAIK, currently, there is no way!

shafeeqmk said:
AFAIK, currently, there is no way!
Click to expand...
Click to collapse
Hi Shafeeqmk. Thanks for your reply.
Could you please elaborate or give me some links where I can read some more?
Kind regards

Try this and write feedback:
1. Turn off device
2. Connect one end of USB to PC
3. Press and hold Vol Up and Down keys simultaneously .. then Connect USB to device.
4. Keep holding the keys until you see BL Unlock menu.
5. Long Press Vol UP
6. Device will auto reboot multiple times and then prompt to Factory reset
7. Complete the Factory Reset and reboot to System
8. Wait few minutes, finish Welcome setup connect WiFi to register OEM unlock.

NextGenMagisk said:
Try this and write feedback:
1. Turn off device
2. Connect one end of USB to PC
3. Press and hold Vol Up and Down keys simultaneously .. then Connect USB to device.
4. Keep holding the keys until you see BL Unlock menu.
5. Long Press Vol UP
6. Device will auto reboot multiple times and then prompt to Factory reset
7. Complete the Factory Reset and reboot to System
8. Wait few minutes, finish Welcome setup connect WiFi to register OEM unlock.
Click to expand...
Click to collapse
That's what I get at step 4. No matter how long I press Vol Up + Vol Down, i can't see the option to unlock BL.

Looks like some restrictions for unlocking are enforced by the region specific Firmware.
You can try to flash alternate stock firmware from different region (probably Asia).
This could hard brick your device. So, it is your choice to proceed or stick with current Working Firmware without root.

chinchulin01 said:
That's what I get at step 4. No matter how long I press Vol Up + Vol Down, i can't see the option to unlock BL.
Click to expand...
Click to collapse
It might be that you are already bootloader unlocked
Try installing twrp for your s22

NextGenMagisk said:
Looks like some restrictions for unlocking are enforced by the region specific Firmware.
You can try to flash alternate stock firmware from different region (probably Asia).
This could hard brick your device. So, it is your choice to proceed or stick with current Working Firmware without root.
Click to expand...
Click to collapse
Thanks for your reply.
Do you know of any specific firmware that allows to unlock the bootloader for this specific model?
Can I cross flash a firmware from a different region?
Can I downgrade my firmware?
Regards

chinchulin01 said:
Thanks for your reply.
Do you know of any specific firmware that allows to unlock the bootloader for this specific model?
Can I cross flash a firmware from a different region?
Can I downgrade my firmware?
Regards
Click to expand...
Click to collapse
1. You can find some clues here:
Guide to root Galaxy S22 (B/E/N/0), unlock bootloader and flash official firmware (noob friendly)
Your warranty is now void. If you root your device, Your KNOX status will be tripped. You can still pass the safety net after you root if you follow the instructions. I am not responsible for bricked devices, dead SD cards although it is not...
forum.xda-developers.com
2. I have not tested cross flashing Samsung Firmware so I cannot give any feedback.
3. Downgrade from A12 to A11 will certainly fail. I have tested this just last month.

> "Custom binary (VBMETA) blocked due to remaining installment balance"
That's seems like another layer of protection by Samsung, so that you first pay off the loan for the phone, and then you can root it.

hi @chinchulin01 ,
is there any news for the root?
At what point do you get stuck?

Xmaster111 said:
hi @chinchulin01 ,
is there any news for the root?
At what point do you get stuck?
Click to expand...
Click to collapse
Hi. I'm at the same spot I was before.
I'm trying to follow this guide
Guide to root Galaxy S22 (B/E/N/0), unlock bootloader and flash official firmware (noob friendly)
Your warranty is now void. If you root your device, Your KNOX status will be tripped. You can still pass the safety net after you root if you follow the instructions. I am not responsible for bricked devices, dead SD cards although it is not...
forum.xda-developers.com
For my phone model they use a EVR firm, so I downloaded SamFw_FRP_Tool_v3.0 and changed the CSC of the phone to EVR. I downloaded the most recent EVR firm and I tried to flash it with Odin 3.14.1 modified, but I keep getting a Fail message.
No idea what to do next.