yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] bovirus:
[MENTION=7223741]bullracing[/MENTION]

There are several clones with MT6572 but different boards.

If you cannot check with board is (using ex FACTORY TEST mode - with POWER & VOLUME-) you cannot flash the right firmware.
[Upgrading, Modifying and Unlocking] bullracing:
[MENTION=637263]bovirus[/MENTION]

OKay, I can understand better, thanks.

Seems that my phone is dead, I try to get into Factory Test, but it only turns ON in a blank white screen blnking, so it maight be is the Main board that its damaged.

Thanks However :)
[Upgrading, Modifying and Unlocking] CVAngelo:
There are two ways to get around the PMT error. First way is to use an earlier version of the SP Flash Tool. Like version 3. But this does not always solve the problem.

The second way is to use the hidden Write Memory tab (hit the Ctrl-Alt-V combination on the keyboard to enter Advanced Mode, then select the Window > Write Memory option from the drop down menu. The Write Memory tab will then appear). Use the Write Memory tab to flash the images directly to the partition you wish starting from the memory address you specify. So if you had made a full ROM backup before you bricked your device (most people unfortunately fail to take this simple precaution), you would simply flash that ROM file starting at address 0x0.

You can find the correct starting addresses for each partition either on the download tab or by looking at the starting linear address in the scatter.txt file. For a softbrick, you might simply want to successively flash the boot.img, the recovery.img and the system.img to their appropriate partitions using the Write Memory tab.

When you use the Write Memory tab to flash, you must turn the phone off BUT leave the battery INSIDE the phone then connect the USB cable.

The Write Memory feature will only work if you identify the Preloader.bin file on the Download tab (so you must check the Preloader box on the Download tab). BUT DO NOT CHECK THE PRELOADER BOX IF YOU ARE GOING TO USE THE DOWNLOAD TAB TO FLASH THE DEVICE. ONLY CHECK THAT BOX IF YOU ARE GOING TO USE THE WRITE MEMORY TAB TO FLASH.

If you don't have the preloader.bin file, simply use the Read Back tab to dump it from the phone.

Finally, be absolutely sure you have the correct ROM for your phone. If the ROM is not the correct one for your device and you flash the wrong boot, recovery or system images to the phone, it will not boot. It will remain or become bricked. The fact that a ROM is for the same MTK chipset as your phone does NOT mean it's the correct ROM for your phone!
[Upgrading, Modifying and Unlocking] bullracing:
[MENTION=6532230]CVAngelo[/MENTION]

Thanks too much! thats very usefull information... I will try it :fingers-crossed:

I have some MTK that are "bricked" I will make what you aere telling me, may I can bring back to life some of them...

Thanks :good:
[Upgrading, Modifying and Unlocking] CVAngelo:
Let us know if you are able to recover any of those bricked devices. I have used the Write Memory tab to unbrick or restore countless bricked devices.

I have also used it to flash custom recoveries on many devices (when the custom recovery image is available). Flashing a custom recovery is the easiest way to root most MTK devices. Once the custom recovery is flashed, you simply need to boot to recovery and install a SuperSu zip and violá...you're rooted.

If you have any questions, just let us know.
[Upgrading, Modifying and Unlocking] bullracing:
[MENTION=6532230]CVAngelo[/MENTION]

its me again... I was trying what you told me about "write memory" lets see if I understood well....

I took up a bricked Lanix X200 from Telcel, I got the Firmware:

"ROM LANIX Ilium X200 Telcel version: ILIUM_X200_TELCEL_SW_07 – Guowei_S408B_QB25S_M402A_6572V1.0.0"

When I try to download it to the Phone with flashtools i get an error "PMT has change to the ROM it must be Downloaded..." this happendes with the version 3.x and 5.x so I proceed with the "Write Memory Tab" with flashtool v5.1524 , already in the tab, in "file path" I loaded the "preloader.bin" that came with the ROM I downloaded, I set the "begin address set" to "0x0", at the "Download Tab" I enabled only the "Preloader check" with the "Preloader.bin" that the scatter file put on it. I pressed finaly "Write Memory" I conected the Phone and it started-finished succesfully. Then I proced to flash the whole firmware at the "Download tab" I press it, conect the device, it is recognized well, but I'm getting this error "BROM ERROR: S_FT_ENABLE_DRAM_FAIL (4032)"

I think I'm making something wrong....
[Upgrading, Modifying and Unlocking] bovirus:
[MENTION=7223741]bullracing[/MENTION]

