Database Develop

[Q] Strange thing happened ! (Dev- XT1068 Indian)

I relocked the bootloader but when i did , I got an error saying 'too many strings' or something
However, I restarted phone in bootloader and saw the status code (It was 2-bootloader status:Locked)
However i gave a 'oem lock' command again.
I get status 2-bootloader status:Locked, after relocking. (well thats ok) but i still see the bootloader unlocked warning.
I could Still flash the warning remover 'logo.bin' file
Now Im confused about whats happening! If my bootloader was locked then how could I get that warning? Rather , How could I ever flash a logo.bin file on my device?
ANy Help AppReciated!

tbiwalkar said:
I relocked the bootloader but when i did , I got an error saying 'too many strings' or something
However, I restarted phone in bootloader and saw the status code (It was 2-bootloader status:Locked)
However i gave a 'oem lock' command again.
I get status 2-bootloader status:Locked, after relocking. (well thats ok) but i still see the bootloader unlocked warning.
I could Still flash the warning remover 'logo.bin' file
Now Im confused about whats happening! If my bootloader was locked then how could I get that warning? Rather , How could I ever flash a logo.bin file on my device?
ANy Help AppReciated!
Click to expand...
Click to collapse
It's no problem to unlock the device again. Just use the same code you received via email.
The bootloader-warning stays because even a relock does not restore warranty.
There's absolutely no reason to relock the device. As long as you are fully unrooted you will be able to install OTA even with unlocked bootloader.

doppelhelix said:
It's no problem to unlock the device again. Just use the same code you received via email.
The bootloader-warning stays because even a relock does not restore warranty.
There's absolutely no reason to relock the device. As long as you are fully unrooted you will be able to install OTA even with unlocked bootloader.
Click to expand...
Click to collapse
I understand but then how am i able to flash logo.bin?

tbiwalkar said:
I understand but then how am i able to flash logo.bin?
Click to expand...
Click to collapse
You have to be unlocked for this. And just keep it unlocked. As I said, there's no point in relocking.

doppelhelix said:
You have to be unlocked for this. And just keep it unlocked. As I said, there's no point in relocking.
Click to expand...
Click to collapse
I am locked and still i am able to flash various logo.bin files using mfastboot

tbiwalkar said:
I am locked and still i am able to flash various logo.bin files using mfastboot
Click to expand...
Click to collapse
Interesting. Thanks for the input. learned somthing new..[emoji4]

Frp locked

I cant unlock frp as It is grayed out the option of oem unlocking in the dev options
pls I need help
Model : LLD-L21
OS : KangVIP Rom (EMUI 8.0.0)
Bootloader Status : Unlocked
In fastboot it says
Phone Unlocked
FRP Locked

did u try dload method?

yes I tried dload
It did not work

I can't upload zipI will send u the file to unlock frp or you can find that file in telegram group of our device

That wont work...
Go to terminal in root mode and do
Code:
Setprop sys.oem_unlock_allowed 1
Than you can change the value and its not longer greyed out.

Darkest-Dark said:
That wont work...
Go to terminal in root mode and do
Code:
Setprop sys.oem_unlock_allowed 1
Than you can change the value and its not longer greyed out.
Click to expand...
Click to collapse
If that dosent work you can also follow the below procedure.
Relock your bootloader. Your phone will factory reset and boot. Then head to developer options and you will see oem unlock is not greyed out. Then just enable oem unlocking and unlock the bootloader. When you boot up again you will see that oem is greyed out but it'll be enabled. So you'll have unlocked fastboot and unlocked frp now.

Fredin_ said:
That wont work...
Go to terminal in root mode and do
If that dosent work you can also follow the below procedure.
Relock your bootloader. Your phone will factory reset and boot. Then head to developer options and you will see oem unlock is not greyed out. Then just enable oem unlocking and unlock the bootloader. When you boot up again you will see that oem is greyed out but it'll be enabled. So you'll have unlocked fastboot and unlocked frp now.
Click to expand...
Click to collapse
This will just brick the device.

Fredin_ said:
If that dosent work you can also follow the below procedure.
Relock your bootloader. Your phone will factory reset and boot. .....<snip>.
Click to expand...
Click to collapse
Never Ever a good idea to try and relock the bootloader.

