yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] mbs22:
Sir, good news. I was able to download a firmware of the local stock rom. But here's the thing, not all of the files are in .bin formata. The PRELOADER, UBOOT & LOGO are in .bin format (so normally this would be automatically selected upon selection of the scatter), the BOOT, RECOVERY, SECRO, SYSTEM are in .img format, while the rest (MBR,EBR1 & SEC_RO) doesn't have any file format but is automatically selected.

I already did a Format whole flash except bootloader, so now will try to reflash it using DOWNLOAD mode & will include the PRELOADER. :)

---------- Post added at 10:14 AM ---------- Previous post was at 09:53 AM ----------

Actually, the forum that I mentioned earlier also doesn't have what I was looking for. However, someone posted there to look at 4shared.com for the unknown firmwares. And its at 4shared that I was able to download the local stock rom for this device, its not the oem.

The flashing went successful. The device still won't power on, but when I connected the device to the charging cable, the charging icon appeared and after a few seconds the battery percentage appeared as well! The battery is 0%, which is understandable since flashing the wrong rom files caused the device not to charge properly, which resulted at the device not booting up. So currently I'm charging it & its at now 2%. Will try to boot it up once the battery is charged enough to be booted.

Just hope that I did right this time. :)
[Upgrading, Modifying and Unlocking] CVAngelo:
Congratulations! I think this is the right ROM. You can usually tell when you have the correct ROM because the battery icon only shows correctly when the kernel (boot.img) is the right one for your device. Just be sure the battery is fully charged.

And before you start the phone, you should boot into the recovery mode and do a factory reset. Then start the phone.
[Upgrading, Modifying and Unlocking] mbs22:
I got the right rom, my tablet has resurrected! :)

When the battery went past 50% , I pressed the power + volume up buttons altogether, & it went into recovery mode. Wiped the data for factory reset & then wiped cache just to make sure. Powered the device, now booted up & back to its original local stock rom. :)

Thank you again sir for all the help. :)

And thanks to 4shared, lol :D
[Upgrading, Modifying and Unlocking] leo_hacker82:
thanks for your reply..but after flash the rom_0 backup..the tablet dont power on...i left it charge for 2 days and no signs of life..

---------- Post added at 09:48 AM ---------- Previous post was at 09:44 AM ----------

is there anyway to convert that rom_0 in sp flashtool with scatter..like mtk droid tools but obviously cant do it with mtk cuz the phone is bricked..if i make a full flash and clean maybe work..
[Upgrading, Modifying and Unlocking] CVAngelo:
Then the custom recovery was intended for your stock ROM, not the custom ROM. Likely you will need to port a special custom recovery that's tuned to the kernel of your custom ROM. In other words, you need to send your kernel to someone who knows how to port custom recoveries. It's out of my league. But you may find experts on the topic in a dedicated thread elsewhere on XDA.

No idea. I don't use MTK Droid Tools to backup anything. Personally, I use MTK Droid only for 2 purposes: 1. Extract the scatter.txt file from a device; 2. Create a CWM recovery (and patched kernel) for compatible devices. Because SPFT cannot perform either of those critical functions.

I explained that your data is always changing, but your system does not. So you should never backup the entire ROM to include both your system and your data. It's very inefficient and may be less that effective. Instead, you should make ONE backup of your system (this is usually referred to as a ROM dump or a ROM_0 dump) and you should make FREQUENT BUT SEPARATE backups of your userdata partition.

This way, if your phone bricks and you flash the system only, the result will be that you will revive your phone, and ALL the most recent data that was on the phone at the moment it bricked WILL STILL BE THERE! You will not lose any of your most recent data. BUT, if your phone bricks and you flash a backup of your system AND userdata, the most recent data that was created between the day you made the backup and the day you bricked WILL BE LOST because it will be replaced by the older userdata that was in the backup! So the sensible approach is to make ONE ROM backup of the system to unbrick your device and to make many separate backups of your userdata so that you have a recent copy of just your data. So for example if your phone is NOT bricked but your 10 year old kid accidentally locks you out of your phone today requiring a factory data reset, then you can simply restore the backup of the userdata partition you made last night and you're back in business.
[Upgrading, Modifying and Unlocking] CVAngelo:
Why would you want to convert ROM_0 with MTK Droid Tools anyway. You don't need to do that to flash ROM_0 to your device with SPFT. As you said, you were able to flash the ROM_0 to your tablet and I'm presuming you did that with the Write Memory tab, correct?

