yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] CVAngelo:
You can only flash one file at a time from the Write Memory tab. If you have 100 files, then you have to use the tab 100 tines to flash them all. Just make sure you are flashing each file to the correct starting linear address! You'll find the starting linear address for each partition in your scatter.txt file.

BTW, if you have all the files from the custom ROM, why aren't you using the Download tab to flash it? You would only use the Write Memory tab if you are getting an error like "PMT changed for the ROM" when you use the download tab. (I presume you have dumped your stock ROM in case you muck up...just flash the ROM_0 single file dump to 0x0 and you'll be back in full working order in no time).

Yes. You MUST check the Preloader line on the Download tab, otherwise the Write Memory function will not work! You can indicate the preloader from the original ROM or from the stock ROM (they should be the same). But do not flash the preloader.bin from the Write Memory tab (and if you're using the Download tab to flash, you should always leave the Preloader line unchecked).

Checking the preloader line on the Download tab does NOT flash the preloader via the Write Memory tab. It is simply the instruction that you must follow in order to allow the Write Memory function to work.

However, if you are using the Download tab to flash, then checking the preloader line WILL flash the preloader and you'll end up soft-bricking many phones, and you'll have a real hard time unbricking a phone with a bad preloader. Do NOT flash the preloader except as an absolute last resort on some phones. If you are doing a Firmware Upgrade on the Download tab, this will automatically put a checkmark on the preloader line, but that is OK because your preloader will still not be flashed on a firmware upgrade.

WARNING: For everyone reading this post...MAKE SURE YOU HAVE A FULL ROM DUMP FROM YOUR PHONE BEFORE YOU USE THE WRITE MEMORY TAB. THINGS CAN GO VERY WRONG, VERY QUICKLY because this tab allows you to flash ANYTHING to ANYWHERE in your device with no checks or balances. Novices beware. You've been warned.
[Upgrading, Modifying and Unlocking] Gentleman_1:
Ok now it is more clear.

There are files in the ROM that dont have an extension so I should flash them all?

In a previous post I asked about PMT error while flashing a custom ROM through the download tab and you suggested the use of advanced mode.

Yes I already backed up the full ROM as you instructed.

Now I understand that I should direct the SPFT to read the preloader of the original ROM and check its box while flashing through the memory tab.

Got it, thanks!
[Upgrading, Modifying and Unlocking] CVAngelo:
Ok. I remember now. That was a while ago. I thought you were someone else newly arriving on the thread.

Yes, image files don't have to have an extension in their file name. Some do, some don't.
[Upgrading, Modifying and Unlocking] Gentleman_1:
I am attaching a shot to compare between the actual blocks of the phone and to the left the files of the custom ROM. I understand that the number under scatter field should be used as the starting address for each file but not all files are found in the custom ROM. What do you think about that?
[Upgrading, Modifying and Unlocking] CVAngelo:
You're looking at the wrong thing on the right! You need to open the scatter.txt file that is on the left. Ignore the block map. You do not use that to guide your flash! You MUST use only the scatter file (which is derived from the block map). In any event you NEVER need to flash every single partition that's in the block map to flash a custom ROM or even the stock ROM.

In addition, even in the scatter.txt file you are not going to flash every single partition listed...for example, there's no point in flashing a new nvram into your phone unless the one that's there is damaged. And do not flash the preloader.

Finally, the names of the images corresponding to the partitions, and the starting linear address of those partitions are found in the SCATTER file, NOT the blocks map.

I repeat again that for your safety please ignore the blocks map. The only thing you need to flash a ROM with SPFT is the scatter.txt file.
[Upgrading, Modifying and Unlocking] Gentleman_1:
Ok understood. Thanks.
[Upgrading, Modifying and Unlocking] Gentleman_1:
I am attaching hereby a comparison shot between the original and custom ROMs that I have. As you see some partitions in the original are not found in the custom and vice versa. Also, the size of the same partition is sometimes not the same in both (like system.img). How does that affect the outcome?. If the custom partition is larger than original, doesn't that disrupt the next partition and take its place? How about the missing partitions in the custom?. Does that mean it is not compatible?
[Upgrading, Modifying and Unlocking] CVAngelo:
If the custom ROM is for your phone, the differences are meaningless. You are looking at the size of the files, NOT the size of the partitions! The size of the partitions are in the scatter.txt file.
[Upgrading, Modifying and Unlocking] PsyOps69:
Hi. If anyone can help me, I'll be very glad. I bricked my Cherry Mobile Flare X (a rebranded Jiayu S3) by following a guide. Long story short, what I hoped to be a smooth upgrade from stock Cherry Mobile OS to Jiayu S3 OS failed. I am trying to flash a stock OS for my device but SPFT won't finish the flashing process. For anyone's reference, I selected "firmware upgrade" since I intended to jump from stock KK OS for my device to Jiayu Lollipop OS. Though, I ticked the "preloader" option when I started the process. Current error is BROM Error: S_FT_ENABLE_DRAM_FAIL (0xFC0). Bottom right status bar shows that I am connected through MediaTek USB Port (COM9)

Any thoughts?
[Upgrading, Modifying and Unlocking] Gentleman_1:
How about the partitions that are not in the original. Obviously I cant flash them because they dont have a reference in the scatter!

Edit: BTW is there a way to combine all ROM files in one file like ROM_0?
[Upgrading, Modifying and Unlocking] Gentleman_1:
The attachment shows a shot for a Lenovo phone. I cant make a scatter file nor there is a block info. How is that possible? In this case I wont be able to do anything with it at all.
[Upgrading, Modifying and Unlocking] PsyOps69:
Angelo! Thanks for your reply. I downloaded a stock KK ROM from the internet and successfully flashed it to my phone. Ergo, my phone now works again!
[Upgrading, Modifying and Unlocking] CVAngelo:
That's great! Don't forget to click the "Thanks" button. And by the way, if I may ask, which approach eventually worked to get the Vcom Preloader driver to connect? Removed the battery? Fully charged the battery? Forced the driver via Legacy Hardware? Kept trying and trying again?
[Upgrading, Modifying and Unlocking] PsyOps69:
I removed the battery first then placed it back on immediately. After that, I forced the MTK driver through the "Legacy Hardware" option in Device Manager. I opened SPFT in Administrator mode, hit download, then connected my phone while pressing a thumb on volume down button. Voila, it connected and successfully flashed a stock KK ROM to my device.

I have been experimenting with a lot of ROMs since then.
[Upgrading, Modifying and Unlocking] Gentleman_1:
Ok good I will be looking for the ADP PC program and tutorial. Thanks.

I havent flashed anything yet because of the many warnings and cautions and regrets that I read about bricking the phone if something goes wrong. I didnt want to do that until I have answers to all questions I have and be clear about all steps needed. Sometimes I get a problem but dont get any answer from anybody :(. Hopefully now I am ready. :o

---------- Post added at 05:57 PM ---------- Previous post was at 05:38 PM ----------

What if the battery is none removable?
[Upgrading, Modifying and Unlocking] CVAngelo:
I think you are ready. The only way you will have a regretful experience is if you don't have a backup of your stock ROM. But you have your backup and I think you have it in ROM_0 single file format which is the best format for unbricking (you would simply flash the ROM_0 file using the Write Memory tab). You have absolutely nothing to fear.

If the battery is non-removable just ignore it. You only need to turn the device completely off and the flashing works the same. Just be sure the battery is fully charged before you begin flashing.
[Upgrading, Modifying and Unlocking] joydip007xxx:
Flash tool says Storage doesn't match error...

Even after flashing compatible rom
[Upgrading, Modifying and Unlocking] Gentleman_1:
Ok I flashed all the files found in the original scatter file one by one using the memory tab. All the writing went well without errors. However, when booting the watch it didnt go beyond the logo (which is not changed from Fifine to Truesmart). It kept on despite all attempts to turn it off. When connecting it to the computer it recognized it and installed its drivers. The shot from MTK is attached. Any obvious reason why it is stuck at the logo?

The only thing I dont find consistent is when flashing the UBOOT partition. I flashed the file 1k.bin for that partition since there was no file called UBOOT. Did that cause the problem?
[Upgrading, Modifying and Unlocking] CVAngelo:
If you read the scatter.txt file you will probably see that the UBoot partition contains a file called lk.bin. That is normal in most ROMs including the stock ROM. So that's unlikely to be the problem.

If the logo did not change, it's probably because the custom ROM did not provide a logo.bin image. Or you failed to flash one that was provided? It may not have been named logo.bin.

One thing I forgot to tell/remind you earlier is that before you flash any custom ROM, you're supposed to wipe Cache, Dalvik Cache (if you have a custom recovery) and do a factory reset (which wipes data). You should also wipe the System partition (if you have a custom recovery). All of this before you flash the custom ROM.

So now, at this point, since you've already flashed the ROM, boot into recovery and wipe Cache, Dalvik Cache and do a factory reset all from recovery. Then reboot the system. This may clear up the bootloop.

If that does not fix the bootloop, then do the wipes (cache, dalvik and system, data) and flash the custom ROM again. After you flash the custom ROM, then wipe the caches (but not system) and do the factory reset again, then reboot. Let me know what happens.

REQUEST: If possible, can you please post the scatter.txt for the custom ROM. I'd like to see the full contents.

EDIT: I just re-read your post. I may be very confused here. Did you say you flashed the files from the ORIGINAL scatter.txt file? I thought you were flashing the files from the scatter.txt of the CUSTOM ROM. Please clarify. Because, if you are trying to install the CUSTOM ROM, you have to flash the files from its scatter.txt. What am I missing? Did you already flash the custom ROM and got it working, and now you're trying to get back to stock? Your earlier post said you had not yet flashed anything.
[Upgrading, Modifying and Unlocking] Gentleman_1:
I am attaching the custom scatter file and a comparison between the two ROMs.

Yes I flashed the custom ROM and I got this problem.

I opened SPFT to the original scatter to use its linear addresses and to see what partitions need to be flashed. I left all fields checked in including the preloader (this is in the download tab only). You said before that checking items in the scatter file in the download tab doest flash them. Partitions are flashed in the memory tab only isn't that right? Are you saying this was wrong and I should have opened the custom scatter?

The custom ROM has a logo.bin image and I flashed it. I used all images from the custom ROM that were also found in the original ROM. They were flashed successfully one by one in the memory tab. The problem now is that I see the logo in the watch upon starting (which is the custom ROM logo) but the booting process doesn't go beyond that. It is stuck at the logo only and nothing could be done to change it including failure to turn the watch off!. I will try to log into the custom recovery from MTK only because the 2 watch buttons are none responsive. That is after I fully recharge the watch since it lost all its charge. Then I will be able to delete cache and userdata...

The custom ROM has a cache and userdata images and I flashed them too, hoping to find some useful info there. Are you saying I shouldn't have?
[Upgrading, Modifying and Unlocking] CVAngelo:
That's correct. Checking the items on the Download tab does not flash them on the Write Memory tab.

And normally, you do not flash cache and data. You're actually supposed to wipe those partitions via factory reset (which repopulates the data partition with the stock userdata). Normally, you would only flash userdata to restore your personal data from a backup.

Failing to do the wipes (cache, dalvik, system and data) before flashing the custom ROM and failing to factory reset after installation MAY be the source of the bootloop in most cases. So you can repeat the process, but this time, do the wipes before and then factory reset after.

But, I suspect you have a different problem. The source of the problem is that you've been referring to the scatter.txt of the original stock ROM for the starting linear addresses of the partitions. Why did you feel you needed to do that?

When you're flashing a ROM that's specifically created for your device, you are only supposed to use the scatter and files provided with the new/custom ROM. You should not mix the two. But in your case, it may have been a "good" or "thoughtful" error.

What's the problem? Is the reason you're using the original scatter.txt for the addresses is because the addresses in the custom ROM are different? If that's true, then the custom ROM is not for your device at all. The file names for the images may be different, but the addresses MUST be identical to those in the stock scatter.txt.

The only other possibility is that the custom ROM is indeed for your device but your PIT/PMT file needs to be modified before flashing the custom ROM and that's a very complex process. If that were the case, you would need to go back to the source of that custom ROM for the complete instructions about how to correctly install that ROM.

So at this point, you could flash your stock ROM and get your watch back to working order. (Get the custom recovery flashed again as you may need it in future). Then fully research that custom ROM. It is either not compatible with your device, or it requires additional processes before you can flash it.

I'd be happy to help research it for you if you provide the link to the source.

Of course, if the partition addresses in the custom ROM's scatter.txt are identical to the scatter.txt for the stock ROM, then the custom ROM may yet be for your device, but you need to do the wipes and factory reset as noted earlier.
[Upgrading, Modifying and Unlocking] Gentleman_1:
Ok will flash back the stock ROM later and try again without those mistakes.

The custom ROM actually came from Om*ate.com . My watch is from Fif*ne which is an exact replica of Om*te true*smart model. I asked Om*ate to send me their factory ROM and they did. When comparing the 2 scatters I found them identical regarding the shared partitions except the cache and userdata. Those have different linear addresses than original. May be that was another mistake. I am curious what those extra partitions are for and if it is safe to flash them as well.
[Upgrading, Modifying and Unlocking] CVAngelo:
Well since the scatter addresses are the same then that custom ROM is likely compatible with your device. The differences in cache and data partitions may well be the problem right there. You should not flash the cache and data partitions. So to do it correctly, you should proceed as follows:

* Restore your stock ROM and flash your custom recovery.

* Enter custom recovery and do factory reset (same as wipe of data and cache), wipe dalvik and wipe system.

* Turn the device off (you should be able to do power off directly from the Reboot menu in TWRP).

* Using ONLY the scatter.txt of the custom ROM, flash all the images that are in the custom ROM (excluding preloader, cache and userdata). Do NOT use any files from the stock ROM, even if they have the same name as the corresponding file in the custom ROM. For example, many custom ROMs have a modified kernel and will still name the file boot.img; so even though the image names are identical, the contents are different. IGNORE the stock ROM.

* Do NOT reboot the system yet. Instead, boot into recovery and do a factory reset.

* Now you can reboot the system.

Hopefully, that will get the job done without the bootloops.
[Upgrading, Modifying and Unlocking] leo_hacker82:
any one can help me to write memory with spft to mt6580 i have a readback backup rom..but cannot write..anyone know how can i write this rom_0 to phone..

---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------

my mtk droid tools obviously dont recognize phone cus its dead..so i only has that readback ROM_0
[Upgrading, Modifying and Unlocking] CVAngelo:
Read post #778. It describes how to access and use the Write Memory tab in SPFT to flash ANY image, including a backup ROM obtained from read back, to any MTK device.

The only requirements are that you must have available a compatible ROM for your device, and your device must not be hard bricked. As long as your computer can connect to the device via the MTK USB Vcom Preloader driver, you should be able to revive your device with SPFT.
[Upgrading, Modifying and Unlocking] Gentleman_1:
I did all the steps above but still got a logo loop. :cyclops:

Before I flashed the Onate ROM I flashed the recovery partition of another ROM which I got from XDA. That was TWRP recovery. It worked well for making a factory reset in the original ROM and deleted all cache, userdata and dalvik cache.

When I flashed the Onate ROM file by file, using its scatter file and partitions, I didn't flash its recovery since I wasn't sure it will be a custom recovery. Most probably it is not so I kept the custom TWRP recovery. That recovery gave me this error message when I tried to do a factory reset. Now the log goes in a circle. Turns on, flashes and turns off and reapeats the cycle again and again. Any ideas?

Edit: I managed to flash the Onate recovery into the watch which was as expected an ordinary one. This didnt change the situation. I am still getting the logo loop.
[Upgrading, Modifying and Unlocking] CVAngelo:
You are supposed to flash ONLY the files that came with the custom ROM. I think I've now repeated this about 20 times including the reason! ???. Yet you choose to do something different. Why?

If it came with its own recovery, use that. The recovery partition is tuned to the kernel! If you did not boot to recovery immediately after flashing the custom ROM, you cannot get the data and cache for the custom ROM to populate. Thus you clearly cannot get rid of the bootloop.

Looks like you have to do it all over again. And do it EXACTLY as I said. Do not flash ANY file that is outside the folder of the custom ROM! Pretend only the custom ROM folder exists. You cannot mix the files!

Hopefully the third time is lucky.
[Upgrading, Modifying and Unlocking] Gentleman_1:
That is because you talked about doing steps that depend on having a recovery with those options. The stock recovery for example doesnt have a capability to turn off the device as you said. Anyway, I will try to do it again....without mistake we cant learn :D
[Upgrading, Modifying and Unlocking] ultimatix:
pmt changed for rom

bro you might be trying to flash lower android version than that is currently running on ur device
[Upgrading, Modifying and Unlocking] Gentleman_1:
Actually no, I am sure the 2 devices use the same android version.
[Upgrading, Modifying and Unlocking] CVAngelo:
Well actually, I had said to boot into recovery and do a factory reset AFTER you flashed the custom ROM. Factory reset is found on every recovery...even the stock one. But the key is to flash only the custom ROM's images including the recovery it comes with (but excluding preloader, cache and data). You enter the recovery that comes with the custom ROM to do the factory reset right after you've flashed the custom ROM.

Just to be perfectly clear, it is only BEFORE you flash the custom ROM that you will use the custom recovery (I think it was TWRP) to wipe cache, dalvik, system and data from the stock ROM. Once you do that, you can then flash the custom ROM and only the custom ROM with its own recovery. Then enter its own recovery to do the factory reset.

Good luck! Will keep my fingers crossed.

---------- Post added at 07:58 PM ---------- Previous post was at 07:47 PM ----------

It doesn't matter as long as everything is in keeping with the level of Android in the ROM being flashed.
[Upgrading, Modifying and Unlocking] Gentleman_1:
Well now I am having hard time turning the watch off to be used with SPFT!. Although I removed the battery and replaced it, when I started charging it the logo loop started again without pressing any button. Is there a way to flash the stock ROm from the SD card using its own recovery because that is still working.
[Upgrading, Modifying and Unlocking] CVAngelo:
Sorry to hear that. This is turning out to be quite a project. Anything that could go wrong has gone wrong. Must be frustrating. Now let's try to deal with this new issue.

First, you should try to flash starting with the battery OUT and kept out. Some devices can be flashed to 100% without the battery for exactly this reason. If the flash doesn't proceed with the battery out, then place the battery into the watch at that point. Normally, if the Vcom Preloader driver is connected, the device will stay in what is essentially "download mode" and won't turn on during the flash.

So try this and let me know if you got it to work. You may have to keep trying this and pulling the battery out and placing it back in to get the timing right. Don't give up after the first try.

ALTERNATIVE METHOD: If that doesn't work, there is a way to create a flashable zip to flash a ROM, including the stock ROM. But it takes some work. Here is the thread that explains the process:

http://xdaforums.com/showthread.php?t=2746044

In the instructions where it tells you to make a backup and extract files from the backup, you don't need to do that because you already have the stock images.

FOR LATER: By the way, your custom ROM has a meta-inf folder, correct? When you downloaded the custom ROM, was it in the form of a zip file? If that's true, I think you were supposed to install the custom ROM by placing the zip on the SD card and flashing it from custom recovery. Let's deal with this question after you get your stock ROM back on the watch.
[Upgrading, Modifying and Unlocking] Gentleman_1:
Finally my worst nightmare is over

I connected with the battery out but the red bar was stuck at red and didnt move. You think putting back the battery is possible? Wishful thinking:laugh: The watch is charged through a cradle only which makes it impossible to remove the battery so I was disappointed and returned the battery in place. Surprisingly enough I noticed that the logo loop has stopped. My explanation for this is that the log was resident in the capacitors and when those capacitors discharged after a long wait the logo was gone :)

So now I flashed the stock ROM successfully and did a factory reset from the recovery so everything went back to normal.

Now waiting for further instructions.

This is the link for the custom ROM where I got it from. You can tell me if it is suitable for SD card flash or not.

https://www.dropbox.com/s/idiqd7xr3tq9tsw/omate_TrueSmart_20140513.2.zip?dl=0

THANKS :good: