Oukitel WP5 Pro

Search This thread
By:
Advanced…
candidosobrinhosa

candidosobrinhosa

Member
Jan 20, 2023
17
1
There was a time all my network traffic passed through TOR. I tried kept myself off-grid, not taking pictures, avoiding being recorded, but whenever I started a new job, WhatsApp was used for official message system, instead of e-mails, also problems while dating etc, so I thank for that. I'm linux user for more than 10 years, I'm aware of F-droid and FOSS principles.

But I prefer my device being tracked because of the theft scenario in my country, while able to retrieve it. 'Google Find My Device' will work until someone get my phone and fact reset it. I'd prefer to pay for a 5EUR that could assist on device tracking even after factory resetting the phone.

A more tech-savvy thief could perform a full cleanup reflashing the system, but I'd still pay for the price.
 
SwedishForenger

SwedishForenger

Senior Member
Mar 26, 2021
335
64
candidosobrinhosa said:
In Brazil theft is considered for major income for many less fortunate. You might be stolen anywhere; commonly, while commuting.

Most of them are savvy, they know how to format, to push systems via adb/fastboot, and I'd like to install Cerberus as a hidden system app.

If they do wipe via adb/fastboot I'll loose Cerberus, but most only perform factory reset to avoid overwork.

EDIT

@SwedishForenger , I've just found instruction steps for enabling to install Magisk in this older thread.

I am with build V11 20210518. Should I still follow that procedure or look somewhere else?
Click to expand...
Click to collapse
.

Yes it's still works, unless Oukitel has made some new updates that I don't know about.

Yes it's possible to install Cerberus Anti-thef as a system app. the problem if i remember correctly the last time i tested it, the settings i set for the app disappeared after the factory reset of the phone. The app was still there, but the settings were gone. Which made the app as a system app useless to begin with. It's been a while since I tested that app, it may be that they fixed this now. But please let us know about the results of the app's function after phone reset.
.
 
Last edited:
C

cnxphysics

Member
Aug 7, 2022
11
2
Hello,
I using LeOS-19.1 with my oukitel wp5 pro which works fine except I have to manually connect to home wifi (auto - connect has to be 'off').
If I install LeOS-20 or LeOS-T (both android 13) then it is not possible to connect with home wifi either manually or with auto-conect 'on'.
The LeOS telegram group has suggested adb shell settings put global restricted_networking_mode 0. It makes no difference to the above.

I was wondering if it is an oukitel issue rather than GSI issue. Any input would be highly appreciated.
Thank you.
 
SwedishForenger

SwedishForenger

Senior Member
Mar 26, 2021
335
64
cnxphysics said:
Hello,
I using LeOS-19.1 with my oukitel wp5 pro which works fine except I have to manually connect to home wifi (auto - connect has to be 'off').
If I install LeOS-20 or LeOS-T (both android 13) then it is not possible to connect with home wifi either manually or with auto-conect 'on'.
The LeOS telegram group has suggested adb shell settings put global restricted_networking_mode 0. It makes no difference to the above.

I was wondering if it is an oukitel issue rather than GSI issue. Any input would be highly appreciated.
Thank you.
Click to expand...
Click to collapse
.

I've run tons of different GSIs for testing purposes, and LeOS-19.1 /LeOS-20 are the only two GSIs I've had problems with the wifi. I can say with certainty that it is the LeOS fractured settings that are causing the problems. Anyway, there are other roms without play services, both with and without su ore root by magisk to try.

To be completely honest with you, LeOS is just a hyped GSI that gives false security for the end user, it makes little or no difference to remove google callback links, as long as you choose a GSI WITHOUT google play services and google apps, that requests this anyway.

Just flash a clean GSI without Gapp. and install only FOSS apps with WebSocket for Telegram Etc. And you're just as safe.

.
 
Last edited:
C

cnxphysics

Member
Aug 7, 2022
11
2
SwedishForenger said:
.

I've run tons of different GSIs for testing purposes, and LeOS-19.1 /LeOS-20 are the only two GSIs I've had problems with the wifi. I can say with certainty that it is the LeOS fractured settings that are causing the problems. Anyway, there are other roms without play services, both with and without su ore root by magisk to try.

.
Click to expand...
Click to collapse
Which on or ones do you prefer/suggest?
 
SwedishForenger

SwedishForenger

Senior Member
Mar 26, 2021
335
64
cnxphysics said:
Which on or ones do you prefer/suggest?
Click to expand...
Click to collapse
.