Youi get "PMT changed" error when you use "DOWNLOAD ONLY" mode and PMT of original ROM and new ROM are difeferent.

If you are sure that the new ROM is for your device you can select all modules and use FIRMWARE UPGRADE mode to avoid PMT error.
[Upgrading, Modifying and Unlocking] CVAngelo:
Well, you were not to flash the preloader.bin file.

Instead, what I had said was that you should flash the boot.img, recovery.img and system.img using the Write Memory tab. The starting address for each of those images you can find in the scatter.txt file (the address to use is called the linear starting address). Or if you had the full ROM backup which is a single file typically about 1GB in size, that is what you would flash starting at 0x0.
[Upgrading, Modifying and Unlocking] bullracing:
Damm it, so I killed my device. I will try to make it again as you said....
[Upgrading, Modifying and Unlocking] CVAngelo:
Not necessarily. If that is the correct ROM for your device, you did not kill it. But always remember that you must never flash the preloader.bin image (neither from the Download tab, nor from the Write Memory tab) EXCEPT if it is part of the absolute last resort.

Now you need to make sure your battery is fully charged and you can try to flash again. You have two choices. You can flash from the Write Memory tab (flash the boot.img, then flash recovery.img, then flash system.img). But do not flash the preloader. However, you need to be sure the preloader box is checked on the DOWNLOAD tab in order for the Write Memory tab to work.

If you are going to use the Download tab to flash, then you must UNCHECK the preloader box but check all the other boxes (except Cache and Usrdata). Then select Download Only. However, if you get the "PMT changed" error, then select Firmware Upgrade. This will check ALL the boxes including the Preloader line. BUT IT IS OK...as this will NOT flash the preloader (because it does not need to be upgraded). This is not guaranteed to solve the PMT error, but it sometimes works. If it doesn't work, your only choice is to flash via the Write Memory tab.
[Upgrading, Modifying and Unlocking] sherlockspringer:
Hi guys! Can anyone help me connect SP Flash Tool to my ASUS X008 (Pegasus 3)? It has worked before, and I flashed a ROM, but now I want (need...) to flash another ROM it just doesn't connect. I'm trying to install the USB VCOM drivers, but whatever I do, it always ends up with a message about the device not starting. I'm running Windows 10 btw.

I suspect it may have something to do with some drivers I installed in order to try to get it working again. Installed several programs like Kingoroot, PDAnet, Driver Auto installer, MAUI META, MTK Droid Tool, MediaTek drivers etc... I've tried to get rid of most of them by now, but I can't seem to uninstall pdanet.

Can anyone help me please?
[Upgrading, Modifying and Unlocking] bullracing:
Try without battery holding volume up and conect the USB cable, or try with another key combinations while conecting the usb cable. Sometimes whe I install a lot of programs and drivers I get problems while conecting devices, before you make something crazy try with another Computer....
[Upgrading, Modifying and Unlocking] sherlockspringer:
Thanks for your help! Unfortunately the battery is non-removable and the button combinations didn't change anything. I'll try it on a different computer, but I'll need to arrange that first... Any tips or tricks I should try in the meantime?
[Upgrading, Modifying and Unlocking] sherlockspringer:
Tried it with a different computer (Win 7) but same problem: no connection. Can anyone point me to the correct VCOM drivers, just to be sure?
[Upgrading, Modifying and Unlocking] CVAngelo:
You say that you are trying to flash another ROM and that previously you had flashed a different ROM. You did not make it clear what state your device is in. So let me ask you a few questions:

Are you able to turn on your device normally? Or is it bricked?

If you are able to turn it on normally, what happens when you connect it to the computer? Does your computer recognize your device?

While your device is turned on, go to Development Options and turn on USB Debugging. Connect your device to the computer. Does the computer recognize the device now?
[Upgrading, Modifying and Unlocking] sherlockspringer:
Thanks for looking into it!!

The device is working normally, only IMEI is wrong. It is not bricked.

The computer recognizes the device when it is switched on. I can access files etc.

USB debugging is already on.
[Upgrading, Modifying and Unlocking] CVAngelo:
Is your device recognized (while it is on) by MTK Droid Tools?
[Upgrading, Modifying and Unlocking] sherlockspringer:
It is indeed recognized by MTK Droid tools.

Hardware : MT6737
Model : ASUS_X008
Build number : CMCC_Phone-13.0.0.5-20160621
Build date UTC : 20160621-073916
Android v : 6.0
Baseband v: MOLY.LR9.W1444.MD.LWTG.MP.V88.P7, 2016/06/21 12:30
Kernel v : 3.18.19+ (wind-kernel@droid) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP Tue Jun 21 15:36:48 CST 2016
Uboot build v : ----- should be root shell
LCD Driver IC : ----- should be root shell
[Upgrading, Modifying and Unlocking] CVAngelo:
So far, so good. Now if you fully charge your device and then shut it off, it is not recognized by the computer? Even if you keep pressing and holding the volume down button while you insert the USB cable?

What I mean by "recognized by the computer" is whether the computer makes a bong sound just as or right after you make the connection.
[Upgrading, Modifying and Unlocking] sherlockspringer:
That's right; the device is not recognized by the computer when it is powered down. Even if pressing (and holding) the volume down button when inserting the USB cable.

The computer makes a sound when I connect the device when it's powered on. An autoplay window pops up asking about what it wants me to do when I connect this device. (Mediaplayer, File explorer, import Pictures and videos)
[Upgrading, Modifying and Unlocking] notaneng:
Help Please

I have Redmi Note 2 (MTK6795) hardbrick.

Everything run smoothly but phone didn't boot up.

- Phone detected by PC

- Driver installed properly

- SP Fash tool run 100%, green ticked appear

I have tried several version of offical fastboot ROM, but ended same thing phone not boot up at all.

Any advice will be appreciated.

Thanks.
[Upgrading, Modifying and Unlocking] jorjee:
I had the same problem. What I did was edit the scatter file to allow TEE1 and TEE2 to download (change false to true). I think I did misc as well. Then from SP Flash Tool download tick those files. After that my tablet booted up.
[Upgrading, Modifying and Unlocking] sherlockspringer:
Any ideas about this?
[Upgrading, Modifying and Unlocking] CVAngelo:
No. I'm not sure what is the problem. Why would your device be recognized when it is on, but not when it's off. Makes no sense to me.

EDIT: Try the following:

1. Attach a wired USB hub to the computer. Then connect your device to one of the USB ports on the hub. See if your computer picks up the Preloader driver.

2. Force the Preloader driver to be permanently present. You can do this on your computer using the Device Manager. Click on ANY device in the device tree then select the Legacy Hardware option in the drop down menu.

Hopefully one of these may work to allow SPFT to connect to your device via the Vcom Preloader driver.
[Upgrading, Modifying and Unlocking] bovirus:
[MENTION=1231669]KimG[/MENTION]mate

The question is OT here. Please read carefull first post.

