Database Info

FRD-AL00 without OEM Unlock option?

Just got a FRD-AL00, whoever there is no OEM Unlock option in the developer menu. What does this means?
I'm still waiting for my Huawei codes since I don't have the phone registered to the Huawei ID in more than 14 days. So I don't know if the bootloader unlock will work without that option.

I also just got this phone and there is no 'oem unlock ' option in developer settings.. Anyone know what the deal is here?

I dont have the OEM Unlock option either. Same case.. I have the honor 8 frd-al00, but my chinese version is already updated to android 7 y emui 5.
All the honor 8 tutorials require that this option should be enable.
So.. what we can do? how we can solve this? I already receive my code for the unlock.
I want to root and debrand the frd-al00 to the international version al09, mentioned here
https://forum.xda-developers.com/honor-8/help/debrand-frd-al00-to-frd-l09-update-to-t3552445
But without this option I cant do it.

AngelLestat said:
I dont have the OEM Unlock option either. Same case.. I have the honor 8 frd-al00, but my chinese version is already updated to android 7 y emui 5.
All the honor 8 tutorials require that this option should be enable.
So.. what we can do? how we can solve this? I already receive my code for the unlock.
I want to root and debrand the frd-al00 to the international version al09, mentioned here
https://forum.xda-developers.com/honor-8/help/debrand-frd-al00-to-frd-l09-update-to-t3552445
But without this option I cant do it.
Click to expand...
Click to collapse
yeah it wont appear there, my friend got al00, he suceessfully rebranded
get bootloader code from offical site and in fastboot , command--> fastboot oem unlock xxxcodexxxxxx
then select unlock in mobile done

AngelLestat said:
I
I want to root and debrand the frd-al00 to the international version al09, mentioned here
https://forum.xda-developers.com/honor-8/help/debrand-frd-al00-to-frd-l09-update-to-t3552445
But without this option I cant do it.
Click to expand...
Click to collapse
Not very good idea...
Phone get unstable in short time with this rebrand made... After watch video or photos in short time applications stop to run...
It will not work good, i had this experience and after all had to go back to AL00...
And it was not only me, on 4pda.ru forum a lot of such cases, so better think twice...

Use this: https://www.youtube.com/watch?v=9ClbjG0ic4U

venugopalu007 said:
yeah it wont appear there, my friend got al00, he suceessfully rebranded
get bootloader code from offical site and in fastboot , command--> fastboot oem unlock xxxcodexxxxxx
then select unlock in mobile done
Click to expand...
Click to collapse
I already have the code as I mention.. but not sure what are you saying.. this mean that even without enabling that option i can make the unlock? but not sure if something bad may happen if the OEM unlock option in disable, and like I said.. that option it does not appear in the development menu, I can find the debugging usb option, but not the other. Some al00 has this OEM unlock option, but not all, maybe depends on the update I get.. my phone auto update to emui 5.0 and android 7.
eseregin said:
Not very good idea...
Phone get unstable in short time with this rebrand made... After watch video or photos in short time applications stop to run...
It will not work good, i had this experience and after all had to go back to AL00...
And it was not only me, on 4pda.ru forum a lot of such cases, so better think twice...
Click to expand...
Click to collapse
you did the same steps that the link guide I quote?
If rebrand is not an option.. then my other options are not good either, because I read that all mods had reboot issues and some other problems.. they dont have the camera apps either, just a basic picture app who does not take a good advantage of double lens system.
So.. what we can do if we have the al00? I just want to use voice search commands (not chinese commands).
TheHunterVN said:
Use this: youtube video link
Click to expand...
Click to collapse
Nice.. but it seems that this is for honor 5.. it will be just a matter to try.. If I have time tomorrow I will give a try to this method.

AngelLestat said:
Nice.. but it seems that this is for honor 5.. it will be just a matter to try.. If I have time tomorrow I will give a try to this method.
Click to expand...
Click to collapse
If u in EMUI 5.0, u must rollback to 4.1, use this method. It's worked with my Honor 8. I think u can.

No OEM Unlock Button
venugopalu007 said:
yeah it wont appear there, my friend got al00, he suceessfully rebranded
get bootloader code from offical site and in fastboot , command--> fastboot oem unlock xxxcodexxxxxx
then select unlock in mobile done
Click to expand...
Click to collapse
The OEM unlock button will be there after the rebrand to a non-chinese version.

BLClark said:
The OEM unlock button will be there after the rebrand to a non-chinese version.
Click to expand...
Click to collapse
Use this: https://www.youtube.com/watch?v=9ClbjG0ic4U
if ur device is on EMUI 5.0, back to 4.1 and use this method. I use Honor 8, use this method and it works.

BLClark said:
The OEM unlock button will be there after the rebrand to a non-chinese version.
Click to expand...
Click to collapse
Correct man

TheHunterVN said:
Use this: "link"
if ur device is on EMUI 5.0, back to 4.1 and use this method. I use Honor 8, use this method and it works.
Click to expand...
Click to collapse
Is any way to debrand without the emui 4.1, I have emui 5.0, my honor 8 is frd-al00, I cant find the rollback file for emui 4.. I find one for frd-al09 from 5 to 4.1, but that is the european version..
I have the bootloader code, but I can not activate the oem unlock option because it does not appear in my development tools, you told me that I have to go back to 4.1, but I have no idea how to do that.. or when I can find the file to do it..
Any advice.. ? What happen if I use the rollback file for the frd-al09?

