yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] bigrammy:
Ok No problem it seems one or more of the .img files is too large for the partition it's trying to fit into. :eek:

Try flash just the EBR files only when completed.

Then try flash the stock rom again in Format + Download mode Use the v5.14 tool as I know this worked on a phone I had once which also had messed up partitions. :good:

Note: You must select all the boxes in the download including the preloader or you will not be able to fully change the partitions otherwise ;)
[Android Q&A, Help & Troubleshooting] Domcek:
Nothing... Format all-Download

S_FT_FORMAT_FAIL

I tried then Firmware upgrade, result:

__NODL_PRO_INFO: Failed to get PMT info.
[Android Q&A, Help & Troubleshooting] bigrammy:
Just try Download only.

Trial and error i am afraid until we can get a successful boot then we can fix things in other ways. :fingers-crossed:
[Android Q&A, Help & Troubleshooting] Domcek:
Tried that, nothing...

Even tried twin ROMS (without preloader) for KVD K7, Cubot one official and HDC One M7, all the same.

Strange is that I can flash all of these preloaders and the result is always the same.

---------- Post added at 08:18 AM ---------- Previous post was at 08:05 AM ----------

Seems that now both the batteries are gone, empty. :(
[Android Q&A, Help & Troubleshooting] Domcek:
Thank you for the info.

But nothing.

I did according to instructions (additionally I tried to get support on 4PDA, thanks to Legiondark), I see the message PMT layout changed but cannot format and cannot download. Tried Download, Format, Firmware upgrade. I got even the PMT and EBR1/EBR2 from Legiondark, but...

USB detectable, when preloader is not flashed it shows MTK USB when I download Preloader on phone it shows Preloader USB VCOM, so it is detectable. I tried to use different ports and install/reinstall drivers.

Yesterday I could not format only android/cache/userdata and today only preloader can be flashed and sometimes the EBR1/2 and PMT files (message recevied at next iteration to user Format all-Download or Firmware upgrade but after trying I get the message F_ST_FORMAT FAIL).

As it was bought from China over internet it seems that it is time to smash it. :(
[Android Q&A, Help & Troubleshooting] bigrammy:
:laugh: Yes these phone's can be very frustrating I spent 5 days recovering one of the phones I had after someone had done a bad flash.

What version's SPFlashTool have you tried :confused:

Try use these different versions some versions format better some download better again just experiment :eek: Here Here and Here
[Android Q&A, Help & Troubleshooting] Domcek:
yup, frustrating...

the problem is that the preloader can be flashed (only from stock) and I have even tried from similar phones but it does not let to flash a wrong one. I can always flash the stock preloader again and again.

Phone is detectable (MTK USB/Preloader USB) and it reads the information (emmc, read back, test,..) but I cannot format it and I've tried using about 10 Sp flash version 3.x and 2 versions 5.x. :crying: I see that I haven't used the first 2 you added so will, the last (5.x version) I've used, always rund as admin and tried.

Tried to flash it also using 4PDA help (http://4pda.ru/forum/index.php?showtopic=500445&st=540), tried flashing "twin" roms: KVD K7, Cubot One, HDC One M7 (several roms) but all without success, it always hangs on format (never goes past 0%). USB port is OK, drivers on PC are OK (used usbdeview and uninstalled all and reinstalled), USB on phone is firm and not damaged, in short phone is like new, :(

Yesterday I tried using the testpoint method, found how to jump start it to detect without battery :mad: but I it seems that it started to charge the battery prior so that part is not needed.

Possible that the emmc flash got fried by itself? Can I test that somehow?
[Android Q&A, Help & Troubleshooting] bigrammy:
Hi bro,

It's really hard for guys like Legion Dark and myself to diagnose the problems when we do not have the phone in our hands I am kinda running out of ideas here :(

Normally these suggestions will work and it's really quite hard to brick these phones normally. :eek:

Most problems happen when a Kernel/boot.img not meant for your phone gets booted because the kernel can sometimes overwrite important files in the /dev area such as the pmt, ebr, mbr and many other files which are located there. SPFlashTools references files contained in there and if there is a file with info that conflicts with what it expects it will error so it could be something like the fstab file not match what the pmt file says. :eek:

Maybe you could try to flash just the stock boot.img then start the phone and leave it for a good while even if it does not fully boot it may rewrite some of the corrupted files :fingers-crossed:

After try to reflash the whole of ROM again and try in all different modes download only, format + download, Firmware Upgrade,

PS: Make sure you use the STOCK ROM I linked earlier 1gbx8gb tronsmart I think the legiondark PMT is modified to 4gb again this will confuse SPflashTool so

Stock ROM all parts selected flash with SPFlashTool.
[Android Q&A, Help & Troubleshooting] Domcek:
Great, thank you for the all advices given.

I have a somewhat more than basic experience with ROMS, porting, linux and Qualcomm based phones (HTC, Huawei, Samsung,...) and I would not qualify myself as a novice but I must admin these MTKs are something new to me, also as it seems a lot of problems which seem unlogical to me so I am a little lost.

Strange to me is that the box says 4 Gb(it had 620 Mb system, cca 120 mb cache and 1,1 Gb of /data with emmc of approx. 2 Gb) and I see that you note that I should use 8 Gb and not 4 GB PMT and scatter (and of course ROM), more strange is that the SP FLash tool sees it as a 8192 Mb device.

I have tried the 8 Gb stock now and I can't flash the preloader (only 4 Gb Stock is OK) nor and other parts of it: S_FT_ENABLE_DRAM_FAIL (4032) and if I am not mistaken that is an error for the wrong ROM flash?!
[Android Q&A, Help & Troubleshooting] bigrammy:
:o Hi bro,

I did not realise that Tronsmart did an MT6589 4gb and 8gb version but it seem's they do :silly:

They also do a MT6582 4gb version just to confuse things further :laugh:

Well now I am really confused :eek: as all but the newest Cubot One's are MT6589 1gb + 8gb

Did all the problems started when you flashed the ColorOSROM :confused:

Was the ColorOS ROM for a Cubot One or Tronsmart and If I it was for Tronsmart was it for 8gb or your 4gb version :confused:

I have ported the stock ColorOS for my own phone and I can say that the ColorOS makes quite a lot of entries on kernel init.rc It also shuffled things around so you don't need to partition things manually :cool:

What I am trying to say is that if the ColorOS zip contained a heavily modified Kernel Which it would need for ColorOS to work properly and it's not for your exact phone then this maybe the cause of the problems and the reason I never shared my Port of ColorOS as I would of had to manually edited all the different Kernels be be sure they all worked example MT6589 1200mhz 1500mhz and 1500mhz "T" version all slightly different and if they become mixed up then you start getting bugs such as screen not waking up no wifi connection camera issues etc etc :crying:
[Android Q&A, Help & Troubleshooting] Domcek:
Yes, it is MTK6589 1Gb/4Gb. :)

This is the last ROM: http://4pda.ru/forum/index.php?showtopic=575125&st=0#entry28631530 - Color OS Alt

It worked great for several days, no issues, then just fell asleep and could not boot - android or recovery.

Problem is the Format in SP Flash tools. Format cannot format to at least 10 different scatter files and the strangest thing is that I cannot format or download the MTKDroid backup which I made, always DRAM error. Format always hangs on 0 % with the message S_FT_FORMAT_FAIL (4010) but read back works?!?

Memory test output:

===============	Memory Detection Report	===============

Internal RAM:

Size = 0x00020000 (128KB)

External RAM:

Type = DRAM

Size = 0x40000000 (1024MB/8192Mb)

NAND Flash:

ERROR: NAND Flash was not detected!

EMMC :

EMMC_PART_BOOT1	Size = 0x0000000000200000(2MB)

EMMC_PART_BOOT2	Size = 0x0000000000200000(2MB)

EMMC_PART_RPMB	Size = 0x0000000000020000(0MB)

EMMC_PART_GP1	Size = 0x0000000000000000(0MB)

EMMC_PART_GP2	Size = 0x0000000000000000(0MB)

EMMC_PART_GP3	Size = 0x0000000000000000(0MB)

EMMC_PART_GP4	Size = 0x0000000000000000(0MB)

EMMC_PART_USER	Size = 0x00000000E2C00000(3628MB)

============	EMMC Test	============

When I tried today to flash "twin" roms sometimes BOOT1/2 changed to 16 Mb (both) and RPMB to 2Mb so it seems that it can alter the memory to one extent.

I think that I realise now the logic of SP Flash tools, it tries to reformat according to scatter but as it cannot find the existing PMT layout it cannot format as the partitions do not correspond. :) I remember, SP FLash tools emmc check clears the emmc on some SP Flash tools, so that is what might've happened, not layout whatsoever now on the phone.

Could I use read back to try locating the correct range of the emmc and then adjust EBR1/EBR2 accordingly for reformat?

Maybe the flash (emmc) is fried? How could I check it?

If you're up for it I can maybe setup teamviewer or something similar for you to see by yourself.

??? I tried a read back of data partition (start from 0x0000000034F80000 end-wild length), stopped at cca 35 Mb, after that the phone screen lights up (black)?!?!
[Android Q&A, Help & Troubleshooting] bigrammy:
Sorry for just the quick reply but I must go to work now :(

MTK DroidTools use's the PMT to make the scatter so maybe it's possible use DroidTools to make another scatter from a Readback and try format again :fingers-crossed:

I will think more about this when at work :laugh:
[Android Q&A, Help & Troubleshooting] Domcek:
Great, thank you.

Some success, I've tried to flash according to partition info selectively partition parts, I managed to format UBOOT and BOOT, I'll try others (cannot find usrdata length). I've tried to user read back for usrdata and android, starts fast but almost stops on usrdata at 25 Mb and on android 69 Mb.

I've contacted yuweng, it seems that only factory rom can save the phone now (all thanks to Sp flash tool and emmc check) :(

Hold your fingers crossed that geekbuying abd tronsmart provide the factory rom (highly unlikely). :(

Seems that I'll have to buy a new phone earlier than expected (6 months is this one old), but probably will go for some brand based on qualcomm as before as I've never till today lost so much time to try mending for the lack of official support for a phone by myself. :(
[Android Q&A, Help & Troubleshooting] bigrammy:
Hi,

Can you upload your working scatter file for me to compare a few things.

I have one last thing I would like to try before we give up but I need to check some things first. :fingers-crossed:
[Android Q&A, Help & Troubleshooting] Domcek:
Of course. :)

Thank you for your time and effort. :)

I am not currently at the PC, my kids are watching cartoons so I can upload it in hour-two. :)

I will provide the stock scatter, my altered scatter (sp flash below 5.x veraion gives info that the regions are not defined good, must calculate some more with hex :) ) and txt file with partitions list which I calculated and managed to manually format (all ok without problems) all parts except android/data/cache (ebr2 gave some problems until located), still have problems finding the start positions of these 3.

I can also upload first firmware.info from MRKDroid which seems OK and the second one (made 1 hour following first which is nonetheless strange, fat partition in particular).

Seems still strange that the device shows as 8192 Mb and then 28 Gb.

I have tried to write raw data (boot.img,recovery.img) to the partitions I managed to format but without success with Sp flash tool.

Sent from Tapatalk
[Android Q&A, Help & Troubleshooting] bigrammy:
Hi,

Please upload.

1, The first firmware.info from MTKDroidTools :good: :cool: (rename to firmware.info.txt to upload here ;) )

2, The scatter that you are able to flash all parts except android/data/cache :good:

I have downloaded the Stock firmware for your phone already :cowboy:
[Android Q&A, Help & Troubleshooting] Domcek:
Great, I've collected the files in the attached ZIP file.

Subfolders are from MTK Droid backup (only main files and in txt names I have added the size of preloader which was strange), in root of zip are scatters and a partitions list with HEX values according which I formatted the partitions (although cannot use regular options for Firmware upgrade, download). The file is in form (name - length (if + beside then I've managed to format according to values manually in SP Flash), second row beginning of partition, next row end of partition).

As MTK Droid cannot find the phone now (SP FLash can) I cannot read the current partitions list, I have even managed to find testoint for the phone (I thought I might get lucky and force it to go through :) )
[Android Q&A, Help & Troubleshooting] bigrammy:
Thanks I got them.

Please allow me 24 hours to reply as It is late now & I have a busy day tomorrow. :(

I think/hope we can fix this as the problem seems to be very very similar to a phone I had which I eventually fixed after many days of trial and error. :laugh:
[Android Q&A, Help & Troubleshooting] Domcek:
Great, thanks.

I hope you'll manage to "cook" something up.

Just some additional info, I've managed to dump all partitions today which I've formatted so it can read back, also now cache range gor finished (126 Mb), gotta find a way to try to read them to see is anything useful in them.

Sent from Tapatalk
[Android Q&A, Help & Troubleshooting] Domcek:
Found the break point... format fails on __NODL_EXPDB 0x3d80000.
[Android Q&A, Help & Troubleshooting] bigrammy:
Things are messed up in the /dev region of the rom it seems :eek:

I notice in your working scatter that you have changed the EBR2 from 0x3d00000 to 0x03700000 :confused:

I would liken it to a car pile up in the /dev region where one car (file) brakes and the rest of the cars/files following on behind crash into the rear of each other. :laugh:

I just hope enough of our cars survived the wreck to be able to restore the phone :fingers-crossed:

So we can but try now.

Take the No1.zip HERE which contains the needed file's and your working scatter (Note I re-edited the scatter to try place the EBR2 file back in its correct location) Load the scatter and select the PMT file then hit download. :fingers-crossed: If it fails use your own scatter and deselect (remove) EBR2 from the flash and try again.

Unplug the Phone and do not try boot it.

Next Download this full stock ROM HERE with modified scatter that now matches the PMT, MBR, EBR1 and EBR2 :fingers-crossed: Load the scatter and hopefully it should look like the attached image with all region start and end address showing.

Now hit Download and connect the phone hopefully there should be no error as the files should all match :fingers-crossed:

If all is well unplug the phone reload the scatter and hit firmware upgrade then connect the phone again and hopefully the partitions will now get formated as part of the firmware upgrade. :fingers-crossed:

Here is the __NODL_EXPDB just incase EXPDB

and misc is attached below.
[Android Q&A, Help & Troubleshooting] Domcek:
Tried step 1. error is -1.png, then I've tried to download stock rom, error is -2.png.

Should I try something different? My scatter is only readable on SP Flash 5.x versions.

Always breaks of EXPDB format (0x0x3d80000), tried to manually format it and then tried to format according to my calculations (0x0x3780000) with length 0x0000000000a00000 but neither way can it format that partition part (all up to that one gets formatted).

Error for formatting S_FT_FORMAT_FAIL (4010), still cannot format it.
[Android Q&A, Help & Troubleshooting] bigrammy:
Use any means you can to get the PMT file and the others if possible :eek: contained in the No1.zip flashed to your phone except EBR2 because in your scatter the EBR2 is not the correct area according to the stock rom and my other mt6589 1gb x 4gb which has a nearly identical layout as the stock tronsmart.

If the PMT flashes then load the full ROM zip I gave you and try different SPFlashTool versions now because you are using a different scatter that should be compatible with older versions v3.1316 works for me most of the time but I am sure you have a good collection by now :laugh: :good:

If you do get a good Download or Firmware Upgrade of the stock then try uncomment (remove _NODL_ from the EXPDB in the scatter) and flash the one I uploaded for you. :good:

PS: What error did you get using Firmware Upgrade as SPFlashtool recommended or does the flash simply stop or break during the formatting part?
[Android Q&A, Help & Troubleshooting] Domcek:
Download/Firware upgrade stops with error PMT changed, error 8038 and the format goes well until it arrives at expdb and then cannot format that part.
[Android Q&A, Help & Troubleshooting] Domcek:
[MENTION=3924647]bigrammy[/MENTION]

I managed to find the testpoint and restart with SP Flash (batteries are not charging) to start the format/download/firmware upgrade, result for download in attachement.

Can I force it somehow?
[Android Q&A, Help & Troubleshooting] bigrammy:
So pre-loader and PMT will not flash even with your working scatter :confused:

Edit: I noticed pre-loader is not selected Please select the pre-loader too. flash the files one by one if needed starting with pre-loader then PMT etc etc.
[Android Q&A, Help & Troubleshooting] Domcek:
[MENTION=3924647]bigrammy[/MENTION]

If I try firmware upgrade, result is in attach.
[Android Q&A, Help & Troubleshooting] bigrammy:
Please try earlier versions of SPFlashTool as suggested and post .PNG of any errors.

Also try this order firmware upgrade (If it fails) download only (If it fails) try format whole flash followed by download only then firmware upgrade :eek: All parts must be selected.
[Android Q&A, Help & Troubleshooting] Domcek:
I am trying, past 5 versions, 7 more to go. :)

I still think that the problem is related to Meteos repartitioning (2.5 Gb data, 203 Mb fat int.storage).

Even went to that extent and disassembled the whole phone, tried to see if some loose ribbon but, all ok.

3 more to go, but seriously loosing hope, managed to flash preloader but getting error 8038 if flashing the No 1 zip.
[Android Q&A, Help & Troubleshooting] bigrammy:
Just a thought could you include the PMT file in the full firmware flash and see if anything changes :eek:
[Android Q&A, Help & Troubleshooting] bigrammy:
Big Thank's [MENTION=4353001]Naddict[/MENTION] :highfive:
[Android Q&A, Help & Troubleshooting] Domcek:
Tried, included PMT and EXPDB in the scatter but without change.

I am continuing to flash now.... :fingers-crossed:
[Android Q&A, Help & Troubleshooting] bigrammy:
Hi [MENTION=1264246]Domcek[/MENTION]

Please add this attached scatter file to the G800_JK808_TRONSMART_A5_V0.2_20130805 ROM I gave you. Rename the original to ORIscatter.txt ;)

