Develop Bugs

[WinApp][v2.4-Beta][+RemixOS] Android-x86 Installer UEFI Version

Code:
*** Disclaimer
Use this software at your own Risk,I am not responsible for any damage that may be caused by this software.
I have tested it on all machines i have, don't know if you have any special cases.
Description
This Installer will let you install Android x86 on your PC like any other application, no risk to Damage HDD Partitions, Boot Data or User Data. After installation you will got an option at boot to select Windows or Android.
This Installer is currently targets only Windows 8 / UEFI-Enabled Devices​
System Requirements
UEFI-Enabled x86 PC
Secure Boot Disabled
Bitlocker disabled on target drive
Windows 8/8.1/10
.Net Framework 4.5
Android System image with UEFI Support
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Change log
v2.4
Update Detection of RemixOS image [Use RemixOS ver: B2016012301 or higher]
Fix UEFI Init Fail with Surface Pro devices
v2.3
Add support for RemixOS
v2.2
Fix reading large UEFI entries
Fix using img file from path with spaces
Trial period Removed
Add GPU Options to GRUB Bootlist
v2.1
User-defined Data size
Responsive UI
Installation Status update
Support Devices with 32-bit firmware
Support booting from NTFS with compression enabled
log includes more info about Device BIOS
v2.0
Initial Version
Features
Install/Uninstall Android directly from Windows
Support UEFI-Enabled devices
Support legacy BIOS devices [not available in Alpha version]
Install to Any FAT32/NTFS partitions
Instructions
Install
Download Android EFI Enabled img file from: [LINK]
Launch the Installer
Select the downloaded IMG file
Select "Data Size" for file which will be used to store downloaded Apps and User Settings
Select the partition which Android will be installed to.
Click Install and wait ... The installation will take about 5 min. or less, it is based on your hard drive speed.
How to Enter Android
Go to Windows power menu and Click on "Restart" while holding shift [Screenshot]
Select "Use a device"
Select "Android-OS"
Now your PC will reboot to Android
Uninstall
Launch the Installer
Select "Cleanup Android"
Under the hood
The installer will verify the system requirements on launch
directory: "<TargetPartition>AndroidOS" will be used for installation
Extract the IMG file
Create user data partition
Install grubx64 to UEFI partition
Install new UEFI boot entry for Android
Downloads:
For UEFI-Enabled PCs: [UEFIInstallerv24-5800.exe]
For Legacy-BIOS PCs: [Old Thread]
Important notes (Read it carefully)
This version for testers only, not for end users
Please don't redistribute this version of the installer
Please please report your device model and if installation was successful or not
Any bug/problem/issue reported shall have installer log (which can be found in your C: ) attached and a screenshot
you can read the log before sending it if you have any privacy concerns
The installer will not allow installation on non-UEFI Devices for now
Verify that you downloaded .IMG file not .ISO file
if you have found a bug inside Android you should contact android-x86 team not to post here
Your feedback is highly appreciated
XDA:DevDB Information
Android-x86 Installer for Windows, Tool/Utility for the Windows 8 General
Contributors
ExtremeGTX
Version Information
Status: Beta
Current Beta Version: V2.4
Beta Release Date: 2016-02-05
Created 2015-10-15
Last Updated 2016-02-13

Looks amazing, gonna try it for sure, thanks for this tool!
EDIT: Tried it (ASUS T100TAM, Windows 10 x86), installation failed unfourtunately. Adding log from installation:
================Installer Info================
Installer Directory:C:\Users\****\AppData\Local\Temp\droidinst_efi
Installer Version:2.0.5761.39882
Secure Boot ... Disabled
Manufacturer: ASUSTeK COMPUTER INC.
Model: T100TAM
Product: T100TAM
BIOS Version: T100TAM.204
Available GPU(s):
GPU: Intel(R) HD Graphics
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
OS Type: ... fail
==========================================
====Install Started on 18.10.2015 10:52:53====
-ISO File: C:\Downloads\android-x86-4.4-r3.iso
-TargetDrive: C
-UserData: 1000k
-Setup Directories...
-Folder Created: C:\AndroidOS
-Extract ISO
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\7z.exex C:\Downloads\android-x86-4.4-r3.iso "kernel" "ramdisk.img" "initrd.img" "system.sfs" -oC:\AndroidOS
-Extract SFS
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\7z.exe x C:\AndroidOS\system.sfs "system.img" -oC:\AndroidOS
-Create Data.img
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\dd.exeif=/dev/zero of=C:\AndroidOS\data.img ibs=1k count=1000k
-Initialize Data.img
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\mke2fs.exe-F -t ext4 "C:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Setup Boot Directory...
-Boot Folder Created: Z:\EFI\Android\
-Copy Boot files
-Add UEFI Entry
UEFI Init Fail
==============Revert Installation==============
-Cleaning up Android Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
Folder is not empty.
-UEFI Init ... fail
-Cleaning up Android Directory ... Z:\EFI\Android\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
Click to expand...
Click to collapse

Check the New version
v2.1
User-defined Data size
Responsive UI
Installation Status update
Support Devices with 32-bit firmware
Support booting from NTFS with compression enabled
log includes more info about Device BIOS