It depends on your purpose of use. Is it security or anonymity, or just being private.
The android WP5 pro works flawlessly in 12.1 GSI's, and here there is now a plethora to choose from. If you have security in mind, there are also firewalls to better control incoming and outgoing traffic.

But with battery saving in mind, it is important to minimize the number of installed apps, and active background processes, to eliminate battery drains. A lot has certainly happened since I tested all these GSIs a year ago. my advice is to search for: GSI arm64 ab 12.1 and start testing GSI's without gaps, or with FOSS apps pre-installed.

.
 
C

cnxphysics

Member
Aug 7, 2022
11
2
SwedishForenger said:
.

It depends on your purpose of use. Is it security or anonymity, or just being private.
The android WP5 pro works flawlessly in 12.1 GSI's, and here there is now a plethora to choose from. If you have security in mind, there are also firewalls to better control incoming and outgoing traffic.

But with battery saving in mind, it is important to minimize the number of installed apps, and active background processes, to eliminate battery drains. A lot has certainly happened since I tested all these GSIs a year ago. my advice is to search for: GSI arm64 ab 12.1 and start testing GSI's without gaps, or with FOSS apps pre-installed.

.
Click to expand...
Click to collapse
Thank you.
 
candidosobrinhosa

candidosobrinhosa

Member
Jan 20, 2023
17
1
Guys, I'd like to install a GSI. I intend to use command scripts made available by @SwedishForenger .

I bought mine couple weeks ago, and it came with EEA_V11_20210508 preinstalled and I've read I should update from V11 -> V12, then V12 -> V15.

V12 or V15 are not available anywhere online, and OTA says my version is the last updated version in the server.

I noticed some people complaining on screen error, unable to actually see or read anything.

1) I'm planning to dump all partitions before try writing anything on the phone. Is it overthinking?

2) After that, should I try installing on mine right away or give up and look for a V15 elsewhere?

Thanks
 
SwedishForenger

SwedishForenger

Senior Member
Mar 26, 2021
335
64
candidosobrinhosa said:
Guys, I'd like to install a GSI. I intend to use command scripts made available by @SwedishForenger .

I bought mine couple weeks ago, and it came with EEA_V11_20210508 preinstalled and I've read I should update from V11 -> V12, then V12 -> V15.

V12 or V15 are not available anywhere online, and OTA says my version is the last updated version in the server.

I noticed some people complaining on screen error, unable to actually see or read anything.

1) I'm planning to dump all partitions before try writing anything on the phone. Is it overthinking?

2) After that, should I try installing on mine right away or give up and look for a V15 elsewhere?

Thanks
Click to expand...
Click to collapse
.

Well, What you should do?, depends on how much you trust 'China that there is no hidden spyware on your phone and what you will use it for.

Formating the phone, sounds like a good idea, and flashing a Android you can trust.
Which type of Android version, depends on what you are going to use the phone for. This is not a Gaming phone, with Super spec hardware. So less is better. The most important thing, I personally think, and the reason I bought this phone, was the battery capacity.So the choice of Android should reflect that.

And here you have Android's Canandrum.
Older versions of Android use less battery power, but lack functions such as powersaving modes Etc. Newer versions of Android generally use more power because there are mor services running in the background to provide more functionality and services for conserving power to apps, that's not being used and have powersaving modes Etc. So the structure is based on catch-22 logic.

So to find a middle ground, it is better to find a newer version of Android, like 12.1 and newer, but with bare minimum of pre-installed apps, and onely run FOSS apps, that doesn't use Google services running constantly in the background and draining your battery. And for all other apps you have installed but don't need all the time, like imged galleries and, calculator Etc Etc, that you 'Restrict them in battery settings. If you do this and find a good balance between Android, settings and apps, it should result in you only charging your phone every 6-7 days.

I have put up enough information here on the forum for you to find all this info you need with a little searching. O and welcom to the Oukitel family here at XDA :)

.
 
Last edited:
candidosobrinhosa

candidosobrinhosa

Member
Jan 20, 2023
17
1
@SwedishForenger I tried installing a GSI image (PixelExperience_Plus_arm64-ab-slim-13.0-20230104-UNOFFICIAL.img), using the AA Installer but I was not able to.

When the script reaches this step:
[LINE9].\fastboot.exe -w [LINE10].\fastboot.exe reboot fastboot

It boots in fastbootd and gives me some options. I choose "reboot to bootloader" so it may enter fastboot mode again.

unnamed.jpg



After that, the script continues.... but the batch script (.bat) fails when trying to modify 'system' and 'product' partitions. Fastboot says these partitions don't exist. Please refer to Lines 34-42.

