Related
Due to organizational requirements the bootloader needs to be locked. So, here go the questions:
After flashing factory image (5.1.0 (LMY47E), is it safe to re-lock bootloader?
And when, after the final reboot and before setup?
And, will the command, fastboot oem lock, wipe EVERYTHING off the phone, like fastboot oem unlock does?
And does the Developer options setting, "OEM unlocking", need to be turned on prior to the lock?
Thanks
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
By the way, this was a completely stock Nexus 6 (5.0.1), no root, no apps other than Google. Before the factory image flash, the "OEM Unlocking" setting in Developer Options was persistent during power on/off. Now, with 5.1 the setting turns itself off during power on/off.
So, should I re-lock the bootloader and satisfy organizational requirements and risk a boot loop or proceed unlocked? Kinda feel like a "deer in the headlights" !
clairez said:
By the way, this was a completely stock Nexus 6 (5.0.1), no root, no apps other than Google. Before the factory image flash, the "OEM Unlocking" setting in Developer Options was persistent during power on/off. Now, with 5.1 the setting turns itself off during power on/off.
So, should I re-lock the bootloader and satisfy organizational requirements and risk a boot loop or proceed unlocked? Kinda feel like a "deer in the headlights" !
Click to expand...
Click to collapse
Well its your choice. I recommend not locking it. However, if you do lock it and end up bricked, at least we know its the locking that causes the loop and not the flash but.... Is it worth it?
If your organization is supplying the device ( or the money for the device) you have no business unlocking it. At my organization people are fired for such things.
If they are not compensating you somehow then I don't see how they can make requirements on your device.
Sent from my Nexus 6
And if it is the unlocking/locking that causes the boot loop (hard brick) then any flashing operation that requires unlocking the bootloader will require that the system remain unlocked forever. A penalty that will afflict a portion (large?) of the Nexus 6 community. Was this an issue before 5.0? Makes one wonder if this is by design or accidental.
DebianDog said:
If they are not compensating you somehow then I don't see how they can make requirements on your device.
Click to expand...
Click to collapse
Yes we totally can. If you work for my company and decide you would rather use your own device for corporate email and data, that data is ours. You may use your own device but we will manage it. If it gets stolen, we will wipe it. You will adhere the same policies for corporate owned data as you will with a phone supplied by us. You will have lock screen, you will be unrooted. You will keep your bootloaders locked. Or you can use this sh*tty Nokia.
My hardware, but if I want to utilize it in the organization, then I must abide by their rules.
This post was not meant to be an organizational ethics discussion, just a request for guidance. If anyone can give me input on the original questions, I would greatly appreciate it. Especially the wipe side effect of the lock operation. Do not want to spend a lot of time configuring the device if it will be erased.
Thanks in advance
clairez said:
My hardware, but if I want to utilize it in the organization, then I must abide by their rules.
Click to expand...
Click to collapse
Yep. Absolutely.
rootSU said:
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
Click to expand...
Click to collapse
Just a little thinking out loud here. Wouldn't it be safe to have OEM Unlock checked under dev options, lock the bootloader, if you happen to bootloop OEM Unlock is still checked so you could still unlock? And then upon first boot OEM Unlock would get unchecked.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
Just a little thinking out loud here. Wouldn't it be safe to have OEM Unlock checked under dev options, lock the bootloader, if you happen to bootloop OEM Unlock is still checked so you could still unlock? And then upon first boot OEM Unlock would get unchecked.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Safe? No.. The flag resets at boot. Boot loop partially boots and it could be enough to reset the flag "at first boot"
Pretty much everything is an unknown here. We do t even know where the "enable OEM unlock" flag is set. Is it in the BL or one of the various partitions? What effect would setting the flag and wiping the OS have? We just don't know.
rootSU said:
Safe? No.. The flag resets at boot. Boot loop partially boots and it could be enough to reset the flag "at first boot"
Pretty much everything is an unknown here. We do t even know where the "enable OEM unlock" flag is set. Is it in the BL or one of the various partitions? What effect would setting the flag and wiping the OS have? We just don't know.
Click to expand...
Click to collapse
Good point. That's why more heads are better than one. I still think my theory would work, but yet I wouldn't be willing to risk my N6 on it, wouldn't suggest others do either.
Sent from my Nexus 6 using XDA Free mobile app
clairez said:
Due to organizational requirements the bootloader needs to be locked. So, here go the questions:
After flashing factory image (5.1.0 (LMY47E), is it safe to re-lock bootloader?
And when, after the final reboot and before setup?
And, will the command, fastboot oem lock, wipe EVERYTHING off the phone, like fastboot oem unlock does?
And does the Developer options setting, "OEM unlocking", need to be turned on prior to the lock?
Thanks
Click to expand...
Click to collapse
1. Unsure at this point. If everything is stock (including recovery), I would suspect that it would be OK, but it has not been verified yet.
2. After you flash the bootloader, radio, boot, system and recovery images, and format data and cache, then would be the time to re-lock and then boot into Android.
3. Yes. But based on what I gather, the process of wiping on an N6 (when unlocking or locking the bootloader) is done via the stock recovery. So, if you have a custom recovery when you lock, I suspect that it will give you a boot loop.
4. I don't know.
Update - Success
I re-locked the bootloader and the device is working normally, no boot loop. I will continue testing over the next few days and then share what I learned.
Thanks for the help ...
Upgraded to 5.1, booted system OK
rechecked the OEM unlock option and rebooted to fastboot and locked bootloader.
No bootloop or other issues noticed.
Hope this helps.
clairez said:
I re-locked the bootloader and the device is working normally, no boot loop. I will continue testing over the next few days and then share what I learned.
Thanks for the help ...
Click to expand...
Click to collapse
Interesting. And you were 100% stock?
Perhaps the loop isn't caused by the lock itself then. Good to know, though still people need to be cautious
androiduser2011 said:
Upgraded to 5.1, booted system OK
rechecked the OEM unlock option and rebooted to fastboot and locked bootloader.
No bootloop or other issues noticed.
Hope this helps.
Click to expand...
Click to collapse
A few question, for understanding:
Rooted?
Stock or TWRP recovery?
Encrypted?
Thanks
rootSU said:
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
Click to expand...
Click to collapse
This happened to me literally tonight. I tried to lock the boot loader which was successful, from there the device would start to root into teamwin recovery. So from there I tired to flash a fully stock rom but the bootloader was locked. And then because you need permission from the OS to unlock the bootloader I was stuck. What I did is from the locked bootloader I ran the stock oem flash from a fresh download and check from wugs with the force flash enabled (make sure everything is right) miracles of miracles it worked and came back to me.
I learned my lesson. Never shall my bootloader be relocked unless my phone is out of my possession. I'm spending the rest of the time making sure that nobody can get to my data. I love the phone, but that data is my life.
So basically, we need to confirm that being 100% stock will safely allow the relocking of the bootloader on 5.1 per official instructions from Google. If it can be determined that having TWRP recovery installed is the cause of bricks then users can be instructed to be sure stock recovery is installed before relocking. My own thoughts are that this is a bug of sorts with the new security features of lollipop and I'm sure the talented folks here will get it figured out. I'm 100% stock on LMY47D that I sideloaded. Not sure I can afford to risk my 6 but I offer any assistance I can to help get this figured out.
Evolution_Freak said:
So basically, we need to confirm that being 100% stock will safely allow the relocking of the bootloader on 5.1
Click to expand...
Click to collapse
Some of the "bricks" happened after fully flashing stock, i.e they had stock recovery. They had a locked bootloader, an OS that didn't boot and a recovery that couldn't flash anything. If they had TWRP installed, they could format data and flash a rom.zip no problem.
A few days ago some users enrolled in MM beta program started receiving new B321 OTA, so I flashed it on top of my B303 MM and so far all good.
Apart from feeling really butter smooth and including WPS Office, Developer Options now again include OEM Unlock option(FRP unlock), solving the no bootloader unlock on MM issue.
Be sure to be on B303 MM stock recovery, extract the \dload folder from zip and place it on root of external SD card;
Get into Advanced Project Menu by dialing *#*#2846579159#*#*
Go to the bottom and select "HOTA Update"
Wait for reboot, EMUI will verify, install and optimize -took about 15 minutes, so be patient.
What I noticed is that on B321 Advanced Project Menu is gone, only standard(*#*#2846579#*#*) is available.
B321 OTA Update: https://mega.nz/#!t5EhnBQK!ewPCJtBvSd3kWOc2DBmL83poB8Lo1oXzHSguE2TIWbo
B303 stock recovery: https://mega.nz/#!Q0dhEZ7Q!stOQ_0oHPfXnMVfBZqBDkq1fEyxUJ8Jrt5z2mUcdYMo
hi, in dload folder, we have two files. which one should we use?
put the hole zip into dload and start the hota-update
Hi.
So i updated to this firmware and got the unlock OEM option, and i unlocked it, got into fastboot mode (well the FRP lock screen that showed b4 when i didn't have the oem unlock option). I did the fastboot unlock process with the oem unlock key i got from Huawei website and it said it unlocked sucessfully, but i have no changes, everytime i try to go into bootloader it says that it is FRP locked :/
Any ideas?
johnwickz said:
Hi.
So i updated to this firmware and got the unlock OEM option, and i unlocked it, got into fastboot mode (well the FRP lock screen that showed b4 when i didn't have the oem unlock option). I did the fastboot unlock process with the oem unlock key i got from Huawei website and it said it unlocked sucessfully, but i have no changes, everytime i try to go into bootloader it says that it is FRP locked :/
Any ideas?
Click to expand...
Click to collapse
Isn't FRP unlock different to bootloader Unlock?
Well basicly i get the same screen as if my phone was still FRP locked :s even tho i enabled oem unlock in dev settings..
johnwickz said:
Well basicly i get the same screen as if my phone was still FRP locked :s even tho i enabled oem unlock in dev settings..
Click to expand...
Click to collapse
You must activate the "Unlock OEM" option, reboot into fastboot and make sure you have "FRP: Unlocked" in red text. Once you confirm this use the bootloader unlock key provided by Huawei.
Well for me it says FRP locked :/ even tho i enabled oem unblock.
johnwickz said:
Well for me it says FRP locked :/ even tho i enabled oem unblock.
Click to expand...
Click to collapse
And from that screen have your run the appropriate command in fastboot using CMD in windows and the key you received from Huaweiupdateextractor?
---------- Post added at 04:42 PM ---------- Previous post was at 04:15 PM ----------
Battery consumption seems a little higher on B321...will need to keep an eye on it over the next few days
If you mean bootload unlock key yeah i have done it. Still only screen i get is FRP locked
johnwickz said:
If you mean bootload unlock key yeah i have done it. Still only screen i get is FRP locked
Click to expand...
Click to collapse
If in fastboot screen(picture, maybe?) you have BL unlocked/FRP locked I understand you have previously unlocked BL while on Lollipop and then somehow FRP re-locked again, maybe wrong TWRP restore...
No thats the thing i didnt have BL unlocked when in lollipop
I have managed to update to b321 from b303 version with little / no issue. Everything seems OK apart from a small annoyance - the haptic feedback for navigation buttons has stopped working. I've checked all settings and all seems OK. This was working fine on b303 so maybe it's a bug? Anyone else experiencing this?
nobbysheep said:
I have managed to update to b321 from b303 version with little / no issue. Everything seems OK apart from a small annoyance - the haptic feedback for navigation buttons has stopped working. I've checked all settings and all seems OK. This was working fine on b303 so maybe it's a bug? Anyone else experiencing this?
Click to expand...
Click to collapse
I'm not sure if it's a bug but I prefer it without the vibration....I was of the understanding that the bug was that it couldn't be turned off in lollipop so I think if anything it's fix.
Battery drain is my biggest concern... On mobile data it's appalling...can't wait to go back to lollipop
brumgav said:
I'm not sure if it's a bug but I prefer it without the vibration....I was of the understanding that the bug was that it couldn't be turned off in lollipop so I think if anything it's fix.
Battery drain is my biggest concern... On mobile data it's appalling...can't wait to go back to lollipop
Click to expand...
Click to collapse
I've checked this on my honor 7 and seems to work ok (e.g. haptic feedback for navigation buttons works) so I'm pretty sure it's not correct on mate s. I'll try factor reset and see if that cures the problem. - unless anyone else has any better ideas
So I am still on 303. will it be possible to flash the 321, then unlock the bootloader, flash custom recovery and thereafter restore an update of someone that provided a clean lollipop build via twrp?
As long as there isn't official 6.0 I would really like to get back to 5.1.1 xD
But my guess is we I still have to wait for a rollback firmware...
Sent from my OnePlus using XDA Labs
Cris7ianO said:
So I am still on 303. will it be possible to flash the 321, then unlock the bootloader, flash custom recovery and thereafter restore an update of someone that provided a clean lollipop build via twrp?
As long as there isn't official 6.0 I would really like to get back to 5.1.1 xD
But my guess is we I still have to wait for a rollback firmware...
Sent from my OnePlus using XDA Labs
Click to expand...
Click to collapse
Still no rollback works..you need to wait for official rollback update from huawei
Sent from my HUAWEI CRR-L09 using Tapatalk
Is anyone able to make an TWRP Flashable file? =/ i got an bootloop und cant flash over the Stock recovery without dialing the key =/
I need the complete Rom or i´m f**** =/
nobbysheep said:
the haptic feedback for navigation buttons has stopped working. I've checked all settings and all seems OK. This was working fine on b303 so maybe it's a bug? Anyone else experiencing this?
Click to expand...
Click to collapse
This error was also in lollipop version. try to switch it off in settings reboot and the switch on again and reboot and it should work like you want.
bgx said:
This error was also in lollipop version. try to switch it off in settings reboot and the switch on again and reboot and it should work like you want.
Click to expand...
Click to collapse
@bgx thanks for suggestion. Tried that and still no joy. I suspect it's a bug tbh. I'll try a factory reset tomorrow and see if that cures the problem. Not a massive problem but annoying as hell.
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
Hello Community,
i have a Problem after the installation of the newest android Update (OTA).
The A2 just Boot till the white AndroidOne Logo and it hangs there after a time it seems it shut down itself.
My Device:
-USB Debugging is disabled, its a new testing device.
-I cant boot in recovery mode (vol-UP+Power) just boots to the white androidOne Screen and there it hangs
- I can enter fastboot(VOL-Down+power) mode and the device is listed when i type fastboot devices in my terminal on pc
- when i fire up MiFlash tool it list my device after clicking refresh, if i want flash the latest FW (http://en.miui.com/download-353.html) i get the error:
error:"Flash bluetooth_a error"
- My bootloader is locked.
Question:
How can I flash a offical Android with a locked bootloader?
is it a good idea? or better send it back for a warranty solution (i dont want wait)
is there another way to solve my problem? i really dont know whats the problem is. i did not rooted the device or anything.
would be lovely if someone could help me. with an instruction what i can try.
Thank you very much and have a nice day
Regards
If you have enabled 'OEM Unlock' setting in Developer settings, you will probably be good, you can unlock bootloader(oem/flashing/critical) and flash the official ROM ( as per now, 10.0.2.0 )
If not, you have 2 options
-Boot into EDL using short points and flash from there
-Warranty
Same thing happened to a friend's phone, it wasn't touched and just went brick after 10.0.2.0 OTA.
Guess everyone should enable 'OEM Unlock' in case this happens(Data Encrypted anyway, worst case stolen phone better than the chance of brick every time an OTA comes)
edit: If you want to save your data, you obviously shouldn't try the bootloader unlock way...EDL flashing allows flashing without wiping data, but haven't tested that personally
wow really? that are bad news...
thank you anyway :crying:
maybe someone other got a idea?
regards
Lot of users faced this after today's update including myself. Since my bootloader is locked, only option left is EDL flashing by connecting motherboard test points.
Just an advice for everyone reading this message from a Xiaomi Android One device: ALWAYS KEEP UR BOOTLOADER UNLOCKED, IT DOESNT MATTER IF USB DEBUG ISNT ACTIVE, JUST UNLOCK BOOTLOADER
sorry for caps, is just an important thing, i also had the issue but with unlocked bootloader i solved it easily
Just flash using fastboot
Sent from my LG-V930 using Tapatalk
Abrilabr said:
Just an advice for everyone reading this message from a Xiaomi Android One device: ALWAYS KEEP UR BOOTLOADER UNLOCKED, IT DOESNT MATTER IF USB DEBUG ISNT ACTIVE, JUST UNLOCK BOOTLOADER
sorry for caps, is just an important thing, i also had the issue but with unlocked bootloader i solved it easily
Click to expand...
Click to collapse
Yea, but if you want use it as enterprise Device the open Bootloader is a problem.
ilyas111 said:
Just flash using fastboot
Sent from my LG-V930 using Tapatalk
Click to expand...
Click to collapse
that seems not possible with a locked Bootloader (very new phone)
or can you provide a working solution with a locked bootloader? i wont use this EDL thing because its just new and i dont want open it.
Thank you all anyways
Try with this tool : https://forum.xda-developers.com/mi-a2/development/tool-mi-a2-xtrem-toolkit-t3879660
(edl included)
Same trouble here, we are fu...ed!
With Xiaomi mi flash tool, you can re active bootloader protection !
Simple flash with this tool with the option "clean and lock critical"
Works for me !
xotob said:
With Xiaomi mi flash tool, you can re active bootloader protection !
Simple flash with this tool with the option "clean and lock critical"
Works for me !
Click to expand...
Click to collapse
you had bootloader unlocked, i dont, i cant flash nothing with bootloader locked and i have unchecked the option in debug menù.
Reptant said:
If you have enabled 'OEM Unlock' setting in Developer settings, you will probably be good, you can unlock bootloader(oem/flashing/critical) and flash the official ROM ( as per now, 10.0.2.0 )
If not, you have 2 options
-Boot into EDL using short points and flash from there
-Warranty
Same thing happened to a friend's phone, it wasn't touched and just went brick after 10.0.2.0 OTA.
Guess everyone should enable 'OEM Unlock' in case this happens(Data Encrypted anyway, worst case stolen phone better than the chance of brick every time an OTA comes)
edit: If you want to save your data, you obviously shouldn't try the bootloader unlock way...EDL flashing allows flashing without wiping data, but haven't tested that personally
Click to expand...
Click to collapse
After got OTA update to 10.0.3.0 and Today i try to unlock bootloader but I can't unlock_critical and I can't flashing unlock
boonc said:
After got OTA update to 10.0.3.0 and Today i try to unlock bootloader but I can't unlock_critical and I can't flashing unlock
Click to expand...
Click to collapse
Same problem here, does anyone have a solution?
Does fastboot mode is detected in pc?
Sent from my MI 6X using Tapatalk
ilyas111 said:
Does fastboot mode is detected in pc?
Sent from my MI 6X using Tapatalk
Click to expand...
Click to collapse
yes, but i cant use more of fastboot comands, cause bootloader is locked, cant use "flashing unlock/unlock_critical"
Cizzle4 said:
you had bootloader unlocked, i dont, i cant flash nothing with bootloader locked and i have unchecked the option in debug menù.
Click to expand...
Click to collapse
I'm in your same situation
Exactly the same situation here... Waiting for a solution without losing warranty.
I think if your bootloader is not unlocked, the only possible solution left is to shorting the test points on motherboard. Those who have warranty can return the unit for claim. Yet another mess up from Xiaomi and this will be my last phone from them.
UnlimitedBB said:
I think if your bootloader is not unlocked, the only possible solution left is to shorting the test points on motherboard. Those who have warranty can return the unit for claim. Yet another mess up from Xiaomi and this will be my last phone from them.
Click to expand...
Click to collapse
I can understand that. I will claim warranty because its new and i dont want do that test point thing.
on private i would buy and recommend xiaomi anyways but if you want these hardware for some enterprise things then better not.
Iam out of this Thread now but if you want talk here some more feel free.. maybe somebody can bring a solution for all you guys who face this problem but i think its not possible without a open BL or the TestPoint Method.
Regards and have a nice day
Hi. I'm with locked bootloader. I received new January update. No change - stock variant updated to Pie. So it's safe to update or waiting for new one? Mi A2 4/64 micron ram
Hi,
I had my Galaxy A6+ (A605F) 3 months ago then I decided to root it. I had the OEM unlock button. I turned it on and device asked for a factory reset and I let it do.
The phone rebooted and everything was reset (I already know that it will happen so I'm ok with resetting).
I waited again for the OEM unlock option to show up but it didn't show after around 170h uptime.
The current recovery values are:
FRP lock : off
OEM lock : off
RMM state : prenormal
And of course it didn't accept flashing twrp because of the pre-normal thing.
My question is, what should I do now? Or this means it's never going to be rooted?
Thanks in advance.
You'll have to wait seven days for the OEM option to return them u can try again
dorian2kx said:
You'll have to wait seven days for the OEM option to return them u can try again
Click to expand...
Click to collapse
Sorry for the very late reply, but you were right, it actually appeared again and it's unlocked now.
I'm now on oreo but I didn't root yet because the lockscreen problem.
Thank you so much.