ExtremeGTX said:
Code:
*** Disclaimer
Use this software at your own Risk,I am not responsible for any damage that may be caused by this software.
I have tested it on all machines i have, don't know if you have any special cases.
Click to expand...
Click to collapse
I get an error saying no kernel is installed
error no such device /AndroidOS/system.sfs
error file /AndroidOS/kernel not found
error you need to load the kernel first
EDIT: Also as a note both those files exist in C:\AndroidOS\system.sfs and C:\AndroidOS\kernel

ChrisJ951 said:
I get an error saying no kernel is installed
error no such device /AndroidOS/system.sfs
error file /AndroidOS/kernel not found
error you need to load the kernel first
EDIT: Also as a note both those files exist in C:\AndroidOS\system.sfs and C:\AndroidOS\kernel
Click to expand...
Click to collapse
it seems like bootloader can't access your Disk!
can you please post a screenshot of "Disk Management" :
- Open run and type: diskmgmt.msc then take screenshot like this [LINK]
- OR open start menu and type Disk Management

New version works perfectly! No problems at all, just tried Android x86 4.4 and Android x86_64 5.1 aswell on ASUS T100TAM (32GB version), both worked without any trouble - thanks a lot for this amazing tool!
Anyway a small question here - is it possible to create a shortcut in Windows, that could restart device directly into Android? Just a quick guess

spenat said:
New version works perfectly! No problems at all, just tried Android x86 4.4 and Android x86_64 5.1 aswell on ASUS T100TAM (32GB version), both worked without any trouble - thanks a lot for this amazing tool!
Anyway a small question here - is it possible to create a shortcut in Windows, that could restart device directly into Android? Just a quick guess
Click to expand...
Click to collapse
Thanks , kindly post the installation log found at C:\AndroidInstall_XXX.log as this give me info about conditions where installation is successful/unsuccessful
For booting to Android we may have 2 options:
- Desktop shortcut "Reboot to Android"
- Set GRUB as default bootloader

ExtremeGTX said:
Thanks , kindly post the installation log found at C:\AndroidInstall_XXX.log as this give me info about conditions where installation is successful/unsuccessful
For booting to Android we may have 2 options:
- Desktop shortcut "Reboot to Android"
- Set GRUB as default bootloader
Click to expand...
Click to collapse
I think, that setting GRUB as default bootloader would be definitely great way to do this. But, of course, whatever you think it's better and/or easier to do
Anyway, my device is (as stated before) ASUS T100TAM (Intel Atom z3775, 2GB RAM, UEFI device), running Windows 10 Home x86. Secure boot, of course, disabled. Adding install log as an attachment.

So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk

dokie80 said:
So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am not the creator of this app, but since I used it succesfully, I can definitely answer these questions:
1. No, you don't need to worry about that.
2. Yes, exactly - all data will be in this folder (as it is on my TF100)
3. It creates "data.img" file inside the "C:\androidos" folder and you can select how big that .img file should be (for storing your Android data). No partitioning - basically everything happens inside the "androidos" folder.

Thanks for the reply.
Whats the benefit of this method over the magic stick one anyway ?
I'm going to try this tomorrow
Thanks
Sent from my Nexus 5 using Tapatalk

dokie80 said:
Thanks for the reply.
Whats the benefit of this method over the magic stick one anyway ?
I'm going to try this tomorrow
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The biggest benefit is (obviously) that you don't need any flash drive for this - everything is done from your tablet's memory (basically a dualboot) and it's very, very easy to do this.

AFAIK, you can install the android x86 to via magic stick, although I haven't try it yet. I'm using it for Ubuntu. Did you use it daily? How about battery life and performance? Can't wait to try
Sent from my Nexus 5 using Tapatalk

Well yeah, you can, but AFAIK you would have to do repartitioning as if you were installing regular dualboot system - that's something you don't have to do here.
Performance is great as expected, very snappy, I've been running KitKat 4.4-r3, Lollipop 5.1 was very unstable for me. Battery life seems great, too, not exactly sure though, since I've been playing with it for two days now

spenat said:
I think, that setting GRUB as default bootloader would be definitely great way to do this. But, of course, whatever you think it's better and/or easier to do
Anyway, my device is (as stated before) ASUS T100TAM (Intel Atom z3775, 2GB RAM, UEFI device), running Windows 10 Home x86. Secure boot, of course, disabled. Adding install log as an attachment.
Click to expand...
Click to collapse
Thanks for posting the log.
My only concern with setting GRUB as default bootloader if GRUB has a problem running on the device the user may think that the device is bricked and no longer usable, anyway we will check back on that.
dokie80 said:
So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
exactly as @spenat told you.
the Advantage of this installer is you will not mess up anythings, no re-partitioning at all or corrupting the current installation of windows. All of the magic just live in <Drive:>\AndroidOS
and if you don't like it you can launch the installer and click on "Cleanup Android" you can check all installation steps in log if you have any concerns.
Thanks
spenat said:
I am not the creator of this app, but since I used it succesfully, I can definitely answer these questions:
1. No, you don't need to worry about that.
2. Yes, exactly - all data will be in this folder (as it is on my TF100)
3. It creates "data.img" file inside the "C:\androidos" folder and you can select how big that .img file should be (for storing your Android data). No partitioning - basically everything happens inside the "androidos" folder.
Click to expand...
Click to collapse
spenat said:
Well yeah, you can, but AFAIK you would have to do repartitioning as if you were installing regular dualboot system - that's something you don't have to do here.
Performance is great as expected, very snappy, I've been running KitKat 4.4-r3, Lollipop 5.1 was very unstable for me. Battery life seems great, too, not exactly sure though, since I've been playing with it for two days now
Click to expand...
Click to collapse
Thanks for your clear answers, appreciate your help

