Database Info

[ROM] official B206 for GEM-702L, march 2018

Since March 12th 2018, Huawei has released on its OTA server a new rom for GEM-702L device :
GEM-702LC209B206 available as "incremential update OTA" (instalable at least on GEM-702LC209B205)
GEM-702LC209B206CUSTC209D001 as "Full OTA".
Changelog is:
Optimizes system stability.
Integrates Google security patches for improved system security.
radio update
firmwareupdate
You can try a official dload of this complete rom, following these isntructions (need to be verified, not sure that dload install will work, then firmware finder below is 100% working installation soltuion)
You can view the OTA on:
https://translate.google.com/transl...l=GEM-702L&firmware_page=0&edit-text=&act=url
You can even download them there. BUT to install them, it's only possible through "Firmware Finder" app or windows software:
https://play.google.com/store/apps/...refinder&ah=u60E7LEmAezozHpNPibQ4HLWhp0&hl=ru
http://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Android app and its proxy is recommended, you'll find plenty of video tutorials:
https://www.youtube.com/watch?v=jm5pFNCO5v8&t=18s&list=PLgw3d3fHTj5E33lNsLcCwcgoraZmfin7V&index=13
https://www.youtube.com/playlist?list=PLgw3d3fHTj5E33lNsLcCwcgoraZmfin7V
Note that the downloaded full OTA file could also by installed through Huawei updater, but it's more tricky than the Firmware Finder app:
https://forum.xda-developers.com/me...ol-huawei-updater-mediapad-x2-hajuuk-t3660689

Also mentioned here
Please report, if you were able to root this version. If yes please zip the system folder and send it to AJ. He could make a new ROM based on this version.
Please test if you have push or GPS problems.

audioralf said:
Also mentioned here
Please report, if you were able to root this version. If yes please zip the system folder and send it to AJ. He could make a new ROM based on this version.
Please test if you have push or GPS problems.
Click to expand...
Click to collapse
Thanks for this link, with file directly installable with official dload method. But this has to be verified, because this site was already wrong on this precise point, for a previous 702L update.
If this work, I wonder if this file is directly installable on 701L or 703L device.
By the way @ajsmsg78 should be able to install this rom on his 703L. Either directly as mentioned above, or by transforming softwarely the device into 702L (by installing : downgrade script, B203 demo, B205). Isn't it?

Djiban said:
Thanks for this link, with file directly installable with official dload method. But this has to be verified, because this site was already wrong on this precise point, for a previous 702L update.
If this work, I wonder if this file is directly installable on 701L or 703L device.
By the way @ajsmsg78 should be able to install this rom on his 703L. Either directly as mentioned above, or by transforming softwarely the device into 702L (by installing : downgrade script, B203 demo, B205). Isn't it?
Click to expand...
Click to collapse
The new B206 update also has a radio update as well as some firmware. The only way to update to that radio and firmware is to flash it on a supported device. However I am finishing up a B206 rom that I put together based off of this and will have it done soon.

ajsmsg78 said:
The new B206 update also has a radio update as well as some firmware. The only way to update to that radio and firmware is to flash it on a supported device.
Click to expand...
Click to collapse
Ok, hope a 702L user will install it , and send the system folder to ajsmsg78

Djiban said:
Since March 12th 2018, Huawei has released on its OTA server a new rom for GEM-702L device :
GEM-702LC209B206 available as "incremential update OTA" (instalable at least on GEM-702LC209B205)
GEM-702LC209B206CUSTC209D001 as "Full OTA".
Changelog is:
Optimizes system stability.
Integrates Google security patches for improved system security.
radio update
firmwareupdate
You can try a official dload of this complete rom, following these isntructions (need to be verified, not sure that dload install will work, then firmware finder below is 100% working installation soltuion)
You can view the OTA on:
https://translate.google.com/transl...l=GEM-702L&firmware_page=0&edit-text=&act=url
You can even download them there. BUT to install them, it's only possible through "Firmware Finder" app or windows software:
https://play.google.com/store/apps/...refinder&ah=u60E7LEmAezozHpNPibQ4HLWhp0&hl=ru
http://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Android app and its proxy is recommended, you'll find plenty of video tutorials:
https://www.youtube.com/watch?v=jm5pFNCO5v8&t=18s&list=PLgw3d3fHTj5E33lNsLcCwcgoraZmfin7V&index=13
https://www.youtube.com/playlist?list=PLgw3d3fHTj5E33lNsLcCwcgoraZmfin7V
Note that the downloaded full OTA file could also by installed through Huawei updater, but it's more tricky than the Firmware Finder app:
https://forum.xda-developers.com/me...ol-huawei-updater-mediapad-x2-hajuuk-t3660689
Click to expand...
Click to collapse
Hi! I have a mediapad X2 702L. It is not rooted, bootloader is not unlocked and without recovery..
I want to install a new stock rom with android 6.0.
Can I install this rom directly with dload metod??
Thanks!!

