Does OEM unlock need to be re-ticked after rom flash? - Samsung Galaxy Note 9 Questions & Answers

Say on stock I ticked it to unlock, flashed twrp, flashed rom, everything is great. Will it relock itself after the rom flash or will the option just disappear? Thanks.

Don't do that
You might get oem jail if you do

TheUndertaker21 said:
Don't do that
You might get oem jail if you do
Click to expand...
Click to collapse
Im not gonna touch it after it's turned on. Just want to check that it won't re-lock itself.

AngryDinosaur said:
Say on stock I ticked it to unlock, flashed twrp, flashed rom, everything is great. Will it relock itself after the rom flash or will the option just disappear? Thanks.
Click to expand...
Click to collapse
depends. once unlocked it would stay unlocked. but if that option was hidden for 7 days and then appeared, it might disappear if flashing a new rim or firmware or wipe and not allow you to boot and force you to flash back stock a d wait 7 more days before it appeared.
i believe rom devs are well aware of this issue and are 'baking' in the fix in their roms.
i know that back on the note 8, the famous OEM unlock issue was widespread. on the note 9 i am not sure if this is still problematic.

bober10113 said:
depends. once unlocked it would stay unlocked. but if that option was hidden for 7 days and then appeared, it might disappear if flashing a new rim or firmware or wipe and not allow you to boot and force you to flash back stock a d wait 7 more days before it appeared.
i believe rom devs are well aware of this issue and are 'baking' in the fix in their roms.
i know that back on the note 8, the famous OEM unlock issue was widespread. on the note 9 i am not sure if this is still problematic.
Click to expand...
Click to collapse
Good god

Related

Going back from 5.1 to 5.0

