EMUI 10 has relocked my bootloader and the fastboot command doesn't work with it.
Under what version of EMUI Do I have to return to be able to use fastboot to unlock my bootloader, 8.1, 9.0 or 9.1?
P.S TOOL_ALL_IN_ONE_2.0.0.9 not working on EMUI 10.
titi66200 said:
EMUI 10 has relocked my bootloader and the fastboot command doesn't work with it.
Under what version of EMUI Do I have to return to be able to use fastboot to unlock my bootloader, 8.1, 9.0 or 9.1?
P.S TOOL_ALL_IN_ONE_2.0.0.9 not working on EMUI 10.
Click to expand...
Click to collapse
Does your bl have status locked or relocked?
Does <Fastboot oem unlock "unlock code" > work? (i assume not, just to confirm)
Is "enable oem unlock" in developer options on?
forever_lol said:
Does your bl have status locked or relocked?
Does <Fastboot oem unlock "unlock code" > work? No
Is "enable oem unlock" in developer options on? Yes
Click to expand...
Click to collapse
Rollback to 345 with Hisuite and state on this version is Unlocked.
Now there is a way to leave the project because my phone wants to reinstall EMUI 10.
titi66200 said:
Rollback to 345 with Hisuite and state on this version is Unlocked.
Now there is a way to leave the project because my phone wants to reinstall EMUI 10.
Click to expand...
Click to collapse
EMUI 10 beta locks bootloader on Mate 10 Pro too and also Mate 20,i think.
You should be able to leave the project from the Beta app.
titi66200 said:
Rollback to 345 with Hisuite and state on this version is Unlocked.
Now there is a way to leave the project because my phone wants to reinstall EMUI 10.
Click to expand...
Click to collapse
So the beta locked your bootloader and rolling back unlocked it?? Did you have to unlock it again yourself or did it just unlock??
Related
UPDATED:
Issue has been solved
( i buy 4 credits from dc unlocker and use HCU to read my boot loader code )
yes i know this is all from dc unlockcer yes they , unbrick my P9 but they also
changed the boot code when you flashed the rom via DC phoenix
im suspecting it that way .
Hello guys. Debranded P9 here
Nougat C432B386 Eva-L09
hw eu :country vendor
Bootloader unlocked and FRP lock
my device gets suffer from a hard brick
and recovered by DC Phoenix. In order to
have a Stable Nougat Firmware i decide to
debrand my phone ......
1st attempt : flashing the (.dgkmts AL10 chinese rom)
after flashing the chinese Al10 firmware
from DCUnlocker (.dgkmts) the device boot and
can be flashed into original stock rom
but the first attempt fails because my
vendor comes from a different build
2nd attempt: flashing the (.dgkmts AL10 chinese rom)
but this time, i decide to wipe NVME and OEM
after booting into system and checking my device
details my IMEI stays the same but Serial No is missing
so i had to use HCU to write my IMEI and Serial No.
and obtain a new vendor from hw eu
after booting system, I start to forced update the
EVA-L09C432B136
then i unlocked my bootloader at this stage
using the same bootloader code from Huawei
FIRMWARE:EVA-L09 C432B136
( please focus on this, i already unlocked the bootloader​
here , and allow the oem to unlock )
status : bootloader unlock
frp unlock
the process is successfully done and after that
i check my device details and perfectly debrand
my P9, after a minute it received an OTA update
from Huawei System Updater ( C432B186 )
I update into it and reboot and received another update
again C432B322 ( Nougat-beta version) and then
received the Final Build C432B386
SUMMARY STAGES:
bricked and wiped oem info / SN rewrite using HCU
1. AL10 Chinese rom >
2. C432B136 ( stock firmware)
( do unlocked bootloader )
3. OTA C432B186
4. OTA C432B322 ( Nougat beta )
5. OTA C432B386 ( Nougat Stable)
status : bootloader unlock
frp lock
I'm into that version C432B386
and now im having a trouble here
flashing the original bootloader code
command : fastboot oem unlock xxx-xxxx-xxx
it says : wrong password
failed to write the command
" is it possible to obtain a new bootloader code ?"
i don't know why the boot code changed even though
i use it in unlocking my Bootloader and it succeed
2nd scenario:
when i try to go to developer options and
go to Allow oem unlock
so that i can be able to obtain FRP unlock
but it is greyed out.
" i've read that if you're on Nougat and you are already
in unlocked bootlader, you will have this issue "
the possible way of unlocking FRP is relocked the
bootloader first and the OEM UNLOCK option will
come out.
i guess the solution is finding a new Bootloader code
but "how?" does anyone knows this?
3rd scenario: flashing new recovery
( expecting to have administrative rights )
i try to flash also the twrp nougat version
but it says verification error
command : fastboot flash recovery twrp3.1.0-3-eva.img
failed
i don't want to end up bricking my device again
I'm having a hard time to resurrect this and I don't
want to happen it again, I'm busy with my work so
i have to asked you guys, finding a best way how
to fixed this..
if someone is having a same situation like me
please participate on the thread and or someone who
already fixed this kind of issue please give us information . thank you !
oem info / SN rewrite using HCU
You rewrited the serial number? Yeah I don't know how to help you there...
benjamen50 said:
oem info / SN rewrite using HCU
You rewrited the serial number? Yeah I don't know how to help you there...
Click to expand...
Click to collapse
yes sir , there is HCU Client tool that can re-write Serial Number/IMEI / read bootcode
i use it and replaced the missing Serial Number of my device
vinfrix said:
yes sir , there is HCU Client tool that can re-write Serial Number/IMEI / read bootcode
i use it and replaced the missing Serial Number of my device
Click to expand...
Click to collapse
Imo, If you change serial.no then your unlock code would be different
Try relocking and again unlocking the bootloader.
_Frostplexx_ said:
Try relocking and again unlocking the bootloader.
Click to expand...
Click to collapse
i tried to but the code seems already changed.
FiKsTyLeR said:
Imo, If you change serial.no then your unlock code would be different
Click to expand...
Click to collapse
even if i write the same serial code ?
vinfrix said:
i tried to but the code seems already changed.
Click to expand...
Click to collapse
Dude i am in a similar situation.
I have the bootloader unlocked but frp is locked.
When you relocked and unlocked was the OEM unlock option changeable (not grayed out, no FRP LOCK) again?
revery0 said:
Dude i am in a similar situation.
I have the bootloader unlocked but frp is locked.
When you relocked and unlocked was the OEM unlock option changeable (not grayed out, no FRP LOCK) again?
Click to expand...
Click to collapse
yes if you unlock again it will come out
vinfrix said:
yes if you unlock again it will come out
Click to expand...
Click to collapse
As it turns out, you need to rollback to b182 and then upgrade to N through OTA.
dload b300
dload b182
OTA b386
OEM Unlock, ADB Debugging, USB Debugging
Unlock bootloader
twrp
revery0 said:
As it turns out, you need to rollback to b182 and then upgrade to N through OTA.
dload b300
dload b182
OTA b386
OEM Unlock, ADB Debugging, USB Debugging
Unlock bootloader
twrp
Click to expand...
Click to collapse
why should i rollback ?
How do i unlock the bootloader?
I'm on Android and EMUI 8.0.0.
ZaKh10 said:
How do i unlock the bootloader?
I'm on Android and EMUI 8.0.0.
Click to expand...
Click to collapse
You can look at this thread. Its have guides to unlock your bootloader and how to install TWRP also updating firmware. https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
But beware, unlocking bootloader will do a factory reset. Backup your data first using hisuite or twrp. Otherwise your data will gone forever.
Hello everyone,
I see that there isn't a way to unlock bootloader in Pie. The only way is to rollback to Oreo and will be unlocked by cmd commands or is there another way?
After that can I go back to Pie with bootloader unlocked or no?
greg10 said:
Hello everyone,
I see that there isn't a way to unlock bootloader in Pie. The only way is to rollback to Oreo and will be unlocked by cmd commands or is there another way?
After that can I go back to Pie with bootloader unlocked or no?
Click to expand...
Click to collapse
Yes, you can update OTA to pie afterwards.
Hi everyone
I bought my nokia 7 plus with Oreo.
Now updated to 10.
The problem is OEM unlock is disabled always in Dev options
How can i unlock to try custom roms.
Any guidance will be thank ful.
sriram reader said:
Hi everyone
I bought my nokia 7 plus with Oreo.
Now updated to 10.
The problem is OEM unlock is disabled always in Dev options
How can i unlock to try custom roms.
Any guidance will be thank ful.
Click to expand...
Click to collapse
You shouldnt have updated it.. Try downgrade it. On android 10 its disabled for evryone
2gg1 said:
You shouldnt have updated it.. Try downgrade it. On android 10 its disabled for evryone
Click to expand...
Click to collapse
OEM unlock switch NOT unlock bootloafer on Nokia7Plus with ANY Android version 10,9,8.1,8...
is need unlock via fastbboot with unofficialy generated/buyed unlocked file... and for unlocking is need have A8 or A9 with <august2019 security patches/update.,,
I managed to turn my on by turning Dev mode off and back on and you have a few seconds where you can turn it on.. Just waiting for Android 10 to turn up on my phone
TG09 said:
I managed to turn my on by turning Dev mode off and back on and you have a few seconds where you can turn it on.. Just waiting for Android 10 to turn up on my phone
Click to expand...
Click to collapse
read my post above...
Don't know whether or not it's a glitch but my 'OEM unlocking' is stuck in the enabled position, even after a hard reset. I'm on Android 10.
EDIT: safe to say that still does nothing.
C:\adb>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
Lord Mashie said:
Don't know whether or not it's a glitch but my 'OEM unlocking' is stuck in the enabled position, even after a hard reset. I'm on Android 10.
EDIT: safe to say that still does nothing.
C:\adb>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
sad?
For unlock Bootloader, u will need to downgrade to oreo than need bootloader key... minimul adb to unlock it with the key.
Sent from my TA-1054 using Tapatalk
Lord Mashie said:
Don't know whether or not it's a glitch but my 'OEM unlocking' is stuck in the enabled position, even after a hard reset. I'm on Android 10.
EDIT: safe to say that still does nothing.
C:\adb>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
READ MY POST ABOVE...
BTW: i think, this thread not too long
k3dar7 said:
OEM unlock switch NOT unlock bootloafer on Nokia7Plus with ANY Android version 10,9,8.1,8...
is need unlock via fastbboot with unofficialy generated/buyed unlocked file... and for unlocking is need have A8 or A9 with <august2019 security patches/update.,,
Click to expand...
Click to collapse
Hm...
So what you're saying is that there are no Nokia 7 Plus' that have an unlockable bootloader? Or, to put it another way, do all Nokia 7 Plus' have the option "OEM unlocking" set to off? With no way of switching it on?
Or is there a way to switch it on?
I have booted into download mode, and fastboot flashing unlock, but it returns 0 or failed to unlock.
oh wait... I saw your other post: https://forum.xda-developers.com/showpost.php?p=78764676&postcount=3 In reference to the first item, the website is hikaricalyx?
---------- Post added at 12:18 PM ---------- Previous post was at 11:55 AM ----------
Ok... so... for Nokia 7 Plus...
I need to download ntools, HMD rom for version 8, android 8, adb/fastboot.
Then downgrade to version 8.
Flash HMD version 8 rom. (But how do I flash when it's still locked? Or does downgrading to 8 allow the option oem unlocking to be turned on?)
Unlock bootloader.
Use magisk to get root.
Is that the steps? Or am I missing something?
Search for techmaesto.
techmesto dot com/how-to-downgrade-nokia-7-plus-from-stable-pie-to-stable-oreo/
I'm using that guide, and I get up to the part where I update via SD card. But it says that the update package is older than the current build and downgrade not allowed.
What can be done about this?
Anyone know if Nokia will ever allow the bootloader to be unlocked?
ardvarkmcgark said:
Anyone know if Nokia will ever allow the bootloader to be unlocked?
Click to expand...
Click to collapse
Maybe.. N7+ is almost at his end of updates. So we have a little chance that they will do that like the nokia 8
downgrade android 8, inbox
Hello
Is there any method yet to unlock bootloader and convert OnePlus 10 pro T-Mobile to global ?
TechForEver said:
Hello
Is there any method yet to unlock bootloader and convert OnePlus 10 pro T-Mobile to global ?
Click to expand...
Click to collapse
Hy there,I can only tell you how to unlock bootloader you can try going to settings about phone buld number press it 7 times and you will be a developer then go to developer settings and open bootloader if it doesn't work try using fast boot method by writing this command fastboot oem unlock
Then it will unlock bootloader
PromiseKaunda said:
Hy there,I can only tell you how to unlock bootloader you can try going to settings about phone buld number press it 7 times and you will be a developer then go to developer settings and open bootloader if it doesn't work try using fast boot method by writing this command fastboot oem unlock
Then it will unlock bootloader
Click to expand...
Click to collapse
This not working with TMobile version
TechForEver said:
Hello
Is there any method yet to unlock bootloader and convert OnePlus 10 pro T-Mobile to global ?
Click to expand...
Click to collapse
FYI: NE2217 T-mobile (Carrier locked, BL locked) <== Dont Flash Any Other Region w/o reading.
!!! This is a HIGH RISK method of performing any form of modification, if you are on a T-Mobile ne2217 !!! There are unidentified files that your device might have conflict with, and cause a bootloop! Proceed at your own risk! You have been...
forum.xda-developers.com
BUT APPARENTLY OPPO SABOTAGED THE PROCESS. Try at your risk.