Nokia 8 official bootloader unlock method.

Search This thread
By:
Advanced…
Sahinbas

Sahinbas

Member
Nov 29, 2013
17
1
I will not definitely do that! Cause, it is a high risk to unlock a device with a cronic image retention problem. I don't want to make my warranty void until I can completely trust this device!

TA-1012 cihazımdan Tapatalk kullanılarak gönderildi
 
Toedwarrior

Toedwarrior

Senior Member
Sep 21, 2015
115
31
Izmir
  • Like
Reactions: MaxisMan and arceuss
E

emoklaga113

Member
Mar 31, 2018
15
0
just unlocked the phone now , but can no longer boot the patched root img to root =.= , anyone unlock throught official and gain root ?
 
OneDream

OneDream

Senior Member
Aug 13, 2010
102
7
I'm getting the following error on a brand new Nokia 8:

CTayBwk.jpg


Anyone else experiencing the same issue? Anyone have an idea how to get around this error message?
 
G

godofknife

Senior Member
Feb 1, 2016
98
15
So, A big question to all participants. If we have already unlocked bootloader via unofficial one, do we need to unlock it via official method?

I want to know if it poses no big deal if you have already unlocked bootloader previously using unofficial method.
 
M

mesaj

Senior Member
Jun 13, 2009
552
114
Katowice
godofknife said:
So, A big question to all participants. If we have already unlocked bootloader via unofficial one, do we need to unlock it via official method?

I want to know if it poses no big deal if you have already unlocked bootloader previously using unofficial method.
Click to expand...
Click to collapse

Simply speaking: the result is the same, because unofficial method calculated the same keys official does. You don't need to unlock again as it's unlocked already.

btw just would like to put this in this topic where it belongs: official announcement post about unlocking https://twitter.com/sarvikas/status/1045298106818949120
 
  • Like
Reactions: godofknife
You must log in or register to reply here.

Similar threads

B
Nokia 8 official Firmware June 2018 Oreo [ V4.88B_B04]
Replies
279
Views
168K
Hassaanbaig
Hassaanbaig
Kiwironic
Nokia 8 Android 9 PIE updates
Replies
1K
Views
167K
theviking33
theviking33
dbpm1
Official Nokia 8 Bootloader Unlock Method from HMD Global
Replies
119
Views
50K
L
LineArc
2WildFirE
Nokia 8 updates
Replies
860
Views
101K
F
Frédéric411
S5Guy
The Unofficial Official Nokia 8 Bootloader Unlock Method
Replies
78
Views
30K
umerhussain298
umerhussain298

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 10
    THMSP
    THMSP
    felipondrioxcl said:
    Im on oct patch and still getting "device not support"
    Click to expand...
    Click to collapse

    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.
    View
    7
    S
    stockandroiddudeone
    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.
    View
    2
    Toedwarrior
    Toedwarrior
    MotoG Gen1 Rishi said:
    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.
    Click to expand...
    Click to collapse
    https://www.nokia.com/tr_tr/phones/bootloader


    Let me help you

    Sent from my TA-1012 using XDA Labs
    View
    2
    L
    ludozatt
    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
    View
    2
    V
    vonManstein
    THMSP said:
    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.
    Click to expand...
    Click to collapse

    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...!
    View

New posts