Oukitel WP5 Pro

Search This thread

2mkl

Senior Member
Jan 2, 2011
160
19
The answer is very simple - just another magisk...
 

Attachments

  • Screenshot_20220115-185749.png
    Screenshot_20220115-185749.png
    133.1 KB · Views: 18

2mkl

Senior Member
Jan 2, 2011
160
19
IMHO. mtk client is a mixture of SPFT and TWRP for Linux.
But you have to be careful, the "debuging mode" inscription says that you ruined the NVRAM
 

Toutlibre

Senior Member
Jan 1, 2022
121
13
The boot.img that's been created from V15 with Bkeler's program then Magisk and Magisk_patched.img.
But at this point it seems even worse than before when I'm looking to get some access throught the terminal.
Well I tried, sorry
 

Attachments

  • magisk_patched.img
    32 MB · Views: 1
  • boot.img
    32 MB · Views: 1
  • Magisk-558710bb-alpha-2(23016).apk
    10 MB · Views: 3

Toutlibre

Senior Member
Jan 1, 2022
121
13
One thing not excluded is, I could have missused this program (while I didn't get any error message during process).
Available for Linux and Microsoft too, not to promote but trying to find by this way or another kind of solutions.
 

2mkl

Senior Member
Jan 2, 2011
160
19
No problem!
We must try different options. I am a research engineer by training. We were lectured for two semesters on the design of an experiment (task - not sure what to do - result). It is necessary to choose the most optimal algorithm of our actions. I think it makes no sense to fight Gogle, but go around. In the beginning, we need to understand where the manufacturer has put his protection and try to get rid of it. Next will be easier...
About debuging mode. Yes, I can be wrong about nvram, but this suggests that some partitions are overwritten and oukitel now knows about it...
 

Toutlibre

Senior Member
Jan 1, 2022
121
13
No problem!
We must try different options. I am a research engineer by training. We were lectured for two semesters on the design of an experiment (task - not sure what to do - result). It is necessary to choose the most optimal algorithm of our actions. I think it makes no sense to fight Gogle, but go around. In the beginning, we need to understand where the manufacturer has put his protection and try to get rid of it. Next will be easier...
About debuging mode. Yes, I can be wrong about nvram, but this suggests that some partitions are overwritten and oukitel now knows about it...

- I'm autodidact on computing, english written&spoken too (put pa sat thai lit noï, mak mak mai dai). Decided when I was over 40 years old to enter at University (French Litturgy) just by challenging myself, to prove nothing finally that I only love to be outdoor and Landscaper & Photographer were my great choices since the beginning.
Then I bought 1 Oukitel wp-5 Pro ...
 
Last edited:
  • Like
Reactions: jon2021

2mkl

Senior Member
Jan 2, 2011
160
19
Hi!
Since we have problems with the sim card when doing a read-write system partition, our friend suggested doing this search

"Did you guys check in one of your init*.rc scripts why sim card makes problems when phone is booted as RW with fstab? Maybe sim card itself is mounted as ro or something? and this causes conflicts with rw in fstab? It must be something simple like that.

To search your init scripts for certain keyword you can try this code:

Bash:
adb shell
su

for a in /etc/init/ \
/etc/init/hw/ \
/system/etc/init/hw/ \
/system/etc/init/ \
/product/etc/init/ \
/product/etc/init/hw/ \
/vendor/etc/init/ \
/vendor/etc/init/hw/; do cd $a; printf "\n\nChecking all files from %s\n\n" $a; grep -nr "sim" $a; done;

also manually check the init scripts in /, /product and /vendor and maybe /odm or whatever. If you check those paths with script it will crash or take forever..."
Does anyone want to do this?
 

Toutlibre

Senior Member
Jan 1, 2022
121
13
Hi!
Since we have problems with the sim card when doing a read-write system partition, our friend suggested doing this search

"Did you guys check in one of your init*.rc scripts why sim card makes problems when phone is booted as RW with fstab? Maybe sim card itself is mounted as ro or something? and this causes conflicts with rw in fstab? It must be something simple like that.

To search your init scripts for certain keyword you can try this code:

Bash:
adb shell
su

for a in /etc/init/ \
/etc/init/hw/ \
/system/etc/init/hw/ \
/system/etc/init/ \
/product/etc/init/ \
/product/etc/init/hw/ \
/vendor/etc/init/ \
/vendor/etc/init/hw/; do cd $a; printf "\n\nChecking all files from %s\n\n" $a; grep -nr "sim" $a; done;

also manually check the init scripts in /, /product and /vendor and maybe /odm or whatever. If you check those paths with script it will crash or take forever..."
Does anyone want to do this?
aheuaheuah ... not really ...
I installed back /e/ to experiment, this program didn't work at all showing errors throught the terminal.
it is really only to be used with stock rom.
Like you said Oukitel seen something happened when I dumped boot.img and vbmeta.img, pushed back pulled back with adb then used command lines below with this program
Code:
python3 mtk w boot,vbmeta boot.patched,vbmeta.img.empty

- My question is could we get at least with this program V15 version ready files so we don't have to update to it each time and which files should we dump and push to sdcard or whatever folder?
 

2mkl

Senior Member
Jan 2, 2011
160
19
I don't know how it happens in mtk client, but in spft you read the first megabyte of the EMMC_BOOT_1
and the first megabyte of the EMMC_USER. In the first - is the preloader, in the second - is the Table of sections (RPT).
Maybe the RPT is wrong?
I posted two files with ota updates. If you look at the checkroot file, it looks like the Chinese just check the checksums...
There is a possibility that their defense is built on this
 

Attachments

  • checkroot.txt
    17.6 KB · Views: 2

Toutlibre

Senior Member
Jan 1, 2022
121
13
I don't know how it happens in mtk client, but in spft you read the first megabyte of the EMMC_BOOT_1
and the first megabyte of the EMMC_USER. In the first - is the preloader, in the second - is the Table of sections (RPT).
Maybe the RPT is wrong?
I posted two files with ota updates. If you look at the checkroot file, it looks like the Chinese just check the checksums...
There is a possibility that their defense is built on this

- How can SPFT or MTKclient have at one given moment write access during process ? Is the Stock Rom allowing them ?
 

2mkl

Senior Member
Jan 2, 2011
160
19
Oh well.. even with that oukitel won't work on updates, they are quiet in late for this phone.
Of couse.
Now only a lazy Chinese does not release smartphones, but not many people have the required qualifications...
That's why the Project Treble was created (IMHO)
But we won't take oukitel seriously... They are not up to us
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    OK bro I'm going to try this after work and I'm going to write about the results. :)

    Edit 1: Unfortunately, the same story. I did everything like before and have GSI.img, using the script and this moment came... (Screenshot and picture below). It stuck at this place, OEM unlocked, USB debugging turn on. Third screen shows device menager after Oukitel went to "fastbootd"
    .

    You have a driver problem. Have you added the Oukitel driver as legacy hardware drivers?.
    fastbootd uses legacy drivers, and fastboot bootloader uses regular drivers.
    The install script works until fastbootd start, and now your computer don't have the drivers for communicating with your phone in fastbootd.

    Below you have all USB and Oukitel drivers. Download and Extract to desktop

    I don't remember exactly which ones I added as legacy drivers, but just add everything in I VCOM DRIVERS directory. then restart your computer and try running the Install script again.
    And if it doesn't work, just keep adding drivers from other folders as legacy until it works.

    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
    Add drivers. And REPEAT for adding more legacy drivers .....

    And don't forget to install them as regular drivers to, by double-clicking on them and clicking install.
    .
    1
    OK I installed /e/OS. I downloaded drivers which you enlosed to this post. @SwedishForenger thank you very much for your script. I am very grateful. Maybe after testing /e/ I will move to ROM with Android 12 later (^.^)
    .

    Glad I could help....
    There are many rums to choose from. Here is a list of roms which are updated periodically for your phone:


    .
  • 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
    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
    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