Question Oukitel WP5 Pro

Search This thread

SwedishForenger

Senior Member
Mar 26, 2021
466
104
Okay, I used

fastboot reboot-bootloader

instead of

fastboot reboot fastboot.

It came back in fastboot screen mode. Looks promising.

Should I just do this?
fastboot flash system GSI.img

Or should I continue with this script?
fastboot erase system fastboot delete-logical-partition product fastboot --disable-verity --disable-verification flash system GSI.img fastboot -w fastboot reboot bootloader fastboot erase userdata fastboot reboot
.

To be completely honest with you, I really don't know what Oukitel has done to their system since I flashed my phone a year ago. Obviously, the way we did it a year ago doesn't work, so your guess is as good as mine right now.

I edited my previous post, try it.

.
 
Jan 20, 2023
18
2
I really appreciate all the effort in helping you've given. But, unfortunately, it does not work:

fastboot delete-logical-partition product
$> .\fastboot delete-logical-partition product Deleting 'product' FAILED (remote: 'unknown command') fastboot: error: Command failed

fastboot --disable-verity --disable-verification flash system GSI.img
$> .\fastboot flash system GSI.img Invalid sparse file format at header magic Sending sparse 'system' 1/21 (130676 KB) OKAY [ 3.180s] Writing 'system' FAILED (remote: 'This partition doesn't exist') fastboot: error: Command failed

Some insights I'd like to share:
I flashed GSI into "super" partition instead "system" partition. It flashed, but it did not work. Why "super" partition?

1)I found via adb shell (cat /proc/partitions) there is not a system partition, but there is a "super partition". This checks with the idea that, when V11 stock is being flashed via SP Tool, the "super" partition is flashed, not "system". ("IsDownload = FALSE" in Scatter file).

2)Googling a bit I found this "super" partition actually holds system, product and vendor images and there's a way to extract this image, and encapsule it back but I believe I'need to read a bit before doing any further.

Once again, thanks for your help.
 

SwedishForenger

Senior Member
Mar 26, 2021
466
104
I really appreciate all the effort in helping you've given. But, unfortunately, it does not work:

fastboot delete-logical-partition product
$> .\fastboot delete-logical-partition product Deleting 'product' FAILED (remote: 'unknown command') fastboot: error: Command failed

fastboot --disable-verity --disable-verification flash system GSI.img
$> .\fastboot flash system GSI.img Invalid sparse file format at header magic Sending sparse 'system' 1/21 (130676 KB) OKAY [ 3.180s] Writing 'system' FAILED (remote: 'This partition doesn't exist') fastboot: error: Command failed

Some insights I'd like to share:
I flashed GSI into "super" partition instead "system" partition. It flashed, but it did not work. Why "super" partition?

1)I found via adb shell (cat /proc/partitions) there is not a system partition, but there is a "super partition". This checks with the idea that, when V11 stock is being flashed via SP Tool, the "super" partition is flashed, not "system". ("IsDownload = FALSE" in Scatter file).

2)Googling a bit I found this "super" partition actually holds system, product and vendor images and there's a way to extract this image, and encapsule it back but I believe I'need to read a bit before doing any further.

Once again, thanks for your help.
.

Unfortunately, I don't have access to my Wp5 pro here, so I can't download, flash and compare the difference between previous and current stock firmware builds. But there have definitely been changes. But when you find a way to flash GSI on you phone, please post a little manual on how to, for othersto follow.

.
 
Jan 20, 2023
18
2
Thanks man. I managed do to it.

fastbootd got access for userspace. fastboot can't. if we try to delete, flash, or even check, it says it does not exist, right?

When in fastbootd I sent a command "fastboot getvar is-userspace". Windows couldn't send any command. It was <waiting on device>.

Your script halted because my Windows drivers were partially installed! Windows can communicate via ADB and fastboot, but not with fastbootd. It seems I got drivers for adb, fastboot, but not for fastbootd.

I decided to try on Linux, then checked with: "fastboot getvar is-userspace"
is-userspace: yes Finished. Total time: 0.001s

YES!!! It communicates with fastbootd! Later, I checked the existence of "system" and "product" partitions, they exist!