Can you go back to 5.0 after flashing 5.1 Roms? Was just wondering because seen a lot of bricks ..Some bricks from licked bootloaders others from flashing..I just don't want to brick because I bought mine from someone and don't have insurance .Unless it could fall under factory warranty replacement....
Sent from my Nexus 6 using Tapatalk
You can upgraded / downgrade from any ROM. Its not a HTC
The locked boot loader issue is user error. If you lock the BL and the phone doesn't boot, you'll have to get Moto to fix it. And yes that would be covered by warranty
rootSU said:
You can upgraded / downgrade from any ROM. Its not a HTC
The locked boot loader issue is user error. If you lock the BL and the phone doesn't boot, you'll have to get Moto to fix it. And yes that would be covered by warranty
Click to expand...
Click to collapse
Do I need to flash old boot loader or radio? Thanks for your time.....mods are welcome to delete
Sent from my Nexus 6 using Tapatalk
kenbrownstone said:
Do I need to flash old boot loader or radio? Thanks for your time.....mods are welcome to delete
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It depends what you're expecting in future. If you want OTA, you'll need everything to be 100% stock and the right version. If you don't care about that, minimum is system.img and boot.img.
i tried to downgrade my bootloader through fastboot from 5.1's bootloader to 5.0.1 and fastboot throws an error from moto saying it cant be downgraded.
have a question. is it ok to flash the factory 5.0.1 system and boot while on the 5.1 bootloader and radio? i have read a few threads of people bricking but it's unclear if it's possible to use an aosp rom that's 5.0.1 or 5.0.2 on 5.1 bootloader and radio.
freebee269 said:
have a question. is it ok to flash the factory 5.0.1 system and boot while on the 5.1 bootloader and radio? i have read a few threads of people bricking but it's unclear if it's possible to use an aosp rom that's 5.0.1 or 5.0.2 on 5.1 bootloader and radio.
Click to expand...
Click to collapse
I had been running Chroma 5.02 with the 5.1 bl and radio. I reverted the radio because of issues with TMo, but the bl seemed fine. FWIW, I made all my changes via fastboot.
kenbrownstone said:
Can you go back to 5.0 after flashing 5.1 Roms? Was just wondering because seen a lot of bricks ..Some bricks from licked bootloaders others from flashing..I just don't want to brick because I bought mine from someone and don't have insurance .Unless it could fall under factory warranty replacement....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Just make sure you have OEM Unlock checked under dev options and you will be fine.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
Just make sure you have OEM Unlock checked under dev options and you will be fine.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It resets on boot. Check it boots before relocking
rootSU said:
It resets on boot. Check it boots before relocking
Click to expand...
Click to collapse
Since it gets reset then do I need to recheck OEM unlock option at every boot or its fine to leave it as it and I can reboot anyway I want?
naresh2990 said:
Since it gets reset then do I need to recheck OEM unlock option at every boot or its fine to leave it as it and I can reboot anyway I want?
Click to expand...
Click to collapse
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
rootSU said:
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
Click to expand...
Click to collapse
Seriously this thing is giving me a headache, I am not going to toggle anything in bootloader now and it's a pain to check this option everytime before doing a reboot, it was good before 5.1, it used to stay as it is.
naresh2990 said:
Seriously this thing is giving me a headache, I am not going to toggle anything in bootloader now and it's a pain to check this option everytime before doing a reboot, it was good before 5.1, it used to stay as it is.
Click to expand...
Click to collapse
Just leave it unlocked. If you plan on manually updating I don't understand why you would lock it. just in case something goes wrong if it's unlocked you have options. If it's locked you have very, very few
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
rootSU said:
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
Click to expand...
Click to collapse
The setting is due to Google's new anti theft options ( http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/ ) . If you have OEM Unlock checked this protection can easily be bypassed with a flash.
Sent from my Nexus 6 using XDA Free mobile app
pwned3 said:
Just leave it unlocked. If you plan on manually updating I don't understand why you would lock it. just in case something goes wrong if it's unlocked you have options. If it's locked you have very, very few
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Konfuzion said:
The setting is due to Google's new anti theft options ( http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/ ) . If you have OEM Unlock checked this protection can easily be bypassed with a flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
But who really cares if a thief can "use" the phone when it is stolen? They can't use it as a phone because the IMEI will be blocked. If they unlock it, it will wipe your data too. I'd rather not have to set an option within android to allow me to unlock my bootloader and the problems here have proven this to be a detriment to people who flash.
naresh2990 said:
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Click to expand...
Click to collapse
rootSU said:
But who really cares if a thief can "use" the phone when it is stolen? They can't use it as a phone because the IMEI will be blocked. If they unlock it, it will wipe your data too. I'd rather not have to set an option within android to allow me to unlock my bootloader and the problems here have proven this to be a detriment to people who flash.
Click to expand...
Click to collapse
I am confused about something if the device is already unlocked does it matter if that OEM is ticked? I reboot twice already and it reset it back to being unticked. So what I am saying is if i go from one rom to another and that isnt ticked will it cause issues even if the bootloader is already unlocked?
naresh2990 said:
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Click to expand...
Click to collapse
No if it is unchecked your bootloader is still unlocked, but you will not be able to unlock it again without booting into your device and checking it again.
Where people are getting bricks is they are downgrading their radio and bootloader, at which point their bootloader relocks, and they are stuck at bootloader as they can't access anything other than bootloader and that is locked.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 07:56 AM ---------- Previous post was at 07:50 AM ----------
the_rooter said:
I am confused about something if the device is already unlocked does it matter if that OEM is ticked? I reboot twice already and it reset it back to being unticked. So what I am saying is if i go from one rom to another and that isnt ticked will it cause issues even if the bootloader is already unlocked?
Click to expand...
Click to collapse
No issues going from Rom to Rom with it unchecked. Issue lies in... No OS so you can't boot up and check oem unlock, stuck at a locked bootloader screen, so you can't flash a custom recover, can't restore because you can't access recovery.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No if it is unchecked your bootloader is still unlocked, but you will not be able to unlock it again without booting into your device and checking it again.
Where people are getting bricks is they are downgrading their radio and bootloader, at which point their bootloader relocks, and they are stuck at bootloader as they can't access anything other than bootloader and that is locked.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 07:56 AM ---------- Previous post was at 07:50 AM ----------
No issues going from Rom to Rom with it unchecked. Issue lies in... No OS so you can't boot up and check oem unlock, stuck at a locked bootloader screen, so you can't flash a custom recover, can't restore because you can't access recovery.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I do use a usb otg stick and usually wipe the entire phone before each rom to make sure I start fresh. After I wipe everything in twrp i go to reboot back into recovery and it brings up the no os are u sure u want to do this. This wont cause issues even if unchecked correct?
the_rooter said:
I do use a usb otg stick and usually wipe the entire phone before each rom to make sure I start fresh. After I wipe everything in twrp i go to reboot back into recovery and it brings up the no os are u sure u want to do this. This wont cause issues even if unchecked correct?
Click to expand...
Click to collapse
No you won't have any issues doing that. If you want to be safe though you should check oem unlock before you start flashing and wiping. We all know flashing doesn't always go as expected and the last thing you want is to end up stuck. As long as oem unlocked is checked recovering from soft bricks is easy.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No you won't have any issues doing that. If you want to be safe though you should check oem unlock before you start flashing and wiping. We all know flashing doesn't always go as expected and the last thing you want is to end up stuck. As long as oem unlocked is checked recovering from soft bricks is easy.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Like I said after a reboot it goes unchecked so if i check it and then reboot to recovery wouldnt that uncheck it again?