installing now. will I be able to change data size later?

dokie80 said:
installing now. will I be able to change data size later?
Click to expand...
Click to collapse
You can only change data size before you actually install the Android. If you wanna change it later, you need to remove Android and install it again with different data size, AFAIK.

working fine here T100TA, well.. the installation that is.
on android x86, I got a freeze on wifi setting... force close and re-set works fine..
if you dont mind me asking questions:
1. what method are you using for this to work? I dont need it to be detailed, I just curious what's it called, and how AndroidOS listed on device option on advanced boot
2. how to do nandroid backup? I assume for "dirty flash" : I backup data.img and put back after new installation? with the downside is data size is from previous setup?
3. I see that sdcard is mounted, but havent try to see it with file explorer, I assume the whole C: is mounted or probably only AndroidOS folder? so I can do Titanium Backup saved there?
4. for now, I have to boot to windows and boot to android using advanced boot? so without keyboard attached, I have to choose settings - recovery - advanced startup? will it be possible to boot using grub bootloader? I'm planning to dual boot with linux later. just realize that it also show up on boot selection.
many thanks for this. attached is the log found at C:

dokie80 said:
working fine here T100TA, well.. the installation that is.
on android x86, I got a freeze on wifi setting... force close and re-set works fine..
if you dont mind me asking questions:
1. what method are you using for this to work? I dont need it to be detailed, I just curious what's it called, and how AndroidOS listed on device option on advanced boot
2. how to do nandroid backup? I assume for "dirty flash" : I backup data.img and put back after new installation? with the downside is data size is from previous setup?
3. I see that sdcard is mounted, but havent try to see it with file explorer, I assume the whole C: is mounted or probably only AndroidOS folder? so I can do Titanium Backup saved there?
4. for now, I have to boot to windows and boot to android using advanced boot? so without keyboard attached, I have to choose settings - recovery - advanced startup? will it be possible to boot using grub bootloader? I'm planning to dual boot with linux later. just realize that it also show up on boot selection.
many thanks for this. attached is the log found at C:
Click to expand...
Click to collapse
Thanks for testing and posting the install log
Answers:
1. Check section "Under the hood" in the first post or check the installer log you have posted, it will give you an idea about the magic
2. This is an old request from a few users to allow reinstall/update android without removing userdata. Till now your workaround is valid, I think you will see message like this one [LINK] at the first boot after upgrade.
3. I 'm not sure right now.
4. here are 2 solutions to access Android:
a Shortcut on Desktop "Reboot to Android"
Set GRUB as default Bootloader, I can't do this right now as the app still in alpha stage and a lot of testing is needed. i don't want to mess up devices with something not ready yet, so currently i just add GRUB to UEFI Boot options but don't make it the default one.
Thanks for your feedback and questions

Just a quick tip to make dual-booting even easier:
Set the "Boot Option #1" in BIOS to Android-OS (instead of Windows Boot Manager), this way it will always boot to GRUB. Just one catch: You will need a keyboard to move in GRUB, or you will always boot to Android But, of course, you can anytime switch back to Windows Boot Manager as default, as long as you can access BIOS
Anyway, just tried this app on my brother's tablet (Lenovo Miix 3 10"), will add installation log ASAP.

[ROOT - ZS570KL] ZenUtil + everything you need to root the Z016D quickly and easily!