AngelLestat said:
Is any way to debrand without the emui 4.1, I have emui 5.0, my honor 8 is frd-al00, I cant find the rollback file for emui 4.. I find one for frd-al09 from 5 to 4.1, but that is the european version..
I have the bootloader code, but I can not activate the oem unlock option because it does not appear in my development tools, you told me that I have to go back to 4.1, but I have no idea how to do that.. or when I can find the file to do it..
Any advice.. ? What happen if I use the rollback file for the frd-al09?
Click to expand...
Click to collapse
u can use Hisuit to go back to EMUI 4.1.
Or may try go to fastboot, unlock bootloader in fastboot? Maybe it work. Shutdown Honor, hold volume down + connect ur device to PC via USB cable. Then u try to unlock, if not, the only way is EMUI 4.1.

TheHunterVN said:
u can use Hisuit to go back to EMUI 4.1.
Or may try go to fastboot, unlock bootloader in fastboot? Maybe it work. Shutdown Honor, hold volume down + connect ur device to PC via USB cable. Then u try to unlock, if not, the only way is EMUI 4.1.
Click to expand...
Click to collapse
hi suite is only for some devices , I did nt seen the rollback in hi suite for our devices

TheHunterVN said:
u can use Hisuit to go back to EMUI 4.1.
Or may try go to fastboot, unlock bootloader in fastboot? Maybe it work. Shutdown Honor, hold volume down + connect ur device to PC via USB cable. Then u try to unlock, if not, the only way is EMUI 4.1.
Click to expand...
Click to collapse
venugopalu007 said:
hi suite is only for some devices , I did nt seen the rollback in hi suite for our devices
Click to expand...
Click to collapse
I was able to rollback to 4.1 with hisuite, and I manage to unlock bootloader and install twrp.
I made a backup of all my files, then download the frd-al09432b131, (my phone is frd-al00 which also has 4gb - 32gb), I unzip the firmware and I place it in the ssd card under the folder dload. (not sure if only the update.app file should be in it, or also the other folders like meta-inf and oeminfo, I try with both).
Then from the twrp I did a format data and I wipe data once. Then I shutdown the phone.
press volume up +down+ power until the update starts to run..
But..
At 5%, a alert come up saying:
------------------
Software install failed!
Incompatibility with current version.
Please download the correct update package.
(reboot system now)
------------------
But well, I dint reach so far to resign now.. I am downloading a new firmware from the honor site:
Honor 8 Firmware(FRD-L09, Android 6.0, EMUI 4.1, C432B131, United Kingdom)
I hope this work... or I may be doing something wrong?
Edit: still happen with the new firmware that I download, not sure what to do.. I need supersu for this?

AngelLestat said:
I was able to rollback to 4.1 with hisuite, and I manage to unlock bootloader and install twrp.
I made a backup of all my files, then download the frd-al09432b131, (my phone is frd-al00 which also has 4gb - 32gb), I unzip the firmware and I place it in the ssd card under the folder dload. (not sure if only the update.app file should be in it, or also the other folders like meta-inf and oeminfo, I try with both).
Then from the twrp I did a format data and I wipe data once. Then I shutdown the phone.
press volume up +down+ power until the update starts to run..
But..
At 5%, a alert come up saying:
------------------
Software install failed!
Incompatibility with current version.
Please download the correct update package.
(reboot system now)
------------------
But well, I dint reach so far to resign now.. I am downloading a new firmware from the honor site:
Honor 8 Firmware(FRD-L09, Android 6.0, EMUI 4.1, C432B131, United Kingdom)
I hope this work... or I may be doing something wrong?
Edit: still happen with the new firmware that I download, not sure what to do.. I need supersu for this?
Click to expand...
Click to collapse
Why are you flashing L09 when your phone is AL00?
Sent from my Honor 8 using XDA Labs

adriansticoid said:
Why are you flashing L09 when your phone is AL00?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
because I want to rebrand my phone.
a friend mine bought it for me in China, I didnt know it would be so different in software without google voice search.
So reading guides from this forum, I saw 3 rebrand guides, from chinese version to the similar version of europe (which seems to be the global), I am from Argentina.
I cant post the link of the guides because I am still newbie in this forum.

AngelLestat said:
because I want to rebrand my phone.
a friend mine bought it for me in China, I didnt know it would be so different in software without google voice search.
So reading guides from this forum, I saw 3 rebrand guides, from chinese version to the similar version of europe (which seems to be the global), I am from Argentina.
I cant post the link of the guides because I am still newbie in this forum.
Click to expand...
Click to collapse
You need to the the rebranding steps before flashing your desired firmware.
Sent from my Honor 8 using XDA Labs

AngelLestat said:
because I want to rebrand my phone.
a friend mine bought it for me in China, I didnt know it would be so different in software without google voice search.
So reading guides from this forum, I saw 3 rebrand guides, from chinese version to the similar version of europe (which seems to be the global), I am from Argentina.
I cant post the link of the guides because I am still newbie in this forum.
Click to expand...
Click to collapse
try my rebranding guide in guide section
---------- Post added at 09:17 AM ---------- Previous post was at 09:16 AM ----------
adriansticoid said:
You need to the the rebranding steps before flashing your desired firmware.
Click to expand...
Click to collapse
yes ,rebranding must