[Q] Android M flash

hello guys ) i just wanna ask if its possible to flash android m with nexus root toolkit or no ??
Apparently, yes. https://plus.google.com/113329792100896065459/posts/ZFUJD6Yn4hm
jj14 said:
Apparently, yes. https://plus.google.com/113329792100896065459/posts/ZFUJD6Yn4hm
Click to expand...
Click to collapse
thank you for the fast reply
Yes I followed those steps and flashed it perfectly.
BossJ said:
Yes I followed those steps and flashed it perfectly.
Click to expand...
Click to collapse
yeah same here, everything went more then well.
Should I relock the bootloader after flashing M ?
M5Rahul said:
Should I relock the bootloader after flashing M ?
Click to expand...
Click to collapse
NOOO!!!!
To many folks have encountered an issue that soft-bricked their device afterwards.
You will still receive OTA with an unlocked bootloader.
M5Rahul said:
Should I relock the bootloader after flashing M ?
Click to expand...
Click to collapse
you can relock it (safer) but if you want to flash any new rom later you will loose all your data. cause everytime you flash you need to unlock the bootloader. its up to you
stricker said:
you can relock it (safer) but if you want to flash any new rom later you will loose all your data. cause everytime you flash you need to unlock the bootloader. its up to you
Click to expand...
Click to collapse
Hang on now, lets be clear about the advice that we're giving here.
Yes, a locked bootloader is safer if a thief were to get his hands on your device. However, locking the bootloader has a whole host of other problems linked to it. For example, if you end up in a boot loop with a locked bootloader because something breaks in the rom or kernel, if you have stock recovery, you can never unlock the bootloader again, without sending it for repair.
I would suggest people using experimental ROMs should keep their bootloader unlcoked to avoid this
danarama said:
Hang on now, lets be clear about the advice that we're giving here.
Yes, a locked bootloader is safer if a thief were to get his hands on your device. However, locking the bootloader has a whole host of other problems linked to it. For example, if you end up in a boot loop with a locked bootloader because something breaks in the rom or kernel, if you have stock recovery, you can never unlock the bootloader again, without sending it for repair.
I would suggest people using experimental ROMs should keep their bootloader unlcoked to avoid this
Click to expand...
Click to collapse
If I did lock the boot loader, can it not be unlocked again using NRT ? I'm wondering since this (Android M) is an official release from Google, there should be a way to unlock the Boot loader if someone wants to roll back to lollipop ... Am I wrong in this assumption ?
Sent from my Nexus 6 using Tapatalk
M5Rahul said:
If I did lock the boot loader, can it not be unlocked again using NRT ? I'm wondering since this (Android M) is an official release from Google, there should be a way to unlock the Boot loader if someone wants to roll back to lollipop ... Am I wrong in this assumption ?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It's a security feature whereby if you do not have "enable OEM unlocking" set in the rom, you cannot unlock the bootloader. If you don't have it set, have stock recovery then have a rom that will not boot, you cannot set that, ergo cannot unlock the bootloader. If you're going to mess with exxperiemental previews, I would suggest not re-locking the bootloader.
danarama said:
It's a security feature whereby if you do not have "enable OEM unlocking" set in the rom, you cannot unlock the bootloader. If you don't have it set, have stock recovery then have a rom that will not boot, you cannot set that, ergo cannot unlock the bootloader. If you're going to mess with exxperiemental previews, I would suggest not re-locking the bootloader.
Click to expand...
Click to collapse
I just checked and the 'OEM unlocking' option is turned on under Dev Options.
So, can I unlock the bootloader and flash back to 5.1.1 ?
Sent from my Nexus 6 using Tapatalk
M5Rahul said:
I just checked and the 'OEM unlocking' option is turned on under Dev Options.
So, can I unlock the bootloader and flash back to 5.1.1 ?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you like.