To use tFalshtool with the device you should installa USB Preloader driover (that it's different than USB ADB driver sued when the device is on).

If the device off is not recognized by PC (pelase check in Device tree if there is yellow question mark) it's a hardware problem of the device or the cable.

[MENTION=7901989]notaneng[/MENTION]

The question is OT here. Please read carefull first post.

This thread only about Falshtool.

Not about how to unbrick your device.

Please check if a thread for device is available and post there or open it.

[MENTION=6532230]CVAngelo[/MENTION]

There are differences in the driver used (USB ADB for device ON - USB preloader for device OFF) and partition used by device (kernerl/system for device on - preloader for device off).

Ex. if the usb preloader driver is not installed or preloader partition is corrupted the device of is not recognized.
[Upgrading, Modifying and Unlocking] CVAngelo:
I understand which drivers are used when device is on versus off. Why I'm confused is that he's installed all the drivers or the drivers were automatically installed. So everything works fine when the device is on. Yet when the device is off, it's not recognized when connected with the computer. Not even as an unrecognized device. It's just baffling.
[Upgrading, Modifying and Unlocking] sherlockspringer:
Skeleton1911 was kind enough to assist me, it turned out that Power Off didn't really mean Power Off. So I had to Power Off through the Recovery. We also checked the USB ports, as Windows 10 is quite fussy about them. I got SP Flashtools to connect now!!!

Many thanks for helping me out, your time and effort is highly appreciated!
[Upgrading, Modifying and Unlocking] CVAngelo:
This is the 2nd time I've seen the following problem. I am using SPFT to flash an Alcatel OT-7040. I've flashed these Alcatels literally hundreds of times. This particular phone, I've flashed many times before. This time, the SPFT initial red bar goes as usual and then SPFT remains stuck at Write Memory 0%. In other words, it simply refuses to flash. Then, eventually a message pops up that says Write Failed. But it doesn't say why!

Anyone else ever get this message? What steps did you you take to resolve the problem?
[Upgrading, Modifying and Unlocking] xfim:
Hi everyone!

I bricked a MTK6572 GSmart Rey R3 phone and I have a MTK droid tools backup but it has completed with an error so I cant convert it to SPFT flashable. The scatter from backup is ok but I dont know how to use it without a working backup. I have a stock rom for it and it has a scatter file in it but SPFT 3 says "Incorrect scatter file format" when I try to load it and SPFT 5 asks me if it is legal when I ty to load it. I tried with the backup scatter and it loads fine but gives a standard DUMP error.

Is there a way for me to flash stock rom using SPFT? I really need to get this phone working again.

Thanks!
[Upgrading, Modifying and Unlocking] CVAngelo:
Can you post a screenshot of the SPFT 5 error? I've never seen or heard of it. I need to see exactly what the screen looks like including the exact wording when the error dialog is thrown.
[Upgrading, Modifying and Unlocking] xfim:
I finally fixed it after 2 days of torture lol, just after I started asking online about the problem. anyway, here's the screenshot
[Upgrading, Modifying and Unlocking] bovirus:
[MENTION=4974544]xfim[/MENTION]

Check you stock ROM and scatter. Check if thw first line of scatter file start with "BIRDA"

If it's true paese remove first line, save the scatter and try to use it.

How do you fix your problem?
[Upgrading, Modifying and Unlocking] xfim:
None of my scater files start like that but it doesn't matter anymore.

I found the SPFT ReadBack fimware for my device somewhere deep in 4pda forum and I flashed it using SPFT 5. Now it's working!
[Upgrading, Modifying and Unlocking] bovirus:
Please post the link for the stock firmware.
[Upgrading, Modifying and Unlocking] kurosava:
when I plug in my turned of phone, it turns on and gets stuck on Samsung galaxy s3 i9300 logo forever... after a minute or so, my pc recognizes it and makes that sound, but sp tool does nothing... I'm very close to smashing it on the wall so if you have any clue how I can get it to be recognized by the sp tool that would be great :D
[Upgrading, Modifying and Unlocking] CVAngelo:
Well, it's definitely no surprise that SPF Tool won't recognize your Samsung S3. SPFT will only work with phones that use the MTK chipset...so you're gonna have to smash your phone on the wall! Can I come watch you smash it for no reason?

For Samsung, which uses the Qualcomm chipset, you need to use ODIN, my friend. Or use Samsung KIES which is Samsung's official software for flashing your device. You're on the wrong thread! Why didn't you search XDA for your own phone first?
[Upgrading, Modifying and Unlocking] kurosava:
I did try both of those

It's not for no reason, but you can come watch it :D Odin won't let me flash anything, it always fails... NAND write operation, fail... I tried almost everything... Stock rom, custom rom, cwm, twrp, kies... In kies, it downloads the wirmware, but when it starts installing it, it gets stuck at 0% forever... I also tried emergency recovery, but my phone won't appear there... Installed all drivers, updated everything... I found I way to flash the firmware to a cd card and it works from it, I'll try it these days when I get the sd card reader for my pc... and then I give up :D thanks for your reply, and telling me i'm using the wrong way, I was just desperate... cheers :D
[Upgrading, Modifying and Unlocking] CVAngelo:
I was trying to be funny and not very successful at it. Thanks for being a sport. Your phone is truly a head-banger. Lol

Perhaps the phone has a locked bootloader or some kind of protection on the system. Who is the operator? Try doing a Google search for your phone from that operator. Maybe you'll find a way to unlock whatever is protecting the system.
[Upgrading, Modifying and Unlocking] jorjee:
Have you tried different versions of ODIN? My phone can only be flashed with 3.09.
[Upgrading, Modifying and Unlocking] bretzelpopo:
hello, i have problem with a smartwatch jm13

https://xdaforums.com/general/help/search-rom-smartwatch-t3531848

i have not enough space to backup my watch with mtkdroidtool, only 30mb and no possibility to add microsdcard .backup begin but write nodl_system.bin error Zero file, no space left on device

i can flash with flashtool but no boot, sytem.img only 17mb, in the backup folder mtkdroid tool keep a system folder and nvram folder . when i readback with spflashtool maybe i do something wrong, preloader end adress stay 0x0000000000 . my system partition is ubifs

with miraclebox 2.26 it write none table at the end of backup, maybe it will work with latest version ?
[Upgrading, Modifying and Unlocking] bretzelpopo:
in mtkdroidtool ROM_flashtool, i have an error ERROR :Boot ungzip: bf.gz: not in gzip format
[Upgrading, Modifying and Unlocking] CVAngelo:
What version of SPFT are you using? And why aren't you doing a read back of the whole ROM? Just do a read back from 0x0 with a length equal to the starting address of the Cache partition! This will extract the complete stock ROM from the device.
[Upgrading, Modifying and Unlocking] bretzelpopo:
Thx for reply, i use last spft and readback from 0x0 to starting address of userdata.

in mtkdroidtool ROM_flashtool, i have an error ERROR :Boot ungzip: bf.gz: not in gzip format
[Upgrading, Modifying and Unlocking] CVAngelo:
Not sure what that error means. But if you are trying to create a CWM custom recovery, don't let MTK Droid read the kernel from your phone because it cannot get the boot.img unless your device is fully rooted.

Other than this issue, I'm not sure why you think you have a problem with your ROM dump. Sounds like your ROM read back is fine (except the length of the read back should be to the starting address of Cache rather than Userdata).

If you're also trying to create the CWM recovery, then you need to check the button to "choose boot and recovery files" manually. Of course you have to make the CWM recovery AFTER you've processed the ROM read back because only then will you have the boot.img and the recovery.img available to manually select.

By the way, this is the SPFT thread and all of the discussions about MTK Droid Tool is off topic. You really should go to the MTK Droid thread to find the best solutions for problems and errors with it.
[Upgrading, Modifying and Unlocking] bretzelpopo:
I think i brick my Watch, i didn't know write in v3 and opt in v5 are the same, i write rom_0 with v3 and now i can't do anything, i have always error S_FT_ENABLE_DRAM_FAIL (4032) or S_DA_NOR_OTP_GETSIZE_FAIL with format, download, otp. I can do memory test which is ok
[Upgrading, Modifying and Unlocking] CVAngelo:
Ouch! Why did you write ROM_0 to the watch? I thought you simply wanted to make a backup of the watch? And create a custom recovery?

What is OTP?

Can you boot recovery?
[Upgrading, Modifying and Unlocking] bretzelpopo:
I didn't want to flash recovery, i have 2 watch jm13, 1 didn't boot cause i put an app in system/app with good permission, i buy an other for recover the system and i have a backup but only 30mb space so mtk droodtool can't make a total backup but keep the file in folder, i try tomorrow with an other pc
[Upgrading, Modifying and Unlocking] CVAngelo:
Make sure you are using SPF Tool to make the backup. That way you can backup to the PC rather than to internal memory. (I can't recall if your watch allows you to access via USB). That way, you backup the ROM_0 from the working watch to the PC and you flash the ROM_0 to the bricked watch. I don't even know why you're using MTK Droid Tools if you're not making a custom recovery. You only need SPFT to backup and to flash.
[Upgrading, Modifying and Unlocking] bretzelpopo:
How to flash rom_0 directly, i can make scatter file without mtk droidtool? Do you think that's because i have not real mt6572 but mt6572aw? When i make scatter with droidtool and readback from spft My preloader end address is 0x0 in table spft but 0x100000 in scatter, when i backup with droidtool preloader end address is 0x1782b in table spft and always 0x1000000 in scatter, i will share my scatter soon
[Upgrading, Modifying and Unlocking] CVAngelo:
The scatter file you made with MTK Droid is fine as you describe. Doesn't matter what the end address is in the table. Only things that matter are the starting linear address and length shown in the scatter!

Tom flash ROM_0 directly, search this thread for "Direct Memory Write". I've explained and discussed the process several times. Too much to write all over again. All you need is the scatter.txt, the ROM_0 and the preloader.
[Upgrading, Modifying and Unlocking] bretzelpopo:
I think spft can't read preloader fot nand mt6572 and i format all, what yout are thinking abou this ? i flash rom_0 like you say but doesnt boot
[Upgrading, Modifying and Unlocking] CVAngelo:
If you flashed ROM_0 from the exact same device, then it's possible your device has a locked bootloader and/or there protections on the system partition.

Are you able to boot into recovery? If you are, then do a factory reset and see if you can boot to the system.

If not, then there's some kind of protection on the system.