The New scatter file will only work with v5.14 SPflashTool hit the firmware upgrade and see if it gives you any arguments. :fingers-crossed:
[Android Q&A, Help & Troubleshooting] Domcek:
Result attached from SP 5.14...
[Android Q&A, Help & Troubleshooting] Domcek:
[MENTION=3924647]bigrammy[/MENTION]

Result attached...

Download and Format all+Download, result for Firmware upgrade same as for Format all...
[Android Q&A, Help & Troubleshooting] Domcek:
[MENTION=3924647]bigrammy[/MENTION]

If using v5.1352 can flash preloader stock and hangs on Flashing firmware at 0% with message attached.
[Android Q&A, Help & Troubleshooting] Domcek:
[MENTION=3924647]bigrammy[/MENTION]

This error is the best one... :)
[Android Q&A, Help & Troubleshooting] Domcek:
[MENTION=3924647]bigrammy[/MENTION]

Sorry for spamming. :)

Format result in attach.

I feel that the motherboard is warmer so it seems that it is trying to format, but... Manual or format by scatter stops on expdb (cannot confirm that for v5.1x but on 3.x that is confirmed).

Seems that it still cannot format as it cannot confirm the location of the partition by scatter?

Manually I have no idea how to locate the current EXPDB parameters.

Can SP tool be somehow forced to flash the rom? (some kind of higher privileges)

