Database Develop

[OTA] Huawei Mate S Firmware C432B321/C900B321 [MM] [Beta] - FRP Unlock enabled!

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.

Please heelp frp lock

I accedentally switched OEM UNLOCK and now after reboot there is an error
Custom Binary Blocked By Frp Lock
Can you please help STEP BY STEP HWO TO FIX IT ?? i dont wanna to brick not8

klisza1993 said:
I accedentally switched OEM UNLOCK and now after reboot there is an error
Custom Binary Blocked By Frp Lock
Can you please help STEP BY STEP HWO TO FIX IT ?? i dont wanna to brick not8
Click to expand...
Click to collapse
Flash stock firmware with latest Odin in download mode. That should get you back up and running. OEM toggle switch should re-appear within 7 days (unless the date change trick works for you). The OEM unlock thread has more background, and there is a sticky thread here for the date workaround.

I have flashed all again and its working. Weird for me is about thso OEM issue - ive never had one xd even after flash srock firmware i could switch oem unlock. Curious what's depends from

klisza1993 said:
I have flashed all again and its working. Weird for me is about thso OEM issue - ive never had one xd even after flash srock firmware i could switch oem unlock. Curious what's depends from
Click to expand...
Click to collapse
Usually that error happens when you are not on stock (rooted with twrp, etc.) and hit the OEM toggle...it sees you have modified your phone in an unauthorized way and puts you in 'jail'.

I toggled it by myself i didnt know that it should be always on...
OEM issue - what is the problem. I have heard that the problem os thatbon some phones therenis no such options .... curious why

klisza1993 said:
I toggled it by myself [emoji14] i didnt know that it should be always on...
OEM issue - what is the problem. I have heard that the problem os thatbon some phones therenis no such options .... curious why
Click to expand...
Click to collapse
Snapdragon bootloaders are locked so OEM unlock toggle isn't really relevant there. For Exynos there is a long thread here with lots of info. Essentially it can take 7 days to appear if you don't see it at first boot or if you end up in jail.

Does OEM unlock need to be re-ticked after rom flash?

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

[Galaxy A6+] OEM Unlock option is gone after turning it on.

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.

Question Relock Zenfone8

Hi, i need to relock my Zenfone 8. Right now it's running newest Beta, but everything is fully operational. Do you have any idea, how to relock?
fastboot oem lock is not working
fastboot oem asus-csc_lk also nothing
Both are giving:
FAILED (remote: Command not supported in default implementation)
Thanks.

Fatso said:
Hi, i need to relock my Zenfone 8. Right now it's running newest Beta, but everything is fully operational. Do you have any idea, how to relock?
fastboot oem lock is not working
fastboot oem asus-csc_lk also nothing
Both are giving:
FAILED (remote: Command not supported in default implementation)
Thanks.
Click to expand...
Click to collapse
As far as I know, once unlocked, it is not possible no relock again.

Asus says it's can't be relocked. At least it was reply to me from their support.

I relocked mine but you cannot restore OTAs since your IMEI is permanently blacklisted with Asus.

thatguy222 said:
I relocked mine but you cannot restore OTAs since your IMEI is permanently blacklisted with Asus.
Click to expand...
Click to collapse
How did you relock it?

SoulMachina said:
How did you relock it?
Click to expand...
Click to collapse
I don't recall but definitely not either of the commands used in th first post.

thatguy222 said:
I don't recall but definitely not either of the commands used in th first post.
Click to expand...
Click to collapse
That would´ve been useful

thatguy222 said:
I relocked mine but you cannot restore OTAs since your IMEI is permanently blacklisted with Asus.
Click to expand...
Click to collapse
I'm bot after OTA, i need this to work with VMware workspace. Also google pay is crucial for me.

SoulMachina said:
That would´ve been useful
Click to expand...
Click to collapse
Found it (just had to relock to return due to flashing ramdump issue):
fastboot oem asus-csc_lk

thatguy222 said:
Found it (just had to relock to return due to flashing ramdump issue):
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
I don't think that it'll help you to fool ASUS service center. imei is blacklisted for OTA updates and i'm pretty sure that S/N too.
See no reason for that...

thatguy222 said:
Found it (just had to relock to return due to flashing ramdump issue):
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
Hi again. One guy tried this and locked his BL (with followed factory reset).
He has Android 12 (beta 2 I think) and experienced some problems with phone auto-reboot when interent/sim card is active. If SIM is removed then he can use his ZF8.
Do you have same behavior or everything is ok for you?

dron39 said:
Hi again. One guy tried this and locked his BL (with followed factory reset).
He has Android 12 (beta 2 I think) and experienced some problems with phone auto-reboot when interent/sim card is active. If SIM is removed then he can use his ZF8.
Do you have same behavior or everything is ok for you?
Click to expand...
Click to collapse
After re-locking I also went back to Android 12 beta 2. I have not had any SIM or reboot issues AND my ramdump error has not re-appeared.

thatguy222 said:
After re-locking I also went back to Android 12 beta 2. I have not had any SIM or reboot issues AND my ramdump error has not re-appeared.
Click to expand...
Click to collapse
That person replied that those reboots were fixed by re-enabling some previously disabled apps through ADB command. It looks like too many apps were disabled.
It's interesting, will you have any OTA-updates in future or your S/N / IMEI still in blacklist for OTA's ?

dron39 said:
That person replied that those reboots were fixed by re-enabling some previously disabled apps through ADB command. It looks like too many apps were disabled.
It's interesting, will you have any OTA-updates in future or your S/N / IMEI still in blacklist for OTA's ?
Click to expand...
Click to collapse
No OTA; S/N is blacklisted :-( It's fine. You just download the update to storage and the phone will see it and do the update.