Re locking boot loader.

Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.
H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.
-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.
Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.
Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.

Oem bootloader v3

Hello. I routed my phone. then i installed alexega rum phone was brick. then I accidentally installed the bootloader v3. my oem key does not appear. I loaded stock rom. Will my OEM key switch on?
cani10101997 said:
Hello. I routed my phone. then i installed alexega rum phone was brick. then I accidentally installed the bootloader v3. my oem key does not appear. I loaded stock rom. Will my OEM key switch on?
Click to expand...
Click to collapse
If your oem is gone you have to wait 7 days or 168 hrs for it to appear again.
Once you get oem back follow the post by BlackMesa123 that removes rlc apk and changes the rmm in build.prop and do it every time you flash a Rom.
https://forum.xda-developers.com/sa...root-january-security-patch-sm-t3739225/page3
BluePhnx said:
If your oem is gone you have to wait 7 days or 168 hrs for it to appear again.
Once you get oem back follow the post by BlackMesa123 that removes rlc apk and changes the rmm in build.prop and do it every time you flash a Rom.
https://forum.xda-developers.com/sa...root-january-security-patch-sm-t3739225/page3
Click to expand...
Click to collapse
So it's coming back in 7 days, OEM?
cani10101997 said:
So it's coming back in 7 days, OEM?
Click to expand...
Click to collapse
Yes it should.
sefrcoko said:
Yes it should.
Click to expand...
Click to collapse
Bootloader locked v3 installed. Will the OEM still open?
cani10101997 said:
Bootloader locked v3 installed. Will the OEM still open?
Click to expand...
Click to collapse
If you have sm-n950f (single sim) or sm-n950f/ ds (duel sim) (Both Exynos SOCs.)
Then it will come after 7 days.
Here read this thread.
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
1 week passed oem did not come What should I do ?
cani10101997 said:
1 week passed oem did not come What should I do ?
Click to expand...
Click to collapse
if you flashed stock or wiped to factory defaults since, then the counter might also have reset each time. wait 7 days without flashing or reseting your phone.
in the mean time read up on the various OEM unlock and bootloader v3 threads. it will stop you from making bad choices since your phone will inevitably go back to 'jail' and you will know what to expect/do.
It's been 8 days but I still have not done anything yet. is there any chance he will not come?

Redmi 9C bootloop issue

