About xiomi redmi note 5 ai fake rom and fake unlocking problem - Xiaomi Redmi Note 5 Pro Questions & Answers

I bought a xiomi redmi note 5 ai which contains a fake rom( 9.5.13.0.0 OEIMIFA). In developers option it shows me that my device is unlocked but in fastboot it is actually locked. I tried to unlock it but couldn't get succeed. I also tried xiaomitool, xiaomi flash, some adb and edl proccess but couldn't get any success. In forum I saw test point twice method for whyred but I couldn't active edl by doing this hardware functionality because my device is new and I am also a noob in those matter. My mi id also unauthorised. Is there any chance that I can flash Official China stable rom and get the official update??? I am so disappointed with this. Experts, please help me to flash official rom on note 5 ai. give e some solutions.

Yeah I wanna know about this topic too. Many sellers are sending unsealed products and bootloader saying unlocked.

I'm in this situation too! So sad

This is really weird....In dev options phone says "Unlocked" but when you reboot there is no "Unlocked" sign under Mi logo...WTF?????

You will need to give some more detailed information for people to help you. Go on the guides section, find one of the many bootloader unlock guides and follow it step by step: at which point does it not work, and what kind of error do you get?
You also mention your account not being authorized: if that is the case, then you absolutely need to get it authorized first, there's no way around that (short of finding someone with an authorized account to help you, I guess).
By the way, I would not focus too much on the fact that Developer options report the device as unlocked, if the ROM is unofficial, that is easy to fake. Whoever flashed the u unauthorized ROM must have then relocked the bootloader after flash.

this is why xiaomi has changed the way bootloader unlocks to prevent sellers from doing this.

raptorddd said:
this is why xiaomi has changed the way bootloader unlocks to prevent sellers from doing this.
Click to expand...
Click to collapse
To my knowledge, the new unlock policy just adds more time before unlock and makes it harder to use the same account for multiple unlocks. I would say it discourages sellers from doing this, but the more resourceful ones will keep doing what they always did, while us users have to endure the whole thing.

I got my redmi note 5 ai, it was already unlocked. can someone point out if it's good? In developer options says unlocked. I turned on usb debugging but OEM unlock is greyed out. Verity mode: true, device unlocked: true and device critical unlocked: true

My first R5+ came with an unlocked bootloader but the unlock process made it for the seller can corrupt eventually some partition or even unsuccesfull, they are not intend to unlock but change a chinese rom for a global and through the process device could get unlocked (time before, I guess not actually).
The most indisputable way without a doubt to know this is simply going to fastboot mode and typing
Code:
fastboot oem device-info
so fastboot reads at a low level directly in the right partition. There are some discussion on where is place this condition, some thinks that is in bootloader itself but others believe that it is in persist partition.

That's what I did. What do you think?
https://imgur.com/a/JO4lNy7

Remig83 said:
That's what I did. What do you think?
https://imgur.com/a/JO4lNy7
Click to expand...
Click to collapse
It's unlocked

SubwayChamp said:
It's unlocked
Click to expand...
Click to collapse
Thanks for the confirm. Still can't figure out how to turn on OEM unlock. Maybe cause I haven't done a mi account yet.

Remig83 said:
Thanks for the confirm. Still can't figure out how to turn on OEM unlock. Maybe cause I haven't done a mi account yet.
Click to expand...
Click to collapse
You mean unlock OEM in developer options? turn off USB debugging and then turn on again and now enable OEM unlock

SubwayChamp said:
You mean unlock OEM in developer options? turn off USB debugging and then turn on again and now enable OEM unlock
Click to expand...
Click to collapse
Yes that's what I meant. Done what you said, still didn't turn on.

Remig83 said:
Yes that's what I meant. Done what you said, still didn't turn on.
Click to expand...
Click to collapse
If it is in a greyish, as unmarked so you can touch the toggle but is in positive OEM unlock? then don´t worry about that.
Just look at it before and after to do some update.

SubwayChamp said:
If it is in a greyish, as unmarked so you can touch the toggle but is in positive OEM unlock? then don´t worry about that.
Just look at it before and after to do some update.
Click to expand...
Click to collapse
It is greyish yes, on negative as in off. I will try and make a mi account, see if it helps.

Related

Boot Loader unlocked but cant install TWRP