If the tablet is not starting after you flashed the ROM_0, there are really two likely reasons: 1) that was not the correct ROM for your device; 2) the battery in your device is completely depleted.

If you're absolutely sure it was the correct ROM, then you need to fully charge the battery in your tablet. You can try to hold the power down button while you connect the tablet to a power charger. Or if than does not work, you will have to open the tablet, disconnect the battery (sometimes the leads are soldered and you need to use a soldering iron to get the leads off and later reconnect them), then you must charge the battery outside of the tablet using a universal charger.

I cannot tell you how often people are trying to work with a device but do not realize all the problems they are having is because the battery is almost or fully depleted and they do not realize it.

The first rule of thumb when flashing ANY device is ENSURE THAT YOU ARE STARTING WITH A BATTERY THAT IS FULLY CHARGED. It is often impossible to tell the condition of the battery on a bricked device, exactly because the device is bricked. Also, charging a bricked device almost always does NOT charge the battery, exactly because the device is bricked. Finally, unbricking a Brickell device very often completely drains the battery and its does not tell you that it is drained.
[Upgrading, Modifying and Unlocking] leo_hacker82:
ok im gonna disolder the battery and try to charging outside maybe that works...
[Upgrading, Modifying and Unlocking] Gentleman_1:
So you are saying if I confirm with TWRP or anyone who knows about it that the custom recovery is designed for my phone I can flash it ALONE safely right?

OK got the idea. Thanks

---------- Post added at 10:02 AM ---------- Previous post was at 09:42 AM ----------

Hmmm. this is quite odd! If the preloader is like a BIOS it should be sealed within a read only memory like how it is in a PC which can NOT be erased. Leaving the "BIOS" subject to be erased like a software doesnt seem wise to me.
[Upgrading, Modifying and Unlocking] CVAngelo:
Not entirely so. A custom recovery is always based on your kernel. So a TWRP for your phone is normally based on the kernel of your STOCK ROM. So if you have a CUSTOM ROM, that TWRP version may not work with it, unless the kernel in the custom is identical to the kernel in the stock. But some custom ROMs have their own special kernel. In that case, you will need to have someone port a custom recovery for that kernel (you simply send the kernel to that individual). Which is why most custom ROMs come with their own custom recovery. Also, you'll note that with MTK Droid Tools, which can create a custom CWM recovery, it always asks for your boot.img file.

A copy of the stock preloader is always stored permanently in a special location on the motherboard of your phone. If you happen to replace or delete the preloader partition, your phone will hardbrick. But there is a procedure involving the soldering of certain points on the motherboard which will restore it back to the partition from the permanent copy. Of course, doing this is the work of a professional tech.
[Upgrading, Modifying and Unlocking] Gentleman_1:
[MENTION=6532230]CVAngelo[/MENTION] Unfortunately I need help again

Remember I flashed my watch successfully with Onate factory ROM. However I didnt like it! It has several problems and not much advantages so I decided to go back to the original ROM. I flashed successfully the first image (boot.img) of the stock ROM through the memory tab but I couldnt proceed with the other images one by one as supposed to. I tried to flash the whole stock ROM but I got the error seen in the shot. What is the problem now and why SPFT is not able to flash the ROM?

PS: Windows is giving a message that "USB device is not recognized" When I plug in the watch. This is because windows couldnt recognized the SD card drive in Onate image. May be it needs a special driver. Onate, by the way, doesnt deal with Play Store. They have their own store so everything in their watch is proprietary!
[Upgrading, Modifying and Unlocking] CVAngelo:
Sorry to hear that you didn't like the Onate ROM. There was also that issue with the camera if I recall.

Well, you can ignore the Windows message. The only messages you need to worry about are the ones you get from SPFT. And from your screenshot, it's clear that Windows is connecting through the preloader driver which is exactly what you want. So you're on the right track.

