Oukitel WP5 Pro

Search This thread

alexshestakov

Member
Mar 25, 2017
11
0
Motorola Defy (2021)
Новый точечный рисунок1.jpg
Новый точечный рисунок2.jpg
Новый точечный рисунок.jpg
 

alexshestakov

Member
Mar 25, 2017
11
0
Motorola Defy (2021)
.

You have a com port conflict. Do you have a USB adapter with several USB connectors in it?.

Message you received, says that you have several usb adapters in the same port, which creates address conflict.Try the other USB ports on the computer. What version of Windows do you have installed?.

.
Thank you for your help. I have an old Lenovo g550 laptop on it with three operating systems win 7 ultim x64, win 10 home edition x64, Ubuntu x64 last build, I use the last working USB port, the other two are not working. Today I plan to disassemble the laptop and replace non-working USB connectors. To the desire of other PC, I do not have (.
 

SwedishForenger

Senior Member
Mar 26, 2021
266
49
Thank you for your help. I have an old Lenovo g550 laptop on it with three operating systems win 7 ultim x64, win 10 home edition x64, Ubuntu x64 last build, I use the last working USB port, the other two are not working. Today I plan to disassemble the laptop and replace non-working USB connectors. To the desire of other PC, I do not have (.
-

It doesn't exist! (Some port not working)
You literally have to desolder the USB port from the motherboard to get this message ....
However ... Old computers have a drawback, running multiple OS...
The computer 'DOS system' bootloader' recognize the different BOOT.ini files--Windows/Linux Etc..some of your ports are told not to start ,In this BIOIS tell's the computer to give power to different part of you motherboard: like your USB com ports ... Update your BIOS or install ONE OS...

IF your running windows, and get a com port conflict... Just change the port number!.

1.png


2.png


3.png
.
 
Last edited:

alexshestakov

Member
Mar 25, 2017
11
0
Motorola Defy (2021)
-

It doesn't exist! (Some port not working)
You literally have to desolder the USB port from the motherboard to get this message ....
However ... Old computers have a drawback, running multiple OS...
The computer 'DOS system' bootloader' recognize the different BOOT.ini files--Windows/Linux Etc..some of your ports are told not to start ,In this BIOIS tell's the computer to give power to different part of you motherboard: like your USB com ports ... Update your BIOS or install ONE OS...

IF your running windows, and get a com port conflict... Just change the port number!.

.
I physically replaced one of the broken usb in my nutbook, deleted all the drivers and devices, and installed them again, and got the result, I managed to send the phone firmware V11 via SP_MDT_AFterSale_20.32, but the problem of red text and getting OTA updates did not solve it, when trying to flash the phone through RomVerify_SP_MDT_v3.1944.00.03_20200611 after scanning the ports and pressing the button "Start ALL" appears a window with a running string and % reaches 8% and disappears, after nothing happens.

I think I understand why, probably it is because the serial number of my device 0123456789ABCDEF, that is, at the first failed firmware I erased not only the IMEI but also the serial number of the device.
I suppose that’s why I can’t upgrade my device by air and via RomVerify_SP_MDT.

If so, can you tell me how to recover the serial number?
Screenshot_20220629-222504.png
 

SwedishForenger

Senior Member
Mar 26, 2021
266
49
I physically replaced one of the broken usb in my nutbook, deleted all the drivers and devices, and installed them again, and got the result, I managed to send the phone firmware V11 via SP_MDT_AFterSale_20.32, but the problem of red text and getting OTA updates did not solve it, when trying to flash the phone through RomVerify_SP_MDT_v3.1944.00.03_20200611 after scanning the ports and pressing the button "Start ALL" appears a window with a running string and % reaches 8% and disappears, after nothing happens.

I think I understand why, probably it is because the serial number of my device 0123456789ABCDEF, that is, at the first failed firmware I erased not only the IMEI but also the serial number of the device.
I suppose that’s why I can’t upgrade my device by air and via RomVerify_SP_MDT.

If so, can you tell me how to recover the serial number?View attachment 5648843
.


.
 

SwedishForenger

Senior Member
Mar 26, 2021
266
49
.

For anyone who has Magisk installed... !
This is a firewall ....

11.png


12.png
 

Attachments

  • Firewall4Magisk-v1.0.2.zip
    6.2 KB · Views: 1
Last edited:

cnxphysics

New member
Aug 7, 2022
1
0
Hello everybody,
These are the steps I did to install /e/os. Apologies for long post.

1. I had stock firmware v5 but it was not updating. It only returned 'you have latest version'.
2. I decided to install v11 hoping it would update to v15.
3. I wrote down the imei numbers.
4. Used windows 10. Did not work on MX Linux.
5. I used SPTools instructions from post #652: I turned the phone off, connected the phone to laptop and hit the download button. Once the 'success' was shown the phone booted to v11.
6. Did some basic setup such as wi-fi connect but not google sign-in. Enabled oem and usb debugging.
7. v11 not updating, just like v5.
8. Went to link for /e/os shown on post #348 and downloaded /e/os 1.2-q
9. Changed name to GSI.
10. Opened folder of Android Installer and then opened terminal inside the folder.
11. It did not work. Tried with Install Android it did not work.
12. Powered phone of then Volume+ and power button and selected 'fastboot'.
13. Opened bat file in a text editor to view file - commands also shown in post #697
14. Whilst in fastboot mode I each command one after another till the end (gave consent on phone when asked).
15. Phone booted to /e/os 1.2-q but had 'lost' imei - no connection to provider and no call.
16. Repeated with SPTool to re-install stock firmware v11. Booted to phone, enabled oem and usb debugging. after basic setup. No imei.
16. Used SN Writer instructions shown on post #652. Powered phone off . Started SPTools and connected phone to lap top. Booted: with imei restored.
17. Downloaded /e/os 1.1-q (changed to GSI) and repeated steps 12-14: successfully booted to /e/os with imei numbers present. TWRP installed as well.

Biggest challenge was to find the right procedure.

I would like to thank SwedishForenger and all others for your posts. I would have not been able to install custom rom without you all. Your contributions have been invaluable.

Best.
cnxphysics
 

2mkl

Senior Member
Jan 2, 2011
166
20
7. v11 not updating, just like v5.
Hi!
Oukitel removed updates via OTA. They also removed android 11 from the download center.
But you can to do updates from microSD (posts #506 and #507)

One more news....
I still have the firmware with stock A11 and lopestom made a fully working TWRP. Completely disable encryption.
You can install new versions of Magisk, to do backup data and so on...
I don't have time to check GSI on A11 right now (I'm trying to extract stock software on Bison Pro and install it on GSI)
 

Attachments

  • Screenshot_20210917-102141.png
    Screenshot_20210917-102141.png
    77.2 KB · Views: 7
  • Screenshot_20210917-102231.png
    Screenshot_20210917-102231.png
    77.6 KB · Views: 8
  • Screenshot_2021-09-17-02-23-47.png
    Screenshot_2021-09-17-02-23-47.png
    65.5 KB · Views: 8
  • Screenshot_2021-09-17-02-24-12.png
    Screenshot_2021-09-17-02-24-12.png
    50.6 KB · Views: 9

SwedishForenger

Senior Member
Mar 26, 2021
266
49
Hi!
Oukitel removed updates via OTA. They also removed android 11 from the download center.
But you can to do updates from microSD (posts #506 and #507)

One more news....
I still have the firmware with stock A11 and lopestom made a fully working TWRP. Completely disable encryption.
You can install new versions of Magisk, to do backup data and so on...
I don't have time to check GSI on A11 right now (I'm trying to extract stock software on Bison Pro and install it on GSI)
.

Can you upload the twrp file or a link to the file please.

.
 

2mkl

Senior Member
Jan 2, 2011
166
20
Ok.
Some Features:
TWRP is installed only after removing the stock recovery - /vendor/ect/recovery.img
there is a ready-made vendor with encryption disabled and stock recovery removed. Flash via fastbootd
After installation TWRP , do not forget to format the data using yes
Later I will give links to the firmware and mod vendor. Be patient......
 

Attachments

  • recovery-WP5_Pro_EEA_R-A11-20220806-FtD.zip
    28.1 MB · Views: 6
  • Like
Reactions: SwedishForenger

SwedishForenger

Senior Member
Mar 26, 2021
266
49
Ok.
Some Features:
TWRP is installed only after removing the stock recovery - /vendor/ect/recovery.img
there is a ready-made vendor with encryption disabled and stock recovery removed. Flash via fastbootd
After installation TWRP , do not forget to format the data using yes
Later I will give links to the firmware and mod vendor. Be patient......
.

It worked perfectly. Thank you very much for your contribution to this forum.

.
 

2mkl

Senior Member
Jan 2, 2011
166
20
Everything is done at your own peril and risk. If you're not sure, don't do it. I am not responsible for your phone
FW A11
Instruction.
1. You must flash FW
2. Unlock your phone
3. Enable USB Debugging
4. Use platform-tools ( in this folder you must have vendor_ModEnc.img, vbmetaAndroidSC_mod.img and recovery-WP5_Pro_EEA_R-A11-20220806-FtD.img)
5. Reboot your phone to fastboot
6. Via platform tools
Code:
fastboot --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vendor vendor_ModEnc.img
fastboot reboot bootloader
fastboot erase userdata
fastboot reboot
7. Set up the phone. (in the security section, we see that encryption is disabled)
8. Flash TWRP via platform tools
Code:
fastboot --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
fastboot flash recovery recovery-WP5_Pro_EEA_R-A11-20220806-FtD.img
fastboot reboot recovery
9. In TWRP - WIPE - Format data - yes
10. Reboot your phone and setup
..........
PROFIT

If I missed or made a mistake, please correct me.
 

Attachments

  • vendor_ModEnc.rar
    167.9 MB · Views: 6
  • vbmetaAndroidSC_mod.rar
    2.4 KB · Views: 3

SwedishForenger

Senior Member
Mar 26, 2021
266
49
Everything is done at your own peril and risk. If you're not sure, don't do it. I am not responsible for your phone
FW A11
Instruction.
1. You must flash FW
2. Unlock your phone
3. Enable USB Debugging
4. Use platform-tools ( in this folder you must have vendor_ModEnc.img, vbmetaAndroidSC_mod.img and recovery-WP5_Pro_EEA_R-A11-20220806-FtD.img)
5. Reboot your phone to fastboot
6. Via platform tools
Code:
fastboot --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vendor vendor_ModEnc.img
fastboot reboot bootloader
fastboot erase userdata
fastboot reboot
7. Set up the phone. (in the security section, we see that encryption is disabled)
8. Flash TWRP via platform tools
Code:
fastboot --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
fastboot flash recovery recovery-WP5_Pro_EEA_R-A11-20220806-FtD.img
fastboot reboot recovery
9. In TWRP - WIPE - Format data - yes
10. Reboot your phone and setup
..........
PROFIT

If I missed or made a mistake, please correct me.
.

I am sorry to say that vendor_ModEnc.me which is the file that deletes your phone system encryption is corrupt. Flashing this file on to your phone will send the phone into permanent fastboot.

.
 

2mkl

Senior Member
Jan 2, 2011
166
20
vendor_ModEnc.me which is the file that deletes your phone system encryption is corrupt
Try to do it differently.
Install the system, unlock, install magisk. Through the root explorer, remove the stock recovery, install TWRP reboot to TWRP. In TWRP -Reboot - Fastboot. Check fastbootd - fastboot devices. If all ok in platform tools -
fastboot flash vendor vendor_Encryptable.img
You must seen like this

D:\Program Android\platform-tools>fastboot devices
OukWP5proxxxxxx fastboot

D:\Program Android\platform-tools>fastboot flash vendor vendor_Encryptable.img
Invalid sparse file format at header magic
Resizing 'vendor_a' OKAY [ 0.008s]
Sending sparse 'vendor_a' 1/2 (262125 KB) OKAY [ 21.909s]
Writing 'vendor_a' OKAY [ 1.920s]
Sending sparse 'vendor_a' 2/2 (243181 KB) OKAY [ 18.331s]
Writing 'vendor_a' OKAY [ 1.761s]
Finished. Total time: 297.665s
Then in TWRP - Reboot Recovery and in TWRP - FORMAT DATA via yes
Just when you deal with two phones at once, you start to forget what you did on each ...
I will reinstall everything on a new one and then I will rewrite the instructions
P.S.. All files are working and screenshots, what happens I posted. But the instructions may not be accurate.
 
Last edited:

SwedishForenger

Senior Member
Mar 26, 2021
266
49
Try to do it differently.
Install the system, unlock, install magisk. Through the root explorer, remove the stock recovery, install TWRP reboot to TWRP. In TWRP -Reboot - Fastboot. Check fastbootd - fastboot devices. If all ok in platform tools -
fastboot flash vendor vendor_Encryptable.img
You must seen like this

D:\Program Android\platform-tools>fastboot devices
OukWP5proxxxxxx fastboot

D:\Program Android\platform-tools>fastboot flash vendor vendor_Encryptable.img
Invalid sparse file format at header magic
Resizing 'vendor_a' OKAY [ 0.008s]
Sending sparse 'vendor_a' 1/2 (262125 KB) OKAY [ 21.909s]
Writing 'vendor_a' OKAY [ 1.920s]
Sending sparse 'vendor_a' 2/2 (243181 KB) OKAY [ 18.331s]
Writing 'vendor_a' OKAY [ 1.761s]
Finished. Total time: 297.665s
Then in TWRP - Reboot Recovery and in TWRP - FORMAT DATA via yes
Just when you deal with two phones at once, you start to forget what you did on each ...
I will reinstall everything on a new one and then I will rewrite the instructions
P.S.. All files are working and screenshots, what happens I posted. But the instructions may not be accurate.
.

Thank you my friend. I'll look into it

.

Update:

Nope ... still boot lope

.
 
Last edited:

2mkl

Senior Member
Jan 2, 2011
166
20
Nope ... still boot lope
Ok...
Let's go the long way...

First you need to install TWRP. It won't install unless you remove the stock recovery. Therefore, /vendor/ect/ recovery.img is deleted.
Then you need to remove the encryption. To do this, you need to edit fstab.
In /vendor/etc/fstab.mt6765 you need change fileencryption=aes-256-xts:aes-256-cts:v2,keydirectory=/metadata/vold/metadata_encryption=> encryptable=/dev/block/platform/bootdevice/by-name/userdata
In vendor_Encryptable.img changed only fstab.mt6765 and deleted recovery.img.
I give another link to vendor_Encryptable.img (in 7z) vendor_mod
P.S. When I manually edited fstab, for some reason it didn’t save after a reboot. Therefore, we made a copy of the edited vendor and then everything worked...
system, product, vendor you need flash only via fastbootd
P.P.S.If you remember, I do not cheat and if I give something, then it is 100% tested and works. If something goes wrong, then you need to pay attention to your phone.
Have a good day!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Ok.
    Some Features:
    TWRP is installed only after removing the stock recovery - /vendor/ect/recovery.img
    there is a ready-made vendor with encryption disabled and stock recovery removed. Flash via fastbootd
    After installation TWRP , do not forget to format the data using yes
    Later I will give links to the firmware and mod vendor. Be patient......
  • 4
    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