fastboot getvar is-logical:system fastboot getvar is-logical:product

Since these partitions now "exist" at fastboot's eyes, it can now delete. I did everything on Linux. Many, many thanks!


EDIT: LineageOS 20 (Android 13) it out of question for daily usage. Very, very slow.
 
Last edited:

SwedishForenger

Senior Member
Mar 26, 2021
466
104
Thanks man. I managed do to it.

fastbootd got access for userspace. fastboot can't. if we try to delete, flash, or even check, it says it does not exist, right?

When in fastbootd I sent a command "fastboot getvar is-userspace". Windows couldn't send any command. It was <waiting on device>.

Your script halted because my Windows drivers are partially installed! Windows couldn't communicate with ADB and fastboot, but not with fastbootd. It seems I got drivers for adb, fastboot, but not for fastbootd.

I went to Linux, then checked with: "fastboot getvar is-userspace"
is-userspace: yes Finished. Total time: 0.001s

YES!!! It is userspace! Later, I checked the existence of "system" and "product" partitions, they exist!

fastboot getvar is-logical:system fastboot getvar is-logical:product

Since these partitions now "exist" at fastboot's eyes, it can now delete. I did everything on Linux. Many, many thanks!


EDIT: LineageOS 20 (Android 13) it out of question for daily usage. Very, very slow.
.

Glad to hear it was just your drivers. If you don't follow these guides on Installing ADB on Windows and installing Legacy drivers and IMEI recovery . It can lead to errors.

If I remember correctly, I have Android 12.1 GSI on my WP5 Pros. If you google: GSI arm64 ab 12.1, should bring up a bunch of Android 12 GSI builds you can try.

Don't forget to reset your IMEI numbers after 'formatting and flashing Stock firmware, BEFORE flashing GSI. it's a tough lesson to flash GSI, make a lot of changes and settings, and then when you think everything is finished and done. It turns out that you forgot to reset the IMEI, and now you can't make calls or send sms. And have to start all over again.

Best of luck with your new phone my frend. And don't be shy to ask if you need help.

.
 
Jan 20, 2023
18
2
Best of luck with your new phone my frend. And don't be shy to ask if you need help.

May my experience serve as example for other users who might try in future.

I'm using Pixel Experience 11. It's as fast as the de-bloated stock ROM.

LineageOS 17.1 seemed the best imo, very responsive, and I'm used with the LineageOS. I removed it because I was not able to install Gapps or Magisk.
 

SwedishForenger

Senior Member
Mar 26, 2021
466
104
May my experience serve as example for other users who might try in future.

I'm using Pixel Experience 11. It's as fast as the de-bloated stock ROM.

LineageOS 17.1 seemed the best imo, very responsive, and I'm used with the LineageOS. I removed it because I was not able to install Gapps or Magisk.
.

It should be no problem runing everything from Android 13 and below on this phone, although some GSIs with very nice layouts and large animations need a reboot or two before everything is loaded into memory, and becom fast and responsive.

When it comes to lineage 17 to 20, there are definitely no problems on this phone I have tested. But to find the right GSI for your needs, you need to look at the designation of the different GSIs.

b = a/b and v = vanilla (no gapps included) and S = superuser included

That means you tried to use a 'Vanilla' version, with 'superuser' pre-installed, which prevents the installation of MAGISK, when SU already exists with in the GSI.

You probably need to download and flash 'bgn' version. It comes preinstall with gapps, and you can install Magisk and everything else you want on your phone.

2023-02-09_10-33.png

___________________________________________

b = a/b
a = a-only

g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)

N = no superuser
S = superuser included

The most suitable GSI ROM for Oukitel WP5 Pro:
Requires A/B ROM instalation file type and Android 10 and up.
Suitable are files with key "arm64-bgN" or "arm64-bgS" in filename. "g" if you want use Google APPS.
b = a/b
g = gapps
N = no superuser
S = superuser included
______________________________________________

And of course to tweak the GSI according to your needs:

.
 
Last edited:

nomexcze