Here is the output of the script:

LINE1 < waiting for any device > LINE2 (bootloader) Start unlock flow LINE3 LINE4 OKAY [ 5.620s] LINE5 Finished. Total time: 5.622s LINE6 (bootloader) Start unlock flow LINE7 LINE8 OKAY [ 4.946s] LINE9 Finished. Total time: 4.948s LINE10 Sending 'recovery' (32768 KB) OKAY [ 0.767s] LINE11 Writing 'recovery' OKAY [ 0.447s] LINE12 Finished. Total time: 1.234s LINE13 Sending 'boot' (32768 KB) OKAY [ 0.762s] LINE14 Writing 'boot' OKAY [ 0.462s] LINE15 Finished. Total time: 1.352s LINE16 Rewriting vbmeta struct at offset: 0 LINE17 Sending 'vbmeta' (4 KB) OKAY [ 0.024s] LINE18 Writing 'vbmeta' OKAY [ 0.008s] LINE19 Finished. Total time: 0.047s LINE20 Erasing 'userdata' OKAY [ 0.930s] LINE21 mke2fs 1.46.2 (28-Feb-2021) LINE22 Sending 'userdata' (316 KB) OKAY [ 0.028s] LINE23 Writing 'userdata' OKAY [ 0.270s] LINE24 Erasing 'cache' OKAY [ 0.030s] LINE25 mke2fs 1.46.2 (28-Feb-2021) LINE26 Sending 'cache' (68 KB) OKAY [ 0.023s] LINE27 Writing 'cache' OKAY [ 0.107s] LINE28 Erasing 'metadata' OKAY [ 0.017s] LINE29 Erase successful, but not automatically formatting. LINE30 File system type raw data not supported. LINE31 Finished. Total time: 1.621s LINE32 Rebooting into fastboot OKAY [ 0.006s] LINE33 < waiting for any device > [I][B]LINE34 fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable. LINE35 Erasing 'system' FAILED (remote: 'Partition table doesn't exist') LINE36 fastboot: error: Command failed LINE37 Deleting 'product' FAILED (remote: 'unknown command') LINE38 fastboot: error: Command failed LINE39 Invalid sparse file format at header magic LINE40 Sending sparse 'system' 1/23 (131060 KB) OKAY [ 3.042s] LINE41 Writing 'system' FAILED (remote: 'This partition doesn't exist') LINE42 fastboot: error: Command failed[/B][/I] LINE43 Erasing 'userdata' OKAY [ 0.255s] LINE44 mke2fs 1.46.2 (28-Feb-2021) LINE45 Sending 'userdata' (316 KB) OKAY [ 0.014s] LINE46 Writing 'userdata' OKAY [ 0.065s] LINE47 Erasing 'cache' OKAY [ 0.019s] LINE48 mke2fs 1.46.2 (28-Feb-2021) LINE49 Sending 'cache' (68 KB) OKAY [ 0.009s] LINE50 Writing 'cache' OKAY [ 0.024s] [I][B]LINE51 Erasing 'metadata' OKAY [ 0.007s] LINE52 Erase successful, but not automatically formatting. LINE53 File system type raw data not supported.[/B][/I] LINE54 Finished. Total time: 0.545s LINE55 Rebooting into bootloader OKAY [ 0.001s] LINE56 Finished. Total time: 0.001s [B][I]LINE57 Erasing 'userdata' FAILED (Write to device failed (Unknown error)) LINE58 fastboot: error: Command failed[/I][/B] LINE59 < waiting for any device > LINE60 Sending 'boot' (10536 KB) OKAY [ 0.266s] LINE61 Writing 'boot' OKAY [ 0.142s] LINE62 Finished. Total time: 0.450s LINE63 Sending 'lk' (818 KB) OKAY [ 0.025s] LINE64 Writing 'lk' OKAY [ 0.016s] LINE65 Finished. Total time: 0.046s LINE66 Sending 'lk2' (818 KB) OKAY [ 0.025s] LINE67 Writing 'lk2' OKAY [ 0.015s] LINE68 Finished. Total time: 0.048s LINE69 Sending 'vbmeta' (4 KB) OKAY [ 0.007s] LINE70 Writing 'vbmeta' OKAY [ 0.002s] LINE71 Finished. Total time: 0.014s LINE72 Sending 'recovery' (24794 KB) OKAY [ 0.600s] LINE73 Writing 'recovery' OKAY [ 0.334s] LINE74 Finished. Total time: 0.941s LINE75 Rebooting OKAY [ 0.000s] LINE76 Finished. Total time: 0.001s
 
