yashsingh1/xdaforums huggingface dataset:
[Oukitel (All phone models)] SwedishForenger:
Stock Oukitel Android 11 recovery​

Let's fix this phone​

Download these files:​

Oukitel WP17 firmware: ASW2100YJ_2201_T2046

Python 6.3.1

Mediatek VCOM, CDC, USB Serial & Smartwatch Drivers

UsbDk_Brom-mode

MTKClient

Flash_Tool_v5.2028

Computer with internet

But before we can start, we need to format the phone, to delete all old configurations and settings.

View attachment 5837877​

1. Start by extracting the firmware file to your desktop. Now open up the MTKClient zip file and drag all files to your firmware folder.

View attachment 5734249
​

2. Now you Install all needed drivers: Mediatek VCOM, CDC, USB / UsbDk_Brom-mode.

3. Extract the Flash_Tool to your desktop and open the flash_tool.exe.

ONLY check the UNverified files. We will flash the verified files later. Click on the Download button when you're done. Take your dead phone and connect it to the computer with the USB cable. Hold down Volume+ Volume- and power-button together, hold the buttons until the flashing start.

View attachment 5734265​

Once you have flashed the UN-verified files to your phone, we start the process of flashing the verified files.

4. Now we need access to the verified files. open a prompt in the firmware.

To do that, go to the start menu and type CMD.

View attachment 5734329​

4. Right-click and copy the address and paste it in the prompt window.

View attachment 5734327

View attachment 5734299

​

5. Now we have to configure MTKClient to be able to communicate with the phone.

Past in these commands one at a time in to the promt window.

python setup.py install
pip3 install -r requirements.txt

6. And now finally after you have set up the environment in python.

The flashing of the verified files to you phone can begin. copy and paste in the hole commands.

python mtk w md1img,spmfw,scp1,scp2,sspm_1,sspm_2,cam_vpu1,cam_vpu2,cam_vpu3,gz1,gz2,lk,lk2,logo,dtbo,tee1,tee2 md1img-verified.img,spmfw-verified.img,scp-verified.img,scp-verified.img,sspm-verified.img,sspm-verified.img,cam_vpu1-verified.img,cam_vpu2-verified.img,cam_vpu3-verified.img,gz-verified.img,gz-verified.img,lk-verified.img,lk-verified.img,logo-verified.bin,dtbo-verified.img,tee-verified.img,tee-verified.img

View attachment 5734307
​

Press Enter,

On the phone: Hold down Volume+ Volume- and power-button together, hold the buttons until the flashing start. Sit back and wait

.

View attachment 5734709
​

Your phone will end up like this after boot.

View attachment 5734311View attachment 5734313View attachment 5734315​

Done ....

Now Update your phone by Android update service by going in to 'Settings / System and update phone.

.
[Oukitel (All phone models)] SwedishForenger:
-- IMEI Restore --​

After formatting the phone. I use ModemMETA tool to restore my IMEI.

View attachment 5737447
​

Select the “Smart Phone” option from “Platform Type” section. Same as , select “USB” option from “PORT” section.

Press the Connect button in Modem METAtool. Hold down the Volume+ Volume- and power buttons at the same time while plugging in the USB cable. Meta tool will detect the device and it will start to load Boot file, karnel port etc. You can see all the process in “Connection Stages” section.

After completing the configuration process, you will be able to see “Connect” message at the bottom of the tool.

Now click on “Load DB”. “Load Database file from target”.

View attachment 5736993​

Now click on search box and select IMEI download option from drop down menu.

View attachment 5736995​

A new IMEI window will pop up in front of you.

Type in yor IMEI : and hit on “Write” button from same window.

ILLEGAL to Creating your own: 12345.12345.1234

View attachment 5736997​

if everything went well, it looks like this.​

View attachment 5737443

​
[Oukitel (All phone models)] SwedishForenger:
Update:

Easy rooting with Magisk ......​

This will Unlock your bootloader!.

Unlocking your bootloader will send your phone in to a emergency state, and delete all personal data on the device. Back up everything that is important to you, before proceeding with rooting your phone -

View attachment 5735787View attachment 5735789
​

Download and extract AA - Install Android to your desktop. Turn off your phone and enter 'fastboot mode'. Connect your phone to the computer and open AA - Install ROOT.dat.

View attachment 5747107
​

Install Magisk25.

.
[Oukitel (All phone models)] SwedishForenger:
-- WARNING --​