ZenUtil was created for use with the Zenfone 3 Deluxe Special Edition ONLY.
Hello everyone my name is Sandman45654. I would like to share a little root utility I put together in my free time over the last couple of weeks. After not having much luck with the root packages/images I found here on XDA and the internet in general I decided to create my own solution! ZenUtil was created specifically for the Zenfone 3 Deluxe Special Edition (SD821) and has been tested on seven different computers. Four physical and three virtual machines. Operating systems from Windows 7 through the latest Windows 10 build have all been tested. Two machines even had fresh Windows installations with no prior ADB driver installations and Wi-Fi set to disabled to ensure drivers were in fact installing and not downloading! This package includes EVERYTHING to get the job done quickly and easily!
Screenshots:
View attachment 4270854 View attachment 4270855 View attachment 4270856
View attachment 4270857 View attachment 4270859 View attachment 4270860
Features:
1. Completely menu driven CMD file! Typing or remembering commands is not required.
2. ZenUtil is able to create a support files (help/uninstaller/log files) dynamically.
3. Install Asus ADB Drivers. Fastboot drivers are also installed but not enabled by default. Instructions below.
4. Install the Asus UnlockTool v1.1 onto your phone.
5. Push the SuperSU 2.82 zip file into \sdcard\ in preparation for rooting.
6. Push just about any file or folder, even over network shares into \sdcard\. Supports drag & drop too!
7. Able to boot TWRP 3.1.1-0 without flashing.
8. Able to boot included stock Asus recovery image (v5.15.44.2562) without flashing. Boots upside down for some reason but works.
9. Reboot into the recovery that is currently installed.
10. Reboot into Fastboot mode.
11. Exit out of Fastboot mode. No more holding for power button for days!
12. Able to flash TWRP 3.1.1-0
13. Flash/restore stock Asus recovery image. It does not boot upside down when flashed.
14. Remove any lock screen PIN/Password/Pattern. Useful after restoring a Nandroid and getting "Incorrect PIN" error.
15. ADB transfers are check and verified as either successful or failed.
16. ADB transfers are also logged with date/timestamps and shown automatically on error.
17. The ADB log file is deleted on each launch to keep it small, clean, and simple.
18. Confirms before any "permanent" actions are completed. (Flash / Pin Removal / Uninstall)
19. Maybe more to come...
ZenUtil will be updated with the latest image files for the foreseeable future regardless.
Included files and versions with notes.
ADB Files = 1.4.2 Minimal (Preferred for logging)
Asus Stock Recovery = Z016_1-WW-5.15.44.2562_recovery.img
Asus UnlockTool v1.1 = UnlockTool-9.0.0.29_ZS570KL_PRO.apk
TWRP = twrp-3.1.1-0-Z016-20170826.img
NO LAG ON BOOT with this version of TWRP!!! I was also able to create, wipe, and restore without the issues of previous versions. Might this be the one?!
Finishing Fastboot driver installation.
Your phone must be connected and in fastboot mode before you are able to install the drivers.
1. Right click on the start button and select "Device Manager" or WinKey+R>devmgmt.msc>enter
2. Right click on "Android" with a yellow ! next to it and select "Update driver".
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of available drivers on my computer"
5. Select "ASUS Android Device" and click next.
6. Select "ASUS Android Bootloader Interface Version: 8.0.0.3 [3/16/2015]" and click next.
7. Click "Yes"
8. Click "Close"
A HUGE thank you goes out to Judago for creating CmdMenuSel!
Downloads:
Download ZenUtil v1.0
Fastboot Help Files (with pics)

hello
I have the ASUS Zenfone 3 Deluxe ZS570KL (Z016S)
but I can not do it ROOT
if it does HELP

alkis68 said:
hello
I have the ASUS Zenfone 3 Deluxe ZS570KL (Z016S)
but I can not do it ROOT
if it does HELP
Click to expand...
Click to collapse
According to the page below that phone has the Snapdragon 820 and not the 821. So there is high likelihood that this would fail. If the included Twrp is compatible across both phones you could install the bootloader unlock tool from Asus website and then finish rooting with Zenutil. I cannot however say for certain that Twrp would be compatible.
https://www.mobosdata.com/asus-zenfone-3-deluxe-z016s#

Any chance of getting this uploaded again, it's no longer available

How To Guide Flash stock ROM or downgrade ColorOS 12 on OPPO Reno6 5g(CPH2251-MT6877 chip) by using free MTK client GitHub tool.

Hey Guys,
After color OS 12 (and android 12) upgrade on OPPO reno6 5G device, users were facing issues like third part apps not working(Intune company portal work profile, Ritam news app etc),battery draing very rapidly,always on display not working and many more.
So, here I have come up with a method to flash stock ROM or downgrade color OS 12 and switch back to Color OS 11.3 which have android 11. So without wasting time lets start
Note: Data will be erased in this method so please take backup of you data on phone.
This has been tested on Indian version, I am not sure if it will work for other countries.
I strongly recommend to take full firmware backup using method below before proceeding
Backup full firmware(ROM) of any MediaTek device using MTK client| Oppo reno6 5G | MT6877
Hello Guys, Many times we encounter a situation where we need to do some software update, flash custom ROM, install stock ROM etc, so it is advisable to take full firmware/ROM backup of your device. If required then you can flash this backup to...
forum.xda-developers.com
Step1: Pre-requisite -Installing required drivers and setup
From links below download and install drivers and setup.
Install mediaTek driver.
Install python (during installation of python please select "install for all user" from customization and tick add path to system variable).
install usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
In default setting it takes 2 hour to flash but after change it takes 13 min only. So, If you want to increase flashing speed then open mtk_daxflash.py file from library folder, search "dsize = min(length, 0x200)" and replace it with "dsize = min(length, 0x2004)" , save and close the file.
You need to close the command prompt and reopoen it in order to take effect of change.
Reference(https://github.com/bkerler/mtkclient/issues/271)
New Qcom Mtk Driver V3.0.5.1.rar | by TUSER HP for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download Python
The official home of the Python Programming Language
www.python.org
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
Step2: Download and extract the stock firmware
CPH2251_A.13_ColorOS11.3_Android11_Latest.rar
drive.google.com
Step3: Flash the firmware
on cmd type below command to flash the firmware
python mtk wl "stock ROM location full path"
it will wait for devices.. Power off the phone, wait 10 sec then press vol up + vol down together and then plug the usb cable.
Once device detected , it will display devices information and start flashing
While flashing it will dump the preloader, this file is very important so, please keep this file safely. this file may require in future.
Step4: Boot the phone
Once flashing completed, press vol up + power button together for 30 sec. Wait for device to boot.
Step5: Flashing the preloader.bin (only if required)
In case, even after flashing completed successfully but some time device does not boot, only black screen, no charging sign either then don't panic, device has entered into emergency download mode, if you face the same then it's time to flash preloader.bin file. Follow below steps
1) download SP flash tool specific version v5.2148. (https://androidmtk.com/smart-phone-flash-tool)
2) download attached preloader.bin, scatter file and auth file from link below and place all these files at same folder.
MT6877_flashing_preloader.zip
drive.google.com
3) open sp flash tool, select download agent files from mtk folder as shown on image and load scater file and auth files respectively.
4) In cmd run command "python mtk payload". Now press and hold vol+ vol- or all the buttons together, it should show payload sent successfully.
5) Now in sp flash tool click on Download button, it should flash the preloader successfully.
6) once preloader is flash successfully you can turn on the phone by pressing vol+ and power button together for 20 sec. If attached preloader does't flash then you can try flashing your device backup preloader.bin created/shown on step3.
So by this way we flashed stock firmware on oppo reno6 5G.
Tips: If due to some reason flashing did not completed successfully then please press vol up and power button together for 30-40 sec to boot the phone (exit the brom mode).
Disclaimer: I have tested this method on my phone, it's 100% working but I will not responsible if damage any damage happens to your device while doing this. So do it at your own risk.