viratbansal001 said:
This will just brick the device.
Click to expand...
Click to collapse
Sparkrite said:
Never Ever a good idea to try and relock the bootloader.
Click to expand...
Click to collapse
Umm why? Its working pretty fine for me. ?

Fredin_ said:
Umm why? Its working pretty fine for me.
Click to expand...
Click to collapse
Have you Unlocked, Relocked and then Unlocked again ?

[/COLOR]
Sparkrite said:
Have you Unlocked, Relocked and then Unlocked again ?
Click to expand...
Click to collapse
I haven't gone that far. I've unlocked and then relocked.
Everything fine. I believe it's completely safe if you have complete stock firmware installed ie, stock rom, stock recovery, stock Kernal and all that stuff. Otherwise you'll end up in a loop. Guess I forgot that part sorry.
So I know this is someone else's thread but can you tell me if I relocked bootloader will the service center be able to know I'd unlocked before? I don't have the phone unlocked warning at boot. Just curious.

Fredin_ said:
[/COLOR]
I haven't gone that far. I've unlocked and then relocked.
Everything fine. I believe it's completely safe if you have complete stock firmware installed ie, stock rom, stock recovery, stock Kernal and all that stuff. Otherwise you'll end up in a loop. Guess I forgot that part sorry.
So I know this is someone else's thread but can you tell me if I relocked bootloader will the service center be able to know I'd unlocked before? I don't have the phone unlocked warning at boot. Just curious.
Click to expand...
Click to collapse
Hey will it work if I have complete stock firmware like you said? I want to take my device to service centre but my bootloader is unlocked and I have L OS installed. Will relockeing bootloader get me back my waranty?
PS. I have already asked in question and answers section but no reply yet. ?I

Fredin_ said:
[/COLOR]
I haven't gone that far. I've unlocked and then relocked.
Everything fine. I believe it's completely safe if you have complete stock firmware installed ie, stock rom, stock recovery, stock Kernal and all that stuff. Otherwise you'll end up in a loop. Guess I forgot that part sorry.
So I know this is someone else's thread but can you tell me if I relocked bootloader will the service center be able to know I'd unlocked before? I don't have the phone unlocked warning at boot. Just curious.
Click to expand...
Click to collapse
Some if not all bootloaders nowadays are not "locked" by the manufacturer using a code but are usually "locked" by employing a digital signature and/or a CID (carrier Id) hard coded into the OS. When we "unlock" a bootloader with a code we are simply using a routine written into the loader by the manufacturer to now ignore signatures and/or CIDs of the OS and this allows us to flash whatever we wish.
Sometimes upon unlocking using a code the DS/CID is erased/altered and cannot be retrieved, so not a good idea to relock an altered bootloader.
At least, that is my understanding of it.

Krazydon said:
Hey will it work if I have complete stock firmware like you said? I want to take my device to service centre but my bootloader is unlocked and I have L OS installed. Will relockeing bootloader get me back my waranty?
PS. I have already asked in question and answers section but no reply yet. I
Click to expand...
Click to collapse
Sparkrite said:
Some if not all bootloaders nowadays are not "locked" by the manufacturer using a code but are usually "locked" by employing a digital signature and/or a CID (carrier Id) hard coded into the OS. When we "unlock" a bootloader with a code we are simply using a routine written into the loader by the manufacturer to now ignore signatures and/or CIDs of the OS and this allows us to flash whatever we wish.
Sometimes upon unlocking using a code the DS/CID is erased/altered and cannot be retrieved, so not a good idea to relock an altered bootloader.
At least, that is my understanding of it.
Click to expand...
Click to collapse
That's too bad. Means we won't get back our waranty if we relock it ?. So thanks for the heads up . I'll be careful while unlocking it again (if ever).?

Fredin_ said:
That's too bad. Means we won't get back our waranty if we relock it . So thanks for the heads up . I'll be careful while unlocking it again (if ever).
Click to expand...
Click to collapse
Not necessarily, I doubt if most service centres would bother delving that deep, but maybe some would.
I don't know...........