Thinking of upgrading to Android 12 / Android 13 ?​

The camera drivers found in the Android 11 version your phone was shipped with -​

Are NOT in the Android 11 version from the Oukitel Download Center !.​

You will brake your 64MP Camera if you flash GSI ore the version from Download Center .​

Although I copied all the files required to restore the camera, which you can find below in a zip file -

Are the drivers in all other roms and GSI's to control the camera missing.

--FM drivers are located in kernel. Most other oem drivers are in vendor. And the definitions are in system

​

However, there is an easy fix for this, and that is to make a backup of your working phone firmware before you start installing other versions of Android, so that you can always restore your phone from this backup, with the correct drivers and get a fully functional phone again.

​

Dump/extract/backup your Oukitel WP17 firmware.​

It is ALWAYS a good practice to backup your firmware. Any phones sooner or later will have issues and since you don't have a copy to restore yor phone, you will spend money sending it in for repair which sometimes costs more than the phone is worth. There are many ways to make a copy of your phone's firmware. search on the internet or use this simple guide:

All the files you need can be found under this video​

And to everyone who already broken their phone and is now looking for a way to restore their phone. Have I already ordered a new WP17 that I will create a firmware backup of, and make available for you and a manual for how to restore. I will keep you updated on that, but it takes a long time to get things shipped from China these days.

.
[Oukitel (All phone models)] SwedishForenger:
Android 12 / 13 on Oukitel WP17 -​

I created a small script that quickly installs Android 12 and 13 on your phone.

Get rid of the pesky red text on the screen.

​

Android 12 ...​

View attachment 5736403View attachment 5736413View attachment 5736411

View attachment 5736407View attachment 5736409

​

Android 13 ...​

View attachment 5736417View attachment 5736419View attachment 5736421

View attachment 5736423View attachment 5736425

​

To begin with, you need to decide which version of Android you want on your phone.

To help you on your way, I suggest you check out the link below. It's important that you choose the ARM64 AB version.

Generic System Image (GSI) list

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

In this example, let's say you want to install Spark OS Android 13.

View attachment 5736495
​

Go to the download page and select the latest version.

View attachment 5736497

View attachment 5736499​

1. Extract Android 13 from the downloaded file to your desktop.

2. Rename the file to GSI.img

3. Download and extract AA - Install Android to your desktop

4. Move the GSI.img file to the install folder.

View attachment 5736509
​

Double-click on AA - Install Android.

View attachment 5736511​

Turn off your phone.

Press and hold Volume+ Power and Ptt button until you get to the bootloader menu.

Select Fastboot mode.

View attachment 5736483

View attachment 5736501
​

Connect your USB cable to your phone, Look at your phone, and press Volume+ button 2 times when prompted to start. That's all. Sit back and relax for a couple of minutes.

View attachment 5736519
​

The installation script will install your chosen Android version and reboot the phone when everything is done. After boot install Magisk25.

.

​
[Oukitel (All phone models)] SwedishForenger:
Udate:

I have created a new lk.img file to remove the 'Orange State' Warning during boot of Android.

The file is added to the installation scripts.
[Oukitel (All phone models)] picipi:
Hi,

I've just intalled SparkOS (the same file you show in the tutorial) on my WP17.

The default camera has been replaced and now I can't use the triple camera or infrared.

I was wondering if you knew how to install/flash the NightVision Camera_Oukitel WP17.zip back onto the phone. Or maybe where to put the files?

Best regards, picipi.

PS: keep on the great work!
[Oukitel (All phone models)] SwedishForenger:
.

No. Sorry, not yet. The problem is the drivers for the camera. The Android version your phone is shipped with has these drivers pre-installed. As I wrote before, if you flash GSI or other versions of android, these drivers are not included, and you will have problems with your camera.

This forum is aimed primarily at those who have had problems with their phone and need help getting their phone to a working condition for calling and normal daily operation. However the NightVision Camera can be partly fixt by installing the default camera app.

It's important for EVERYONE with Android 11 stock firmware, to extract a copy of the firmware as a backup, before flashing other GSI roms. And share a link here on the forum, so others can restore their phones to.

There are many ways to do this. Find a method that suits you best:

pull Stock Android Firmware - Google Search

Perhaps this one for Windows users:

How to use SP Flash tool to backup Mediatek firmware