I bought Redmi Note 5 AI today which Boot Loader status was unlocked in the "developer option" previously and installed Global Stable 9.5.13 previously.
now when I tried to flash TWRP through cmd, it says "flashing is not allowed in lock state"
then when I checked OEM status through cmd, it shows :
Verity mode: true
Device Unlocked: false
Device Critical unlocked: false
What happen when you unlock again by MiUnlocker?
That is fake unlock. Still trying to figure it out that problem. Even flashing couple of time didn't solve it.
Zanr Zij said:
What happen when you unlock again by MiUnlocker?
Click to expand...
Click to collapse
Yes. I forget to mention that. It says "this account is not bound to this device" when I connected with mi unlock tools. For additional information, I used the same MI account for both mobile and mi unlock tools. I also synced successfully and activated find my device on mi web before I connected to the PC.
yulikn said:
That is fake unlock. Still trying to figure it out that problem. Even flashing couple of time didn't solve it.
Click to expand...
Click to collapse
Fake unlock ??? what is that.? The phone was in Chinese stable rom. Then the seller changed it's rom to global by himself. I don't know anything else. But did you face the same problem like me ?
You need to do:
- Add your device to OEM unlock if need
- Activate Mi Message through Setting - System app - Message
zahidhasanzahid said:
Fake unlock ??? what is that.? The phone was in Chinese stable rom. Then the seller changed it's rom to global by himself. I don't know anything else. But did you face the same problem like me ?
Click to expand...
Click to collapse
Yes, one of my friend's whyred got fake unlock. It is still locked, but you can't unlock it because the status is unlocked. You must entering EDL mode and flash it. But you need permission from Xiaomi to do it. I don't know if they still open for new permissions.

Bootloader bounty? Too soon?

Is it too soon to start a bounty for a bootloader unlock? Do we even have any devs using this device(Lm-G710TM)? Im good for $100+.
It's not soon for USA unlocked (G710ULM) because 11th July was the release, till now why there's no bootloader for this unlocked variant! Already European variant enjoying root.
I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.
totally agree, this is a great and solid phone. Could use a few tweaks and it'll be even better!
Alcolawl said:
I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.
Click to expand...
Click to collapse
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I know VZW it's all locked The OEM switch is missing also. I'm assuming for at least Verizon there needs to be an exploit if ever found.
For now, I am just talking about the TMO version.
-- Brian
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-g7-thinq/help/t-mobile-oem-unlock-t3833156
runningnak3d said:
For now, I am just talking about the TMO version.
-- Brian
Click to expand...
Click to collapse
Welcome aboard mate, been looking for your presence here but was doubting it as you don't have this device as of yet. I'm happy to see you and say that I was wrong, can't thank you enough for the work you have done on other devices.
Will be more than willing to help anyway I can, although I am currently on the sprint variant for the moment.
Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian
runningnak3d said:
Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian
Click to expand...
Click to collapse
LG G710ULM owner here. I know it's not specifically a T-Mobile version but it does allow OEM unlocking by default. I could be wrong, but I'm guessing the differences between the G710TM and G710ULM aren't that big (if any at all). If you need any info from my end, let me know. I'd love to get the ball rolling on bootloader unlocks for this phone. Lots of untapped potential here.
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Upon rebooting into Bootloader I'm presented with a quick guide for unlocking the phone:
1) Read Device ID
:fastboot oem device-id
2) Write Unlock Key
:fastboot flash unlock unlock.bin
3)Check bootloader is unlocked
:fastboot getvar unlocked
fastboot oem unlock results in a FAILED (remote: 'unknown command') message. Screenshot attached. My first attempt didn't work because I guess I didn't have the right bootloader drivers installed.
So it looks like even the unlocked models are in the same boat as everyone else, except Europe.
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.
20degrees said:
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.
Click to expand...
Click to collapse
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.
Alcolawl said:
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.
Click to expand...
Click to collapse
Be forewarned, I've noticed that fastboot doesn't always work, despite latest drivers. As of late, the Pixel has been known to hang on these same commands at times as well. My Moto Z2 Force suffers from this error as well.
---------- Post added at 04:11 AM ---------- Previous post was at 04:04 AM ----------
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I hope you know many are INCREDIBLY excited to have you on board! I'm not advanced, but once I receive my computer back, I'll definitely be available to help with providing info and helping test, as I have a TMO variant (I may or may not work for TMO as well, so yeah... )
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Own a TMobile variant, oem unlocking option is there, fastboot commands do not work (or are extremely limited)
getprop | grep unlock (if it means anything)
[Ro.oem_unlock_supported]: [1]
[Sys.oem_unlock_allowed]: [1]
I know I probably didn't help out much, if you have any other questions feel free to ask I'll help out as much as I can. thank you for contributions and congrats on the V30 root.
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I have the tmobile variant. Let me know what you might need.
Unlock Slider is present in developer settings and is not greyed out. Unlock command just hangs.
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Sprint variant also has "Allow OEM unlocking" available and it is changeable
So you can issue fastboot flashing unlock_critical but not fastboot flashing unlock -- that is just weird.
If you issue the unlock_critical, do you get the warning that your phone is possibly corrupt, but will continue to boot?
-- Brian