hello, i have a problem with my redmi 9c
my phone just started bootloping alone, i went to sleep and i woke up with my phone dead
the phone is stock, no root, no custom recovery and still with bootloader locked because i don't need features who need it, i can access fastboot but recovery is not posible to reach because Vol+/Power is useless, the phone do nothing pressing those buttons, only with Vol-/Power, so i can't make a factory reset or wipe data, the only thing what i did a couple of hours before the phone broke was change my security pattern (i don't think it's related anyway...), and it was 8 or 10 hours before the issue. sadly the phone warranty expired in january and i have nothing to do at this moment
the phone stops the bootloop after draining the battery, with the bootloader locked of course i'm unable to flash a stock rom, even with MiFlash
what could be the problem?
thanks! (and sorry for my bad english, spanish native here)
aniangaZR said:
hello, i have a problem with my redmi 9c
my phone just started bootloping alone, i went to sleep and i woke up with my phone dead
the phone is stock, no root, no custom recovery and still with bootloader locked because i don't need features who need it, i can access fastboot but recovery is not posible to reach because Vol+/Power is useless, the phone do nothing pressing those buttons, only with Vol-/Power, so i can't make a factory reset or wipe data, the only thing what i did a couple of hours before the phone broke was change my security pattern (i don't think it's related anyway...), and it was 8 or 10 hours before the issue. sadly the phone warranty expired in january and i have nothing to do at this moment
the phone stops the bootloop after draining the battery, with the bootloader locked of course i'm unable to flash a stock rom, even with MiFlash
what could be the problem?
thanks! (and sorry for my bad english, spanish native here)
Click to expand...
Click to collapse
Hi, my first guess would be faulty hardware, for example a dead motherboard.
Is there any error when attempting to flash the Stock ROM with MiFlash? Afaik you should be able to flash Stock ROMs even with locked bootloader.
Fatal_Scythe said:
Hi, my first guess would be faulty hardware, for example a dead motherboard.
Is there any error when attempting to flash the Stock ROM with MiFlash? Afaik you should be able to flash Stock ROMs even with locked bootloader.
Click to expand...
Click to collapse
Thanks for the quick reply
MiFlash said "not allowed in locked state" and I guess it's because of locked bootloader, I should try with a specific stock rom?
aniangaZR said:
Thanks for the quick reply
MiFlash said "not allowed in locked state" and I guess it's because of locked bootloader, I should try with a specific stock rom?
Click to expand...
Click to collapse
Hmm okay, yeah that sounds like it's preventing you from flashing simply because your bootloader is locked.
Which Stock ROM did you try? Same as the currently installed version or an older one?
Fatal_Scythe said:
Hmm okay, yeah that sounds like it's preventing you from flashing simply because your bootloader is locked.
Which Stock ROM did you try? Same as the currently installed version or an older one?
Click to expand...
Click to collapse
I tried with the last available rom and the previous one, automatic updates were disabled, but I know I updated the phone after buying it
I don't remember if the phone was running last version...
MiFlash should let me flash the phone with the same installed ROM even with bootloader locked?
aniangaZR said:
I tried with the last available rom and the previous one, automatic updates were disabled, but I know I updated the phone after buying it
I don't remember if the phone was running last version...
MiFlash should let me flash the phone with the same installed ROM even with bootloader locked?
Click to expand...
Click to collapse
If you tried an older firmware, it's possible that it didn't flash because of Xiaomi's "Anti-Rollback" Feature which exists to prevent users from Downgrading.
But yes, it should let you flash the same version afaik.
What Region is your Device? On Locked Bootloader you can only flash Firmwares that are from the same Region. (For example Global or EEA)
Fatal_Scythe said:
If you tried an older firmware, it's possible that it didn't flash because of Xiaomi's "Anti-Rollback" Feature which exists to prevent users from Downgrading.
But yes, it should let you flash the same version afaik.
What Region is your Device? On Locked Bootloader you can only flash Firmwares that are from the same Region. (For example Global or EEA)
Click to expand...
Click to collapse
Device is global region, I will try with all versions available, I'll keep updated
Thanks!
aniangaZR said:
Device is global region, I will try with all versions available, I'll keep updated
Thanks!
Click to expand...
Click to collapse
Alright, have you btw tried flashing directly via fastboot?
Meaning opening terminal and from there flashing all partitions one by one for example "fastboot flash boot boot.img" ?
Fatal_Scythe said:
Alright, have you btw tried flashing directly via fastboot?
Meaning opening terminal and from there flashing all partitions one by one for example "fastboot flash boot boot.img" ?
Click to expand...
Click to collapse
Fastboot doesn't work either, said similar message related to locked bootloader
I'm downloading a couple of roms now
aniangaZR said:
Fastboot doesn't work either, said similar message related to locked bootloader
I'm downloading a couple of roms now
Click to expand...
Click to collapse
Oh okay then.
If in the worse case nothing works, your last (paid) solution would probably be to contact one of these "Mi Auth" Guys on Telegram. They have acess to Authorized Accounts that are able to flash your Phone in EDL Mode (might need to open your phone to short test-points though)
I had to pay them about 20€ to get my old Mi 11 (which I sold a while ago) running again after it got stuck in EDL Mode. :/
Fatal_Scythe said:
Oh okay then.
If in the worse case nothing works, your last (paid) solution would probably be to contact one of these "Mi Auth" Guys on Telegram. They have acess to Authorized Accounts that are able to flash your Phone in EDL Mode (might need to open your phone to short test-points though)
I had to pay them about 20€ to get my old Mi 11 (which I sold a while ago) running again after it got stuck in EDL Mode. :/
Click to expand...
Click to collapse
same problem with all ROMs, same message related to bootloader
thanks anyway!

Categories

Resources