[ROOT]Root Guide for Huawei MediaPad M5

DISCLAIMER: I'm not responsible for anything that happens to your device. Use the steps below at your own risk . Be mindful of the facts unlocking bootloader voids your warranty and also hard resets your device - ALL YOUR DATA, SETTINGS, FILES AND APPS WILL BE DELETED. Rooting your device voids warranty as well. I own the Chinese SHT-AL09 8.4" LTE device and tested this root procedure ONLY WITH THIS MODEL. However, I believe there is a good chance the steps below will work for all other models of MediaPad M5, including WiFi only variants and 10" models. You MUST unlock your bootloader first. Do NOT use ramdisk image I provide in the steps below for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. Ramdisk I provided is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Credits:
@Wirmpolter - this root method largely based on his Magisk guide for Mate 9
@topjohnwu for creating the awesome Magisk Manager, which was used to patch ramdisk image with superuser binary
People, who created HuaweiUpdateExtractor
@magnumlove who pointed me in the right for developing root method in this post
This site, for hosting stock firmware for Huawei MediaPad M5
1. First, you will need to unlock the bootloader of your M5. Follow this guide
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
3. Once bootloader is unlocked, install latest Magisk Manager from the official Magisk thread
4. Once Magisk Manager gives you a pop-up prompt to either download Magisk zip or patch the boot image file - chose to patch the boot image, but instead of boot.img select ramdisk.img from step 2. Magisk Manager should give you a message the image was successfully patched. It will be saved as patched_boot.img in MagiskManager folder on your sdcard. If it does not say success - do NOT proceed
5. Transfer the newly created patched_boot.img back to your PC
6. If you already have ADB and Fastboot tools installed on your PC you can just use what you've got. If not - get them from here
7. Connect your M5 to PC via USB cable
8. Run command prompt. If your ADB and Fastboot are installed as system app - you can do this from any path in CMD. If not - you need to switch in CMD to your ADB and Fastboot folder. Either way, the patched ramdisk patched_boot.img file must be in the same path, from which you will be running commands below in CMD window
9. Type "adb " in CMD window to start android debug bridge
10. Type "adb reboot-bootloader" and wait until your device restarts in Download mode
11. Once in Download mode, type "fastboot flash ramdisk patched_boot.img" - you should see some output from flash procedure, indicating successful flash
12. Once patched ramdisk is flashed, type "fastboot reboot"
That is it - you're done. Once your device reboots it will be rooted.
Note 1: Magisk Manager has it's own built-in superuser app and uses Systemless root, which works completely differently - you will not see external, standalone app like SuperSU or SU you might be familiar with in your App Drawer. The way to control the superuser app is from Magisk Manager itself: Settings->Superuser section
Note 2: I don't do tech support via PM, so don't PM me for help or with questions. Use the thread instead, and some other XDA members or myself will probably help you. Good luck!
Note 3: You may find some links to Huawei stock firmware in the 2nd post
UPDATE - August 6, 2018
Huawei officially approved 8.0.0.171 firmware with GPU Turbo for installation on SHT-AL09 devices. If you're doing first time root - just follow the original steps above. If you are already rooted and want to upgrade to 8.0.0.171 - follow the steps below:
1. Boot into download mode:
Code:
adb reboot-bootloader
from CMD window
2. Flash stock recovery from 8.0.0.171 to your device in fastboot:
Code:
fastboot flash recovery_ramdisk recovery_ramdis.img
3. Download and install the official OTA through Settings (full or just the update)
4. Boot into download mode again and flash patched ramdisk from 8.0.0.171
Code:
fastboot flash ramdisk patched_boot.img
5. OPTIONAL: If you were using TWRP or any custom recovery - you will need to reflash it back
Code:
fastboot flash recovery_ramdisk twrp.img
or whatever you named your custom recovery image
REMINDER: Do NOT use ramdisk image I provided for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. This patched ramdisk is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Needless to say, all the images you are going to flash must reside in the same directory, from which you are going to be running the CMD commands. If your ADB/Fastboot folder is not in your WIndows' PATH environmental variable - the images must be placed in the same folder where ADB/Fastboot binaries are, and CMD commands must be run from that folder.