Could I somehow read back/read the current partition layout and according to that try to alter the scatter and download? Seems that something like that would work (of course if the current existing layout supports sizes if the flashed parts)
[Android Q&A, Help & Troubleshooting] Domcek:
[MENTION=3924647]bigrammy[/MENTION]

Attached the 3.x version info.

3rd one shows the format which leads to Format/Firmware upgrade error - EXPDB.

Even full Format not working (start 0x0000000000... to 0xE3020000
[Android Q&A, Help & Troubleshooting] bigrammy:
:crying:

Select Format Tab / Select Auto Format/ Select Whole Flash

Post image of any error ;)
[Android Q&A, Help & Troubleshooting] bigrammy:
On v3.xxx SPFlashtool try again and deselect (untick) the DA DL All with Check sum box in the Title Bar.
[Android Q&A, Help & Troubleshooting] Domcek:
:( Always the same, full or partition EXPDB selected.
[Android Q&A, Help & Troubleshooting] Domcek:
Always the same error. Cannot format - 4010 (3.x and 5.1x versions).
[Android Q&A, Help & Troubleshooting] Domcek:
[MENTION=3924647]bigrammy[/MENTION]

Some good news!!! :)

Found the location of EXPDB. :) Managed to Format by range. :)

Beginning: 0x0000000004380000