The OST LA we're using isn't completely patched

Someone gave me this screenshot (attached below), he has the account to OST LA - as you can see, the interface is much more complete like old SUT L3.
After he clicked Edit Phone Information, the phone booted into FTM Mode successfully.
It means the OST LA we're using isn't fully patched, and it could explain why it can't automatically erase data after flashing.

hikari_calyx said:
Someone gave me this screenshot (attached below), he has the account to OST LA - as you can see, the interface is much more complete like old SUT L3.
After he clicked Edit Phone Information, the phone booted into FTM Mode successfully.
It means the OST LA we're using isn't fully patched, and it could explain why it can't automatically erase data after flashing.
Click to expand...
Click to collapse
May be you are right but the screenshot thay you provided is having samsung S8, there for the FTM mode may be appears on samsung phones, nokia 6 don't boot into FTM mode, as it has fastboot mode
Aslo we all dont have OST tool account, therefore we should thanks the developer who provided this tool
Hit thanks button if you find this helpful
Happy flashing

sltushar said:
May be you are right but the screenshot thay you provided is having samsung S8, there for the FTM mode may be appears on samsung phones, nokia 6 don't boot into FTM mode, as it has fastboot mode
Aslo we all dont have OST tool account, therefore we should thanks the developer who provided this tool
Hit thanks button if you find this helpful
Happy flashing
Click to expand...
Click to collapse
I forgot to mention. It's Nokia 7.
It's internal code name is C1N.

hikari_calyx said:
I forgot to mention. It's Nokia 7.
It's internal code name is C1N.
Click to expand...
Click to collapse
Okay
Well bro we all don't have nokia 7 here, as it was launched in china only
There you must visit nokia 7's forums or threads
Or wait for developers to make a solution for your problem
Till just use your phone if it is alive or try to find the answers in diffrenet threads, if i would find any kind of solution for your problem
I will definitely help you..
Stay happy, and keep faith into yourself
Hit thanks button if you find this helpful
Happy flashing

sltushar said:
Okay
Well bro we all don't have nokia 7 here, as it was launched in china only
There you must visit nokia 7's forums or threads
Or wait for developers to make a solution for your problem
Till just use your phone if it is alive or try to find the answers in diffrenet threads, if i would find any kind of solution for your problem
I will definitely help you..
Stay happy, and keep faith into yourself
Hit thanks button if you find this helpful
Happy flashing
Click to expand...
Click to collapse
You haven't understand why I post it...
I only want to mention the OST LA we're using for Nokia Android Phones haven't completely patched, which also related to every phone made by FIH Mobile including Nokia 2, 3, 5, 6, 6 2018, 7, 8 and 9, Sharp Aquos S2 and Razer Phone.
The guy who provided this screenshot only have Nokia 7.
If I also have the account for original OST LA, I can also enter FTM Mode properly on my Nokia 6.

hikari_calyx said:
You haven't understand why I post it...
I only want to mention the OST LA we're using for Nokia Android Phones haven't completely patched, which also related to every phone made by FIH Mobile including Nokia 2, 3, 5, 6, 6 2018, 7, 8 and 9, Sharp Aquos S2 and Razer Phone.
The guy who provided this screenshot only have Nokia 7.
If I also have the account for original OST LA, I can also enter FTM Mode properly on my Nokia 6.
Click to expand...
Click to collapse
Well mate, then i would like to request you to share the account details which is used to login to the official OST tool
Or the answer would be same, we all dont have the login id or password for OST tool, i know there is more options or features available when we login to OST tool officially
So till the developers get any solution for that we would happy to use it as its been provided on the thread
If you want to help then share the login details so we can also use those features
You will be thanks by everyone :angel:

Nokia 8 TA-1004 July OTA patch 00WW_4_88C zip

OTA update metainfo:
ota-required-cache=0
ota-streaming-property-files=payload.bin:1466:82956364,payload_properties.txt:82957888:154,care_map.txt:562:857,metadata:69:445
ota-type=AB
post-build-incremental=00WW_4_88E
post-timestamp=1530191421
pre-build-incremental=00WW_4_88C
pre-build=Nokia/TA-1004_00WW/NB1:8.1.0/OPR1.170623.026/00WW_4_88C:user/release-keys
post-build=Nokia/TA-1004_00WW/NB1:8.1.0/OPR1.170623.026/00WW_4_88E:user/release-keys
pre-device=NB1
Download link
update_security_patch_2018_07.zip 79.1 MB
[url]https://mega.nz/#!wopjQaIQ!uu2kXUCZsSv25vo1oCzj5ZU0AcaqmVV-rGzRf2JmVgo[/URL]

dbpm1 said:
OTA update metainfo:
ota-required-cache=0
ota-streaming-property-files=payload.bin:1466:82956364,payload_properties.txt:82957888:154,care_map.txt:562:857,metadata:69:445
ota-type=AB
post-build-incremental=00WW_4_88E
post-timestamp=1530191421
pre-build-incremental=00WW_4_88C
pre-build=Nokia/TA-1004_00WW/NB1:8.1.0/OPR1.170623.026/00WW_4_88C:user/release-keys
post-build=Nokia/TA-1004_00WW/NB1:8.1.0/OPR1.170623.026/00WW_4_88E:user/release-keys
pre-device=NB1
Download link
update_security_patch_2018_07.zip 79.1 MB
[url]https://mega.nz/#!wopjQaIQ!uu2kXUCZsSv25vo1oCzj5ZU0AcaqmVV-rGzRf2JmVgo[/URL]
Click to expand...
Click to collapse
Hi
Have you got the ota for TA1012?
Thanks

cption said:
Hi
Have you got the ota for TA1012?
Thanks
Click to expand...
Click to collapse
Unfortunately no, this is the security update ota extracted from a TA-1004 after the download.
It's not a full firmware update as mistakenly noted on the post title, my bad!

Can it be flashed on TA-1012??

whalesplaho said:
Can it be flashed on TA-1012??
Click to expand...
Click to collapse
Probably not, but you can try to recover using this thread as a guide:
https://forum.xda-developers.com/nokia-8/how-to/solved-nokia-8-bricked-downgraded-t3820474

dbpm1 said:
Probably not, but you can try to recover using this thread as a guide:
https://forum.xda-developers.com/nokia-8/how-to/solved-nokia-8-bricked-downgraded-t3820474
Click to expand...
Click to collapse
Okay bro but I don't have unlocked bootloader plus root yet and I tried flashing the June Oreo 488B to flash with OST from here, https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487 but the file is password and no one to help with the password yet.
I like the Nokia 8 but I'm not enjoying it yet and no money to unlocked the bootloader yet also. Its frustrating not been able to use the phone well yet.

whalesplaho said:
Okay bro but I don't have unlocked bootloader plus root yet and I tried flashing the June Oreo 488B to flash with OST from here, https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487 but the file is password and no one to help with the password yet.
I like the Nokia 8 but I'm not enjoying it yet and no money to unlocked the bootloader yet also. Its frustrating not been able to use the phone well yet.
Click to expand...
Click to collapse
Unfortunately you can't do much with a locked bootloader.. but since you're curious you can extract the nb0 file with this tool:
https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464
You need to have at least 8gb of ram on your computer or else it will throw errors during the extract operation!

dbpm1 said:
Unfortunately you can't do much with a locked bootloader.. but since you're curious you can extract the nb0 file with this tool:
https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464
You need to have at least 8gb of ram on your computer or else it will throw errors during the extract operation!
Click to expand...
Click to collapse
I don't even have upto date at all... I ll just find a way to unlocked my bootloader. I'm having issues running OST on my windows 10 pro, it pops Microsoft net framework error message.

whalesplaho said:
I don't even have upto date at all... I ll just find a way to unlocked my bootloader. I'm having issues running OST on my windows 10 pro, it pops Microsoft net framework error message.
Click to expand...
Click to collapse
Maybe you can create a thread about the .Net error to document it for others to see an to get help too!
Also you should check this other thread:
https://forum.xda-developers.com/nokia-8/how-to/qualcomm-edl-entry-to-root-bl-unlock-t3821246
Look for the link on the OP and check @YasuHamed 4th post, there may be a way to achieve BL unlock!

dbpm1 said:
Maybe you can create a thread about the .Net error to document it for others to see an to get help too!
Also you should check this other thread:
https://forum.xda-developers.com/nokia-8/how-to/qualcomm-edl-entry-to-root-bl-unlock-t3821246
Look for the link on the OP and check @YasuHamed 4th post, there may be a way to achieve BL unlock!
Click to expand...
Click to collapse
Im not really good in ramdisk editing, when using Sony, there was a tool dat just patches our boot.img for us... I ll create a thread now. Thanks!

whalesplaho said:
Im not really good in ramdisk editing, when using Sony, there was a tool dat just patches our boot.img for us... I ll create a thread now. Thanks!
Click to expand...
Click to collapse
the script which specially patches SONY KERNEL is/was popular because of the DRM FIX which is/was specific with SONY kernels only
however there is GENERAL script to perform many kernel operation by using ANDROID IMAGE KITCHEN
https://forum.xda-developers.com/showthread.php?t=2073775
all we need with NOKIA is to
1. unlock bootloader
2. find flasher & download official firmware
3. flash kernel via fastboot ( AIK can switchoff the dmvarity)
4. flash magisk
and DONE
we should have ROOTED NOKIA 8 / 7+ whatever

YasuHamed said:
the script which specially patches SONY KERNEL is/was popular because of the DRM FIX which is/was specific with SONY kernels only
however there is GENERAL script to perform many kernel operation by using ANDROID IMAGE KITCHEN
https://forum.xda-developers.com/showthread.php?t=2073775
all we need with NOKIA is to
1. unlock bootloader
2. find flasher & download official firmware
3. flash kernel via fastboot ( AIK can switchoff the dmvarity)
4. flash magisk
and DONE
we should have ROOTED NOKIA 8 / 7+ whatever
Click to expand...
Click to collapse
Yes you right, the drmfix is really a big deal for Sony Xperias and it makes it easier for patching of kernel ing and with Sony providing bootloader unlocking officially.
I really love the Nokia 8 and Dats why I purchased it. I hope things turn around soon cos it's almost a year from date of release.