Update: I suggest you use Wwr tool + SP flash tool for the dump instead of SP Flash tool alone as you can proceed without first having the scatter file and using MTK Droid Tools (which is now outdated

www.hovatek.com

PS..

When you extract you firmware. DO NOT copy the USERDATA partition!, this partition can hold up to 20-40 gigabits of your old useless user data, of you using your phone on a daily bases.

.
[Oukitel (All phone models)] SwedishForenger:
--- BlissOS Android 13 and lightning fast ---​

View attachment 5747695View attachment 5747697View attachment 5747699

View attachment 5747701View attachment 5747703View attachment 5747705
​

This rom has the bare minimum of needed apps, no bloatware and lightning fast.

highly recommended and fit's the Oukitel WP17 spec perfectly.

Download the rom here:

BlissOSv16.0-arm64-bgN-slim-Unofficial​

1. Extract Android 13 from the downloaded file to your desktop.

2. Rename the file to GSI.img

3. Download and extract AA - Install Android to your desktop

4. Move the GSI.img file to the install folder.

View attachment 5747727

View attachment 5747729​

Enjoy ...
[Oukitel (All phone models)] SwedishForenger:
If you choose to go back to stock rom, and you have formatted the phone to flash GSI, is the precise partition deleted, and you end up with missing google key / Red txt on the top of your phone.

View attachment 5762961​

Here is the file you flash to get rid of that Red txt…

fastboot flash persist persist.img

_____________________________________________________________________________________

Update:

Some users reported it doesn't work for them.

For me it did the trick, but it doesn't work for everyone.

.

.
[Oukitel (All phone models)] JustNabus:
Hey, thank you so much, got my WP17 working again but now I don't have IMEI and I'm getting a watermark saying "No google key and tee key" any ideas how to fix this ?
[Oukitel (All phone models)] SwedishForenger:
.

The IMEI fix: https://xdaforums.com/t/oukitel-wp17-root-gsi-arm64-a-b-treble-enabled.4504207/post-87571063

Working on a solution for the "No google key and tee key".

Don't forget to update the Android system for camera fix.

.
[Oukitel (All phone models)] JustNabus:
I forgot to say that I don't have any backup on my IMEI and I've no idea where the box is. Is there any other way to get it ? I've sent an email to Oukitel but no answer so far
[Oukitel (All phone models)] SwedishForenger:
.

Yes. just copy and paste these numbers. Ore just scramble the numbers around.

IMEI 1: 35524555061532

IMEI 2: 35524555061573

View attachment 5778811
​

If you don't want to use these IMEI numbers, you can just take the IMEI number under the battery from one of your old phones you already have lying around. it doesn't matter how old they are, even an old Nokia from 1990 works perfectly fine.

_______________________________________________________________________________________
​

Disclaimer​

Editing or changing the serial number or IMEI of your device is illegal in some countries.

I take no responsibility for your actions. This is for educational purposes only.

.
[Oukitel (All phone models)] SwedishForenger:
To remove the Red txt "No google key and tee key".​

Some people have sent me a pm and say that flashing persist.img didn't work for them.

Try this instead:

adb devices
pm uninstall -k --user 0 com.mediatek.engineermode

Reboot the phone.

.
[Oukitel (All phone models)] dalelad:
noob here, can you create a youtube video on how to install a custom rom to this phone?
[Oukitel (All phone models)] SwedishForenger:
.

It's not relay necessary.

There are only 4 small simple steps to perform, the Installer does everything else for you.

https://xdaforums.com/t/oukitel-wp17-root-gsi-arm64-a-b-treble-enabled.4504207/#post-87582555

It's important for EVERYONE with Android 11 stock firmware, to extract a copy of the firmware as a backup, before flashing other GSI roms. And share a link here on the forum, so others can restore their phones to.

There are many ways to do this. Find a method that suits you best:

pull Stock Android Firmware - Google Search

.
[General Topics] Mike Cutter:
This may be a general problem but one I haven't solved yet. I have a P3300 running WM6 on a microSD card formated for FAT32. I am using a GPS navigation program that requires a large number of Google map png files (approx 1400) to be transferred to a cache on the card. I tried using ActiveSync and the transfer bombs out indicating that there is too little memory on the card. The 1400 files corresponds to 9MB and the card has 600MB free space. To get around this I zipped the data up and transferred it across as a single file. However, when I tried to unzip the file I ended up with the same problem. I haven't counted how many files have been transferred but it is a sizeable number. I have a few extra routes to try but would be interested in any feedback on this problem

Mike
[Redmi Note 10 Pro] zepolyerf:
I f****d up.

Hi everyone. I may have bitten more than I can chew. I'm trying to install a custom ROM to my recently unlocked Redmi Note 10 Pro. It's crDroid in case that's necessary.

I did a lot of things but I forgot most of them. Here's what I remember doing:

Connected my phone to my Linux computer.

Go into fastboot modevia the following command:

adb reboot bootloader

Use TWRP by running this in a terminal:

fastboot boot twrp.img

Went in to the wipe option in TWRP and do a complete factory reset and format data.

Pushed the custom ROM file to /sdcard.

Attempted to install the zip file via TWRP.

Got an error code. Forgot the code and I didn't take note of it. (Please make fun of me).

Attempted to reboot TWRP recovery by going to Reboot > Recovery

Reached stock MIUI Recovery.

And here I am.

I can only access MIUI Recovery 5.0 and fastboot mode, both by pressing the right buttons on the device.

I don't know what a bricked device is, but it sure does feel like my device is one.

Is there a way to solve this?
[Redmi Note 10 Pro] Xavind:
Drivers installed?
[Redmi Note 10 Pro] zepolyerf:
Hi! How can I check if drivers are installed? I'm on Linux, if that matters.
[Redmi Note 10 Pro] V0latyle:
Your device isn't bricked until you can do absolutely nothing with it. Start by reflashing the factory firmware; this should get your device running again.

You should also still be able to boot TWRP just like you did. What ROM were you trying to use?
[Redmi Note 10 Pro] zepolyerf:
That's good to hear.

I'm trying to make another attempt to boot to TWRP. I'm currently in fastboot mode: running fastboot -l devices shows this:

f8b471a6 fastboot
usb:1-5

I tried to following official TWRP instructions to flash it. Ran fastboot flash recovery twrp.img and all I get is <waiting for device> as a response after running the command in the terminal.

I unplug the cable, then plug it back in to the computer, then this is what I got:

Sending 'recovery' (131072 KB) FAILED (Write to device failed (Device or resource busy))
fastboot: error: Command failed

Any ideas on how to get around this?
[Redmi Note 10 Pro] V0latyle:
Your device might not have a recovery partition; in A/B partition layout devices, recovery lives in the boot image.

A bit of an explanation:

When you use fastboot boot <image> you're telling the device to load the image you're sending - so if you use fastboot boot twrp.img you're telling it to load the TWRP.img on your computer. This is what you should be using if you want to boot TWRP.

When you use fastboot flash <partition> <image> you're telling bootloader to flash the specified partition with the specified image. So, if you used fastboot flash boot twrp.img, bootloader will overwrite /boot with the TWRP image...meaning the device will only boot into TWRP.

As for why the device would only boot into stock recovery after you flashed the custom ROM, I suspect that it didn't flash the kernel, or otherwise may have corrupted the boot image. So, when the device tries to start the kernel, it failed and just boots into recovery instead.
[Redmi Note 10 Pro] zepolyerf:
What should I do at this point if I can't do fasboot boot <image> or fastboot flash <parition> <image> because of the <waiting for device> thing I get everytime I run those commands?
[Redmi Note 10 Pro] V0latyle:
Reboot to bootloader. If you're currently in recovery mode, cancel the command (Ctrl+C) and use adb reboot bootloader. If you're currently in bootloader but it's not responding, just use the button combo to force a reset.

Remember, you can only use fastboot commands in bootloader mode. If you're in recovery, you can only use some ADB commands, but in this case, I don't think that will be much help.
[Redmi Note 10 Pro] BigChungus321:
This is just soft brick. A hard brick means no life in the device as well. In your case, you can still access recovery and fastboot. You can either use MiFlash and use fastboot to flash the stock rom (your choice if you want to relock the bootloader or not) or flash miui recovery rom directly in the custom recovery.

If I remember correctly too, crDroid requires it's provided recovery instead of TWRP so maybe that's why the installation failed.
[Redmi Note 10 Pro] zepolyerf:
It might as well be a brick haha. I must be dumb (very likely) or there's just not a lot of clear and comprehensive resources out there to fix this kind of thing.
[Redmi Note 10 Pro] BigChungus321:
Ahh anti roll back error is pretty simple to fix, you just have to remove the check from the .bat files, there are tutorials on YT that can help, after that reflash stock rom in MiFlash.

If you're worried about anti roll back, don't worry, ARB value for the device has been 3 so far so it's safe to downgrade. Goodluck
[Redmi Note 10 Pro] gazza35:
Seeing a ton of Bricked Notes on here this last week, Y`all making me nervous about doing anything with mine lol
[Redmi Note 10 Pro] A6d5:
I faced this problem in linux got around it with usb 2.0 interface doesn't worked with usb 3.0 and above but my device was different when I got this recovery flash waiting problem. Also try to updated the platform tools.
[Redmi Note 10 Pro] zepolyerf:
So the solution was to entirely ditch Linux and use Windows to play with fastboot and adb commands via the terminal.

I don't understand why it worked when I did it on Windows when I was using the same platform tools on Linux. Oh well.
[Fire General] SzosszeNET:
Just wondering if someone could maybe point me in a direction. Maybe the tablet has died just find what I discovered recently interesting and wondering if makes it recoverable or still rubbish.

So the tablet seemingly doesn't function screen stays dark, no sound etc. Pressing the power button for a minute doesn't do anything, not sure which side of the volume button is down and tried both combinations but pressing the power button and one of the volume buttons doesn't seem to do anything either. Was about to put it into the bin when I decided to connect to my windows laptop and noticed that when connected for a short period it comes up as a com4 device.

Grabbed ADB but neither ADB or fastboot recognises. Any thoughts?
[Realme GT 2] 1411283270:
much better，but take photo is note good
[Realme GT 2] neo_bpm:
Realme ui4? What is this and how you tried it?
[Realme GT 2] 1411283270:
View attachment 5739381
[Realme GT 2] 1411283270:
View attachment 5739383
[Realme GT 2] smashda:
Have they still not fixed audio?

Can you check, when recording video/audio?
[Realme GT 2] 1411283270:
目前我没有这方面的bug
[Realme GT 2] ludoverblog:
Hi, my phone is a RMX3311_11 under

Someone know when the UI4.0 will be update to this device?

or

Someone know how to update it from UI3.0 to UI 4.0?

regards,

Ludovic
[Realme GT 2] 1411283270:
it will get ui4.0
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ClockWorkModEra:
I have been in the andorid moding since the clockworkmod recovery era.(andorid 4) I have nvr seen something so unusual. I was booting into recovery(twrp), I was about to install magisk but i couldnt find the zip file, so I was going to boot into system. And when it was booting. The first time boot bar thingy showed up(pixel experience) which mean it is usually bricked in the os. Has anyone have the same experience? Now I have to reinstall Pixel experience and lose data. Wow.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Bruh.

It's hard to understand what you're getting at. What is a Boot bar thingy? Please describe in proper english.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ClockWorkModEra:
Haha. Im new to the xda thingy sorry! So the boot bar im refering to is when the rom is booting for the first time and there will be a little bar at the bottom.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] 3zozHashim:
i dont understand much about flashing custom roms without formating but apparently Android 11 and Android 12 are encrypted, so, you cant flash/boot any custom roms without formatting the data.
[Tilt, TyTN II, MDA Vario III General] pazookie:
Ok i know the tilt SHOULD have had an acceleromter (gsensor) but it doesnt and i KNOW we can remap a button to change the orintation but what IF it would do it like the touch pro does?

Ok heres where my idea comes in and i hope it hasnt already been thought of but is it possible to create a program that wold use the camera to detect which position the device is in theoretically using the first image captured or viewed (not quite sure exactly how the camera soft works) and comparing that to the next (saving image and then deleting once compared).... it sounds crazy and i dont even think it can work but it was JUST AN IDEA..what do you guys think?
[Tilt, TyTN II, MDA Vario III General] Junner2003:
Yes, it can work but why would I want to waste my working memory with running the camera in the background if I finally only would have to push a button to get the same result? :D

However, if you have a need for such application, simply have a look at the video on the following page:

http://www.freewarepocketpc.net/ppc-download-gsen.html
[Tilt, TyTN II, MDA Vario III General] kilrah:
The Kaiser indeed doesn't have an accelerometer, so the above program is useless.

And about the camera - if you want to slow down your phone badly and run down your battery in a couple of hours, go for it....
[Tilt, TyTN II, MDA Vario III General] pazookie:
dang guys why so negative..never said i was gonna make it but itw s just an idea...calm down fools
[Tilt, TyTN II, MDA Vario III General] diomark:
Good idea, but it would drain the battery too fast.

-m