To Content farms like GETDROIDTIPS: DO NOT REPOST OR REFORM MY TOPIC ON YOUR WEBSITE WITHOUT INFORMING ME!
Recent Android 10 update fixed support for TA-1054 hardware, so we can do global conversion right now. Anything older will break the phone and you have to disassemble the phone and utilize EDL to unbrick it (test point indicated below).
Therefore, we have to install Android 10 directly, but for some reason, the bootloader will be reverted back to locked state, so it has to be unlocked again via some tricks.
This guide will tell you how to install Android 10 into TA-1054. If you don't have unlocked bootloader, you have to unlock it first.
If you don't have unlocked bootloader, you may need to look for Global conversion service online.
PLEASE MAKE SURE YOU HAVE BACKED UP EVERYTHING BEFORE YOU DO SO.
Step 1: Change SKUID
To change SKUID, you need to ensure your phone is rooted, or your phone booted to TWRP (official TWRP for Nokia 6.1 is OK to use) to allow us change SKUID written in deviceinfo partition.
If you booted to TWRP via these commands under Download mode:
Code:
fastboot reboot-bootloader
fastboot boot twrp-3.4.0-0-PL2_sprout.img
Once phone booted to TWRP (even if stuck at splash screen is OK), then you can dump the devceinfo and securefs partition:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/deviceinfo of=/tmp/deviceinfo.img
adb shell dd if=/dev/block/bootdevice/by-name/securefs of=/tmp/securefs.img
adb pull /tmp/deviceinfo.img
adb pull /tmp/securefs.img
The reason why I suddenly mentioned securefs partition is, it contains Widevine DRM key that related to video-on-demand services like Netflix.
You have to back it up just in case.
Then follow this guide to edit SKUID written in deviceinfo into 600WW:
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-change-skuid-to-worldwide-t3808520
Once SKUID changed, write the deviceinfo partition back:
Code:
fastboot flash deviceinfo deviceinfo_600WW.img
After SKUID changed, you'll find the launcher becomes weird, which is expected behavior.
Step 2: Install Android 10 full OTA
Please download it from here:
https://android.googleapis.com/pack.../c6260831df0acdfe9828f18bcea7ffb556f4b2e5.zip
And rename it into PL2-9999-0-00CN-B99-update.zip. Copy it to root directory of internal storage, and dial *#*#874#*#* to install it.
Once install complete, you might be asked for erasing userdata, just erase it.
Step 3: Unlock bootloader again (optional)
If you think it's OK to use Android 10 without unlocked bootloader, then that wraps up the procedure and enjoy it.
But if you want to unlock the bootloader again, you have to follow some trick.
Once the phone booted to welcome screen again, power it off, boot to Download mode by using this command:
Code:
fastboot oem alive
And connect the powered off phone to PC, it will be booted to Download mode again.
Next, check which slot is Android 10 installed:
Code:
fastboot getvar current-slot
If current-slot is A, execute this:
Code:
fastboot --set-active=b reboot-bootloader
If current-slot is B, execute this:
Code:
fastboot --set-active=a reboot-bootloader
Once slot changed, you'll be switched back to the previous version with unlocked bootloader.
Now you have to downgrade the abl/xbl to allow it being unlockable again.
Now check which slot is Chinese Nokia 6.1 Android build installed:
Code:
fastboot getvar current-slot
If current-slot is A, execute these:
Code:
fastboot flash abl_b C1N-0-0430-abl_service.elf
fastboot flash xbl_b C1N-0-0430-xbl_service.elf
fastboot --set-active=b reboot-bootloader
If current-slot is B, execute these:
Code:
fastboot flash abl_a C1N-0-0430-abl_service.elf
fastboot flash xbl_a C1N-0-0430-xbl_service.elf
fastboot --set-active=a reboot-bootloader
Both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf can be obtained from https://fih-firmware.hikaricalyx.com/hmd_en.html#c1n (extract it from C1N-0-0430-0-00CN-B05 firmware).
Then you can unlock the bootloader again with what you have done before:
Code:
fastboot flash unlock unlock.bin
fastboot flashing unlock_critical
(confirm bootloader unlock on the phone)
(while waiting for erasing, execute this immediately)
fastboot oem alive
fastboot flash unlock unlock.bin
fastboot oem unlock-go
(confirm unlock again)
(while waiting for erasing, execute this immediately)
fastboot oem alive
After we unlocked the bootloader, we have to switch back to previous Chinese Nokia 6.1 Android build to reinstall Android 10.
Check which slot is Android 10 installed:
Code:
fastboot getvar current-slot
If current-slot is A, execute this:
Code:
fastboot --set-active=b reboot
If current-slot is B, execute this:
Code:
fastboot --set-active=a reboot
Repeat the step 2 to reinstall Android 10 Full OTA, and enjoy Android 10 on Chinese Nokia 6.1 with unlocked bootloader.
Under Android 10, if bootloader unlocked, you'll lose Widevine DRM key permanently, that's why I asked you to backup securefs partition.
Is the shorting wires solution to unbrick the phone or to change china to global version?
Ok, pins shorted. Whats now?
Spacepl said:
Ok, pins shorted. Whats now?
Click to expand...
Click to collapse
flash nbo Nokia 6 2018 firmware with OST LA
Sent from my TA-1054 using Tapatalk
juwelrana091 said:
flash nbo Nokia 6 2018 firmware with OST LA
Click to expand...
Click to collapse
Do i need to unlock the bootloader to do this?
And if so can so post a link for a way that doesnt require the app provided by nokia?
J0NS3N said:
Do i need to unlock the bootloader to do this?
And if so can so post a link for a way that doesnt require the app provided by nokia?
Click to expand...
Click to collapse
Is your phone already bricked? Then shorting the pins will trigger EDL mode and then you can use Qualcomm tools to flash the abl and xbl. That can make the phone usable again, but yes you will still need to flash the CN firmware as Global will not be usable on this device.
help
hello i tried shortening all 4, or one of the 2 sets but it did not trigger EDL, my phone is stuck in Download mode as soon as it turns on, my pc only recognizes it as Fastboot device, my bootloader is locked, i have the exact same model, can you help me??
Could you please clarify:
is it possible to install PL2-410C-0-00WW-B03 on TA-1054 China Version , i.e. convert it into Android 10 Global Version? So it is impossible to install earlier global versions, but it is possible to install PL2-410C-0-00WW-B03?
Thank you.
vanechka25 said:
Could you please clarify:
is it possible to install PL2-410C-0-00WW-B03 on TA-1054 China Version , i.e. convert it into Android 10 Global Version? So it is impossible to install earlier global versions, but it is possible to install PL2-410C-0-00WW-B03?
Thank you.
Click to expand...
Click to collapse
Yes, but remember to change SKUID to 600WW before installing PL2-410C-0-00WW-B03.
Also, flash PL2-410C-0-00WW-B03 into bootloader unlocked TA-1054 will revert the bootloader back to locked state, you have to unlock it again with some trick, will talk about that later.
If you use some flashing tool that can elevate like NTool, just go ahead and flash PL2-410C firmware.
hikari_calyx said:
Yes, but remember to change SKUID to 600WW before installing PL2-410C-0-00WW-B03.
Also, flash PL2-410C-0-00WW-B03 into bootloader unlocked TA-1054 will revert the bootloader back to locked state, you have to unlock it again with some trick, will talk about that later.
If you use some flashing tool that can elevate like NTool, just go ahead and flash PL2-410C firmware.
Click to expand...
Click to collapse
Thank you for the quick answer!
Hmm... Is it possible to change SKUID for this phone with locked bootloader?
I know, for some other phones it could be done using fastboot command like this:
fastboot oem CustomerSKUID set 600WW
but I'm not sure that this method is applicable to TA-1054. I checked the command CustomerSKUID:
fastboot oem CustomerSKUID get
and it is unknown.
Do you know any easy way to change SKUID without unlockng / rooting?
What will happen if I try to flash PL2-410C-0-00WW-B03 without SKUID changing?
Actually, the main reason to update the phone is the problem with mobile internet. My local mobile operator SIM does't allow to use it, but the voice service works OK. When I set this SIM to another phone, internet works, when I set SIM of another operator to TA-1054 - it works again. So, certain operator internet settings and settings in chinese ROM are different. I suppose, it is required to change bands modes or something like this, but I dont't know the real reason of this issue.
Maybe you could give me an advice about this internet problem, so I don't need to update phone to global ROM at all.
vanechka25 said:
Thank you for the quick answer!
Hmm... Is it possible to change SKUID for this phone with locked bootloader?
I know, for some other phones it could be done using fastboot command like this:
fastboot oem CustomerSKUID set 600WW
but I'm not sure that this method is applicable to TA-1054. I checked the command CustomerSKUID:
fastboot oem CustomerSKUID get
and it is unknown.
Do you know any easy way to change SKUID without unlockng / rooting?
What will happen if I try to flash PL2-410C-0-00WW-B03 without SKUID changing?
Actually, the main reason to update the phone is the problem with mobile internet. My local mobile operator SIM does't allow to use it, but the voice service works OK. When I set this SIM to another phone, internet works, when I set SIM of another operator to TA-1054 - it works again. So, certain operator internet settings and settings in chinese ROM are different. I suppose, it is required to change bands modes or something like this, but I dont't know the real reason of this issue.
Maybe you could give me an advice about this internet problem, so I don't need to update phone to global ROM at all.
Click to expand...
Click to collapse
If you don't have some special flashing utility (requires USB dongle), you cannot change SKUID without unlocked bootloader.
You can search about global conversion service remotely which could be paid.
Install global firmware with mismatch SKUID will cause the OS itself buggy, many feature missing and cannot pass Google Play Certification.
hikari_calyx said:
If you don't have some special flashing utility (requires USB dongle), you cannot change SKUID without unlocked bootloader.
You can search about global conversion service remotely which could be paid.
Install global firmware with mismatch SKUID will cause the OS itself buggy, many feature missing and cannot pass Google Play Certification.
Click to expand...
Click to collapse
Thank you very much for the answer. You clarified a lot of things!
Downgrade from android 10 to android 9
vanechka25 said:
Thank you very much for the answer. You clarified a lot of things!
Click to expand...
Click to collapse
Hey can you help me for downgrading android 10 to android 9 with locked bootloader .i want to unlock bootloader to downgrading to android 9 and also i am facing wifi disconnected and mobile restarting issues .also what this ss show is that bootloader locked or unlocked
hikari_calyx said:
If current-slot is A, execute these:
Code:
fastboot flash abl_b C1N-0-0430-abl_service.elf
fastboot flash xbl_b C1N-0-0430-xbl_service.elf
fastboot --set-active=b reboot-bootloader
If current-slot is B, execute these:
Code:
fastboot flash abl_a C1N-0-0430-abl_service.elf
fastboot flash xbl_a C1N-0-0430-xbl_service.elf
fastboot --set-active=a reboot-bootloader
Both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf can be obtained from https://fih-firmware.hikaricalyx.com/hmd_en.html#c1n (extract it from C1N-0-0430-0-00CN-B05 firmware).
Then you can unlock the bootloader again with what you have done before:
Click to expand...
Click to collapse
A very complete guide, thank you, but I have a question. From what I've seen both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf refer to Nokia 7 (android OS 7.1.1), is it ok to flash them on a Nokia 6.1 with android OS 8.1 ?
21prods said:
A very complete guide, thank you, but I have a question. From what I've seen both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf refer to Nokia 7 (android OS 7.1.1), is it ok to flash them on a Nokia 6.1 with android OS 8.1 ?
Click to expand...
Click to collapse
Yes it will work on both Nokia 6.1 and 7.
hikari_calyx said:
Yes it will work on both Nokia 6.1 and 7.
Click to expand...
Click to collapse
Thank you
Hello, EveryoneMy Nokia 6.1 2018 Hmd Global TA-1054 with Build number - 00WW_3_270 will receive a global system update and security update. Will this method described above work for me? So you will get a global version of version 10 or have to wait. My latest security fix for Android is from October 1, 2018. Can you explain in detail what steps to take to make the updates.
I posted this in the appropriate forum but this phone is so old I've not received any response.
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help. Even installed everything in the root directory on my hard drive - no help
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone before. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Things I have not tried yet:
Another computer
Tested fastboot command on one of my other phones
Any help is appreciated.
theandies said:
I posted this in the appropriate forum but this phone is so old I've not received any response.
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help. Even installed everything in the root directory on my hard drive - no help
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone before. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Things I have not tried yet:
Another computer
Tested fastboot command on one of my other phones
Any help is appreciated.
Click to expand...
Click to collapse
The process to unlock a moto phone is a bit different. OEM commands are as it says, defined by the OEM. They need to be precise and functional. The command:
Code:
fastboot oem unlock
alone will not work.
Step1:
Instead, You should enter:
Code:
fastboot oem get_unlock_data
You will get an unique 131 ID string that looks for example like this:
Code:
(bootloader) 0000000000000000000000000000001
(bootloader) 0000000000000000000000000000002
(bootloader) 0000000000000000000000000000003
(bootloader) 0000000000000000000000000000004
(bootloader) 0000005
Copy the output to a text editor and delete the (bootloader) and the spaces in between, so it's one whole string.
Step2:
Visit the official Moto unlock website. Sign-in with your account, you will be using the E-mail used to create said account to receive the unlock key. Paste the edited 131 ID string and click Can my device be unlocked? button. If it is unlockable, then a conformation page will appear asking for consent and warranty bla bla bla.... Just read it and accept.
Step3:
When you click unlock, you will receive a KEY through your E-mail attached to the moto account used. Save that E-mail somewhere offline, as it can be used to re-unlock the bootloader in the future if you relock it. Connect your device in fastboot again and type:
Code:
fastboot oem unlock KEY
Where KEY is the one you got in the E-mail.
Done!!! Enjoy your freedom , also check the mark near my answer if it solved your question so others don't have to search for long.
Thanks for your reply. Yes I wrote the fastboot command wrong in my post.
The problem I'm having is even when using the fastboot command you posted I still get "access denied" when using fastboot commands. ADB works fine allowing me to reboot into the bootloader through the command prompt/USB as in ADB devices.
theandies said:
Thanks for your reply. Yes I wrote the fastboot command wrong in my post.
The problem I'm having is even when using the fastboot command you posted I still get "access denied" when using fastboot commands. ADB works fine allowing me to reboot into the bootloader through the command prompt/USB as in ADB devices.
Click to expand...
Click to collapse
As long as in Android -> Settings -> Developer options the option "OEM unlock" isn't got enabled - and phone got rebooted afterwards - you receive the reported error.
OEM unlocking is turned on in developer settings
I'll post up some screenshots soon. Right now I'm on day three of work on the 12 hour night shift.
I have a TCL 10 Pro, and like a small group of others, we'd like our bootloaders unlocked. We have OEM Unlock in our Developer settings, and if you do
Code:
fastboot oem device-info
It does show device lock status false. I was wondering if there's a list of obscure/lesser known bootloader unlock commands anyone knows/has that I could try?
We've tried the standard oem unlock, flashing unlock, device unlock, etc.
What Fastboot commands are supported on an Android device depends on its OEM, means how Fastboot is implemented differs.
Hence do a Google search for supported Fastboot commands on mentioned device.
Hi, i am loading booting to bootloader from adb with commnad (adb reboot bootloader) this isnt working, only restart its instantly switch to normal os, any ideas ?
Run
Code:
adb reboot
or
Code:
fastboot reboot
oh sorry man, i am idiot, and i am say it wrong.. I trying boot to fastboot but not working instantly switch to os, any ideas please ?
Unlock bootloader if not done yet.
where i unlock bootloader ? In developer settings ? (i have unlocked)
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
xXx yYy said:
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
Click to expand...
Click to collapse
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Matyas66055 said:
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Click to expand...
Click to collapse
I have new thread, where i am writing all info :/ https://forum.xda-developers.com/t/zte-blade-a7-2019-fastboot-mode-missing.4462035/
I don't know if you are still interested in accessing Fastboot but you can access it using a specific firmware version.
Still, let me tell you that unlocking the bootloader is virtually impossible. Since the well-known generic method doesn't work for the SoC SC9863A, you need to have a special Fastboot's program version and a dedicated private key that only they provide.... and I emphasize the word "dedicated" since apparently ZTE did not use a generic key to sign their ROMS. At least on this device.
Unless they decide to release the key or give support to unlocking the bootloader, all we can do is wait for them to change their minds. Because they don't want to provide it. I know because I tried to order it several times.
i lost all my serial numbers after flashing stock rom nokia 3 ta-1032
now when i try to unlock bootloader which requires the serial number, and i lost that.
'fastboot oem key SERIAL_MD5_HASHED'
its not on the box either, only sim1 imei and sim2 imei thats all.
so now i cant unlock it.
when i do fastboot devices i get
fastboot devices
0123456789ABCDEF fastboot
so please tell me how to fix this issue
What returned by cmd fastboot devices is the serialnumber.
jwoegerbauer said:
What returned by cmd fastboot devices is the serialnumber.
Click to expand...
Click to collapse
That's common knowledge. I'm talking about that I need to flash a new Serial Number onto the device as I am unable to unlock the bootloader now.