The same place that the phone got it from, I got the url from logcat. Maybe I’ll write a complete guide, because there are a couple of funny things about unlocking this thing. Like for example you need to change the dpi to be able to see the ‘OEM unlocking’ option in dev options.
3 Likes
i’d appreciate the guide
2 Likes
Well first of all, the disclaimer. Mudita states that unlocking the bootloader will void the warranty (this is against EU regulations). Also this will factory reset the phone AND you will not be able to automatically get OTA updates.
Also I assume a base level of knowledge, and a working adb and fastboot setup on your computer.
Files can be found here.
Short guide to getting rooted (using magisk):
- Turn on developer options (tap build number 7 times)
- Go to developer options and change “Smallest width” to 400 because otherwise you won’t be able to click “OEM unlocking”
- Turn on “OEM unlocking”
- On your computer, run “adb reboot bootloader”
- Then run “fastboot flashing unlock” (this will factory reset your phone)
- The screen won’t display it, but there is a dialog here where you have to press the volume up key to accept.
- When it is succesfull, run “fastboot flash boot [your patched boot.img]” (for example, the boot_1.1_magisk_patched-28100.img on the google drive)
- When done, “fastboot reboot”
- Download magisk and install it using “adb install Magisk-v28.1.apk”
Then you will be able to do whatever you want with your phone!
I used this guide to install microG. But one thing to note: when you use LSposed, you will of course not be able to interact with the notification as needed. The solution is to use the dialer shortcut: ##LSPOSED##
I hope this helps!
5 Likes
i wonder how you will be able to update the system when its rooted.
i assume u get the link from log, download it, patch the boot.img and put it back into zip archive and then somehow flash the zip via fastboot?
2 Likes
I just checked, OTA still installed as normal but obviously removed magisk. I just extracted the new boot.img and patched it in the same way.
I also put the new patched boot.img in the shared google drive folder.
2 Likes
I’m also Swedish and just got my Kompakt. I kind of wanted BankID but it was not a dealbreaker so ordered the phone without knowing and kind of expecting it not to work.
However I installed aurora store and installed BankID. And while it notified me after installation “This device does not have google services and BankID will not work” it did launch without issues and I added it through my bank and the normal process.
I can confirm that I can log in to my bank with BankID so it is working. This is the only test I’ve done so far and who knows when/if it will stop working.
Anyway, I thought it would be a good thing to add to the conversation.
7 Likes
That is great news indeed, thanks for testing this!
1 Like
I’m not a lawyer but I don’t think its legal for company’s to void warranty in the USA if you unlocked the boot loader 
2 Likes
I´m Norwegian, and it seems like the BankID applies to all nordic countries. I just got in touch with my bank about a physical code device, and they basically said that they are phasing out small code devices (you can get one phone-sized but…), and not recommend to use anything else than the app… In Norway (and I belive Denmark, Finland, an also Sweden?) we also use the app Vipps/Mobile pay quite often - from buying second hand to sharing expenses with friends… Both apps seems to require google services. That´s the only thing holding me back from fully adopting the Kompakt as my only phone.
Any options or advice? What I find perfect about the Kompakt is the lack of a playstore + battery life 
2 Likes
push back. this is just an excuse to not have the expense. how are old people supposed to bank for example? many dont have smart phones.
4 Likes
Thanks for giving the tutorial! Could you do us Nordics a huge favor and try to download the Vipps Mobile Pay app and see if it displays “needs google services” when starting it after rooting/Magisk/microG?
1 Like
Alrighty I checked, and at first it did not work (even though my banking app does). Then I followed this guide and now I get into the mobilepay app, but I don’t have a Norwegian national identity number so I can’t check further 
2 Likes
In both Norway and Sweden 97 percent of the population use smartphones. Old people use smartphones, and smartphones have been around since before they were old. Probably the only significant demographic without smartphones is toddlers. I am not saying this is good, but it is the reality. Pushing back at this point is not going to change things on a larger level, and it is not helping some disadvantaged group. Adults without smartphones are conscious refusers who likely used to use smartphones, and they do it mainly for themselves and know the challenges they are up against.
1 Like
at the end of the day you do you, the fact remains if no one says anything, no one will see there’s a problem. that person who needs to say something is you
2 Likes
Certainly. It’s just… to me it seems a bit arbitrary to regard this app and its widespread usage as a problem, but to be alright with relying on a slightly more limited phone which can still beep and nag and track you in many ways and which keeps you tethered to a network run by state or commercial actors.
When I know I won’t need those apps, I will not carry my phone at all. Phone calls, messengers, SMS… that stuff can usually wait until I’m home.
1 Like
i get it, its probably a topic for another thread. there is some research into this kind of thing though its not extensive and early days, part of the problem is these types of devices have become so ubiquitous so fast no one noticed the health and well-being issues they cause (to be fair we do push back on it a bit in my country), theres an assumption that its just ‘normal’ or ‘ok’, not to mention simple societal problems like the fact you seem to have to buy a mega corporation device (google or apple) to be able to function in society and the government is just ok with that is frankly ridiculous.
2 Likes
Just to note, if you run into an issue with unlocking and getting into a bad state (dm_verify) or others, you can always get into fastboot mode by holding Power + Volume Up for 10s. Once here you can install adb from android platform tools and
- type
fastboot reboot recovery - from there you can load an OTA update from adb.
- Download the ota update that was saved in the Drive link mentioned
- and then
adb sideload <your-path-to-ota.zip>.
That should fully reset the device.
2 Likes