It's work sir
Many thanks
Nand kumar said:
Step1: Pre-requisite -Installing required drivers and setup
Install MediaTek drivers, in windows 10 you need to disable driver signature enforcement.
Install paython, usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
Click to expand...
Click to collapse
In this step the command should be
pip install -r requirements.txt
it's will work

killian07 said:
It's work sir
Many thanks
In this step the command should be
pip install -r requirements.txt
it's will work
Click to expand...
Click to collapse
Did you also took firmware back using my method or you just flashed the ROM?

Thanks for your work

You are welcome sir.

Edit : Comment removed it can create confusion

Edit : Comment removed it can create confusion

Thank you

Edit : Comment removed it can create confusion

Edit : Comment removed it can create confusion

Thank you sir

Edit : Comment removed it can create confusion

Thank you

Edit : Comment removed it can create confusion

Edit : Comment removed it can create confusion

Nand kumar said:
Hey Guys,
After color OS 12 (and android 12) upgrade on OPPO reno6 5G device, users were facing issues like third part apps not working(Intune company portal work profile, Ritam news app etc),battery draing very rapidly,always on display not working and many more.
So, here I have come up with a method to flash stock ROM or downgrade color OS 12 and switch back to Color OS 11.3 which have android 11. So without wasting time lets start
Note: Data will be erased in this method so please take backup of you data on phone.
I strongly recommend to take full firmware backup using method below before proceeding
Backup full firmware(ROM) of any MediaTek device using MTK client| Oppo reno6 5G | MT6877
Hello Guys, Many times we encounter a situation where we need to do some software update, flash custom ROM, install stock ROM etc, so it is advisable to take full firmware/ROM backup of your device. If required then you can flash this backup to...
forum.xda-developers.com
Step1: Pre-requisite -Installing required drivers and setup
Install MediaTek drivers, in windows 10 you need to disable driver signature enforcement.
Install paython, usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
View attachment 5541629
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip | by karimovic44 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download Python
The official home of the Python Programming Language
www.python.org
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
Step2: Download and extract the stock firmware
View attachment 5541657
CPH2251_A.13_ColorOS11.3_Android11_Latest.rar
drive.google.com
Step3: Flash the firmware
on cmd type below command to flash the firmware
python mtk wl "stock ROM location full path"
it will wait for devices.. Power off the phone, wait 10 sec then press vol up + vol down together and then plug the usb cable.
Once device detected , it will display devices information and start flashing
View attachment 5541639
View attachment 5541641
View attachment 5541645
While flashing it will dump the preloader, this file is very important so, please keep this file safely. this file may require in future.
View attachment 5541661
Step4: Boot the phone
Once flashing completed, press vol up + power button together for 30 sec. Wait for device to boot.
so by this way we flashed stock firmware on oppo reno6 5G.
Tips: If due to some reason flashing did not completed successfully then please press vol up and power button together for 30-40 sec to boot the phone (exit the brom mode).
Disclaimer: I have tested this method on my phone, it's 100% working but I will not responsible if damage any damage happens to your device while doing this. So do it at your own risk.
Click to expand...
Click to collapse
Thank you sir, it's working.
I followed this method and now I have successfully downgraded my ColorOs 12 to ColorOs 11.3 on my oppo reno6 5g.

How To Guide Backup full firmware(ROM) of any MediaTek device using MTK client| Oppo reno6 5G | MT6877

