tested on ta-1054.
WHY flash ?
nokia system use 2GB memory after boot. there's lots of things auto start. if you try to disable it ,some app else will crash sometime.
in chinese version, there's some spy action in the system apps. for example:
you'll find a folder called "baidu" in /storage/emulated/0/. in the folder,there's some files used to trace your action. but you never installed any app. this is done by a build-in app called weather service.
again, a folder called ".com.nb.filemanager" created by the build-in file manager.
lots of service backend , for example: tencentlocationservice.
in /system/priv-app/cust, there're lots of service only for chinese version. you know what does it mean. and can't be deleted.
treble rom from phh works on my ta-1054. both AOSP and lineageOS works.
it takes only 1.2GB memory when start up. when you install apks, it act fast ,unlike the OEM one ,pause 4seconds more when goes to 90%.
but there's one problem : wifi couldn't be switched on. ------This has been fixed now.
but another problem found. about the calling. when flash the system to slot a, it recognize two sim. both could receive calling.but calling panel will auto quite when calling out. (the other side will ring, but hear nothing when pick up).
when flash the system to slot b, it recognize one sim card only. call and receive ok.
so take your choice, try to go away from rubbish app or not. flash system may brick your phone,take your risk.
HOW TO :
1. unlock your bootloader.
2.backup your things on the phone.
3. fastboot tools. optional: adb tools.
4.download a boot image from https://dospy.wang/forum.php?mod=viewthread&tid=69.
now treble is build on android 8.1, so download B2N-222A-0-00WW-B06-patched-boot.img .
now , i've extracted the stock boot kernal from my nokia 6.1, version android 8.1. use this instead of the former one , the wifi will works.
https://pan.baidu.com/s/1R0ZconptEvAuth5nJt_ekQ
5.download gsi system image :
lineageOS
AOSP [recommend]
important: choose ab one , instead of a only system. choose arm64 instead of arm.
6.turn your phone to download mode.
you may use adb command:
or shutdown and hold on volume+ and power key to boot, when a doid picture appear, press these two keys again. then choose reboot to bootloader.
optional: see which slot you are in, a or b:
check "current sloct:" and remember it. if you faild to start system later, you may go back to fastboot. if you failed to boot ,sometimes the bootloader will load another slot. so, check it. and you could be aware where you are. we flash one slot is enough, two works too.
7. wipe user data,type:
8.flash the system image:
9.flash the boot image:
tips: if your former system is android 8.1, and you didn't rooted it, then you may skip this step.
10.wipe data again:
11.reboot your phone:
ok, you may see lineage os starts up now.
if you want to root your phone, just install magisk.apk, and then add the magisk.zip module. reboot, that's ok.
maybe problem:
fastboot waiting devices.
two reason. 1. your fastboot version . please use the one extracted from android SDK, the one installed by apt install doesn't work. 2. udev rules .add your device ID to /etc/udev/rules.d/51-android.rules.
find your device id by lsusb.
bootloop
if you could enter recovery ,this means boot img ok. try to flash system again. remember to check wich slot you are in. if not the former one, just switch it by "fastboot set_active a/b" a or b choose the currect one.
if you couldn't enter recoery, just flash boot.img again.
WHY flash ?
nokia system use 2GB memory after boot. there's lots of things auto start. if you try to disable it ,some app else will crash sometime.
in chinese version, there's some spy action in the system apps. for example:
you'll find a folder called "baidu" in /storage/emulated/0/. in the folder,there's some files used to trace your action. but you never installed any app. this is done by a build-in app called weather service.
again, a folder called ".com.nb.filemanager" created by the build-in file manager.
lots of service backend , for example: tencentlocationservice.
in /system/priv-app/cust, there're lots of service only for chinese version. you know what does it mean. and can't be deleted.
treble rom from phh works on my ta-1054. both AOSP and lineageOS works.
it takes only 1.2GB memory when start up. when you install apks, it act fast ,unlike the OEM one ,pause 4seconds more when goes to 90%.
but there's one problem : wifi couldn't be switched on. ------This has been fixed now.
but another problem found. about the calling. when flash the system to slot a, it recognize two sim. both could receive calling.but calling panel will auto quite when calling out. (the other side will ring, but hear nothing when pick up).
when flash the system to slot b, it recognize one sim card only. call and receive ok.
so take your choice, try to go away from rubbish app or not. flash system may brick your phone,take your risk.
HOW TO :
1. unlock your bootloader.
2.backup your things on the phone.
3. fastboot tools. optional: adb tools.
4.download a boot image from https://dospy.wang/forum.php?mod=viewthread&tid=69.
now treble is build on android 8.1, so download B2N-222A-0-00WW-B06-patched-boot.img .
now , i've extracted the stock boot kernal from my nokia 6.1, version android 8.1. use this instead of the former one , the wifi will works.
https://pan.baidu.com/s/1R0ZconptEvAuth5nJt_ekQ
5.download gsi system image :
lineageOS
AOSP [recommend]
important: choose ab one , instead of a only system. choose arm64 instead of arm.
6.turn your phone to download mode.
you may use adb command:
Code:
adb reboot bootloader
optional: see which slot you are in, a or b:
Code:
fastboot getvar all
7. wipe user data,type:
Code:
fastboot -w
Code:
fastboot flash system your-image.img
Code:
fastboot flash boot B2N-222A-0-00WW-B06-patched-boot.img
10.wipe data again:
Code:
fastboot -w
Code:
fastboot reboot
if you want to root your phone, just install magisk.apk, and then add the magisk.zip module. reboot, that's ok.
maybe problem:
fastboot waiting devices.
two reason. 1. your fastboot version . please use the one extracted from android SDK, the one installed by apt install doesn't work. 2. udev rules .add your device ID to /etc/udev/rules.d/51-android.rules.
find your device id by lsusb.
bootloop
if you could enter recovery ,this means boot img ok. try to flash system again. remember to check wich slot you are in. if not the former one, just switch it by "fastboot set_active a/b" a or b choose the currect one.
if you couldn't enter recoery, just flash boot.img again.
Last edited: