We are trying to get hold a custom recovery for Lenovo Tab3-710F. We are using hundreds of Lenovo tablets in our projects and have up until now used Tab2 A7-10 which has a custom recovery build for it (found here att XDA).
The reason we need the custom recovery is for cloning the unit which works good in CWM or TWRP.
The problem now is that Lenovo have stopped selling Tab2 so we are now stuck with a unit we cant clone.
Have somebody successfully created a custom recovery for the unit? If not or if you have we are offering payments/devices to get this working asap. Are you interested please PM us? When we have it we can share it to the world here no problems for us.
If you need to root the device KingoRoot latest APK works.
So hope somebody can help us.
Perhaps useful for you: I've managed to extract the stock rom of a brand new TB3-710F
http://forum.xda-developers.com/android/help/lenovo-tab-3-7-essential-tb3-710f-mt8127-t3416397
This also includes the "recovery.img" so you could try to change this image and simply flashing it. If it does not work you'll have a stock rom to restore it.
gogetrd said:
We are trying to get hold a custom recovery for Lenovo Tab3-710F. We are using hundreds of Lenovo tablets in our projects and have up until now used Tab2 A7-10 which has a custom recovery build for it (found here att XDA).
The reason we need the custom recovery is for cloning the unit which works good in CWM or TWRP.
The problem now is that Lenovo have stopped selling Tab2 so we are now stuck with a unit we cant clone.
Have somebody successfully created a custom recovery for the unit? If not or if you have we are offering payments/devices to get this working asap. Are you interested please PM us? When we have it we can share it to the world here no problems for us.
If you need to root the device KingoRoot latest APK works.
So hope somebody can help us.
Click to expand...
Click to collapse
Did u manage to get TWRP or CWM for TB3-710F ?
zwirc said:
Did u manage to get TWRP or CWM for TB3-710F ?
Click to expand...
Click to collapse
Yes, I built it for them. Download here
@Tzul @gogetrd We are trying to achieve something similar, configure about 700 tablets of this model. I have played with custom ROMs in the past, but mostly as a consumer (e.g. Cyanogen on personal devices).
It is my understanding that installation using the files provided by @Tzul would require to;
0. create a custom ROM.
Then for each device
1. root device (e.g. Developper mode, allow "Unknown source"s, adb install one rooting apk, run it, etc).
2. install custom recovery on device
3. flash custom ROM
Am I right?
If so do we agree that the time spent doing these operations might be about similar than the time spent e.g. manually installing / configuring the device? Or is there a way to automate the steps above?
You can configure 1 tablet, then extract the ROM and flash it with the "download mode". You don't even need to boot the tablet!
If you want more info let me know, back from holiday in a few days
@lacostej You can certainly automate some steps, and you do not always need root. (And the best way to root is to install the latest SuperSU via TWRP; no need for questionable apps that are doing who knows what...)
There are three ways to install another firmware:
The MediaTek SmartPhone Flash Tool (SPFT). This is a PC program (Windows and Linux) that allows reading and writing of the entire internal storage (on a partition granularity). Via USB, while the device is powered down. Only for devices based on MediaTek chips, of course (this tablet is MediaTek-based).
Fastboot. This is a little USB protocol implemented by the bootloader. A Fastboot client on PC can communicate with the bootloader via USB and execute certain commands, e.g. "fastboot flash" for flashing partitions. However, there are a few drawbacks with this:
First, you need to boot the device into fastboot mode. Some devices have a boot menu that allows you to do this, but this device doesn't. Starting the tablet via power+volumeUP takes you directly to the recovery instead of a boot menu. But in the recovery, whether stock or TWRP, there's a reboot to bootloader option. Using ADB (adb reboot bootloader) should also take you there.
Second, the "fastboot flash" command is restricted on this tablet. If you were to use "fastboot flash recovery <recoveryfilename_here>", for example, it would abort with an error message. I have patched the bootloader to allow the flash command, but you'd first need to install this patched version on your tablet(s), of course, via SPFT or other means.
Third, the "fastboot flash" command has a size limit - the bootloader needs to buffer the USB data in RAM before it can be written, and since the tablet has only 1 GB of RAM, you obviously can't flash a 1 GB system image this way. The buffer is actually a lot smaller: just 128 MiB. Meaning whatever file you send to the tablet via "fastboot flash", it cannot be larger than 128 MiB. So, how do you flash the system or userdata partition then, which are much, much larger? By splitting their image file into many smaller "sparse" image files, each of which is below the size limit. There's probably a tool for doing this, but I don't know any details.
TWRP, or another custom recovery. They allow you to create and restore backups. TWRP has some automation support via OpenRecoveryScript.
So, if you have 700 tablets to configure, you can configure just one, then save its state via SPFT or TWRP, then restore that on each other tablet.
What is its "state"? Well, the system, cache, and data partitions. The system partition is normally read-only and won't change, therefore you do not need to clone it. Unless you install root and modify stuff on the system partition, of course. The cache partition is quite irrelevant. It is the data partition that has all the app settings.
However, if you clone the data partition from one tablet to others, then you're causing each tablet to use the same Android ID (a long number identifying an Android device, usually randomly generated when Android is first booted after a factory reset), the same Bluetooth and WiFi MAC addresses, and some other IDs that should be unique on each device (the tablet's Lenovo serial number might be in some cloned files as well, e.g. the WiFi settings).
You can at least avoid cloning the MAC addresses by deleting the entire directory /data/nvram/ before you create your backup. MediaTek devices have a dedicated NVRAM partition that contains the MAC addresses and some other stuff, and this data gets unpacked to /data/nvram/ when Android boots. Unless the files there already exist. So, by deleting /data/nvram/ before you clone, you force each tablet to extract its unique MAC addresses again at the next boot...
Thanks a lot for the feedback. Really appreciated.
Tzul said:
@lacostej And the best way to root is to install the latest SuperSU via TWRP; no need for questionable apps that are doing who knows what...
Click to expand...
Click to collapse
Doesn't SuperSU already requires root? (http://forum.xda-developers.com/showthread.php?t=1538053)
How did you get root on your Lenovo device? (I assume you had one to dump the image)
However, if you clone the data partition from one tablet to others, then you're causing each tablet to use the same Android ID (a long number identifying an Android device, usually randomly generated when Android is first booted after a factory reset), the same Bluetooth and WiFi MAC addresses, and some other IDs that should be unique on each device (the tablet's Lenovo serial number might be in some cloned files as well, e.g. the WiFi settings).
.
Click to expand...
Click to collapse
That's exactly the thing I was worried about when it comes to cloning. Those problems might arise later during QA, and I probably don't have the time required to do it properly this time.
lacostej said:
Doesn't SuperSU already requires root? (http://forum.xda-developers.com/showthread.php?t=1538053)
How did you get root on your Lenovo device? (I assume you had one to dump the image)
Click to expand...
Click to collapse
SuperSU is just like any other root manager. It provides the actual "su" (superuser) binary that other programs rely on to obtain root privileges, plus an Android app for managing permissions and settings. The su binary needs to be installed on the system partition (at least traditionally), but in order to get write access there, you need root privileges. Therefore, this is a chicken and egg problem: SuperSU provides root, but it also needs root in order to be installed. Other root manager are no different - except that some try to exploit security flaws in Android in order to temporarily obtain root and install their su binary.
Anyway, the classic solution to this conundrum is the (custom) recovery: it basically has root built-in. It can write to the system partition by default, after all one of its jobs is to install firmware updates.
TWRP includes a SuperSU stub. If you leave TWRP via the Reboot menu, it checks whether or not the su binary is installed (at least in Android 4 and 5), and if it isn't, it asks if you'd like to install the SuperSU stub. Which you can then use in Android to update to the latest SuperSU via Play Store. But you can also install SuperSU's latest "update zip" in TWRP to immediately install the full version.
lacostej said:
That's exactly the thing I was worried about when it comes to cloning. Those problems might arise later during QA, and I probably don't have the time required to do it properly this time.
Click to expand...
Click to collapse
Yeah, it is annoying. MediaTek apparently wisened up a bit. Newer platforms they produce do not unpack the NVRAM partition to the data partition anymore. Instead, they use a dedicated "nvdata" partition for that purpose. That way, if you clone the data partition, you at least won't include the unpacked NVRAM data (MAC addresses and IMEI). But still, some other IDs such as the Android ID, references to the serial number, etc. will very likely be referenced by some other files on the data partition.
I created a little "update zip" that can be "installed" via TWRP, which is just a shell script that tries to delete all the files on the data partition that contain unique or sensitive info. I use it to "clean" a data partition before publishing it. But it's not perfect yet...
@Tzul Your modified rom is great. But I have one problem with it.
When you connect your turned off device to the power supply there is a clock and charging animation. The clock is several hours ahead of the system clock. System clock and clock during the charging are connected (when I change the system time the 2nd clock also changes the hour).
I was trying to use hwclock but without success.
Is there some kind of file where I can set the correct time zone for the 2nd clock?
Sorry for my English.
@Yozen I didn't modify the ROM. I extracted and packaged it.
When the tablet is turned off and then connected to a power supply, it will usually start "off-mode charging" (can be disabled, so that Android will boot up instead). This is handled by the bootloader (LK, lk.bin), which also displays the battery animation and the clock that you see. Apparently the bootloader on this device doesn't handle time zones, because the clock shown uses China Standard Time (CST, UTC+08:00). This is the first MediaTek-based device I've seen which shows a clock in the off-mode charging screen at all. I guess they normally don't because they have no simple way to figure out the user's correct time zone at that stage.
Will this method and these files work for TB3-730F?
Sir, is there a custom ROM available for Lenovo tab3-710f ?
lacostej said:
@Tzul @gogetrd We are trying to achieve something similar, configure about 700 tablets of this model. I have played with custom ROMs in the past, but mostly as a consumer (e.g. Cyanogen on personal devices).
It is my understanding that installation using the files provided by @Tzul would require to;
0. create a custom ROM.
Then for each device
1. root device (e.g. Developper mode, allow "Unknown source"s, adb install one rooting apk, run it, etc).
2. install custom recovery on device
3. flash custom ROM
Am I right?
If so do we agree that the time spent doing these operations might be about similar than the time spent e.g. manually installing / configuring the device? Or is there a way to automate the steps above?
Click to expand...
Click to collapse
How did you do it in the end? I'm trying to do something similar here and am very curious!
.acy said:
How did you do it in the end? I'm trying to do something similar here and am very curious!
Click to expand...
Click to collapse
For us it is this "simple".
1. Manually configure a single device
2. Readback the ROM (get the ROM from the device and store it on your PC) using SP Flash Tool
3. Parse the ROM from a single file to multiple files using Mtk Droid Tool
4. (clear cache partition & remove stuff like serial number)
5. Load your ROM in SP Flash Tool
6. Click start
7. DO NOT START your new tablet
8. Connect it to USB
9. Wait (assuming you already have the preloader drivers installed)
10. Done, new ROM is flashed to your tab!
edit:
Oh and with 700 tablets it might be nice to look into compressing the file as the full 8gb dump we flash (and we don't do a lot these days) will take ~30-40 minutes
mattiemvs said:
3. Parse the ROM from a single file to multiple files using Mtk Droid Tool
Click to expand...
Click to collapse
That's unnecessary, because the SP Flash Tool can already read back partitions into separate files.
Also, you don't need to clone some partitions like cache, and you really should not clone nvram and parts of data, otherwise you'll end up with tablets sharing unique IDs such as MAC addresses, which will cause problems.
Tzul, you are absolutely right! I typed the items from my mind as it has been quite some time since I've created the ROM
tb3-710f s000028
Tzul said:
Yes, I built it for them.
Click to expand...
Click to collapse
Hello tzul,
Thanks for your jobs.
I want to install Lenovo_TB3-710F_S000027_TO_S000028_Patched_Tzul.zip
But i don't know how i do this when i try with SPFT i choose teh scatter-file and i have an error :
sp flash toll error : 5417
The load scatter file is invalid !
hint :
please check the scatter file and select again
Can you help me ? please
@siegheart73 That is a patched OTA update. It needs to be installed by the recovery (stock or TWRP). If a zip file contains a "META-INF" folder, then it's most likely intended for the recovery, and not for the SPFT.
Tzul said:
@siegheart73 That is a patched OTA update. It needs to be installed by the recovery (stock or TWRP). If a zip file contains a "META-INF" folder, then it's most likely intended for the recovery, and not for the SPFT.
Click to expand...
Click to collapse
Thanks for your answer.
I go to test it.
I want to root this kernel 000028 and i have difficult to do it ?
Do you have a easy solution ?
Thanks a lot for your help.
Coolpad Rogue 3320A - Stock 5.1.1 Build No. 5.1.157.00.T2.150810.LMY47V
Fastboot Flashable Recovery, Kernel, Modem & Misc. Firmware Images
Disclaimer You flash these images at your own risk. I am not responsible for bricked or otherwise inoperable devices as a result of flashing any of the files provided herein.
These partition images will help you recover a soft bricked device in the event you have missing or corrupt partitions. Additionally, in the event you are having signal or connectivity issues, flashing the modem/radio firmware could resolve those problems. I have provided all partition images for the 3320A with the exception of /system and /userdata. The stock /boot and /recovery images are always good to have in case you ever need them. At a minimum, save these images to external storage in case of future need. I will provide a full /system image in future at request.
WARNING Flashing bootloader or bootloader dependent partitions can result in a hard bricked device. Please do not flash bootloader type partitions unless you are well versed in this area. Tampering with these particular partitions is best left for developers and experts. I will clearly label any bootloader type partitions, in hopes that it will alleviate any confusion.
INSTRUCTIONS:
Install Minimal ADB and Fastboot on your PC or Laptop. The installation files can be found here on XDA Forums. Install the USB Drivers for your Coolpad Rogue 3320A. (The drivers are pre-installed on the device itself. If you are able to boot up, connect your 3320A to your PC and look in your PC's directory for an installation option.) Place the .img files you need on an external SD card or in internal storage. With your device powered off, boot into Recovery Mode by holding power and +volume simultaneously until the Coolpad logo appears -- then let off of power but continue to hold +volume until the stock recovery screen appears. Use your volume button to scroll down to Bootloader and press power to select. When the Fastboot screen appears, connect your device to your PC with a suitable micro USB syncing cable and press +Volume. In your Minimal ADB and Fastboot directory open a command window (Shift and Right Click).Type: fastboot devices If you are properly connected, your device serial number will be displayed in your command window under connected devices. If your serial number doesn't appear, repeat the above steps, ensure your USB drivers are installed correctly, and try changing USB ports on your PC or trying a different cable. Once you are connected properly, the rest is simple: I have named each partition image synonymous to its corresponding partition. In other words, the name of the file is also the name of your device's partition to be flashed.
EXAMPLE If you are flashing the "carrier" partition, you simply type fastboot flash carrier carrier.img Again, I will label each partition as to the type (e.g. recovery, bootloader, modem firmware, etc.)
DOWNLOAD LINK:
https://drive.google.com/folderview?id=0B7-zQU1VihD3eXE1SjBIby02Rmc
PARTITION NAME / TYPE
tz - "Trust Zone" Bootloader Dependent Partition
tzbak - Allotted Partition Backup of tz
ssd - Firmware Partition
sec - Firmware Partition
sbl1 - Secondary Bootloader
sbl1bak - Allotted Partition Backup of sbl1
rpm - Primary Bootloader
recovery - Stock Recovery Image
persist - Firmware Partition
params - Firmware Partition
panic - Firmware Partition
pad - Firmware Partition
oem - Manufacturer/Device ID Partition
modem - Radio Firmware
modemst1 - Radio Firmware
modemst2 - Radio Firmware
misc - Carrier/Region ID Partition
keystore - Firmware Partition
fsg - Radio Firmware
fsc - Firmware Partition
devinfo - Manufacturer/Device Info Partition
ddr - Radio Firmware
config - Carrier Specific Info Partition
boot - Stock Kernel/Ramdisk
aboot - Application Bootloader Partition
Hopefully this guide will help you restore your device from an inoperable state or restore connectivity from problems originating from damaged/corrupt partitions.
Relaying A Message from MotoJunkie01
Relaying A Message from MotoJunkie01
I apologize for not being in closer contact. I have some pressing issues going on and, coupled with work, man I've been tied up something awful. I'm going to need to drop off XDA for a month or better to get my personal issues attended to. I need a huge favor from you.
My little threads I have started, if you could go on and explain I'll be gone for a month or so. I'd appreciate it.
I've Not enough time to even do that.
So if anyone needs a reply I'd figure sometime in July, and I hope you all will understand and allow this time for MotoJunkie01 to attend to his personal matters. Signed: ResistanceIsFutile
Link not working
Your above link does not work. Also I have no idea why you are trying to share images. Fast boot only pushes zip files
Gamesmedic said:
Your above link does not work. Also I have no idea why you are trying to share images. Fast boot only pushes zip files
Click to expand...
Click to collapse
Sorry about the broken link. I just added a new working link with all listed firmware images.
You are obviously extremely confused about the purpose & function of fastboot commands. Allow me to educate you a bit. First, contrary to your statement, fastboot does not "push" files. And it most certainly does not push "zip files." In fact fastboot cannot be used to manipulate zip archives at all. . If you go back and read the thread, fastboot is used primarily, and as a preferred method by many, to flash firmware images to your device. (.img, .bin, mbn, etc) The firmware images in my link can be flashed to the Coolpad Rogue, via fastboot, to restore the partitions to pure stock/factory condition, in the event of a soft brick, bootloop, corrupt OS, etc.
I hope this clears your confusion some, before you hard brick a device trying to "push zip files" with fastboot.
Sim unlock
would this help to do a sim unlock
rachinda said:
would this help to do a sim unlock
Click to expand...
Click to collapse
No. SIM unlocking involves an entirely separate procedure. I am not even sure a SIM unlocking procedure is available apart from using a remote unlocking service or requesting an unlock code through the carrier directly. This thread is merely a source for stock firmware partitions for devices which are stuck in boot loop, soft bricked, poor or lost cellular service, connectivity issues, etc.
Hi All,
Today I wanted to install LinageOS on my S7. Before that I wanted to backup my data using Titanium Backup.
To get the full function of Titanium Backup I wanted to root the device before that.
I installed TWRP using heimdall and installed SuperSU from the external SD card.
Then I booted again and during boot the device asked me as usual for my pin (black screen, only pin input and emergency calls possible, NOT the pin input on the lock screen).
But when I entered my pin as usual the device said that the pin is invalid (it is the correct pin).
After several tries I got a message that after 8 more tries my data get will get erased permanently... ;-((
So long story short, does anyone has an idea of how I can decrypt my data on the data partition now???
Things to mention and tried so far:
* During the install of SuperSU the /data partition can not be mounted.
(Also adb shell twrp decrypt your_password does not work because of this I think)
I think this is because TWRP can't decrypt data partitions on Samsung Phones which is a known problem.
But this does not seem to be a problem for SuperSU.
* After I couldn't boot because of the problem the first time I also installed no-verity-opt-encrypt-5.1 in hope for a fix, didn't solve the problem either (But I am not shure if it adds to the problem after reading to a lot of postings today).
* I am not sure if it has to do, that asking for the PIN during boot was enabled in Settings on the device. But there was no hint, that this could be a problem in the instructions I used.
https://wiki.lineageos.org/devices/herolte/install
and
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
* I am not shure if this all has to do with dm-verity
see: https://twrp.me/devices/samsunggalaxys7.html[/QUOTE]
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
I am also not shure if Dm-verity and Forced Encryption Disabler is already included in SuperSU.
* Versions used:
Buildnumber: NRD90M.G930FXXU1DQEF
Baseband: G930FXXU1DQD7
twrp-3.1.1-0-herolte.img
SR3-SuperSU-v2.82-SR3-20170813133244.zip
no-verity-opt-encrypt-5.1.zip
* I also tried to make a backup of the encrypted partitions but copying of the partitions using TWRP and adb does not work because the phone gets reconnecting ca. every 45 seconds. And it seems it is not possible to decrypt an encrypted android partition on linux or windows even with the correct pin. (right?)
* The only thing I found is this, but I am not shure if this is the way to go, besides I don't know how to get the encrypted partitions of the phone.
http://www.forensicswiki.org/wiki/H...ypting_Samsung_Full_Disk_Encryption_.28FDE.29
I also saw as similar post like that today, but I have a pin and no password and I need to unlock my data partition with the correct pin (right?).
So does anyone has an idea how to decode the data partiton or to access my data in any way?
If I will be able to get my data of the device I could simply flash LinageOS and everything should be fine.
Thanks!
I was trying to apply the installation of the eXistenZ (https://forum.xda-developers.com/xz...om-existenz-pie-v3-5-0-beta-31-01-19-t3895452)
But aside from that I found the following problem:
Following the instructions I downloaded the last ROM, I specifically downloaded the G8141_Customized UK_1308-5320_47.2.A.10.62_R3C
First of all I made a clean flash and restart, then I installed the TWRP v.3.3.1 via ADB, next the Magisk 19.3, later reboot the system normally and finally a tried to do the part of rebooting in the recovery and wiping data, cache, dalvic, etc.
However I noted that when the system started up the first time (after flashing) it appears a legend describing a process of encryption, it said the cel phone was going to be encrypted and it restarted once again.
When I start in the recovery mode and slide the bar to authorize to modify system partition nothing happens.
The first try I stored the Magisk.apk file in the internal memory but in TWRP interface the system partition is not mounted, the storage space says is 0 GM (or mb).
I started up the system one more time, trying to disable the encrypted function but is not possible, I disable Find my Device function as administrator maybe thinking it was the reason deactivating encryption was blocked but nothing.
I have to mention that when I enter recovery mode is not asking me to enter any pass or pin as it does when there is a pin protected phone.
Please can anyone help me to find the solution to this problem
Zur75 said:
I was trying to apply the installation of the eXistenZ (https://forum.xda-developers.com/xz...om-existenz-pie-v3-5-0-beta-31-01-19-t3895452)
But aside from that I found the following problem:
Following the instructions I downloaded the last ROM, I specifically downloaded the G8141_Customized UK_1308-5320_47.2.A.10.62_R3C
First of all I made a clean flash and restart, then I installed the TWRP v.3.3.1 via ADB, next the Magisk 19.3, later reboot the system normally and finally a tried to do the part of rebooting in the recovery and wiping data, cache, dalvic, etc.
However I noted that when the system started up the first time (after flashing) it appears a legend describing a process of encryption, it said the cel phone was going to be encrypted and it restarted once again.
When I start in the recovery mode and slide the bar to authorize to modify system partition nothing happens.
The first try I stored the Magisk.apk file in the internal memory but in TWRP interface the system partition is not mounted, the storage space says is 0 GM (or mb).
I started up the system one more time, trying to disable the encrypted function but is not possible, I disable Find my Device function as administrator maybe thinking it was the reason deactivating encryption was blocked but nothing.
I have to mention that when I enter recovery mode is not asking me to enter any pass or pin as it does when there is a pin protected phone.
Please can anyone help me to find the solution to this problem
Click to expand...
Click to collapse
Wipe cache and data
To factory reset and then boot your system
Turn off / flash twrp/ restart/turn off / enter twrp/ magisk / restart to twrp/flash existenz/ reboot
You will loose all data
Yes i have same problem. When use TWP Swipe but always failed
I try use flashtools, flash .ftf firmware .62 and choose all swipe in box Flashtools.
Now, folder is working.
You can try.
ngocthang26 said:
Yes i have same problem. When use TWP Swipe but always failed
I try use flashtools, flash .ftf firmware .62 and choose all swipe in box Flashtools.
Now, folder is working.
You can try.
Click to expand...
Click to collapse
I'm sorry, didn't understand you, did you fallow the sequence karrouma gave me in the first answer?
This phone can only fastboot, but without authorization to pc, I tried turning to recovery/normal start, it does nothing but blinks(screen light turns on and off). I can't factory reset nor can I get the firmware to factory reset. any help would be greatly appreciated!!
You probably have wiped a partition ( especially that where adbd is located ): re-flash phone's Stock ROM.
that emmc is weared-out and therefore either the emmc controller or kernel decided to provide block device ro (before it finally dies on wear-leveling)
use a drilling machine through emmc chip to destroy user data
jwoegerbauer said:
You probably have wiped a partition ( especially that where adbd is located ): re-flash phone's Stock ROM.
Click to expand...
Click to collapse
How am I supposed to do so? I don't have the stock rom...
seems it's Mediatek SoC you can just dump stock ROM off the phone itself.
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
I personally prefer mtkclient cmd line for linux (python) it's maybe not that easy to setup but it's easy in usage. it even provides a simple gui. for readback ROM device needs to be powered off and usb disconnected (as usual for Mediatek devices). plug in usb cable when PC is ready for preloader mode, then "rl": Read all partitions from flash to a directory
Code:
python3 mtk rl /path/to/outdir
Note: Android partitions are mounted ro it's unlikely ROM itself is damaged (if not forcefully modified). "only" userdata + cache partitions are writeable to Android, formatting userdata partition is "same" as factory reset.