Hello Guys,
Many times we encounter a situation where we need to do some software update, flash custom ROM, install stock ROM etc, so it is advisable to take full firmware/ROM backup of your device. If required then you can flash this backup to restore your device.
We will use MTK client Github tool for this backup process and using same tool we can flash the backup firmware.
This method has been tested on OPPO Reno6 5G which is powered by MediaTek MT6877 chip. Backup size was approx 12 GB. Using this method you can backup firmware of any other supported MediaTek chip in this tool. In this method I don't backup userdata because this tool backups entire partition size irrespective of actual data stored.
Step1: Pre-requisite -Installing required drivers and doing setup
Install MediaTek driver.
Install python(during installation of python please select "install for all user" from customization and tick add path to system variable).
install usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
View attachment 5541629
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip | by karimovic44 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download Python
The official home of the Python Programming Language
www.python.org
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
Step2: Create a new folder/directory in your computer to store the backup files.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step3: Run full firmware backup
In cmd run command below, please skip userdata partition only because of very huge size.
python mtk rl --skip userdata "<full path to store the backup files>"
Once all the partitions dumped it will show message "All dumped partitions success"
During backup process it will dump the device preloader, this file is very important so, please keep this file safely. this file may require in future.
Step3: Reboot the phone
Once backup is done, you can restart your phone by pressing vol up and power button together for 30 sec.
Step4: How to Restore (if required)
Backup process might have created approximately 58 files but we do not need to flash all those files.
We only need to flash below files, so create a new folder and copy all these 33 files from original backup to your newly created folder.
audio_dsp.bin
boot.bin
cam_vpu1.bin
cam_vpu2.bin
cam_vpu3.bin
cdt_engineering.bin
dpm_1.bin
dpm_2.bin
dtbo.bin
gpt_backup.bin
gpt_main.bin
gz1.bin
gz2.bin
lk.bin
lk2.bin
logo.bin
mcupm_1.bin
mcupm_2.bin
md1img.bin
oplusreserve2.bin
pi_img.bin
recovery.bin
scp1.bin
scp2.bin
spmfw.bin
sspm_1.bin
sspm_2.bin
super.bin
tee1.bin
tee2.bin
vbmeta.bin
vbmeta_system.bin
vbmeta_vendor.bin
open cmd and type below command
python mtk wl "<full path where 33 files are stored>"
Backup should be restored on same device from which it was taken else device may brick.
Thanks and Regards
Nand,

thanks a lot why only 33 files restored ?

Please please, i have a question. can i use that firmware on oppo reno4 z 5G, has a model CPH2065
if not where i can find one for my device?
please i have oppo reno4 z 5G and model number CPH2065

jason__ said:
Please please, i have a question. can i use that firmware on oppo reno4 z 5G, has a model CPH2065
if not where i can find one for my device?
please i have oppo reno4 z 5G and model number CPH2065
Click to expand...
Click to collapse
No. you can NOT use.

Nand kumar said:
No. you can NOT use.
Click to expand...
Click to collapse
please where can i find fireware for my model. i searched everywhere and i can't find it.

jason__ said:
please where can i find fireware for my model. i searched everywhere and i can't find it.
Click to expand...
Click to collapse
Try this. I think You need to buy unlock tool license to flash the firmware. Search unlock tool.net in google.
https://oppostockrom.com/oppo-reno-4-z-5g-cph2065

Nand kumar said:
Try this. I think You need to buy unlock tool license to flash the firmware. Search unlock tool.net in google.
https://oppostockrom.com/oppo-reno-4-z-5g-cph2065
Click to expand...
Click to collapse
is it country neutral? what does that PU stand for?
i appreciate your time so much for trying to help me out.

jason__ said:
is it country neutral? what does that PU stand for?
i appreciate your time so much for trying to help me out.
Click to expand...
Click to collapse
Firmware size is 8 gb so I think it support all countries. You will get drop down list to select country while flashing. Download and extract and see if it has ofp file

okay sir, i'll get back to you when it's downloaded.

Nand kumar said:
Firmware size is 8 gb so I think it support all countries. You will get drop down list to select country while flashing. Download and extract and see if it has ofp file
Click to expand...
Click to collapse
Sorry for being late sir.
Yeah it has that file. but i installed realme flash, and some drivers were available in the package. then when i try to fastboot my phone (down volume key + power key) i find that my phone is not accessible.
i download every possible driver that i could find online and nothing.
also, when i try to fastboot my phone, i enter recovery mode. are they the same?
Please help me.

jason__ said:
Sorry for being late sir.
Yeah it has that file. but i installed realme flash, and some drivers were available in the package. then when i try to fastboot my phone (down volume key + power key) i find that my phone is not accessible.
i download every possible driver that i could find online and nothing.
also, when i try to fastboot my phone, i enter recovery mode. are they the same?
Please help me.
Click to expand...
Click to collapse
i think you need to enter EDL mode aka download mode and not fastboot for that tool...