whalesplaho said:
Yes you right, the drmfix is really a big deal for Sony Xperias and it makes it easier for patching of kernel ing and with Sony providing bootloader unlocking officially.
I really love the Nokia 8 and Dats why I purchased it. I hope things turn around soon cos it's almost a year from date of release.
Click to expand...
Click to collapse
i am badly hung on Xperias! planning to buy XZP lol

YasuHamed said:
i am badly hung on Xperias! planning to buy XZP lol
Click to expand...
Click to collapse
Its really a good choice man... I so much enjoy using Xperias!!!

WARNING to potential buyers of the Nokia 8

I just got done chatting with Nokia support (both chat and email) about getting the required unlock.key file that you need to unlock the bootloader for the Nokia 8, which they said they would unlock. First, a little background. The process Nokia wants you to go through to get the file is to download an apk of theirs which will analyze your phone a bit and then generate a code which you put into a form on their website to get the file emailed to you. Rather clunky but alright. I do so, but then I get an error when the apk runs. "Error messages: Device not support." Very well. I then talk to support. Chat had no idea how to fix it. Email fared just as well. I will copypaste the entire exchange. (Save for the original email I sent as I forgot to save it. Sorry about that.)
Nokia said:
Welcome to Nokia Mobile Care ,
​Thank you for your time writing us and thanks for using our Nokia 8 products. We understand why you came to us thats why we will try our best to assist you !
In order to assist you better and more accurately we would like you to provide us a little bit more information :
​
​- Could you please provide us the screenshot with the error message? Thank in advance!
​- How are you unlocking bootloader ? in which step are you at ?
​Additionally we will provide you the steps unlocking bootloader below :
​
1-Go to https://www.nokia.com/en_int/phones/bootloader, accept the terms and sign in
2-Scroll down until you see the phone validation form.
3-Download and install NokiaPhoneUnlockBootloader.apk, there is an included link on the page.
4-You will receive a validation code that must be entered into the form on the website along with the email used, note the validation code is only valid for 30 minutes.
5-You will receive an email containing a link to download a file, the name will contain your IMEI number and have an extension .key, it should be renamed to "unlock.key"
6-Start the phone in download mode.
7-Download and set up ADB
8-Start an ADB shell and run the following commands, unlock.key must be in the platform-tools directory from the ADB setup
fastboot flash unlock unlock.key
fastboot oem unlock
You should then see
Unlock success!
9-then run the command
fastboot reboot
​
Remember that you are important to us and we're looking forward to your response.
If you have questions or face any difficulties, please contact us at your convenience.
Wish you all the best.
Best regards,
Nokia Mobile Care
-----------------------------------------------------------------------------------------------------------------------------------
© 2019 HMD global All rights reserved.
Nokia is a registered trademark of Nokia Corporation.
HMD global is the exclusive licensee of the Nokia brand for phones and tablets.
-----------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
S5Guy said:
I have downloaded the official apk from Nokia to get the verification code to put on the website form. When I launch the app and put in my email though, it merely shows the error message shown in the attachment.
Click to expand...
Click to collapse
Nokia said:
Thank you for getting in touch with Nokia Mobile Care. It's important for us to have you as our customer.
I can see that you are trying to unlock your phone's bootloader, you have already downloaded the app and you are receiving the message saying that "device not supported".
​
HMD Global allows the bootloader on certain Nokia phones to be unlocked, allowing for customizations. This feature is intended for developers only.
​
Once the device is being unlocked, it is no longer covered by the manufacturer's limited warranty provided by HMD Global.
If you have religiously followed the steps my colleague provided to you on the previous e-mail and after it you have received the message "Device not Supported" this mean that your device is not supported to have the bootloader unlocked.
If you are facing some issue with your phone, you can send it to a repair center, out specialists has the information on how to handle it. Note that Nokia only provides the possibilities to unlock bootloader to developers.
We hope that the above information is useful.
Any other question you may have are always welcome. Please feel free to contact us again.
You can reach us via chat daily, English support is available 24/7. The live technical support channel is easily accessible from the Nokia support application your Nokia smartphone and from your PC, at: https://www.nokia.com/en_int/phones/support#contact-us.
Kind regards,
REDACTED
Nokia Mobile Care
[email protected] email is operated by HMD global, the exclusive licensee of the Nokia brand for phones and tablets. Nokia is a registered trademark of Nokia Corporation, visit us online at www.nokia.com/mobile-support
© 2019 HMD global All rights reserved.
Click to expand...
Click to collapse
S5Guy said:
"If you have religiously followed the steps my colleague provided to you on the previous e-mail and after it you have received the message 'Device not Supported' this mean that your device is not supported to have the bootloader unlocked."
^ This is not correct at all. At least for the Nokia 8. https://twitter.com/sarvikas/status/1045298106818949120
I have followed the prior instructions rigorously, but since the apk does not work, I must ask you for the needed "unlock.key" file. I am very well aware of the consequences of unlocking the bootloader.
Click to expand...
Click to collapse
Thank you for getting back to us. ​I'm sorry to hear that the previous solutions didn't make any difference.
I can see that you are not happy about the previous answer you have had. I understand that can be frustrating sometimes.
As explained before the allowing will depend on many factors, as market, for example. If you have the app running well, if you have tried all the steps to have your bootloader unlocked and still receiving the message "device not supported" there is no other reason than that the app itself is saying the device you are trying to unlock is not supported.
Did you tried to uninstall and reinstall the app? did you tried to restart the process?
Note that here we are a customer care for technical issues customer may face with their device, we do not produce the rules or the policy we just follow then. There is no other advise to you at this moment.
If you have any other question not related to bootloader, please feel free to get back to us any time.
You can reach us via chat daily, English support is available 24/7. The live technical support channel is easily accessible from the Nokia support application your Nokia smartphone and from your PC, at: https://www.nokia.com/en_int/phones/support#contact-us.
Kind regards,
REDACTED
Nokia Mobile Care
[email protected] email is operated by HMD global, the exclusive licensee of the Nokia brand for phones and tablets. Nokia is a registered trademark of Nokia Corporation, visit us online at www.nokia.com/mobile-support
© 2019 HMD global All rights reserved.
Click to expand...
Click to collapse
-
So basically, to sum up, if you're thinking of unlocking the bootloader at all for any reason, steer WAY CLEAR of this phone. My phone may for whatever reason have fallen through the cracks perhaps, but a lot more people than me are reporting this issue. On top of that, I've checked my phone's IMEI to be sure it wasn't stolen or fake and it was perfectly fine and legit. Honestly, I hate that I have to post this message because the Nokia 8 actually has some features I like that aren't really on other phones, but because of this software travesty, I can't recommend it at all.
Nokia, if you're out there, this is a disgrace in both software and support. Please fix this.