C5Longhorn said:
Yes, they still work. I have the same model and build as you and I'm rooted.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.

samiller said:
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
Click to expand...
Click to collapse
Unlocking is possible *only* if you've gotten already your unlock code. As this service was suspended about 2 years ago there is no easy way to get it unlocked.

Small request to developers, or people with access to reliable file hosting: I don't have a developer account, so all the files I linked or referenced in the OP are hosted on free hosting sites. That file hosting has expiration date and max downloads limit, so the files will become inaccessible sooner rather than later. Please upload these files to reliable hosting and create a post with the links. I will link your post in the OP as a mirror.
In the meantime, mirror for SHT-W09 firmware: https://mega.nz/#!asVjmZrR!bW2OmXgTjnyVN4pqb9fA7OzAJ4bzil7YZxNW14qoCmk

I can confirm that this works on the 10.8" wifi model using the devices relevant ramdisk.img.

Hello, can somebody test sixaxis controller tool with root and magisk? There is a Trial in Google Play Store, that is called sixaxis compatibility checker without purchise the App. Maybe i want to buy the Tablet, but only with Dualshock 4 Support...

Just a heads up, been following threads on this forum for flashing a GSI. Now that you guys can root, you can also make backups of your own stock system image if you can't find one from Firmware Finder. Then you can safely try flashing the GSI.

@MishaalRahman well it's bit like chicken egg dilemma. As we do not have a stock system image for e.g. SHT-W09 we cannot patch the ramdisk.img and so we cannot get the stock system image ...

Thanks Apo11on, great to have root so soon for the M5! Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.

Question is, for those of us with the Non Pro version, can this still be done.

@OHP Yes. The OP did it with the 8.4" version which has no pro option.
I'm looking to buy the Chinese 10" wifi version myself but need Google Play Store + Services on it which I'm guessing the Chinese version doesn't have. Is one of the firmwares at the website you link to a global version of the firmware that will work on this model?

OHP said:
Question is, for those of us with the Non Pro version, can this still be done.
Click to expand...
Click to collapse
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.

magnumlove said:
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
Click to expand...
Click to collapse
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:

OHP said:
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
Click to expand...
Click to collapse
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).

magnumlove said:
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
Click to expand...
Click to collapse
I took the plunge, and I am sucessfully rooted now :silly:

struggling with this part
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
I have a CMR-W09 :s i can got the files downloaded and the huwai software not sure how i make a img

The good news is I followed these instructions yesterday and they worked perfectly (SHT-AL09).
The bad news is, I seem to have lost root overnight.
---------- Post added at 06:41 AM ---------- Previous post was at 06:22 AM ----------
And I figured out why I lost root; I was playing around with Developer options and switched the default GPU renderer from 'default' to 'Skia.' Apparently, this disables root access until you switch back. I regained root access on a reboot, lost it again after switching back to Skia, and then regained it after switching back to default.

I got the right image file from the site and huwai extract. I have googled how to use this app but what files do I extract as there appears to be. Alot ? I extracted all of them ? I don't have a ramdisk.img
Also thanks for writting this up. Without it I would be lost

Thanks for the efforts making this thread. Unfortunately my device is SHT-W09 and I'm still waiting for the right firmware. Is there anything I can help, considering I have the device?

@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...

This works perfectly no issues. i had some how maanged to download the wrong rom first. AND thankfully it did not have a ramdisk in. it is important that your firmware matches the firmware present on the site as explained. This was easy guide to follow now to flash it with somthing other then andriod

AndDiSa said:
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
Click to expand...
Click to collapse
I'm on 8.0.0.101

Update .152 question

Hello,
I get a notification that I can update my P20 Pro from .131 version to .152 version.
The update has around 700MB, the problem is that when my update gets downloaded and when I reboot the device it reboots the device in to a TWRP where I get an error 9 with an information that the update has failed to install.
What can I do?
Should I remove TWRP, would that help?
I really want that update since I have very bad SOT (4 hours of SOT max )
Thank you all in advance

Hi,
We can't do it if you have TWRP. You must use HuRUpdater.
I did it on my P20.
You can use Huawei Firmware Finder APK on play store to download the packages.
(I will do it with 8.1.0.164 )
How to use:
Warning: Make sure you know what you are doing and do not flash firmware from other devices.
Download firmware files (for official firmware use Huawei Firmware Finder).
Put files you want to flash in a seperate folder on sdcard.
Supported zip files to flash are (name must match):
update.zip (use FullOTA file)
update_all_hw.zip
update_data_public.zip
Optional: Put recovery.img in same folder if you want to keep custom recovery.

My One Plus 6 says "Your system is up to date" but I am running OOS 9.0.4

As described in the title, my OP6 is currently on Oxygen OS 9.0.4. I know the current version is 10.X.X. My device is rooted and I usually upgrade my phone manually through TWRP.
Before I make any changes, I would like to know if there is a reason why the update is not showing up under Settings > System > System updates...
I know One Plus usually rolls out the updates on a few devices at a time, but it should be universally available at this point.
If it's safe to update, is there a thread where I can find instructions to go from 9.0.4 to the current version?

Wrong section, post in the Q/A this is for ROMs, kernels and recoverys.
Now that you know, here's the cake.
Just download 10.3.4 (latest Full OTA) Google it OTA 46
THEN move it from wherever it was (/sdcard/Downloads/) to just your root storage (/sdcard). Perform manual install from settings > system >system update (in here select from the advanced options manual update.
Orrrrrrrrrr
Plug into PC and flash with mauronofrios fastboot utility he's got 10.3.3. run the flash_all.bat in fastboot mode.

@shagexpert
I don't know why you are running this problem...
if you want run all the updates following system update, after made and moved a backup of your data, you can factory reset, then try again the system update (if It works you will receive all the update one at once)
a faster way could be using the latest "10.3.4.fastboot.zip" and flash if via adb - your phone will be reset and you will need to update recovery again of you prefer a custom One
otherwise you can simply get the latest stable build from OnePlus support web Page
https://www.oneplus.com/it/support/softwareupgrade/details?code=PM1574156173727 - global version
or
https://www.oneplus.com/cn/support/softwareupgrade/details?code=PM1574150497163 - china version
it's enought to download It and flash via recovery
- after the install finish you will need to update recovery (if you prefer a custom one)
ensure to flash It on both (a/b) partitions

I used this video to update my OnePlus 6
https://m.youtube.com/watch?v=P9_9Ksw_TXg

Oukitel WP5

This is a great rugged phone, perfect for the outdoors (I'm a keen mountaineer). I couldn't see a thread so I thought I would start one! A couple of posts re. rooting to follow....

Hey @dwastell, I know this thread is a couple months old, so I wanted to see if you have any root instructions?
Do you think the process for rooting the OUKITEL K13 here on the forum will work on the WP5?

Rooted!
Hi all,
I rooted my WP5. Sorry for not having time to write a full tutorial, only a concise story. Of course this is ONLY for experienced users...
My phone is 4GB version Android 10, build 10.0_V02_20200508.
1) download the firmware from oukitel website: https://oukitel.com/pages/download-center (1)
2) download and install SP Flash Tools https://spflashtool.com/download/
3) download and install Android Platform Tools https://developer.android.com/studio/releases/platform-tools
4) connect the phone to PC and verify that adb is working
5) WARNING: make a backup af your data!
6) unlock the bootloader:
- in Developer options enable the unlock
- adb reboot bootloader
- fastboot flashing unlock
- fastboot reboot
Now the phone restarts and is completely virgin!
7) shutdown the phone.
8) using SP Flash Tools readback the following partitions:
- boot
- recovery (2)
- vbmeta
9) download the attached patched_vbmeta.img
10) transfer the boot.img that you just readback to the phone download folder
11) install Magisk Manager (today 7.5.1)
12) Use Magisk Manager to patch the boot.img and copy back to PC
13) flash the images:
- fastboot flash --disable-verification vbmeta patched_vbmeta.img
- fastboot flash boot magisk_patched.img
- fastboot reboot
14) if the phone boots up run Magisk Manager to check if it's installed.
14b) if the phone goes in bootloop... flash back the original images you have read back (do not use the firmware you downloaded from Oukitel, it's necessary only to have the scatter file (the partition table).
Enjoy
Nicola
Notes:
(1) actually there are 2 firmware available and despite having different names are the same. This fw is Android 9.
(2) not used now but may be useful in the future

Rooting the WP5
totallybeachin said:
Hey @dwastell, I know this thread is a couple months old, so I wanted to see if you have any root instructions?
Do you think the process for rooting the OUKITEL K13 here on the forum will work on the WP5?
Click to expand...
Click to collapse
I eventually succeeded in rooting my WP5 with Magisk. For a while, the firmware was not available but once the official ROM was published, I managed to patch boot.img and install via fastboot. My phone is the 4 GB version -copies of the stock and patched boot image are available at: github.com/dwastell/Oukitel_WP5_magisk
I have experienced some complications as detailed in my next post...
Cheers, Dave

Rooting the WP5
Thanks for your post Nicola. You'll see that I did succeed in rooting my phone (Android 9) with Magisk, once I was able to get hold of the stock firmware. All is working though there are a couple of points worth noting.
The phones is SAR ("system-as-root") and the magisk instructions suggest that recovery.img is patched rather than boot.img. I proceeded by patching boot.img, as in your instructions, as this seemed a better solution - and it works fine.
One problem has occurred with updates. Magisk manager appears to assume that the recovery partition is the one that has been patched. When you do the direct install for the update, partition 2 is flashed (recovery) rather than partition 26 (boot). On rebooting the phone inevitably goes into boot loop.
To avoid this, I go for "select and patch a file" option, and then install again via fastboot as per the original installation. A bit of a hassle but better than the alternative!

Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.

vivekiny2k said:
Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.
Click to expand...
Click to collapse
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
N
---------- Post added at 20:10 ---------- Previous post was at 19:59 ----------
dwastell said:
The phones is SAR ("system-as-root") and the magisk instructions suggest that recovery.img is patched rather than boot.img. I proceeded by patching boot.img, as in your instructions, as this seemed a better solution - and it works fine.
Click to expand...
Click to collapse
This phone is NOT a SAR. Neither Android 9 nor 10. The proof is that patching the boot.img worked!
One problem has occurred with updates.
Click to expand...
Click to collapse
Have you unrooted before applying the update?
Which kind of update? Not all are the same!

Android version
vivekiny2k said:
Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.
Click to expand...
Click to collapse
My phone was originally Android 9 so no reversion...

SAR
Both "Treble Check" and "Magisk Manager" confirm that the phone is SAR. I agree this is odd.... your thoughts?
The update I was referring to is the Magisk update, handled by Magisk Manager. Given that the phone is seen as SAR, it attempts to patch recovery.img, with an ensueing boot loop.
No, I don't unroot the phone
nicolap8 said:
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
N
---------- Post added at 20:10 ---------- Previous post was at 19:59 ----------
This phone is NOT a SAR. Neither Android 9 nor 10. The proof is that patching the boot.img worked!
Have you unrooted before applying the update?
Which kind of update? Not all are the same!
Click to expand...
Click to collapse

Thanks Nicola for your tutorial. I'm eager to root my WP5 Pro with Magisk, but first I need a backup of boot vbmeta and recovery. I have made extensive use of SP Flash Tools but never to readback partitions so I'm having some problems here. Could you please detail your technique to extract such files? Thank you
Michele
Build number OUKITEL_WP5Pro_EEA_V01-20200624 CPU MT6762D, 8 cores,64 Gb ROM, 4 Gb RAM.

wallace108 said:
Thanks Nicola for your tutorial. I'm eager to root my WP5 Pro with Magisk, but first I need a backup of boot vbmeta and recovery. I have made extensive use of SP Flash Tools but never to readback partitions so I'm having some problems here. Could you please detail your technique to extract such files? Thank you
Michele
Build number OUKITEL_WP5Pro_EEA_V01-20200624 CPU MT6762D, 8 cores,64 Gb ROM, 4 Gb RAM.
Click to expand...
Click to collapse
Beware: your phone is different! So I don't know:
1) Android version.
2) which kind of booting are using, read here https://topjohnwu.github.io/Magisk/install.html#knowing-your-device
Before writing an image you MUST have a backup of it!
To read back a partition with SP Flash Tools you need to know the start address end the length of the partition. This information is available only (because your phone is not yet rooted) from the scatter file (from the SAME phone).
In the Readback page hit "Add" then input a name for the image file. Follows a new dialog "Readback block start address" where you have to write the values.
After this you can give the Read Back command. If it doesn't start shutdown the phone.
N