Member
Mar 27, 2021
21
0
Greetings!
At fist, I would like to thanks SwedishForenger for his very good job here for WP5 pro community.
I installed that Pixel Android 13, just with bat file. Smooth.
I have feeling that Android 13 is not so fast on this WP5pro. If I will go for android 12, will it be better? If yes, could you recommend good image (prefer stock android 12), because of some work tools (Intune) I need to have atlest 12.
Thanks
EDIT: Intune recognized this phone is rooted, is possible to unroot? (Already fixed by OTA update)
 
Last edited:

2mkl

Senior Member
Jan 2, 2011
175
20
N = no superuser
S = superuser included
Hi!
There is also Z. This is a switchable SU. It fits too
Yes, they gave me a backup. Only I have to remove the nvram. I think you understand that there is data from another phone and I cannot give it away. Hope you have your nvram. When flashing, use download only and uncheck nvram.
I'll try to post a link tomorrow.
Firmware - V14_20221010
 
Jan 20, 2023
18
2
.

It should be no problem runing everything from Android 13 and below on this phone, although some GSIs with very nice layouts and large animations need a reboot or two before everything is loaded into memory, and becom fast and responsive.

.

I thought the performace would stay that slow. It was really slow for my standards, slower than OEM.

Well... I'll install them again and wait the ROM accomodate better.
 

SwedishForenger

Senior Member
Mar 26, 2021
466
104
Greetings!
At fist, I would like to thanks SwedishForenger for his very good job here for WP5 pro community.
I installed that Pixel Android 13, just with bat file. Smooth.
I have feeling that Android 13 is not so fast on this WP5pro. If I will go for android 12, will it be better? If yes, could you recommend good image (prefer stock android 12), because of some work tools (Intune) I need to have atlest 12.
Thanks
EDIT: Intune recognized this phone is rooted, is possible to unroot? (Already fixed by OTA update)
.

HIDING ROOT from apps. Magisk 25.2​

If you're rooted through Magisk, you can now hide your root from different apps.
Start by deleting 'Storage and 'Cache for the apps you want to hide root for.

1.png
2.png


HIDING ROOT :​

1. Open your Magisk Manager app and go into the settings.

1.png


Scroll down and toggle 'Zygisk and 'Deny List.

2.png

Now Open the 'Configure Deny list' and check the apps you want to hide Root for.
In my case, my banking apps didn't work.

3.png

Reboot the phone .....
.
 

Attachments

  • Magisk-v25.2.apk
    10.8 MB · Views: 15
Last edited:

Eloqnam

Member
Jan 20, 2018
14
1
Hi!
There is also Z. This is a switchable SU. It fits too

Yes, they gave me a backup. Only I have to remove the nvram. I think you understand that there is data from another phone and I cannot give it away. Hope you have your nvram. When flashing, use download only and uncheck nvram.
I'll try to post a link tomorrow.
Firmware - V14_20221010

thank you, awaiting for the backup to test on my devices.
thanks for the info with the nvram.
 

Eloqnam

Member
Jan 20, 2018
14
1
failed on two flash tools:
See Screenshots.

Idea what i can do to disable Verified Boot?
without access to the screen.



edit: only changing the md1 to "md1img-verified.img" from the Android 10 Stock ROM.
will give me a Success while flashing, but Device is Stuck at "Red State"

(But the Screen does work!! i can see again :) but not boot anymore )
 

Attachments

  • failed 2.png
    failed 2.png
    21.6 KB · Views: 30
  • failed.png
    failed.png
    2.7 KB · Views: 33
Last edited:

2mkl

Senior Member
Jan 2, 2011
175
20
failed on two flash tools:
See Screenshots.

Idea what i can do to disable Verified Boot?
without access to the screen.



edit: only changing the md1 to "md1img-verified.img" from the Android 10 Stock ROM.
will give me a Success while flashing, but Device is Stuck at "Red State"