The error message from SPFT suggests that maybe your battery is quite low. Have you fully charged the battery? Also, you may need to disconnect the battery from the watch first before you flash. I think it's just a matter of trying multiple times after you've gotten a full charge. Keep trying to flash with the Download tab after you get the battery fully recharged.

By the way, are you using the scatter.txt file from the stock ROM folder? And, when you used the Download tab did you uncheck the preloader line? And, what error were you getting when you tried to flash your stock ROM with the Download tab? Also, you might need to select a different download option such as Firmware Upgrade (it will automatically check the preloader box and that's ok as upgrade will not flash your preloader...but it will format the partitions that need to be formatted).

One other thing I should point out. You really, really need to make a ROM_0 dump of your stock ROM system (excluding cache and userdata) using the Read Back tab! We talked about that before. I thought you had already done so. That way, you won't need to be flashing images one by one via Write Memory. You just do one single flash of the ROM_0 with Write Memory then a factory reset, and violá, you've revived your device.
[Upgrading, Modifying and Unlocking] Gentleman_1:
The battery was fully charged. I cannot disconnect the battery then reconnect it since it is charged through a cradle only so this maneuver - like in a phone - is not possible here. (unless I find a way to connect the battery to the watch through special wiring which is going to be a hassle).

when I was using the download tab, I was trying to flash another custom ROM. I used its scatter file and unchecked the proeloader, the cache and the userdata. I used download only tab but that way never got through so I gave it up and tried the memory tab. I flashed boot.img well from the custom ROM using its scatter file while preloader was checked. When I tried to move to EBR1 partition of that custom ROM I havent succeeded yet.

I already have the stock ROM in one file. I was trying to flash it with the memory tab - after I gave up on the custom ROM- as you see in the shot from the previous post. I never tried to flash the stock ROM through the download tab.

Now I noticed that when I plug in another phone with its battery is out I get 2 preloader drivers in the device manager but when I plug the watch I get only one driver on com4. If you look back at the shot from last post you find that the watch was connected through com3 so that driver doesnt seem to be consistent. Should I uninstall the driver on com4?
[Upgrading, Modifying and Unlocking] CVAngelo:
Yeah ok. I did not realize you were trying to flash the stock ROM_0. I thought you were flashing images of the stock ROM one by one starting with boot.img. I misunderstood your post.

So, you should uninstall the Vcom driver on com4. That appears to be the driver that you installed as Legacy Hardware at some point.

But you simply have to keep trying the Write Memory flash of the stock ROM_0. If the battery is full, then it should eventually flash. But usually, a bricked device will not allow the battery to be charged (even via a dock)...so I'm not sure how you know the battery is fully charged at this moment. And, try the volume down or volume up button on the watch.

In any event, if it still doesn't work, you should try flashing the stock ROM from its folder with all the stock images via the Download tab. I can't recall if you have all the component images. If you don't, use MTK Droid Tools to break down the ROM_0 stock file.
[Upgrading, Modifying and Unlocking] Gentleman_1:
Well I am getting different errors from SPFT as in the shots. You notice that everytime the watch connects, it has to be through com3 only.

After that I uninstalled all preloader drivers (through USBDviewe) and tried to reinstall. I ran a file called installdrv64.exe then plugged the watch. I was supposed to get an entry in the device manager called MTK preloader and should open it and upgrade its driver into the one I have under win 7 BUT I got the preloader driver installed automatically on com5 as you see in shot. It seems that SPFT is insisting on reading the com3 only for the preloader while that driver is installed on com5 now. When I plug the watch this com5 appears and it disappears when unplug it. Is there a way to make SPFT read the driver on com5 or how to completely uninstall and reinstall the driver?
[Upgrading, Modifying and Unlocking] CVAngelo:
Your drivers appear to be fine actually. Those errors may have nothing to do with the drivers.

But then again, anything is possible. You can actually change the com ports that the drivers connect through. Right click on the driver in Device Manager then click properties and there should be an "advanved options" button. You may have to uninstall the driver that's using com5 and change the com3 driver to com5. But this is tricky business and getting more complicated by the minute. I don't really know enough about how to help with those kinds of things.

Before doing any of that...try rebooting your computer then trying to flash again. Did you try changing the actual physical USB slot you're connecting the watch to? Do you have another computer you can use?
[Upgrading, Modifying and Unlocking] Gentleman_1:
Finally, after struggling with SPFT and the driver I got the stock ROM flashed :victory:

Now let me understand something well. You are saying I can flash the other custom ROM I have through the download tab (Not the Write memory) by picking its scatter file and use the firmware tab which will require the preloader CHECKED and that is OK?
[Upgrading, Modifying and Unlocking] CVAngelo:
Yes. That's what I wrote and I meant it. The NORMAL procedure for flashing any ROM is via the Download tab. You must select its scatter.txt. But there are various options for downloading. If Download Only (always with preloader unchecked) doesn't work, you can try Firmware Upgrade (this option does not flash the preloader even though it is checked along with every other partition...only the partitions which are to be upgraded are formatted and flashed). In some devices, the ONLY way to flash even the stock ROM is via Firmware Upgrade (like some BLU models).

The option to Format All and Download is a last resort option because this will format everything (except preloader) and some partitions if formatted may not be recoverable on certain devices like some Alcatels where it will obliterate your nvram making the phone no longer a phone!

Hence, Download Only and Firmware Upgrade are the two options that one should try first. If neither of these work, that is when you use the Write Memory option (or like I do, to quickly flash custom recovery or ROM_0). Remember this is an advanced, HIDDEN option. They didn't really want us using that hidden tab because you can easily softbrick or even permanently wreck any device with it. Lol
[Upgrading, Modifying and Unlocking] Gentleman_1:
Ok I tried to use the download tab. As you see in the shot the location of the android partition was empty. When I tried to locate that partition from the same custom ROM I got the message in the shot and the location was not filled. What can you say about that?

PS: offcourse I pointed at the system.img file for that location.
[Upgrading, Modifying and Unlocking] CVAngelo:
When you respond "Yes" to the dialog, what happens next?

Well those rows are all controlled by the contents in the scatter.txt file. So what does the scatter.txt of the custom ROM have for the specifications of the Android partition? Can you post/attach the scatter.txt file so I can read it?

Also, you are in Download Only mode, so you would uncheck the preloader, cache and userdata rows correct?
[Upgrading, Modifying and Unlocking] Gentleman_1:
Ok here is the scatter file

when I press yes nothing happens but the location remains empty so no address for the system is filled in

Yes I was going to uncheck the preloader, cach and userdata.
[Upgrading, Modifying and Unlocking] CVAngelo:
The scatter.txt file seems fine, although it's that horrible old format that only gives starting addresses and whether the partition line will appear on the SPFT Download tab.

There could be a problem with your system.img file. It appears to have a length of 0 or it may be damaged in some way. Take a snapshot of the files in your custom rom folder (Windows Explorer) and post it.

Just for curiosity, select the system.img file from your stock folder (or select any image file from any folder) just to see if that line gets filled in. If it does get filled in when you select some other image, it may suggest that there is indeed a problem with your custom system.img file. Maybe it was a bad download.
[Upgrading, Modifying and Unlocking] Gentleman_1:
This is a shot of the custom ROM in SPFT. Notice that both recovery and system have the same END address. Is that normal? If I select a system recovery from the stock ROM it does NOT fill in. If I select the stock scatter file this problem doesnt happen.
[Upgrading, Modifying and Unlocking] CVAngelo:
Appears to be a problem with the scatter.txt file. It's not that system and recovery have the same ending address..it is that the ending address is zero.
[Upgrading, Modifying and Unlocking] Gentleman_1:
In this case I am left with the option of using the Write Memory tab right?
[Upgrading, Modifying and Unlocking] CVAngelo:
Yes. That's your option.

But it would have been great to know what might be wrong with that scatter.txt and how to fix it.
[Upgrading, Modifying and Unlocking] zbysogi:
It would be beneficial to show how to flash a new rom without loosing data and apps - what should and what shouldnt be ticked off in sp tool
[Upgrading, Modifying and Unlocking] CVAngelo:
It's pretty simple. Do not tick the userdata row otherwise the new user data will be flashed over your existing userdata. No tutorial or video needed.
[Upgrading, Modifying and Unlocking] GuardianOTB:
Guys in need help ASAP. My mother-in-law got a Zopo zp700 for her birthday, but after a while it started downloading apps.. stuff like that. Nod+malware found trojans. Factory reset didn't work. I rooted it and flashed it to CM13 - MM6.0.1. Worked great for 24hours. after that started lagging, crashing... now i can not flash it back to stock 4.4.4 it came with. I downloaded flashtool, firmware, but when i connect the phone to the PC it just doesnt start. like the SP FLash tool doesn't recognize it. Any ideas? i need to get this up and running ASAP. i lost 6 hours today. i am out of ideas.

edit: i tried something..now i'm in bootloop.... damn it...
[Upgrading, Modifying and Unlocking] rmms:
Hi, I have a I960_V2.0 with with a Jlinksz rom I have made a backup from rom and I've already tried several "downloads" on Sp flash tool including with a rom on needrom by Excelvan (Excelvan Jlinksz MT13 9.6″Tablet i960) but no luck. The upload of the rom goes well (the Sp flash tool gives ok on the end) but when turn on the tablet the message "boot error!!!" appear and nothing happens ... This started to happens after format the internal emmc.

Anyone have an idea to solve this?
[Upgrading, Modifying and Unlocking] CVAngelo:
Use the scatter.txt file that you created (on search for one online) to do a read back of the stock ROM from your working phone! This will give you a ROM_0 file dump. You can flash this directly to the bricked phone using the Write Memory tab of SPFT. To get the Write Memory tab to appear, hit Control-Alt-V in SPFT. Then, go to the Window menu option in SPFT and select Write Memory. The tab will then appear. To use this tab, you must check the preloader tab on the Download tab of SPFT. And you must, of course, also have the preloader.bin file available. If you don't have that file, just use the Read Back tab to extract it from the working phone.

The next step is to fix the driver issue so that you can properly connect SPFT to the phone for flashing. (BTW, are you running SPFT as Administrator?)

Is your battery in the bricked phone fully charged? Charge outside the bricked phone (i.e., use working phone) to get to 100% charge.

Also, you may need to force installation of the MTK USB Vcom Preloader driver using the Legacy Hardware option in the Device Manager on your computer. It is this driver that allows SPFT to connect to your phone for flashing. Once you've forced the install, then try to flash the L23 ROM again.

You may have to play with the USB cable and the battery of your phone to eventually get the Vcom driver to connect. Also, try holding the volume - or + button when you are connecting the USB cable to the phone.
[Upgrading, Modifying and Unlocking] NOORWAZIR:
help me

i install the usb driver in window 8.1 and also disable the signature in the window start up option and the install the vcom driver but it give code error (10).. then i open sp flash tool latest version and i also try the old version too of sp flash tool. then i open the scatter.text and the press the download and connect my mobile through usb cable and start press volume up key and nothing happen also try volume down key but same nothing happen no mobile is detected kindly help me to resolve this issue
[Upgrading, Modifying and Unlocking] CVAngelo:
Is your phone turned off? Are you sure the phone is off?

Is the battery fully charged?

By the way, what is wrong with your phone? You never gave any background.
[Upgrading, Modifying and Unlocking] Android-UK:
Wondering if anyone could offer some advise. I have windows 10 enterprise on my laptop. I followed the guide to install the mtk drivers for Windows 10 but my elephone p9000 doesn't seem to install correctly. It installs but sp flash tools does nothing when I click download. No errors or unresponsive app, it just doesn't do anything. Anyone know what could be causing this issue?

I haven't tired another flash tool as of yet.
[Upgrading, Modifying and Unlocking] lotstolove:
How long should I wait for this to work on my Blu Studio 6.0 HD? I am not even seeing a red bar, yet.
[Upgrading, Modifying and Unlocking] CVAngelo:
Flashing should commence in under 15 seconds but could take up to 10 minutes to flash an entire ROM (or 30-60 minutes to read-back).

If you're stuck on red bar for more than a minute then something is wrong. SPFT should eventually throw an error. What's the error number?

If not, then you need to make sure you have a fully charged battery.
[Upgrading, Modifying and Unlocking] hero.heneral@gmail.com:
I own Acer Liquid Z530. I have the same error "Obrain DRAM Failed!!! Please check your load matches to your target which is to be downloaded"