Update options not listed in config, and no OEM unlock listed in Dev Options

The title pretty much describe the whole issue: I get a persistent notification that there's an OTA update to install, but touching the notification does nothing.
There seem to be no way of manually installing it either, because there is no update option listed in the configuration.
Can't unlock the bootloader either, because there is no OEM unlock listed in the dev tools.
I've never seen anything like this. Spent days researching, but found nothing. So here I'm hoping someone might have a clue about how to enable updates and OEM unlock in a situation like this.
Any help is appreciated.
This phone is a Xiaomi Mi A2 Lite model M1805D1SG, running Android 8.1 (OPM 1.171019.019.V9.6.6.0ODLMIFF)
you system is clean or modified (magisk etc)?
eremitein said:
you system is clean or modified (magisk etc)?
Click to expand...
Click to collapse
How should he modify or root it with a locked bootloader?
nquil said:
Can't unlock the bootloader either, because there is no OEM unlock listed in the dev tools.
Click to expand...
Click to collapse
for unlocking the bootloader you have to use ADB tools. you can't just unlock it in developer setting.
for your problem i would recommend you too check the forums on how to unlock the bootloader with adb and then grab the latest official A2 lite rom (10.0.40. or something i guess) and flash it with the MiFlashTool.
this procedure will upgrade your device without any loss of data.
I'm telling you this because that's how i update my device (which is rooted and kernel modified) with no problems.
thorin0815 said:
How should he modify or root it with a locked bootloader?
Click to expand...
Click to collapse
maybe early somebody did this with his phone:laugh:
so need to more checking
eremitein said:
you system is clean or modified (magisk etc)?
Click to expand...
Click to collapse
It is clean.Brand new device, unable to do anything, as it is OEM locked.
merlin.berlin said:
for unlocking the bootloader you have to use ADB tools. you can't just unlock it in developer setting.
for your problem i would recommend you too check the forums on how to unlock the bootloader with adb and then grab the latest official A2 lite rom (10.0.40. or something i guess) and flash it with the MiFlashTool.
this procedure will upgrade your device without any loss of data.
I'm telling you this because that's how i update my device (which is rooted and kernel modified) with no problems.
Click to expand...
Click to collapse
True. We usually need to run 'fastboot oem unlock' to actually unlock the bootloader. Problem is, the command needs one to enable OEM unlocking in the developer options beforehand, otherwise it fails. And I dont have any means to enable OEM unlocking in the dev options, because it is not listed at all!
And without that I'm unable of doing any flashing.
The only report I found regarding a missing an OEM unlock option in the dev tools concern Samsung S9. Apparently one needs to wait 7 days for it to appear. But such a thing is unheard of concerning a Xiaomi phone.
eremitein said:
maybe early somebody did this with his phone:laugh:
so need to more checking
Click to expand...
Click to collapse
I have been researching this for days, couldn't find anything... Didn't find a single report about OEM unlock not showing up in Developer options for Xiaomi Mi A2 Lite, at all.
nquil said:
True. We usually need to run 'fastboot oem unlock' to actually unlock the bootloader. Problem is, the command needs one to enable OEM unlocking in the developer options beforehand, otherwise it fails. And I dont have any means to enable OEM unlocking in the dev options, because it is not listed at all!
And without that I'm unable of doing any flashing.
The only report I found regarding a missing an OEM unlock option in the dev tools concern Samsung S9. Apparently one needs to wait 7 days for it to appear. But such a thing is unheard of concerning a Xiaomi phone.
Click to expand...
Click to collapse
Could you post a screenshot of your System menu under settings?
nquil said:
I have been researching this for days, couldn't find anything... Didn't find a single report about OEM unlock not showing up in Developer options for Xiaomi Mi A2 Lite, at all.
Click to expand...
Click to collapse
show screenshots from dev settings with blanked OEM unlock and from about phone information (build, kernel etc)
capajga said:
Could you post a screenshot of your System menu under settings?
Click to expand...
Click to collapse
Sure. Let's see if it works this time around
Here are the screenshots. (Attached)
nquil said:
Here are the screenshots. (Attached)
Click to expand...
Click to collapse
Could it be that the OEM unlock option is under Development tools?
capajga said:
Could you post a screenshot of your System menu under settings?
Click to expand...
Click to collapse
Sure, here goes (i hope!) --> https://imgur.com/gallery/c77LPsS
capajga said:
Could it be that the OEM unlock option is under Development tools?
Click to expand...
Click to collapse
Nope. See screenshots.---> https://imgur.com/a/b0SXeV0
I wonder if there's a way to enable it through command line, in a local shell (inside android)
nquil said:
Nope. See screenshots.---> https://imgur.com/a/b0SXeV0
Click to expand...
Click to collapse
Strange
I'm on 9.6.11.0 version and it's there. You're on 9.6.6.0 version. Maybe there's someone who had experience with 9.6.6.0 and OEM unlocking but if not there's always the option to do an OTA update to a newer firmware version.
Just don't update to a 10.x.x.x version (Pie) if you want to keep Oreo
capajga said:
Strange
I'm on 9.6.11.0 version and it's there. You're on 9.6.6.0 version. Maybe there's someone who had experience with 9.6.6.0 and OEM unlocking but if not there's always the option to do an OTA update to a newer firmware version.
Just don't update to a 10.x.x.x version (Pie) if you want to keep Oreo
Click to expand...
Click to collapse
Can't do an OTA update either. Check closely: along with OEM unlock, there is no system update option.
eremitein said:
show screenshots from dev settings with blanked OEM unlock and from about phone information (build, kernel etc)
Click to expand...
Click to collapse
I have posted them in posts previous to this one. Please take a look.
nquil said:
Can't do an OTA update either. Check closely: along with OEM unlock, there is no system update option.
Click to expand...
Click to collapse
Yeah, saw it the second time i looked
It sais security update from December 2018 but the build is 9.6.6.0
My screenshots:

Unlock bootloader on Samsung A300FU without OEM Unlock by carrier design

Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
-sofiann- said:
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
Click to expand...
Click to collapse
I assume you know that the OEM unlock toggle is in the developer settings? To enable developers settings, tap build number repeatedly until it says you are now a developer. You will need no fancy trick to show it as the lock that hides OEM unlock, only came out in oreo. I don't think carriers disable OEM unlock on Samsung's but I could be wrong. Lastly, if you get it figured out, go over here to the right thread and get it rooted. Good luck! https://forum.xda-developers.com/sa.../how-to-root-twpr-flash-a300fu-a300y-t3494362
SnowFuhrer said:
I assume you know that the OEM unlock toggle is in the developer settings? To enable developers settings, tap build number repeatedly until it says you are now a developer. You will need no fancy trick to show it as the lock that hides OEM unlock, only came out in oreo. I don't think carriers disable OEM unlock on Samsung's but I could be wrong. Lastly, if you get it figured out, go over here to the right thread and get it rooted. Good luck! https://forum.xda-developers.com/sa.../how-to-root-twpr-flash-a300fu-a300y-t3494362
Click to expand...
Click to collapse
Thank you for the answer.
You assume right. I enabled developers settings first, saw that I didn't have OEM unlock option visible, then started to look about this issue. It is quick to see that in many case, even for phone not on OREO (I'm with Marshmallow 6.0.1), this OEM unlock is missing. But based on internet available data, it seems that in most of the case there is a trick to make it visible again. It is a sort of samsung security against thief that hide this option for seven days.
The trick didn't work for me and by looking more I saw that some people seems to be facing the same situation as mine. Some suggest that it is disabled by carrier.
But I couldn't find a solution anywhere for that context.
My question remains.
Here is a more detailed explanation :
from https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
""There are two kinds of phones in this world: Those that let you unlock your bootloader, and those that don’t.
Whether you’re allowed to unlock your bootloader depends on the manufacturer of your phone, the model you have, and even your carrier. Nexus phones are all unlockable by nature, and many phones from Motorola and HTC allow you to unlock your bootloader through a similar process as the Nexus.
Other phones, however–and some carriers–don’t allow you to unlock your bootloader the official way, which means you have to wait for developers to exploit a security vulnerability if you want to root and flash ROMs. If you have one of those phones, this guide will sadly not help you.
The best way to find out which category your phone falls into is to browse its section at XDA Developers. If you have an HTC or Motorola phone, you may be able too research its unlockability on HTC or Motorola’s website. If it doesn’t support unlocking, you’ll have to use an unofficial unlocking or rooting method, which you’ll usually find on the XDA Developers forums.""
-sofiann- said:
Thank you for the answer.
You assume right. I enabled developers settings first, saw that I didn't have OEM unlock option visible, then started to look about this issue. It is quick to see that in many case, even for phone not on OREO (I'm with Marshmallow 6.0.1), this OEM unlock is missing. But based on internet available data, it seems that in most of the case there is a trick to make it visible again. It is a sort of samsung security against thief that hide this option for seven days.
The trick didn't work for me and by looking more I saw that some people seems to be facing the same situation as mine. Some suggest that it is disabled by carrier.
But I couldn't find a solution anywhere for that context.
My question remains.
Here is a more detailed explanation :
from https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
""There are two kinds of phones in this world: Those that let you unlock your bootloader, and those that don’t.
Whether you’re allowed to unlock your bootloader depends on the manufacturer of your phone, the model you have, and even your carrier. Nexus phones are all unlockable by nature, and many phones from Motorola and HTC allow you to unlock your bootloader through a similar process as the Nexus.
Other phones, however–and some carriers–don’t allow you to unlock your bootloader the official way, which means you have to wait for developers to exploit a security vulnerability if you want to root and flash ROMs. If you have one of those phones, this guide will sadly not help you.
The best way to find out which category your phone falls into is to browse its section at XDA Developers. If you have an HTC or Motorola phone, you may be able too research its unlockability on HTC or Motorola’s website. If it doesn’t support unlocking, you’ll have to use an unofficial unlocking or rooting method, which you’ll usually find on the XDA Developers forums.""
Click to expand...
Click to collapse
The trick didn't work for you because there is no security thing on marshmallow. What carrier are you on if you don't mind telling? Samsung's aren't bootloader unlocked like other phones.
-sofiann- said:
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
Click to expand...
Click to collapse
The Galaxy A3 2015 (SM-A300FU) has no OEM unlock as A3 from 2015 don't even have FRP Lock, neither it has RMM state. That means there is no lock which prevents you to flash any custom binaries like TWRP recovery with Odin. You'll only lose access to knox apps/services (because of knox 0x1), rest remains the same.
SnowFuhrer said:
The trick didn't work for you because there is no security thing on marshmallow. What carrier are you on if you don't mind telling? Samsung's aren't bootloader unlocked like other phones.
Click to expand...
Click to collapse
Hi !
About my device, here are details :
Samsung A300FU
Android 6.0.1
BASEBAND VERSION : A300FUXXU1CPH3
Build number : MMB29M.A300FUXXS1CQD5
Carrier was French company called Bouygues.
About bootloader lock or not, I can see on various website that many samsung are bootloader locked but can be unlocked easily by this OEM unlock option. Sometimes it is missing. Two reasons for that : Security check that is removed after 7 days or apparently permanently removed by carrier or geographic area control.
If i'm in that last case, is there any other solution to unlock the boatloader ?Or the phone is just unrootable. It seems strange to me that some phone are just unrootable.
Thanks again !
-sofiann- said:
Hi !
About my device, here are details :
Samsung A300FU
Android 6.0.1
BASEBAND VERSION : A300FUXXU1CPH3
Build number : MMB29M.A300FUXXS1CQD5
Carrier was French company called Bouygues.
About bootloader lock or not, I can see on various website that many samsung are bootloader locked but can be unlocked easily by this OEM unlock option. Sometimes it is missing. Two reasons for that : Security check that is removed after 7 days or apparently permanently removed by carrier or geographic area control.
If i'm in that last case, is there any other solution to unlock the boatloader ?Or the phone is just unrootable. It seems strange to me that some phone are just unrootable.
Thanks again !
Click to expand...
Click to collapse
If you read @prototype74 's post it explains it quite well. I think your bootloader is already unlocked if I read right.
SnowFuhrer said:
If you read @prototype74 's post it explains it quite well. I think your bootloader is already unlocked if I read right.
Click to expand...
Click to collapse
Hi !
Thank you very much both of you for your help. Indeed there was no OEM unlock.
Many posts talking about OEM unlock existing on that A3 and the fact that I couldn't check if it was locked or not using the two methods advised (with adb or with a special code to dial up on the phone interface) led me to stop at that step to be sure before going on.
It is advises not to root a divise with a bootloader locked to avoid bricking it.
Anyway, trusting your input I did the whole process of rooting and putting a custom rom and it's all great !

