Nokia 8 official bootloader unlock method.

Search This thread

Gemmik

Senior Member
Apr 5, 2015
116
10
Mexico City
I cant unlock my Nokia 8 i got an error "Device is not Supported" I contact with Nokia Support and some guy told me that the way to unlock is closed :/ is it right??? I'm on June patch
 

webvan

Senior Member
May 20, 2008
1,165
69
There were issues with the October update at one point. Why haven't you updated?
 

czupyt

Senior Member
Apr 3, 2012
125
60
Poland
I cant unlock my Nokia 8 i got an error "Device is not Supported" I contact with Nokia Support and some guy told me that the way to unlock is closed :/ is it right??? I'm on June patch

Official unlock is possible from September Security patch. Unofficial is possible till July one. On August one you can do nothing. There are two ways for you:
1) Stay on June, unlock unofficially and than update till later patches.
2) Update till at least September and unlock officially.

The difference would be that for unofficial you have to pay couple of bucks, but you do not inform HMD that you unlocked bootloader. So if you need to use your warranty, you can always relock and HMD won't know that you did something with bootloader. With official way unfortunate you will inform them and process of using your warranty is totally up to them. In general applying for official unlock you agree to skip you warranty. That is official statement from hmd. Of course of something worth your phone goes wrong, you can always try, but all in all they can say no.
 
  • Like
Reactions: Gemmik

Audioboxer

Senior Member
Aug 24, 2010
3,035
670
Has anyone asked or been able to find out if the Sirocco is going to follow given it's pretty much a variant of the Nokia 8?

Would be a shame if Nokia ignored it. I'd be happy if it even just got the ability to root.
 

Gemmik

Senior Member
Apr 5, 2015
116
10
Mexico City
There were issues with the October update at one point. Why haven't you updated?

I'm stuck with June Update :/

---------- Post added at 03:08 PM ---------- Previous post was at 03:04 PM ----------

Official unlock is possible from September Security patch. Unofficial is possible till July one. On August one you can do nothing. There are two ways for you:
1) Stay on June, unlock unofficially and than update till later patches.
2) Update till at least September and unlock officially.

The difference would be that for unofficial you have to pay couple of bucks, but you do not inform HMD that you unlocked bootloader. So if you need to use your warranty, you can always relock and HMD won't know that you did something with bootloader. With official way unfortunate you will inform them and process of using your warranty is totally up to them. In general applying for official unlock you agree to skip you warranty. That is official statement from hmd. Of course of something worth your phone goes wrong, you can always try, but all in all they can say no.

Thanks for reply, I'm stuck with June Update... I tried reset and change language to update ( it works with Nokia 5) also I tried to clear data of Google Framework and nothing happened. I have TA-1012 model
 

czupyt

Senior Member
Apr 3, 2012
125
60
Poland
I'm stuck with June Update :/

---------- Post added at 03:08 PM ---------- Previous post was at 03:04 PM ----------



Thanks for reply, I'm stuck with June Update... I tried reset and change language to update ( it works with Nokia 5) also I tried to clear data of Google Framework and nothing happened. I have TA-1012 model

Exactly like @webvan, what would be your sympthoms. No possibiliy of update? Even no suggestion of new SW?
 

theviking33

Member
Jan 27, 2019
35
3
Asgard
waiting for the code...

just sent the email and waiting for the code. I hope there will be info on HOW to proceed then. It has been over 1 hour so far and no reply. But at least the email and pin popped up and I am on Pie w/Jan update.
 

theviking33

Member
Jan 27, 2019
35
3
Asgard
Got all done BUT the confirmation code. When I run the app on the phone, email and pin works but how would this finish up? Mine just displays ...loading.. and then disappears. So no code.
Even though I did not see any mention of the setting in developer mode mentioned at Nokia site, my setting is greyed out! Cannot switch it on.
Any suggestions with that? Did this happen so somebody else and was resolved?
Does this setting really have to be on for this?
Thanks for any help...
 

MDV106