Length: 0x0000000000a00000

:D:D:D

The question now is... How to use that? :crying:
[Android Q&A, Help & Troubleshooting] Domcek:
[MENTION=3924647]bigrammy[/MENTION]

I see now what could seems like the current layout. From a 8 Gb phone? Cubot One maybe?

:(
[Android Q&A, Help & Troubleshooting] Domcek:
[MENTION=3924647]bigrammy[/MENTION]

The problem is out of range...

Attached, cannot format as it seems that the layout is out of bounds (8 Gb on 4GB). How to mend/correct that? :(
[Android Q&A, Help & Troubleshooting] bigrammy:
Hi sorry I had to go out for a while. :)

Well done bro :highfive: little by little we seem to be making some progress.

It's all about the PMT file bro if we can get that file to the phone then there should be no problem because SPFlashtool will not be looking for a partition that does not exist.

The PMT and scatter are matched so will work once we can get the PMT on the phone this why I asked if adb was working :crying:

You could try to manually format the PMT region of the rom so that spflashtool should then prompt you to download the rom.

Warning though you will probably lose nvram so if you have or can get this backed up first that would be cool .:cowboy:

Edit added 4GB Firmware.info for the PMT range :good:
[Android Q&A, Help & Troubleshooting] bigrammy:
Opps Double posted :laugh: :cowboy:
[Android Q&A, Help & Troubleshooting] Domcek:
Ok, strange.

I format the PMT (as the first part prior to EXPDB can be formatted) and try to download but nothing.

Cannot flash anything, only preloader.

How could I force the PMT on it? :)

Always the same message on v5.1x, PMT changed for the rom, must download (on 3.x versions the error is 8038),

Started to look for a new phone, but currently due to finances all that I can afford is 2x weaker than this one. :)
[Android Q&A, Help & Troubleshooting] Domcek:
Is this progress? :)
[Android Q&A, Help & Troubleshooting] Domcek:
:( Sorry to say, cannot flash pmt (no 1)

Tried to format/fw upgrade/download but format error still... :(