Thank you all for
the data to root! I just got a 4/32 android 10 version. Is there a custom recovery yet? Been a looooong time since I have dabbled but want to root it and customise. I have replaced most of google apps or disabled them already but want more room. I have never created a TWRP but have been reading about it and they already have many Oukitel versions, so should I wait? TIA

Thanks, it's clear.
I bought it for my son, don't have plans to root it yet. will probably wait till later.
nicolap8 said:
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
Click to expand...
Click to collapse

No Joy with
Hardware : MT6761V/WE
Model : WP5
Build number : OUKITEL_WP5_NOEEA_V01_20200701
Build date UTC : 20200701-071441
Android v : 10
Baseband v: MOLY.LR12A.R3.MP.V114.9,MOLY.LR12A.R3.MP.V114.9
Kernel v : 4.9.190+ ([email protected]) (Android (5484270 based on r353983c) clang version 9.0.3 (based on LLVM 9.0.3svn)) #2 SMP Wed Jul 1 15:19:21 CST 2020
It seems locked down as I lose adb in fastboot and even patching the boot.img I create fails. MTKdroid tools can't create scatter.

vivekiny2k said:
I bought it for my son, don't have plans to root it yet. will probably wait till later.
Click to expand...
Click to collapse
Remember that you will lose ALL YOUR DATA! Usually it's better to root before start using the phone...
oncouch1 said:
No Joy with
Build number : OUKITEL_WP5_NOEEA_V01_20200701
It seems locked down as I lose adb in fastboot and even patching the boot.img I create fails. MTKdroid tools can't create scatter.
Click to expand...
Click to collapse
You have to describe well what you have done and error messages.
Note also that your firmware is never... maybe there is some difference.
N

As of today the firmware for the WP5 PRO has not been posted yet. I'll wait. Meanwhile I want to ask Nicolap8: what does the vbmeta file do? Why is it important to patch it. Isn't patching the boot enough? Thanks

TWRP for WP5 (Pie, 4GB)
If anyone wants to install TWRP, I've built and tested it for my WP5 (Android 9.0, 4GB). A copy of the image may be found in the MISC folder at: https://github.com/dwastell/TWRP_Oukitel_WP5
Note that the data partitiion is not accessible due to encryption (not a major limitation), and that the null version of vbmeta (thanks Nicola) does need to be flashed. Also, I have had problems flashing some versions of Magisk - please read the README.md.

nicolap8 said:
Remember that you will lose ALL YOUR DATA! Usually it's better to root before start using the phone...
You have to describe well what you have done and error messages.
Note also that your firmware is never... maybe there is some difference.
N
Click to expand...
Click to collapse
Sorry it has been a while I HAD WRONG USB DRIVERS! I got bootloader unlocked and will try again.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
A WP5 (android 10) .zip file is now on the site. It contains less files though?

For some reason the images taken in windows are corrupt. Magical fails to run on them. The one taken in llinux patches fine. One question though the original image is 32 meg the magical patches is only 10 meg is that correct? Also the vbmeta is 8 meg off the phone but the patches 256 k?

oncouch1 said:
For some reason the images taken in windows are corrupt. Magical fails to run on them. The one taken in llinux patches fine.
Click to expand...
Click to collapse
Strange but... with W all is possible!
One question though the original image is 32 meg the magical patches is only 10 meg is that correct? Also the vbmeta is 8 meg off the phone but the patches 256 k?
Click to expand...
Click to collapse
Both are correct.
The Magisk patched image is not "filled" to the partition size.
The vbmeta also is smaller because it's empty (is present only the "index").
N