Sparkrite said:
Not necessarily, I doubt if most service centres would bother delving that deep, but maybe some would.
I don't know...........
Click to expand...
Click to collapse
Thanks for your quick reply but do you know any way to get back CID/DS

No, but I haven't delved that deeply into Huaweis bootloaders, but I NEVER attempt to re-lock them.

Sparkrite said:
No, but I haven't delved that deeply into Huaweis bootloaders, but I NEVER attempt to re-lock them.
Click to expand...
Click to collapse
Anyways thanks for your replies. Means a lot ?

huawei P9 bootloader relock fail

Hi, I would like to relock the bootloader but I am getting the following message:
FAILED (remote: stat not match)
I use command line and the following command:
fastboot oem relock *******(unlock code)
Any idea?
Thanks

Goldak said:
Hi, I would like to relock the bootloader but I am getting the following message:
FAILED (remote: stat not match)
I use command line and the following command:
fastboot oem relock *******(unlock code)
Any idea?
Thanks
Click to expand...
Click to collapse
Do you see in the Fastboot that Phone (Bootloader) and FRP are unlocked.
If Phone unlocked but FRP locked, you have to enable OEM Unlocking
Do not attempt unlocking Bootloader with TWRP or custom ROM - it triggers Factory resetting and it can brick the phone
Btw, for OTA updates it doesn't matter if Bootloader is locked or not

I am on stock Nougat. I unlocked the bootloader some time ago, then some OTA update came. Right now, what I see in Fastboot is "Phone locked, FRP unlocked"... So it seems that the bootloader was actually locked by the OTA. However the Safetynet test fails and I cannot use NFC payments now. I suppose its the unlocked FRP that causes this. How could I fix it?
Thanks

Goldak said:
I am on stock Nougat. I unlocked the bootloader some time ago, then some OTA update came. Right now, what I see in Fastboot is "Phone locked, FRP unlocked"... So it seems that the bootloader was actually locked by the OTA. However the Safetynet test fails and I cannot use NFC payments now. I suppose its the unlocked FRP that causes this. How could I fix it?
Thanks
Click to expand...
Click to collapse
Some OTA updates do lock the Bootloader.
FRP should not affect SafetyNet.
Btw, which stock ROM you have and do you have Magisk/root (why are you concerned about SafetyNet)?
I'm not using NFC (pay)... but due to certain Google API changes some apps fail to verify SafetyNet

I am on stock EVA-L09C150B388, no root or other modification. So I think the only reason for NFC payment not working/ Safetynet failure might be the unlocked FRP...

Goldak said:
I am on stock EVA-L09C150B388, no root or other modification. So I think the only reason for NFC payment not working/ Safetynet failure might be the unlocked FRP...
Click to expand...
Click to collapse
You can easily uncheck OEM Unlocking and reboot

zgfg said:
You can easily uncheck OEM Unlocking and reboot
Click to expand...
Click to collapse
Unfortunatelly, that did not help...?

Goldak said:
Unfortunatelly, that did not help...
Click to expand...
Click to collapse
Test if your SafetyNet is really (not) ok with the apps attached to
https://forum.xda-developers.com/showpost.php?p=77339761&postcount=566

zgfg said:
Test if your SafetyNet is really (not) ok with the apps attached to
https://forum.xda-developers.com/showpost.php?p=77339761&postcount=566
Click to expand...
Click to collapse
Those two apps show no fails... However SafetyNet Test app from Google play says 'Failed'

Goldak said:
Those two apps show no fails... However SafetyNet Test app from Google play says 'Failed'
Click to expand...
Click to collapse
There is a link in that post - there was some change in SafetyNet/API or key causing not updated apps to fail

The command is "fastboot oem lock", not "relock"

zgfg said:
There is a link in that post - there was some change in SafetyNet/API or key causing not updated apps to fail
Click to expand...
Click to collapse
Thats probably the problem, thanks!

Is it possible to re-lock bootloader after official unlock?

I'm doing some research before I commit to unlocking my bootloader, and I can't find anything definitive on whether or not it's possible to re-lock after unlocking with the official tool. I have experience unlocking and re-locking bootloaders, flashing custom recoveries/ROMs/kernels etc but only with Nexus and Samsung phones, so I just want to make sure I'm clear on how Nokia's setup differs (If at all). Would also be interested to find out if Nokia will still offer me OTA's with unlocked bootloader.
Thanks for any help, and feel free to move or close the thread if it matches another one that I've missed.