Nand kumar said:
Hello Guys,
Many times we encounter a situation where we need to do some software update, flash custom ROM, install stock ROM etc, so it is advisable to take full firmware/ROM backup of your device. If required then you can flash this backup to restore your device.
We will use MTK client Github tool for this backup process and using same tool we can flash the backup firmware.
This method has been tested on OPPO Reno6 5G which is powered by MediaTek MT6877 chip. Backup size was approx 12 GB. Using this method you can backup firmware of any other supported MediaTek chip in this tool. In this method I don't backup userdata because this tool backups entire partition size irrespective of actual data stored.
Step1: Pre-requisite -Installing required drivers and doing setup
Install MediaTek driver.
Install python(during installation of python please select "install for all user" from customization and tick add path to system variable).
install usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
View attachment 5541629
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip | by karimovic44 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download Python
The official home of the Python Programming Language
www.python.org
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
Step2: Create a new folder/directory in your computer to store the backup files.
View attachment 5543511
Step3: Run full firmware backup
In cmd run command below, please skip userdata partition only because of very huge size.
python mtk rl --skip userdata "<full path to store the backup files>"
View attachment 5543497
View attachment 5543501
Once all the partitions dumped it will show message "All dumped partitions success"
During backup process it will dump the device preloader, this file is very important so, please keep this file safely. this file may require in future.
Step3: Reboot the phone
Once backup is done, you can restart your phone by pressing vol up and power button together for 30 sec.
Step4: How to Restore (if required)
Backup process might have created approximately 58 files but we do not need to flash all those files.
We only need to flash below files, so create a new folder and copy all these 33 files from original backup to your newly created folder.
audio_dsp.bin
boot.bin
cam_vpu1.bin
cam_vpu2.bin
cam_vpu3.bin
cdt_engineering.bin
dpm_1.bin
dpm_2.bin
dtbo.bin
gpt_backup.bin
gpt_main.bin
gz1.bin
gz2.bin
lk.bin
lk2.bin
logo.bin
mcupm_1.bin
mcupm_2.bin
md1img.bin
oplusreserve2.bin
pi_img.bin
recovery.bin
scp1.bin
scp2.bin
spmfw.bin
sspm_1.bin
sspm_2.bin
super.bin
tee1.bin
tee2.bin
vbmeta.bin
vbmeta_system.bin
vbmeta_vendor.bin
open cmd and type below command
python mtk wl "<full path where 33 files are stored>"
Backup should be restored on same device from which it was taken else device may brick.
Thanks and Regards
Nand,
Click to expand...
Click to collapse
Can I ask how much time will it take to backup without userdata

hi i want this backup

idk why but my hanshake keeps failing.
i installed drivers as mentioned,but no coms showing up on device manager.
i think that when we install all drivers it usually shows like mtk device in devmgr,but it doesnt.
also i cant go to preloader mode easily.when i switch off phone and connect usb,it automatically turns back on.
why does it keep failing please help.are there any other methods for backup.like using sp flashtool.
pls help someone.

mohdsha said:
View attachment 5695877
idk why but my hanshake keeps failing.
i installed drivers as mentioned,but no coms showing up on device manager.
View attachment 5695881
i think that when we install all drivers it usually shows like mtk device in devmgr,but it doesnt.
also i cant go to preloader mode easily.when i switch off phone and connect usb,it automatically turns back on.
why does it keep failing please help.are there any other methods for backup.like using sp flashtool.
pls help someone.
Click to expand...
Click to collapse
ihave the same issue, did you find any solution to going into preloading?

mamomia said:
ihave the same issue, did you find any solution to going into preloading?
Click to expand...
Click to collapse
no bro.. im still trying .. i use a 5a cable..maybe we need og cable to coonect.idk i will try some troubleshooting.if successfull ,i will let you know.

Nand kumar said:
python mtk wl "<full path where 33 files are stored>"
Backup should be restored on same device from which it was taken else device may brick.
Click to expand...
Click to collapse
can a backup of the 33 files be applied to a new device which is exactly the same model without bricking it? (ie. a rom transfer to create a clone onto second device)

Hello and thank you so much for your guide. I was able to get everything setup for the most part, but I am held up by two problems, I'm sure they are simple but I would appreciate any help if anyone knows the answer.
Problem number one, is the correct vcom driver, the preloader one as shown in this
Spoiler: PIC
Or should I be using another?
My other question is, what is the correct terminology for what we are trying to achieve by getting the phone to register in the MTK client? Like, are we trying to get it to "boot into preloader mode"?
Spoiler: PIC
I am unable to get my phone to register or show in device manager or with the mtk client, to get it to post into the "preloader" mode. Since I do not know how to adequately describe what I am trying to do, I am having a hard time even searching on google for more help. If anyone can give me any help in grammer google search or direct knowledge on this simple part i would appreciate it

The answer to the driver question is to install all of them not just one. This discussion on reddit has some comments which go into more discussion of the bootrom protection and other github repos to achieve this. So to answer my main question about the phone not being detected by the MTK client it seems there is one more step for myself and other folks in this condition.
Spoiler: show link
https://www.reddit.com/r/androidroot/comments/wj6zrv
This guide explains how the MTK devices load the preloader. It is only up for 1 second apparently
Spoiler: show link
https://www.reddit.com/r/Smartphoneforensics/comments/xwd562

thanks a lot!!!! i have installed easily mtk client on garuda linux, and works very well (used for restore stook boot and solve a bootloop that seems impossible to solve). this guide is what i'm searching from some week. a way to do a full backup of my phone, userdata included
my suggestion for install mtkclient and other android tool is switch to garuda linux. if you try linux, you will never use windows again. garuda app manager with chaotic-aur have all software that you need. try to believe

