Related
Hi,
I have used this utility to Grab rom image from my Toshiba G10 and recieved bin large bin. file .( 131,072 ).
I want to be able to extract and image file and to add/remove unwanted utilities.
In the end if possible I want to close it and flash rom again.
Is there specifc tool to use?
I also have rom image EXE. file on PC if it might help..
please advice,
Tnx.
Ran.
Hello guys...
We all know that a custom recovery is far more important thing i rooted phone. But since we're talking about mediatek,its hard to find a suitable recovery.
Now these days,its very easy to create CWM based recovery through Mtkdroidtools. But,CWM is quite a oldschool yo!!
But TWRP is awesome!! Cuz its touch based and far more easy to use...but its so hard to find mediatek TWRP,so this guide will be helpfull i guess!!
~~Requirements~~
1.A computer with Windows 7 32 bit
2.The stock recovery.img[it can be found in your phone's stock rom]
3.TWRP script>>
Download link>> htt p://www .me diafire.com/folder/ca6 n5bb8 ocu87/TWRP_an d_CWMR
Download "Port-TWRP-V2.4.4.0-MT6589.7z" file from that link!!!
Now extract that 7z file and put the folder in your computer's C:// drive.....and put your stock recovery.img in C:// too.
Now open That extracted folder and you'll see a .exe file. Run that file as administration and a command window will appear.
Now it'll ask you to put your recovery.img in C:// and that is already done. So press Enter and follow the next steps. It'll ask you too put your device's chipset,resolution....so enter correctly.
When it is all done, close that Window and you'll see a folder is created called "Ported TWRP" open it and you'll get your newly created TWRP recovery.img. Copy that in your sdcard and flash it via latest Mobile Uncle Tools and voila!! You'll be rebooted to your TWRP custom recovery!!!!!
N.B>> this process is only for mt6577,mt6589 and mt6575.
Hit thanks if you like it.
Android Devilzz[root n stuffs]
Click to expand...
Click to collapse
This seems so easy I will try it
bro it shows error found please help me
Hello
Yesterday I tried (Xperia XZ2 Compact H8324) to flash on the new Android 9.
My device was built in Hong Kong.
I went like this:
First I downloaded the current German Android 9 Stock Rome via Xperifirm. H8324_Customized DE_1313-6204_52.0.A.3.84_R2B
Before the flash, I created the * .ftf file in flash tool 0.9.25.0, as shown in a Youtube video. The whole thing worked fine.
Then I put my device into Flash mode and integrated the latest drivers into my PC.
Before I could start the flash process, I had to move the *. Fsc script from the folder "devices \ H83XX" in the folder "my devices" and rename in the current firmware. Since he gave me the message when starting the flash process that no update script would be available.
Then the flash process started asking if he should skip certain things stored in the script. Of course I confirmed that.
The flash process ran without any further error message and ended with the message that the flash was successful.
However, after starting the Xperia, the message "Your device is corrupted - it can not be trusted" was displayed. The device shuts down after 5 seconds.
Fortunately, I was able to recover my original firmware through the PC Companion.
Can someone tell me where I might have made a mistake on the way and how can I fix this? I would like to have Android 9, but that has not arrived in Hong Kong yet.
This is my first tutorial, hope you enjoy it and take you further.
Thank you first to juandiazmora
So you get Android 9 on your smartphone without any regional restrictions.
The following programs are required: Xperifirm, flashtool 0.9.25.0
1. Download the Rome at Xperifirm which is compatible with your device and you want it. For me, the firmware was unpacked directly by Xperifirm otherwise uses Flashtool Tools> Bundles> FILESET Decrypt
!!! Important with the downloaded files the "fwinfo.xml delete" !!!
2. In the Flash tool go to Tools> Bundles> Create
2.1 There you choose the folder in which the firmware is located.
2.2 Then select your device at Device.
2.3 When branding enter your country version. In my case Germany.
2.4 In version your firmware version you want to install.
2.5 Now important and careful. With folders list you add all files except * .ta files to the firmware content.
2.6 Then click Create and wait.
3. Adapt Flashtool. Go to the folders "Users" \ flashTool \ devices \ H82XX and the
"User". \ Flash tool \ devices \ H83XX
3.1 Copies the 52.fsc from the H82XX to the H83XX
Deletes the 51.1.fsc
3.2 Then copy the complete folder H83XX into the folder "User" \. FlashTool \ mydevices
4. Connect the mobile phone in Flash mode to the PC. Do not forget to install the appropriate driver. Flashtool also provides drivers and Xperia Companion.
4.1 If everything is ready then go to step 5.
*
5. Flashing
5.1 Click on the flash symbol in the flash tool.
5.2 Select flash mode
5.3 For Source folder, select the folder with the previously created firmware file in * .ftf.
5.4 Select Device for Device Filter.
5.5 At Firmwares, select your created firmware.
5.6 For Wipe Sin, select APPSLOG / USERDATA
5.7 Select Disable final verification.
5.8 Flash
6. When flashing, he asks if he should use the 52.fsc.
Simply confirm everything then works well.
For me it all worked out but of course I take no guarantees. Everything at your own risk.
Double that. I havent flashed pie too, requesting a little guide how to do it properly to have full stock firmware.
I think you should use a fsc for 52 firmware, not just remane the 51.1. On github page is available the data for create that specific file. Also you can use xperifirm to download the firmware easily and safely
52.fsc
juandiazmora said:
I think you should use a fsc for 52 firmware, not just remane the 51.1. On github page is available the data for create that specific file. Also you can use xperifirm to download the firmware easily and safely
Click to expand...
Click to collapse
Hi, I need help on the flashscript thingie.
Don't have a clue where to get it from.
Thanks in advance.
I'm with Customized CE1 in my H8314 and I'm still in Oreo. It would be possible do this steps with my same firmware without doing wipe? Only deleting the country restricion.
Regards
Why can't we just flash using the downloaded and unpacked firmware from Xperiafirm? Why this need to exclude some specific .ta files and disable final verification checks?
Quarzkopf said:
Hello
Yesterday I tried (Xperia XZ2 Compact H8324) to flash on the new Android 9.
My device was built in Hong Kong.
I went like this:
First I downloaded the current German Android 9 Stock Rome via Xperifirm. H8324_Customized DE_1313-6204_52.0.A.3.84_R2B
Before the flash, I created the * .ftf file in flash tool 0.9.25.0, as shown in a Youtube video. The whole thing worked fine.
Then I put my device into Flash mode and integrated the latest drivers into my PC.
Before I could start the flash process, I had to move the *. Fsc script from the folder "devices \ H83XX" in the folder "my devices" and rename in the current firmware. Since he gave me the message when starting the flash process that no update script would be available.
Then the flash process started asking if he should skip certain things stored in the script. Of course I confirmed that.
The flash process ran without any further error message and ended with the message that the flash was successful.
However, after starting the Xperia, the message "Your device is corrupted - it can not be trusted" was displayed. The device shuts down after 5 seconds.
Fortunately, I was able to recover my original firmware through the PC Companion.
Can someone tell me where I might have made a mistake on the way and how can I fix this? I would like to have Android 9, but that has not arrived in Hong Kong yet.
This is my first tutorial, hope you enjoy it and take you further.
Thank you first to juandiazmora
So you get Android 9 on your smartphone without any regional restrictions.
The following programs are required: Xperifirm, flashtool 0.9.25.0
1. Download the Rome at Xperifirm which is compatible with your device and you want it. For me, the firmware was unpacked directly by Xperifirm otherwise uses Flashtool Tools> Bundles> FILESET Decrypt
!!! Important with the downloaded files the "fwinfo.xml delete" !!!
2. In the Flash tool go to Tools> Bundles> Create
2.1 There you choose the folder in which the firmware is located.
2.2 Then select your device at Device.
2.3 When branding enter your country version. In my case Germany.
2.4 In version your firmware version you want to install.
2.5 Now important and careful. With folders list you add all files except * .ta files to the firmware content.
2.6 Then click Create and wait.
3. Adapt Flashtool. Go to the folders "Users" \ flashTool \ devices \ H82XX and the
"User". \ Flash tool \ devices \ H83XX
3.1 Copies the 52.fsc from the H82XX to the H83XX
Deletes the 51.1.fsc
3.2 Then copy the complete folder H83XX into the folder "User" \. FlashTool \ mydevices
4. Connect the mobile phone in Flash mode to the PC. Do not forget to install the appropriate driver. Flashtool also provides drivers and Xperia Companion.
4.1 If everything is ready then go to step 5.
*
5. Flashing
5.1 Click on the flash symbol in the flash tool.
5.2 Select flash mode
5.3 For Source folder, select the folder with the previously created firmware file in * .ftf.
5.4 Select Device for Device Filter.
5.5 At Firmwares, select your created firmware.
5.6 For Wipe Sin, select APPSLOG / USERDATA
5.7 Select Disable final verification.
5.8 Flash
6. When flashing, he asks if he should use the 52.fsc.
Simply confirm everything then works well.
For me it all worked out but of course I take no guarantees. Everything at your own risk.
Click to expand...
Click to collapse
@Quarzkopf I know this thread is a bit old but I ran into similar "Your device is corrupted..." error when trying to flash US customization to my UK Xperia 1 ii. I was wondering how you got resolved this to a clean flash without this error at the end? Wasn't clear from instructions. Much appreciate your help
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
link is restricted
Bro. Share file pls on your googledrive. We cantdownload it
Flar4eg said:
Bro. Share file pls on your googledrive. We cantdownload it
Click to expand...
Click to collapse
Excuse me, is that I uploaded the files to my google drive cloud and I detect a dll, or part of the flashtool as a virus, now I upload it again and put the link
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
multiuploader error: WinDNWApi.dll file could not be found.
Skyfall191299 said:
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Click to expand...
Click to collapse
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Skyfall191299 said:
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
Click to expand...
Click to collapse
getting error that el3mon_dram not found. can you help me?
Hello someone has the files ? The download link is inactive
The download link is inactive, please active or reupload please.
Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
good jod
im follwed to this instruction but all links not woriking
pla give me ur telegram or whtas app
and upload files to the new link plz
eldon301 said:
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Click to expand...
Click to collapse
how to create with hex bro ?
links not woriking
link isn't working please fix
akbarshoxdedamirzayev said:
how to create with hex bro ?
Click to expand...
Click to collapse
Find the exact firmware that’s currently in the device, extract sboot from the firmware. You need to find correct location of bl1 bl2 el3 and others, names correspond to which is cut. You need 5 files from sboot. Am stuck on the forth file failing and I still don’t understand how to find them. What I did was follow others with exactly the same problem to see and understand how they got there’s and then tried it on my sboot. I am failing on part4 don’t even know how to make a cfg but from what I understand e for exynos and the number after so mine is e7885. Still not sure like I said
http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip/file download link
Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
Can you check the addresses and lenghts of the partitions cut out of sboot?
I think you've made a mistake.
Can give me the precise partition details?
Are you 100% positive that this is valid at least for most devices of the same chipset?
I'd like to try to make an automated script or a tool of some sort.
Also when I was dividing my A515F U5 sboot I've spotted some long breaks in data which I assumed were empty blocks at the end of partitions.
What confused me about it is that I didn't find those where you said partitions are ending.
Can you demonstrate graphically your partitions in a linear projection?
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
eldon301 said:
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
Click to expand...
Click to collapse
I'd like to help
NonStickAtom785 said:
I'd like to help
Click to expand...
Click to collapse
Hello my friend I am try to get life back into a A750G, it’s completely hard bricked showing exynos usb in device manager. Can i direct message you or should I keep it in the forums. I was falling on part 4 off the files needed to create, I didn’t even know if my cfg file was correct but I tried my best at understanding the creation of the files. Plz help my brothers
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