Bb

2WildFirE said:
I'm really sure you can relock bootloader. Why not?
And yes ota works fine with open bootloader if you are on stock
Click to expand...
Click to collapse
Awesome, cheers for the assist ?

2WildFirE said:
I'm really sure you can relock bootloader. Why not?
And yes ota works fine with open bootloader if you are on stock
Click to expand...
Click to collapse
Nokia says that relooking isn't possible. Is there anybody who tried the command 'fastboot oem relock'?

And why says this text please lock ? the bootloader, if it is not possible?

2WildFirE said:
And why says this text please lock ? the bootloader, if it is not possible?
Click to expand...
Click to collapse
Dude, crop out that serial number?

Go to download mode
Run adb:fastboot oem lock
Choose lock bootloader in your phone

namle98 said:
Go to download mode
Run adb:fastboot oem lock
Choose lock bootloader in your phone
Click to expand...
Click to collapse
confirmed, i did it today

Since I also unlocked critical, I ran: fastboot oem lock_critical and then fastboot oem lock
Phone will factory reset both times.

Has anyone tried the re-lock with a custom kernel/ROM?

dimitar10 said:
Has anyone tried the re-lock with a custom kernel/ROM?
Click to expand...
Click to collapse
No, and nobody should do it. It will brick your device.
The point of a locked bootloader is to prevent unofficial software from running, and the point of unlocking it is to make that possible. So relocking the bootloader with unofficial software installed will make the phone think that the software got corrupted and rightfully lock down the device.

THMSP said:
No, and nobody should do it. It will brick your device.
The point of a locked bootloader is to prevent unofficial software from running, and the point of unlocking it is to make that possible. So relocking the bootloader with unofficial software installed will make the phone think that the software got corrupted and rightfully lock down the device.
Click to expand...
Click to collapse
Basically anyone should be able to do it and it shouldn't brick your device, as per Google's bootloader recommendations. However, manufacturers decide to cripple bootloaders not to support it in the verified boot chain (where kernel verification can be explicitly made against a custom root of trust set after the device has left the factory i.e. set by the user, instead of the original root of trust). As far as I know, only Pixel devices implement this, and can be achieved by issuing the command:
Code:
fastboot flash avb_custom_key <key_blob>
I'm sure there are lots of advanced users/modders that can find this feature beneficial (if implemented by the device vendors).