Question i heard something about bootloader un/relocking

is it true that relocking a unlocked bootloader erases everything, but you can re-unlock it ever again on xiaomi devices?
testask123 said:
is it true that relocking a unlocked bootloader erases everything, but you can re-unlock it ever again on xiaomi devices?
Click to expand...
Click to collapse
yep i already tried it
khazzey said:
yep i already tried it
Click to expand...
Click to collapse
there's no tool to re-unlock it? its forever locked?
testask123 said:
there's no tool to re-unlock it? its forever locked?
Click to expand...
Click to collapse
Just use xiaomi flash tool, as it can also re-lock your bootloader.
Hi,
I am new Poco F3 owner,
I got the Amazon black Friday deal £50 off,
my variant has 8gb of rom & 256gb of ram, all this for £269.00p,
what an Amazing price and also comes with 2 years warranty here in the UK.
I have been a LG users for many years, using the (G2, G4, and for now a G7) .
I have installed many custom roms on these devices over the last 8 years.
Unlocking/locking there bootloader have been relatively straight forward.
I asking the same question that I am sure has been asked many times before,
once my 7 days are up and i have unlocked my bootloader and i then lock it again,
but then further down the line i decide to unlock it again,
do i have to wait another 7 pointless days.
I'm loving the new poco F3, apart from the firmware is a bit restrictive,
hence why I'm unlocking the bootloader.
What a great community the F3 has , long may it continue,
regards,
Johnr64
johnr64 said:
Hi,
I am new Poco F3 owner,
I got the Amazon black Friday deal £50 off,
my variant has 8gb of rom & 256gb of ram, all this for £269.00p,
what an Amazing price and also comes with 2 years warranty here in the UK.
I have been a LG users for many years, using the (G2, G4, and for now a G7) .
I have installed many custom roms on these devices over the last 8 years.
Unlocking/locking there bootloader have been relatively straight forward.
I asking the same question that I am sure has been asked many times before,
once my 7 days are up and i have unlocked my bootloader and i then lock it again,
but then further down the line i decide to unlock it again,
do i have to wait another 7 pointless days.
I'm loving the new poco F3, apart from the firmware is a bit restrictive,
hence why I'm unlocking the bootloader.
What a great community the F3 has , long may it continue,
regards,
Johnr64
Click to expand...
Click to collapse
No, you only have to wait the first time.
This waiting time is not so pointless as it seems however. It is there to discourage a.o. the many traders flashing (often fake) 'global' roms on Chinese phones and selling them as genuine global models for extra profit. So in the end it's only for your protection, because flashing roms invalidates warranty.
so just to clarify there is no limit on unlocking and relocking this phone right?
testask123 said:
there's no tool to re-unlock it? its forever locked?
Click to expand...
Click to collapse
xiaomi unlock tool its infinite dont worry, but be extreme cautious when you are locking your bootloader make sure your are in your right stock rom and dont forget to unlock again when you are going to flash custom roms and recovery
To lock the bootloader you can simply use "fastboot oem lock" in fastboot mode. Note that doing so will (obviously) factory reset your phone.
user0u said:
To lock the bootloader you can simply use "fastboot oem lock" in fastboot mode. Note that doing so will (obviously) factory reset your phone.
Click to expand...
Click to collapse
ok, another question:
in the event where i lose my phone an unlocked bootloader can bypass any password protection if they have the knowledge right?
is there any way to protect the phone from this?
testask123 said:
ok, another question:
in the event where i lose my phone an unlocked bootloader can bypass any password protection if they have the knowledge right?
is there any way to protect the phone from this?
Click to expand...
Click to collapse
If you mean screen lock, yes they can bypass it. But they cannot get into your banking apps or others which have their own passwords.
If you are really keen on it, just lock the bootloader.

Categories

Resources