Senior Member
Jan 4, 2019
481
169
not working on January update of Android Pie. It says "device not supported" :(

im starting to regret ever buying this phone.
 
  • Like
Reactions: damian101

MDV106

Senior Member
Jan 4, 2019
481
169
Thank you for getting in touch with Nokia Mobile Care. It's important for us to have you as our customer.

I understand how frustrating is when we do not get the answer we want to have. please note that here we are just a remote customer care and there nothing else we can do to you, we will always say the same thing, because this is what we are advised to do. Whit doesn't mean that we are not giving you a good and satisfactory support.

Every Nokia phone, after manufactured receives a series number and it is delivered to a specific market that it was manufactured for, each market has different specification, pieces, system, laws, government technology statement, etc. with means that even you you get two Nokia 8 from the same store at the same day, there is a possibility that that two devices can be manufactured with different series number.

This is the reason why Nokia says that it will allow to certain phones only, it means that none all phones, even if they are all Nokia 8 will be allowed to have the bootloader unlocked. If you are receiving the message "device not supported" that means that your device is not supported to have the bootloader unlocked.

Thank you so much for your understanding on the situation here. Now understanding that I have already gave all the information that I have in order to explain you why we do not have the information about the Bootloader unlocking code, I will then be closing this ticket.

I 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,
Tamara

This is what HMD sent me after a couple of back and forth emails. The nerve of them. SMH
 
  • Like
Reactions: damian101

singhnsk

Senior Member
Nov 11, 2012
199
77
www.techmesto.com
This is what HMD sent me after a couple of back and forth emails. The nerve of them. SMH
Again shows how uninformed they are. While that generic statement is correct, for example the phones sold in China aren't probably eligible for unlocking. The remainder is a uninformed reply. The not supported is a problem due to the latest update for which the server is not modified. So, none of the Nokia 8 on Pie will be supported, irrespective of the model or the market where it was sold.

Sent from my Nokia 8.1 using XDA Labs
 
  • Like
Reactions: MDV106

MDV106

Senior Member
Jan 4, 2019
481
169
Again shows how uninformed they are. While that generic statement is correct, for example the phones sold in China aren't probably eligible for unlocking. The remainder is a uninformed reply. The not supported is a problem due to the latest update for which the server is not modified. So, none of the Nokia 8 on Pie will be supported, irrespective of the model or the market where it was sold.
I was so upset about the silly response. Luckily i found a workaround posted a few posts above. Downgraded manually to 8.1 november security patch then used the app, it gave me the unlock code without error and i was finally able to unlock the bootloader. I then sideloaded the december pie update and then flashed a december pre-patched boot img to finally get root on this phone. Now im busy restoring backups and all. If it wasnt for the community i'd have given up and sold this phone
 

shivaji namburu

Senior Member
Mar 16, 2017
52
3
Thanks, I finally got it to work with Win10, not sure what did the trick though as I tried a ton of things. Oh andAll of course once you're in fastboot you can't get ADB to work, it's only fastboot, had forgotten about that so I wasted a bit of time with that.

Up and running now but I'm a bit concerned about future updates as I can't do the October update when I'm booted into Slot A, even with Magisk removed and with stock_boot_nb01_488_sp04_sep.img - that should work right ? Or it sees it's not my original boot image ?

I am also facing this problem my device is not getting detected in fastboot mode.any suggestions......?
Help......!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Im on oct patch and still getting "device not support"

    I had the same problem on my device (TA-1004), and decided to take a closer look at it. Running "adb logcat" while performing the steps in the app gives out multiple SELinux warnings and app exceptions related to opening the file "/proc/fver".
    I also used a proxy to intercept and read the requests by the app to the HMD server.

    I could prefectly open the file through "adb shell", and made the observation that the app probably tries to figure out which firmware the phone is running (NB1-488J-0-00WW-B01 for october patch). However, it seemed that october patch messed up the SELinux permissions
    so every app that tries to access it gets blocked (shell works because it is some kind of elevated process I think, I vaguely recall that apps run in a different PID range). A side effect of that is that the app always reports the firmware as NB-1.0-0-00WW-B01 and gets
    an error code that the version is not in the compatibility list.

    As a next step I decided to take apart the apk itself and decompiled it into java code. The code is obfuscated (this means all elements are called a, b, c, d, etc. instead of the original names HMD uses) - so basically unreadable without lots of time,
    but thankfully I had a starting point - the errors in the logcat included the spot where the code fails. Reading the file, I found that reading the firmware from /proc/fver is actually just a fallback, the prefered way is to read it from the "ro.build.odm.fver" property,
    which, according to running "getprop ro.build.odm.fver" and just "getprop" to list all properties, does not exist.

    What does this mean? Either the property never existed and HMD/Google/whoever broke accessing the /proc/fver file in the october patch, or the property existed on september patch, and they forgot to include it in the october patch as well.
    (This seems more likely, since, for example, you also needed the september patch to run the app at all, even though they changed keys in august. That already indicates that they had to change something and forgot it now).

    Is this solveable? Thats actually a good question. After I already had the code, I thought why not try to get it working.
    The problem with that is that even though you can patch the app to stop erroring and force it to send a somewhat correct looking request, there are lots of security mechanisms put in place by HMD

    • The app generates a hash of itself, and uses that to verify itself against the HMD server (solveable, SafetyNet just dumps those hashes into the logcat so I assigned them to their variables)
    • The app seems to have some form of negotiation between itself and the HMD Server, I couldn't just resend a previous request. (Might be solveable, but hard without knowledge about the HMD server)
    • The app does some work inside of a native library that cannot be decompiled. This is a problem.

    That last point is important, because the whole body of the request is encrypted, with only a public key availabe in the apps files (public key is for encrypting, to read the data we would need the private key). It probably contains your IMEI numbers since they aren't anywhere else in the request.
    Because we can neither decrypt the data to see whats actually sent, nor check out the code that generates the request, we are basically screwed. While you can edit the unencrypted version number in the request header, it did not work so far for me with the october patch version. I tried guessing the version number from september (I went straight from July to October due to having to reflash my device before sending it in for speaker repair, so I don't know the exact number), but it didn't work either.

    I would be interested if anyone that is still running september patch could post the firmware version, so I can try that out. If it doesn't work we can say for sure that the firmware version is added a second time to the request body.
    I would also be interested if this is a device specific issue. I have the dual-SIM version, maybe it works for the single SIM one?
    Maybe it also never worked like it should on the dual-SIM one?

    After writing such a long and probably hard to read post, I had a final thought: I wonder if the keys that are used to generate the unlock key are the same for all devices. If yes, and someone manages to figure out how to modify the request, it could be possible to have all different HMD phones (like Nokia 7 Plus for example) to identify with a Nokia 8 firmware and get an unlock key generated. But thats probably just a dream.
    7
    Rejoice people, Nokia just released an official bootloader unlock method for Nokia 8 confirming via a tweet from Juho Sarvikas.
    Please check the tweet or Nokia website for more information, I am not yet allowed to post links/urls on XDA threads yet.
    2
    Rejoice people, Nokia just released an official bootloader unlock method for Nokia 8 confirming via a tweet from Juho Sarvikas.
    Please check the tweet or Nokia website for more information, I am not yet allowed to post links/urls on XDA threads yet.
    https://www.nokia.com/tr_tr/phones/bootloader


    Let me help you

    Sent from my TA-1012 using XDA Labs
    2
    unlocker is working

    gr8 news,
    the HMD Bootloader Unlocker official app is now working on my TA-1052 with October patch.
    It does give back the requested code and no more "not support" error.
    Have a nice rooting
    2
    The best way is probably to wait until Pie gets released. If it works on Pie, everything is good. If not, take your phone to a service point and ask them to downgrade it to Oreo,
    either with a made up excuse like you have a critical work app that only runs on oreo, or just with the real reason, it's supposed to be official after all.
    This would bring you back to May or June IIRC, so you could just update to September and unlock officially, or use the unofficial method if you got a key for it.

    Hi all,

    Just got off the chat through the support app, the client service rep confirmed that the latest security update deactivated boot loader unlock for Nokia 8.

    He also confirmed they have escalated the issue and it will be addressed by their android department.

    And that the solution should come with the next security update.

    Let's wait and see...!