Last edited:
SwedishForenger

SwedishForenger

Senior Member
Mar 26, 2021
335
64
.

Did you forget to OEM Unlock the phone before you started this flashing process ?
From what I can see here, your bootloader is still locked. Which means you don't have permission to edit system partitions, Ergo the error messages you getting.

2023-02-05_20-12.png

​
1. Format the phone using SP flash tool, and reinstall stock firmware from Oukitel website.

2. Ad back your IMEI from here: https://forum.xda-developers.com/t/oukitel-wp5-pro.4180209/post-84780513

3. head over to the 'Settings
Scroll all the way down to find the System
Find the 'About phone
Scroll down to find the Build number section and tap on it 7 times
Go in to Developer Options,

Enable OEM unlocking​


Get this done first, and I'll help you from here, so we're both on the same page.
You need to send me your boot.img so I can patch it for you. but fix the above first.

.
 
Last edited:
candidosobrinhosa

candidosobrinhosa

Member
Jan 20, 2023
17
1
It was unlocked. Actually, it stills
Screenshot_20230205-201414~2.png


I'll install stock ROM using SP and try using the script once again.

I'll report as soon I manage to do it.

Thanks.
 
candidosobrinhosa

candidosobrinhosa

Member
Jan 20, 2023
17
1
First try:

1) Flashed stock V11 with SP Flash Tool.
2) Checked if OEM was unlocked in Developer Tools. It was.
3) Ran the script again but did not work.

Later:

1) Flashed stock V11 once again.
2) Locked the bootloader. $ fastboot flashing lock
3) Locked the 'OEM Bootloader' in Developer Tools and restarted.
Then:
4) Enable OEM Bootloader unlock in Dveloper Tools.
5) Re-ran the script but unfortunately, same error.

=/
 
SwedishForenger

SwedishForenger

Senior Member
Mar 26, 2021
335
64
candidosobrinhosa said:
First try:

1) Flashed stock V11 with SP Flash Tool.
2) Checked if OEM was unlocked in Developer Tools. It was.
3) Ran the script again but did not work.

Later:

1) Flashed stock V11 once again.
2) Locked the bootloader. $ fastboot flashing lock
3) Locked the 'OEM Bootloader' in Developer Tools and restarted.
Then:
4) Enable OEM Bootloader unlock in Dveloper Tools.
5) Re-ran the script but unfortunately, same error.

=/
Click to expand...
Click to collapse
*

Are you just reflashing stock over previously flashed Android versions without formatting in between?.
If so, Please don't do that, You accumulate old configuration files, which confuses the new flashed Android on which to use. Format the phone in SP-flash tools, flash stock Android, ad back your IMEI. Then flash GSI.

Download the Install Android.zip and Extrackt-

After you have downloaded the Android version you want to your desktop, you must Extract the img file from the downloaded file, by right-click and select 'Extract to desktop. Rename the extracted file to GSI.img.... Move the GSI.img to the Android Installer folder. Open the Android Installer folder and enter CMD in the addressbar and press Enter:

2023-02-06_05-17.png


Enter these commands manually: And tell me where it goes wrong in the command structure.

Code: 
fastboot flashing unlock  /look at your phone and press Volume + button
fastboot flashing unlock_critical  / Look at your phone and press Volume + button
fastboot flash recovery recovery.img
fastboot --disable-verification flash boot boot.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot fastboot
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
 

Attachments

  • Install Android.zip
    90.8 MB · Views: 4
  • Magisk-v25.2.apk
    10.8 MB · Views: 1
Last edited:
candidosobrinhosa

candidosobrinhosa

Member
Jan 20, 2023
17
1
No, I wasn't Formatting. I hope this was the issue.

Which options should I select?

1 Validation? Yes or No.
2 Autoformat Flash (rather than Manual)?
3 Format whole flash except bootloader?
 
candidosobrinhosa

candidosobrinhosa

Member
Jan 20, 2023
17
1
Cleanup:

1. Format (Auto Flash / Whole flash) -> OK.
2. Install Stock -> OK.

First Boot:
>I've noticed now there's a "Debugging mode" watermark. This didn't show up before.
> Skipping all settings... no wifi, no accounts. Straight to Unlocking...

4. Dev Tools > Enable OEM Unlock -> OK.
5. Dev Tools > USB debugging -> OK.
6. Normal reboot.
7. Rebooting to fastboot with PWR + VOLUP

Fastboot mode:

$> .\fastboot.exe flashing unlock
(bootloader) Start unlock flow OKAY [ 5.472s] Finished. Total time: 5.473s

$> .\fastboot flashing unlock_critical
(bootloader) Start unlock flow OKAY [ 5.593s] Finished. Total time: 5.595s

$> .\fastboot flash recovery recovery.img
Sending 'recovery' (32768 KB) OKAY [ 0.792s] Writing 'recovery' OKAY [ 0.447s] Finished. Total time: 1.253s

$> .\fastboot --disable-verification flash boot boot.img
Sending 'boot' (32768 KB) OKAY [ 0.783s] Writing 'boot' OKAY [ 0.461s] Finished. Total time: 1.370s

$> .\fastboot --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0 Sending 'vbmeta' (4 KB) OKAY [ 0.023s] Writing 'vbmeta' OKAY [ 0.008s] Finished. Total time: 0.046s

$> .\fastboot -w
Erasing 'userdata' OKAY [ 0.915s] mke2fs 1.46.2 (28-Feb-2021) Creating filesystem with 13945851 4k blocks and 3489792 inodes Filesystem UUID: 085d4b3c-a646-11ed-a7bd- Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424 Allocating group tables: done Writing inode tables: done Creating journal (65536 blocks): done Writing superblocks and filesystem accounting information: done Sending 'userdata' (316 KB) OKAY [ 0.028s] Writing 'userdata' OKAY [ 0.276s] Erasing 'cache' OKAY [ 0.029s] mke2fs 1.46.2 (28-Feb-2021) Creating filesystem with 110592 4k blocks and 110592 inodes Filesystem UUID: 08a8b888-a646-11ed-94c9- Superblock backups stored on blocks: 32768, 98304 Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done Sending 'cache' (68 KB) OKAY [ 0.024s] Writing 'cache' OKAY [ 0.111s] Erasing 'metadata' OKAY [ 0.017s] Erase successful, but not automatically formatting. File system type raw data not supported. Finished. Total time: 1.624s

$> .\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.008s] < waiting for any device >
Untitled.jpg

Note: Serial has change for a dummy value.

When it reaches this step, I select Reboot to bootloader, then this happens:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

From this point foward, nothing works

$> .\fastboot erase system
Erasing 'system' FAILED (remote: 'Partition table doesn't exist') fastboot: error: Command failed

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

SwedishForenger

Senior Member
Mar 26, 2021
335
64
.

Try this:
Hold down the Power button and the Volume button until you can select the bootloader again.
The phone may reboot a couple of times , don't release the buttons until the menu comes up.


Then try flashing the GSI file again:

fastboot flashing unlock /look at your phone and press Volume + button
fastboot delete-logical-partition product
fastboot reboot-bootloader
fastboot flash system GSI.img
fastboot -w
fastboot reboot

Or this

fastboot flashing unlock /look at your phone and press Volume + button
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system GSI.img
fastboot -w
fastboot reboot

.
 
Last edited:
candidosobrinhosa

candidosobrinhosa

Member
Jan 20, 2023
17
1
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
 
You must log in or register to reply here.

Similar threads

jan177
  • Locked
Homtom HT7 PRO./ 2GB 16GB Mt6735/ Info /TWRP
Replies
595
Views
140K
R
Robbycs
D
Oukitel WP5
Replies
73
Views
16K
forart.eu
forart.eu
leepriestenator
Primary Windows Live Messenger Thread (LAST UPDATED: 11-JAN-10)
Replies
693
Views
489K
A
aion_w
S
Check It Out The Xda Flame!
Replies
862
Views
217K
xeirwn
xeirwn
__TrungDK__
Google Product Sans for Android 10 OneUI 2.5 (Samsung Phone)
Replies
124
Views
275K
Badger50
Badger50

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 6
    SwedishForenger
    SwedishForenger
    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
    View
    3
    xmucio
    xmucio

    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 ":""
    Click to expand...
    Click to collapse
    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}
    Click to expand...
    Click to collapse

    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}
    Click to expand...
    Click to collapse
    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}
    Click to expand...
    Click to collapse
    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}
    Click to expand...
    Click to collapse
    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!
    View
    3
    2
    2mkl
    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.
    View
    2
    SwedishForenger
    SwedishForenger
    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



    ​
    View
    2
    SwedishForenger
    SwedishForenger
    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

    1.41 GB file on MEGA

    mega.nz mega.nz

    And all the tools needed to make the upgrade possible, you can find it here

    174.12 MB folder on MEGA

    5 files
    mega.nz mega.nz
    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
    View

New posts