(But the Screen does work!! i can see again :) but not boot anymore )
Hi!
This happens pretty often. This is a backup. If something is not flashed - uncheck.
You have a model with a new screen, so the drivers with this firmware came up
You need to somehow unlock the bootloader.
You can not mix files from A10 and A11
Don't use format All + - you will lose nvram
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Hi all... Until we get ROOT to this phone.

    I have been using WP5 Pro as my daily driver for 9 months now, and am super happy with it.
    However... After 3 months, the large 8000Ah battery didn't last as long as it should.
    So I opened it up in ADB :
    adb shell 'pm list packages -f' | sed -e 's/.*=//' | sort
    ore
    adb shell pm list packages
    and took a closer look at the pre installed crap on the phone. And I was shocked by all the unnecessary s*it i found. com.mediatek.atmwifimeta : Why is all my Wifi traffic logged and sent to a remote server !!!.

    To you who are interested in removing bloatware on your phone.
    I put together a list of crap you can delete without affecting your daily use of the phone.

    Just Copy & Paste in terminal and restart the phone.

    adb shell pm uninstall -k --user 0 com.ssui.chdmodel adb shell pm uninstall -k --user 0 com.android.companiondevicemanager adb shell pm uninstall -k --user 0 com.android.dynsystem adb shell pm uninstall -k --user 0 com.android.wallpaper.livepicker adb shell pm uninstall -k --user 0 com.google.android.apps.tachyon adb shell pm uninstall -k --user 0 com.google.android.apps.docs adb shell pm uninstall -k --user 0 com.google.android.apps.googleassistant adb shell pm uninstall -k --user 0 com.google.android.apps.wellbeing adb shell pm uninstall -k --user 0 com.google.android.apps.youtube.music adb shell pm uninstall -k --user 0 com.elephanttek.faceunlock adb shell pm uninstall -k --user 0 com.android.emergency adb shell pm uninstall -k --user 0 com.android.nfc adb shell pm uninstall -k --user 0 com.elephanttek.faceunlock adb shell pm uninstall -k --user 0 com.adups.privacypolicy adb shell pm uninstall -k --user 0 com.android.backupconfirm adb shell pm uninstall -k --user 0 com.adups.fota adb shell pm uninstall -k --user 0 com.android.bips adb shell pm uninstall -k --user 0 com.android.cts.ctsshim adb shell pm uninstall -k --user 0 com.android.cts.priv.ctsshim adb shell pm uninstall -k --user 0 com.android.localtransport adb shell pm uninstall -k --user 0 com.android.partnerbrowsercustomizations.example adb shell pm uninstall -k --user 0 com.android.printspooler adb shell pm uninstall -k --user 0 com.android.sharedstoragebackup adb shell pm uninstall -k --user 0 com.android.wallpaperbackup adb shell pm uninstall -k --user 0 com.debug.loggerui adb shell pm uninstall -k --user 0 com.android.traceur adb shell pm uninstall -k --user 0 com.android.htmlviewer adb shell pm uninstall -k --user 0 com.google.android.apps.restore adb shell pm uninstall -k --user 0 com.google.android.apps.restore adb shell pm uninstall -k --user 0 com.google.android.feedback adb shell pm uninstall -k --user 0 com.google.android.onetimeinitializer adb shell pm uninstall -k --user 0 com.google.android.gms.location.history adb shell pm uninstall -k --user 0 com.google.android.videos adb shell pm uninstall -k --user 0 com.mediatek.atmwifimeta adb shell pm uninstall -k --user 0 com.android.calllogbackup adb shell pm uninstall -k --user 0 com.ssui.setupwizard adb shell pm uninstall -k --user 0 com.ssui.sos

    You can Reinstall one or all apps again by putting:
    adb shell cmd package install-existing com.app name

    With USB Debugging enabled on your phone.....
    There is a lot to copy and paste, so I created a script that cleans your phone in 10 seconds from all this bloatware. Download it at the bottom of this post to your desktop, unzip it to your desktop, connect phone and double-click the Claning file.


    The default launcher on this phone is terrible. Here is a good alternative...
    Using Mod SMART LAUNCHER 5 PRO
    You can download it here: here.... here.... ore here..... just incase here too......

    photo_2021-03-26_04-47-14.jpgphoto_2021-03-26_04-47-19.jpgphoto_2021-03-26_04-48-57.jpg

    2.png
    3

    SOLUTION: DISSAPPEARING NOTIFICATIONS AFTER APPS UPDATES THROUGH THE GOOGLE STORE


    I do not understand what was the reason to make such a ****ty software by Oukitel, but finally i found a way to fix this. It was so annoying, when You have to check if notifications settings are all right every few days.

    Quick tutorial:
    1. You need root privileges. Installing Magisk was described some many times that i will skip this part.
    2. You need list of packages names for the apps, where You want to keep notifications settings all the time. You can obtain it for example through the shell:
    adb shell "pm list packages|cut -f 2 -d ":""
    You can also use some 3rd party app manager, which shows installed package names or check it via Google store. It does not matter.
    3. Now it is time to pull & edit /data/system/ssui_notification file.
    This is content of my ssui_notification:
    {packageName='com.ssui.keyguard', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=0, cornerSwitch=2, userOptSwitch=1, listType=1, status=1, userOperated=0}
    {packageName='com.ssui.launcher3', mainSwitch=0, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=0, cornerSwitch=2, userOptSwitch=1, listType=1, status=1, userOperated=0}
    {packageName='com.android.music', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=0, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
    *
    *
    *
    {packageName='com.twitter.android', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
    {packageName='com.android.email', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
    {packageName='com.linkedin.android', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}

    All You have to do is copy one line for example:
    {packageName='com.facebook.orca', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
    and past it on the bottom with changed package name:
    {packageName='YOUR.APP.PACKAGE.NAME', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
    This is example for Signal messenger:
    {packageName='org.thoughtcrime.securesms', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
    Repeat this for all apps with disappearing notifications and save the file.
    4. After that You have to overwrite stock ssui_notification with just modified file. If You can not do this because of permission denied error, try to first delete stock file and after that copy modified file to the /data/system. It works for me.
    5. Reboot your phone*
    * I do not know if it is necessary step, but i did it to make sure that it will work.

    Voila, your notifications should not disappear anymore after apps update. I have checked it on few apps and so far it works!

    Unfortunately, this is not the best solution and You have to repeat this procedure after installing new apps, but probably most of people do not install new apps very often. I think it will be not a problem to make easy script to add automatically every installed app to the ssui_notification file, but the best solution will be if we will find which exactly process is responsible for this and just kill it. Maybe somebody will find that.

    I hope that it will be helpful for the rest of frustrated Oukitel users ;) Good Luck!
    3
    Ok.
    You need the latest stock firmware (v15) with unlocked bootloader. Install all drivers.
    To unlock bootloader you need to do this:
    1. In setting - About Phone - tap several times on Build number (developer options)
    2. In Satting - System - Developer options set OEM unlocking and USB debbuging.
    Reboot to bootloader -Vol UP+ Power and select fastboot (Vol Up- select, Vol Down -confirmation)
    In platform-tools ( I copyed cmd.exe to this folder)
    Code:
    fastboot flashing unlock
    Code:
    fastboot flashing unlock_critical
    (Every time you need confirm with Vol UP)
    !WARNING! All data will be lost.
    Reboot to system.
    Repeat steps 1 and 2.
    Then we install GSI (with TWRP or without).
    Boot.img must be from stock firmware.
    You must have vbmetaAndroidSC_mod.img and Havoc-OS-v3.12-20201230-Official-GApps-arm64-ab.img in platform-tool folder.
    Link for Havos 3.12 - https://sourceforge.net/projects/havoc-os/files/arm64-ab/ ( second with Gapps). Extract img from zip.
    Reboot to fastboot.
    In fastboot mode
    Code:
    fastboot --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
    Code:
    fastboot -w
    Reboot to fastbootd
    Code:
    fastboot reboot fastboot
    In fastbootd
    Code:
    fastboot erase system
    Code:
    fastboot delete-logical-partition product
    Code:
    fastboot --disable-verity --disable-verification flash system Havoc-OS-v3.12-20201230-Official-GApps-arm64-ab.img
    Code:
    fastboot -w
    Return to normal fastboot
    Code:
    fastboot reboot bootloader
    In fastboot
    Code:
    fastboot erase userdata
    Code:
    fastboot reboot

    The system will boot in a few minutes
    But your phone won't have a Googl Play certificate.
    To fix this problem I did this:
    Install Magisk-v23.0.apk (disabled Check Updates and in Update Chanel set Custom Channel)
    Reflash boot.img to magisk_patched_boot.img by @xmucio
    In fastboot
    Code:
    fastboot flash boot magisk_patched_boot.img
    Code:
    fastboot --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
    In Magisk set MagiskHide.
    From Magisk repository I installed Riru, BusyBox, MagiskHide Props Config and manualy SafetyNet Fix 2.1.1 (via Install from storage). Then I dissabled all Googl apps (Play market and so on).
    With help from MagiskHide Props Config I made a substitution of the phone and installed the certificate.
    In Termix I done this:
    Code:
    su
    Code:
    props
    You will seen like on picture.
    At first I done 2 (Forse BASIC key attestation)
    2
    d - (pick value from device list)
    3 - (Ulefone, becouse I have it)
    All confirmed.
    Then I done 1 (Edit device fingerprint
    1
    f
    3 - Ulefone
    Then enabled Google apps
    SafetyNet passed. The device is certified.
    2
    OUKITEL IMEI recovery
    1,1.jpg
    Had trouble making calls after flashing the Oukitel firmware to the phone.
    and daild *#06# and discovered that I had lost my IMEI number, which is used to register my phone on the carrier network. Without an IMEI number, you can either call, text or surf the internet. So it's crucial that you restore that number. Here is a small guide on how to reset your IMEI number on ALL smart phones, As long as you have USB drivers for that specific phon.
    I will use Windows 10 in this example, as this is the most common operating system to date. If linux users want a guide too, send me a pm.
    Ok, that out of the way, let's begin....

    Drivers...
    Is the key component for your phone to communicate with a computer, and for communicating with the different chipsets in your phone.

    Oukitel uses Mediatek drivers and can be downloaded here..…
    Extract the folder to your desktop. You will need a copy of the OUKITEL firmware.

    Oukitel WP5 here... and Oukitel WP5 pro here...


    Right click on windows taskbar icon, and click on Device manager.

    1.png


    Click on Action and on Add legacy hardware.
    2.png


    Click on install ....
    3.png


    Click on Brows...
    5.png

    Go in to the Mediatek folder you downloaded earlier and double-click on the android driver.
    You can do this for one or all the drivers, and the drivers in the 64 folder to.
    Reboot the computer....

    Now it's time to fix the missing IMEI number issue....
    To make this job as easy as possible for us, we will use the SN Write Tool.
    There are a lot of versions and editions of this tool for different phones, but for WP5 and WP5 pro we use v1-1924 which can be downloaded here ....
    Ok, let's begin....

    Open the SN_Write_Tool_v1.2020.00 folder and open the SN_Writ program.
    6.png


    Click on System Config.
    0Ww25wWsuT.png


    Onely IMEI and Dule IMEI is checkt.
    Now we need to tell the program to retrieve all the necessary information about your phone from the firmware databases. Now click on the MD1_DB button, and go in to the download OUKITEL firmware folder and in to the database folder.

    7.png

    8.png


    Double click on the MDDB file. Go to the next button AP_DB and add the next database file APDB file. Click the SAVE button.
    9.png


    Now we are ready to write the IMEI number to the phone. Click on the STRT button.
    Now enter your IMEI number. If you have not written it down, you can find it on the packaging the phone came with. Turn off your phone and prepare the USB-c cable.
    11.png


    Ckick OK button , and plug the USB cable into the computer and phone and wait a few seconds. A small text is displayed on the phone screen at the bottom left.
    12.jpg


    The program will verify with the database, before writing the IMEI number to the phone, This may take up to 1 min. If the program finds errors in your IMEI number, you will receive an error message. you can check your number or click OK.
    13.png


    When everything is ready, you will get a green light from the program.
    14.png


    Restart the phone and you now have a new IMEI numbers.....
    1,2.jpg



    2
    Runing on old Android 10?

    WP5 pro are being shipped with Android 10 V3 and V4 version of the firmware.
    However, ther is a new release of Android 10 V5 available for this phone!.

    Android 10 V5 can be downloaded here

    And all the tools needed to make the upgrade possible, you can find it here
    If you are wondering if it is difficult to do the update, you can watch a video on how to do it in this tool folder to.

    photo_2021-04-02_13-28-28.jpg