Hi
I have the Nokia 8 TA-1012 but I have not tried to unlock the BL. I am currently on Pie so see no reason for doing so as I am happy with the OS.
As most people do not buy a phone to modify the OS I see no problem not recommending this phone for normal use.
Sent from my TA-1012 using Tapatalk

While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?

ironman38102 said:
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
Click to expand...
Click to collapse
It is not related to models, but instead to the build ID's the phones run. (Nokia software is completely generic) Back when Nokia announced the unlock process and the october security patch dropped, phones on october patch started to
report the same issue the OP has encountered. One or two weeks later (after some public outrage ) the app started working again, likely because Nokia added the build ID of the october patch to their
database of allowed versions.
The only solution that doesn't rely on Nokia might be to tear apart their apk and use a rooted phone or an emulator to fake the properties it reads, so the app thinks it runs on a security patch that is supported.
But this approach requires people to send their IMEI to random people on the internet so there are additional risks.

ironman38102 said:
While I didn't unlock through official methods
Click to expand...
Click to collapse
I have heard someone else mention this as well. How did you unofficially unlock the bootloader?

THMSP said:
It is not related to models, but instead to the build ID's the phones run. (Nokia software is completely generic) Back when Nokia announced the unlock process and the october security patch dropped, phones on october patch started to
report the same issue the OP has encountered. One or two weeks later (after some public outrage ) the app started working again, likely because Nokia added the build ID of the october patch to their
database of allowed versions.
Click to expand...
Click to collapse
Perhaps downgrading and then trying the unlock app again might work?: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178

frankoid said:
Perhaps downgrading and then trying the unlock app again might work?: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Click to expand...
Click to collapse
To downgrade without an unlocked bootloader, you need a full OTA image that is configured accordingly, directly from Nokia. You boot into stock recovery and sideload that image, and in theory you should get an Oreo system.
However: The only full OTA downgrade I have done so far was using the revert-OTA from the Pie Beta Labs build. That gives you Oreo with November / December update and AFAIK those builds are not enabled.
The only other full OTA I know of happened it May, and it might be possible to sideload that one to get a system that you can then update and unlock on September / October patch.
But I never used this zip file so I don't know if stock recovery would accept and flash it if you sideload it.
If anyone here wants to try it out: You can download the file from my nokia cloud folder (https://bit.ly/nokia-nb1 - OTA Updates/NB1-488B-00WW-B01-update.zip).
I would be curious about the results. (Only oreo users should try this.. When you downgrade a Pie install it corrupts your userdata)
(I am intentionally not posting a detailed guide. If you can sideload this, you also know about the risks of messing with your phones software )

THMSP said:
To downgrade without an unlocked bootloader, you need a full OTA image that is configured accordingly, directly from Nokia. You boot into stock recovery and sideload that image, and in theory you should get an Oreo system.
However: The only full OTA downgrade I have done so far was using the revert-OTA from the Pie Beta Labs build. That gives you Oreo with November / December update and AFAIK those builds are not enabled.
The only other full OTA I know of happened it May, and it might be possible to sideload that one to get a system that you can then update and unlock on September / October patch.
But I never used this zip file so I don't know if stock recovery would accept and flash it if you sideload it.
If anyone here wants to try it out: You can download the file from my nokia cloud folder (https://bit.ly/nokia-nb1 - OTA Updates/NB1-488B-00WW-B01-update.zip).
I would be curious about the results. (Only oreo users should try this.. When you downgrade a Pie install it corrupts your userdata)
(I am intentionally not posting a detailed guide. If you can sideload this, you also know about the risks of messing with your phones software )
Click to expand...
Click to collapse
I'm your man. With nothing left to lose. o_o Will report back with the results ASAP.

I'm back and with bad news. The update process via the recovery menu seemed to run into an error where it complained about the timestamp on the update zip being too old, but for whatever reason, it proceeded anyway. OK, wiped the data (what data?) and did a factory reset, now it's booting up. I check the system information to be sure and it is 8.1.0. Installed the apk. Ran it. AND THEN...
Device not support.
I'm gonna try this with the zip mentioned in frankoid's post and do another update again, but honestly, it looks like Nokia just wants to be an asshole at this point.

!!!!!!!!!!!!!!! SUCCESS !!!!!!!!!!!!!!!!!!
This update zip is what you need: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.

Thank you apple boy for this topic.
100% troll.

S5Guy said:
*snip*
Click to expand...
Click to collapse
Great to hear that you got it working! My zip likely not worked because it just throws you back half a year (where official unlock didn't even exist) - you would have to update until you find a security patch that works.
But if November patch worked for you thats great! Since the May OTA worked for you that also means that people could choose to use the unofficial (paid) unlock method so Nokia doesn't know about whether they are locked or unlocked (warranty reasons).
Those OTA zips are model-agnostic btw. Whether they say TA-1004 or TA-1012 doesn't matter, they are the same. Only google makes that distinction on their servers, the software doesn't.

foxbatul said:
Thank you apple boy for this topic.
100% troll.
Click to expand...
Click to collapse
What's less useful...
A detailed set of instructions aimed at helping other forum members
... Or your post?

On mine that option is greyed out...
Thank you that was indeed very helpful. Will do the same now...
If I can find out WHY on my device that option is greyed out. How can I overcome this? Thanks

theviking33 said:
Thank you that was indeed very helpful. Will do the same now...
If I can find out WHY on my device that option is greyed out. How can I overcome this? Thanks
Click to expand...
Click to collapse
Did you touch the option in the past at all? If you did, it will be greyed out. As long as it's switched on though, it's fine. (I heard it will "ungrey" itself after a week, but there you go.)

No, did not do anything and it is off and greyed. I don't think it will magically ungrey itself. I did however download that unlock.apk and sent out email and pin, now waiting if a reply will come with the unlock code and procedure. Its been a few hours and no reply, so perhaps that's not working either.

theviking33 said:
No, did not do anything and it is off and greyed. I don't think it will magically ungrey itself. I did however download that unlock.apk and sent out email and pin, now waiting if a reply will come with the unlock code and procedure. Its been a few hours and no reply, so perhaps that's not working either.
Click to expand...
Click to collapse
I'm assuming you have a brand new TA-1004? And yeah, you should have gotten back a code long ago.
Try some of these options. https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
It could be though that it's just been flat out disabled due to region or whatever. If the solutions in the above link don't work, try downgrading back anyway and then using the apk as explained in an earlier post of mine.

It seems to be a case of "flat out disabled". I did a factory reset already and this setting won't change. I actually bought 2 of those phones and on both is the same.
How do I see or find out what region they are for?
And for the booloader, seems I have to go the old fashion way now...
---------- Post added at 11:38 ---------- Previous post was at 11:25 ----------
I have the TA-1004 DS which is International. So wouldn't understand why ist greyed.

ironman38102 said:
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
Click to expand...
Click to collapse
Mine has same problem and I've also been through similar online-forum attempts to help.
Model: TA-1012
Hardware version: 3.1
Patch level: 1 Jan 2019
Build No: 00WW_5_11A, 00WW_5_110_SP01

Downgrade your phobe and you can unlock, i have the same phone and this is what i did. I downloaded my phone firmware,i place the update file on my external sd card, i reset my phone to factory stock, i shut down my device an while shut down i press vol + and plug in my cable, i wait for the no comand screen and press power while holding vol up and get in recovery where i update from sd card and boom oreo

[GUIDE] How to install Internal Android 10 build for Nokia 6.1 (non TA-1054)

If you want to repost this internal OTA to other websites (other than XDA itself), please ask me for permission, thanks.
Click to expand...
Click to collapse
WARNING!
This is early internal test build, so LATER OTA UPDATES CAN'T BE GUARANTEED!
If you don't have unlocked bootloader, you'll unable to roll back to stable build!
Please be careful when testing!
Click to expand...
Click to collapse
To users who have installed this internal build, please share your experience report here if you're willing to, thanks.
UPDATE: Thanks everyone. To fix microphone bug, please disable the microphone permission of the "Google" app.
You'll lose "OK Google" ability, but you can make telephone call properly.
Click to expand...
Click to collapse
Now I think it's time to bring you back to canary labs faster than beta labs.
Internal build version: PL2-4040-0-00WW-B01
It will be updated from: PL2-354N-0-00WW-B01, which is released October 2019 Security Update
As I've warned before - having an unlocked bootloader is strongly recommended.
So recent builds removed handy 874 dialing codes, we have to install them under recovery or Nokia Extensions.
Let me tell you how to verify:
1. Dial *#*#227#*#* to check current Version. If older than PL2-354N-0-00WW-B01, update to 354N before proceed.
FYI, 354N is October 2019 Security Update.
Alternately, you can use command "fastboot oem getversions" under fastboot mode / Download mode to check current firmware version.
2. Install PL2-4040-0-00WW-B01-354N-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
3. Reboot your phone.
That's it.
If minor fixes released, I will upload them as well, then use the same method to install it.
To root the phone, you may want to use Magisk 20 released October 12th, 2019 or newer.
Download link:
https://www.androidfilehost.com/?w=files&flid=300345

reserved

Installed it on my TA-1043.
OS installed fine over adb sideload, everything seems to be working, and it shows "5" next to my wifi icon - guess it's cause it's 5GHz, also the mobile data icon is still not AOSP and some custom thing. Menus kinda feel stutter-ish. Screenshots were broken on first boot.

alternate download links like google drive?

The update wont install
version no. L2-354O-0-00WW-B01

Update: "Photo" mode in stock camera is broken, says "Action not support: 708". Pro mode works fine

how to use magisk?
i tryed to patch boot on magisk and boot from ADB, but phone going n bootloop and doesn't want up

Hi @hikari_calyx I'm currently on the DRG-354N-0-00WW-B01 stock build version with an unlocked bootloader. But the version on the post has PLC. Also, if after sideloading this rom I decide to go back to the October PIE update how hard will that be. Thanks.

solozeeh said:
Hi @hikari_calyx I'm currently on the DRG-354N-0-00WW-B01 stock build version with an unlocked bootloader. But the version on the post has PLC. Also, if after sideloading this rom I decide to go back to the October PIE update how hard will that be. Thanks.
Click to expand...
Click to collapse
Hi. DRG is Nokia 6.1 Plus. This thread is for Nokia 6.1 (2018) which is PL2.

Getting error when the camera app is set to save photo to sd card.
---------- Post added at 03:24 PM ---------- Previous post was at 02:58 PM ----------
So right now for me on the Internal Stock... I cannot boot any TWRP of any kind or boot any patched magisk boot img. Has anyone been able to boot either TWRP or boot a patched boot img from magisk?

May I ask, can Nokia 6.1 plus use this rom?

joshclaudio said:
Hi. DRG is Nokia 6.1 Plus. This thread is for Nokia 6.1 (2018) which is PL2.
Click to expand...
Click to collapse
The confusion is caused by the fact that the Nokia 6.1 Plus (DRG) forum on XDA was recently deleted and now redirects here.
Apparently XDA is working to restore the DRG forum but it will take some time. Until that is done you can expect to see a lot of confused DRG users here on the PL2 forum. Please help them out if you can.

kazekiri said:
The confusion is caused by the fact that the Nokia 6.1 Plus (DRG) forum on XDA was recently deleted and now redirects here.
Apparently XDA is working to restore the DRG forum but it will take some time. Until that is done you can expect to see a lot of confused DRG users here on the PL2 forum. Please help them out if you can.
Click to expand...
Click to collapse
Yeah, noticed that, too. I've been experiencing redirect problems since yesterday. Anyway, I installed Android 10 leaked internal build on my Nokia 6.1 Plus with a locked bootloader :silly: . Been using it for more than 48 hours and I have not faced any major issue, except for the not working microphone during calls (plugging in earphones can suffice, though).

solozeeh said:
Hi @hikari_calyx I'm currently on the DRG-354N-0-00WW-B01 stock build version with an unlocked bootloader. But the version on the post has PLC. Also, if after sideloading this rom I decide to go back to the October PIE update how hard will that be. Thanks.
Click to expand...
Click to collapse
Here's the link for the DRG version for anyone who needs it. (Since the DRG forum is currently down.)
Only install this if you are using a Nokia 6.1 Plus or X6 (DRG). DO NOT try to install on Nokia 6.1 2018 (PL2).
https://androidfilehost.com/?w=files&flid=300344

Hi hikari calyx! Please help me downgrade my Nokia 6.1 to Android 9. Bootloader locked

kaktyys71 said:
Hi hikari calyx! Please help me downgrade my Nokia 6.1 to Android 9. Bootloader locked
Click to expand...
Click to collapse
"If you don't have unlocked bootloader, you'll unable to roll back to stable build!"
Literally on top of the OP post. As every downgrade/restoration method needs an unlocked bootloader, you can either unlock yours (paid external service), or wait for an eventual OTA zip (not guaranteed, as stated by the OP) that will bring you back on Android 10 official Beta/Release in a couple of weeks.

Solannae said:
"If you don't have unlocked bootloader, you'll unable to roll back to stable build!"
Literally on top of the OP post. As every downgrade/restoration method needs an unlocked bootloader, you can either unlock yours (paid external service), or wait for an eventual OTA zip (not guaranteed, as stated by the OP) that will bring you back on Android 10 official Beta/Release in a couple of weeks.
Click to expand...
Click to collapse
Project Treble A/B? B slot don't help me?

I guess it ils worth a try. Reboot to bootloader, then "fastboot getvar all" to get active slot and "fastboot --set-active=[a/b, your inactive slot]
The thing is, with official OTA updates, once the update is over and everything went well, the previous slot is not necessarily in a bootable/usable state anymore. It is not the case with most custom roms/gsi as you either update directly on the current slot or on the other without modifying the active one, so you can switch between slots without issues.

kaktyys71 said:
Project Treble A/B? B slot don't help me?
Click to expand...
Click to collapse
If you switch inactive slot to active slot and reboot... it will ask to do a factory reset. Perform the factory reset and you should be back to the Pie version. Use the fastboot commands Solannae posted above.
---------- Post added at 11:58 PM ---------- Previous post was at 11:36 PM ----------
Battery draining fast on Internal Android 10.

The battery drain was due to the Adguard app. Everything is working normal again.