Oukitel WP17 [Root][GSI ARM64 A/B Treble-Enabled]

WP17 is a rugged phone with Infrared Night Vision Camera, Helio G95 8GB+128GB 6.78“FHD+ 90Hz 64MP Triple Camera+16MP Selfie 8300mAh Android 11 Global Version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bought me a Oukitel WP17, but couldn't find much information about this phone.
So I'm going to post info here for everyone to see and participate in how to flash, root and update the phone.

Update:
Using the MTK-bypass Small utility to disable bootrom protection(sla and daa).
According to this Exploit, this MT6785 Oukitel WP17 is fully unlocked, and should be flashable:
Windows10:
[2022-10-13 02:45:23.376773] Found device = 0e8d:0003
[2022-10-13 02:45:23.766358] Device hw code: 0x813
[2022-10-13 02:45:23.776413] Device hw sub code: 0x8a00
[2022-10-13 02:45:23.786386] Device hw version: 0xca00
[2022-10-13 02:45:23.796588] Device sw version: 0x0
[2022-10-13 02:45:23.806536] Device secure boot: False
[2022-10-13 02:45:23.816739] Device serial link authorization: False
[2022-10-13 02:45:23.816739] Device download agent authorization: False
[2022-10-13 02:45:23.836660] Disabling watchdog timer
[2022-10-13 02:45:23.846734] Insecure device, sending payload using send_da
[2022-10-13 02:45:23.896695] Found send_dword, dumping bootrom to bootrom_813.bin
Linux:
[2022-10-13 09:15:03.350097] Found port = /dev/ttyACM0
[2022-10-13 09:15:03.423994] Device hw code: 0x813
[2022-10-13 09:15:03.425119] Device hw sub code: 0x8a00
[2022-10-13 09:15:03.425523] Device hw version: 0xca00
[2022-10-13 09:15:03.425902] Device sw version: 0x0
[2022-10-13 09:15:03.426248] Device secure boot: False
[2022-10-13 09:15:03.426595] Device serial link authorization: False
[2022-10-13 09:15:03.426923] Device download agent authorization: False
However, flashing this phone in any Sp flash tool, is ending up in:
ERROR : STATUS_SEC_PUBK_AUTH_MISMATCH_N (0xC002001B)
​The PUBK_AUTH part of this error message, is the Authorization for flashing Signed/verified image files. In the Oukitel WP17 firmware folder, downloaded from Oukitel Downlod Center, are their only certain files marked as verified.img, and now after testing in Sp flash tool, loading ALL non-verified files, you can flash these files to the phone without problems.
.

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.
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.
​
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.
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.
4. Right-click and copy the address and paste it in the prompt window.
​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.
Code:
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.
Code:
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
​Press Enter,
On the phone: Hold down Volume+ Volume- and power-button together, hold the buttons until the flashing start. Sit back and wait
.
​Your phone will end up like this after boot.
Done ....
Now Update your phone by Android update service by going in to 'Settings / System and update phone.
.

-- IMEI Restore --​
After formatting the phone. I use ModemMETA tool to restore my IMEI.
​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”.
Now click on search box and select IMEI download option from drop down menu.
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
if everything went well, it looks like this.​
​

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 -
​
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.
​Install Magisk25.
.

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

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 ...​
​Android 13 ...​
​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.
​Go to the download page and select the latest version.
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.
​Double-click on AA - Install Android.
Turn off your phone.
Press and hold Volume+ Power and Ptt button until you get to the bootloader menu.
Select Fastboot mode.
​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.
​The installation script will install your chosen Android version and reboot the phone when everything is done. After boot install Magisk25.
.
​

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.

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!

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

--- BlissOS Android 13 and lightning fast ---​
​
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.
Enjoy ...

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.
Here is the file you flash to get rid of that Red txt…
Code:
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.
.
.

.....

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 ?

JustNabus said:
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 ?
Click to expand...
Click to collapse
.
The IMEI fix: https://forum.xda-developers.com/t/...rm64-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.
.

SwedishForenger said:
.
The IMEI fix: https://forum.xda-developers.com/t/...rm64-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.
.
Click to expand...
Click to collapse
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

.
Yes. just copy and paste these numbers. Ore just scramble the numbers around.
IMEI 1: 35524555061532
IMEI 2: 35524555061573
​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.
.

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:
Code:
adb devices
pm uninstall -k --user 0 com.mediatek.engineermode
Reboot the phone.
.

noob here, can you create a youtube video on how to install a custom rom to this phone?

dalelad said:
noob here, can you create a youtube video on how to install a custom rom to this phone?
Click to expand...
Click to collapse
.
It's not relay necessary.
There are only 4 small simple steps to perform, the Installer does everything else for you.
Oukitel WP17 [Root][GSI ARM64 A/B Treble-Enabled]
WP17 is a rugged phone with Infrared Night Vision Camera, Helio G95 8GB+128GB 6.78“FHD+ 90Hz 64MP Triple Camera+16MP Selfie 8300mAh Android 11 Global Version. Bought me a Oukitel WP17, but couldn't find much information about this phone. So...
forum.xda-developers.com
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
.