dimitar10 said:
Basically anyone should be able to do it and it shouldn't brick your device, as per Google's bootloader recommendations. However, manufacturers decide to cripple bootloaders not to support it in the verified boot chain (where kernel verification can be explicitly made against a custom root of trust set after the device has left the factory i.e. set by the user, instead of the original root of trust). As far as I know, only Pixel devices implement this, and can be achieved by issuing the command:
Code:
fastboot flash avb_custom_key <key_blob>
I'm sure there are lots of advanced users/modders that can find this feature beneficial (if implemented by the device vendors).
Click to expand...
Click to collapse
I accidently locked the bootloader and without locking critical with custom recovery in system.
now it's saying data is corrupt and phone can't be trusted.
that unlock key url got expired and there is no way i can get that unlock key .
is there any other way to fix my phone??
Code:
fastboot flash avb_custom_key <key_blob>
how to use this code? any specific key_blob for nokia 8 or is it supported on this phone?
help me guys ;(
Edit:
After so many tries, I went to service centre and they fixed the phone in few mins :highfive::silly:

Crazy Tweaks said:
I accidently locked the bootloader and without locking critical with custom recovery in system.
now it's saying data is corrupt and phone can't be trusted.
that unlock key url got expired and there is no way i can get that unlock key .
is there any other way to fix my phone??
Code:
fastboot flash avb_custom_key <key_blob>
how to use this code? any specific key_blob for nokia 8 or is it supported on this phone?
help me guys ;(
Edit:
After so many tries, I went to service centre and they fixed the phone in few mins :highfive::silly:
Click to expand...
Click to collapse
I have the same problem right now. May i ask how they fixed it and what did you tell them ?
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
CommieTurtle said:
I have the same problem right now. May i ask how they fixed it and what did you tell them ?
Click to expand...
Click to collapse
Did they fix it for free since bootloader is locked? I'm going to service centre in few hours

CommieTurtle said:
I accidently locked the bootloader and without locking critical with custom recovery in system.
now it's saying data is corrupt and phone can't be trusted.
that unlock key url got expired and there is no way i can get that unlock key .
is there any other way to fix my phone??
I have the same problem right now. May i ask how they fixed it and what did you tell them ?
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
Did they fix it for free since bootloader is locked? I'm going to service centre in few hours
Click to expand...
Click to collapse
Well it wasn't in warranty xD so just asked me this and boom it was not free after that but well yeah it doesn't matter if it's locked or unlocked lol as long as they are getting paid, they'll do it hahahha

Crazy Tweaks said:
Well it wasn't in warranty xD so just asked me this and boom it was not free after that but well yeah it doesn't matter if it's locked or unlocked lol as long as they are getting paid, they'll do it hahahha
Click to expand...
Click to collapse
lol my device was under warranty so I got it fixed for free

I can assume that, in service centers, they are able to reflash the entire firmware including the (secondary) bootloader. They would probably boot the device into EDL mode, and flash it with stock firmware, with a properly signed Qualcomm EDL programmer, and use Qualcomm's QFIL tool to do this.

CommieTurtle said:
lol my device was under warranty so I got it fixed for free
Click to expand...
Click to collapse
Glad to hear that

Unlocking bootloader: definitive bye-bye to automatic updates?

With the Moto Z, after I returned the phone to stock (flashed stock firmware and locked the bootloader), I'd be able to flash stock firmware with the flashing locked.
Not so with the Motorola One Zoom. In other words, flashing stock and re-locking didn't return the phone to its pristine state. Even when flashing stock firmware over stock firmware, I have to unlock the bootloader.
Differences I observed: on the bootloader screen, when re-locked the Z would show "oem_locked" again. On the One Zoom, it shows "flashing_locked" instead. I'm pretty sure it showed "oem_locked" before unlocking.
WIth the Z, every time I wanted to unlock the bootloader, I had to issue "fastboot oem unlock" followed by the unlock code. The code isn't necessary with the re-locked One Zoom.
In other words, maybe it was a one-way trip. It seems that the phone won't return to its original state, it looks it's modified for good. And I'm afraid this means bye-bye to automatic updates.
Am I missing something here?

My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.

rafikowy said:
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
Click to expand...
Click to collapse
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.

Whammamoosha said:
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Click to expand...
Click to collapse
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.

rafikowy said:
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
Click to expand...
Click to collapse
Don't bother, I have mine. Thanks.

I would like the flash script if someone would share it

Help with unlocking bootloader
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.

Bodeman12345 said:
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Click to expand...
Click to collapse
In the settings for developers you gave permission for Factory Unlock?

ilia3367 said:
In the settings for developers you gave permission for Factory Unlock?
Click to expand...
Click to collapse
I enabled the setting to unlock oem bootloader is that the same?

Bodeman12345 said:
I enabled the setting to unlock oem bootloader is that the same?
Click to expand...
Click to collapse
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
Code:
fastboot devices
If the device is detected, enter the command:
Code:
fastboot getvar all
And copy the result here.

ilia3367 said:
yes.
Click to expand...
Click to collapse
Yes I did that

Bodeman12345 said:
Yes I did that
Click to expand...
Click to collapse
Answer the other questions, please!

diculpe por que mi pc no ve el fastboot de mi one zoom?

ilia3367 said:
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
If the device is detected, enter the command:
And copy the result here.
Click to expand...
Click to collapse
I used this youtube video
I dont know where it is manifactured but I live in the netherlands.
I dont get the 3th question
I will do the commands in a couple minutes

Hey all,
I have the Moto One Zoom running on Android 9.
Also, It's Rooted with Magisk and have Riru EdXposed installed, can I install my OTA updates without bootloop or do I have to Uninstall Magisk, relock bootloader and factory reset/flash stock firmware to get latest OTA updates?
Any feedback is appreciated.
Thanks