I have Bluebo B3000 Android 4.0.4 smartphone, and I am able to flash rom to it.
But if I try to create a backup of my changed ROM, I am unable to flash it, I get the error message:
brom error: s_ft_nand_readlen_not_page_alignment (4017)
It must be something wrongs with the parameters of the backup I perform.
Does anybody know what should be the parameters of the backup operation? what should be the segment sizes?
Thanks!
The scatter file I have contains:
PRELOADER 0x0{}
DSP_BL 0x40000{}
__NODL_NVRAM 0x00000{}
__NODL_SECCFG 0x400000{}
UBOOT 0x420000{}
BOOTIMG 0x480000{}
RECOVERY 0x980000{}
SEC_RO 0xE80000{}
__NODL_MISC 0xFA0000{}
LOGO 0x1000000{}
__NODL_EXPDB 0x1300000{}
ANDROID 0x13A0000{}
CACHE 0x117A0000{}
USRDATA 0x153A0000{}
__NODL_BMTPOOL 0x1FFF0050{}
Related
need samsung copy s duos s7562 cpu 6575 flash file
phone was in pattern lock and dead while format in volcano
China Samsung S7562 flash file needed, please help me
Cpu mt6575
File size= 1.75gb
Analysis of system files...
PRELOADER addr:0x000000 --length:0x040000
DSP_BL addr:0x040000 --length:0x5C0000
MBR addr:0x600000 --length:0x004000
EBR1 addr:0x604000 --length:0x05C000
__NODL_PMT addr:0x660000 --length:0x400000
__NODL_NVRAM addr:0xA60000 --length:0x300000
__NODL_SECCFG addr:0xD60000 --length:0x020000
UBOOT addr:0xD80000 --length:0x060000
BOOTIMG addr:0xDE0000 --length:0x600000
RECOVERY addr:0x13E0000 --length:0x600000
SEC_RO addr:0x19E0000 --length:0x600000
__NODL_MISC addr:0x1FE0000 --length:0x060000
LOGO addr:0x2040000 --length:0x300000
__NODL_EXPDB addr:0x2340000 --length:0x0A0000
EBR2 addr:0x23E0000 --length:0x004000
ANDROID addr:0x23E4000 --length:0x20100000
CACHE addr:0x224E4000 --length:0x20100000
USRDATA addr:0x425E4000 --length:0x74000000
__NODL_FAT addr:0xB65E4000 --length:0x2C03C000
__NODL_BMTPOOL addr:0xFFFF0050 --length:0x000000
Format addr:0x425E4000 --Format length:0x31A1D000
>>Read phone information success.
Your file
This is file you need
www . 4shared . com/get/J-ldd1Jqba/S7562_china_mt6575_by_midou01_.html
I attach scat file, you can preview. Pls remove blank in link
Hello.
I recently bought a Chinese Mediatek 'pbablet' phone/tablet combination; running Android 4.2.2 Model: MTK6572.
Due to it being cheap, it was ideal so I thought, for flashing and development, however I maybe wrong.
However I cannot get it into recovery mode. It won't display the menu when holding down volume + and the power button when powering on.
When pressing these two buttons together on start-up, it actually remains a black screen, and it won't turn on after doing this, and I have to keep pressing the tiny reset button on the side of this device every time I attempt to enter recovery, to get it to turn on as normal again.
Pressing and holding volume - and power at the same time on start-up brings up "Factory mode" (in Chinese) and has no options available for flashing/ROM/ functions, except 'testing' the devices' hardware. This phone doesn't have any other physical buttons except power, volume + and -
I am able to successfully enter CWR by flashing it with MTKDroidTools and rebooting into the recovery mode (while powered up and in the android OS) however I still cannot get into CWR or any recovery mode at all while powering up with power and volume +
I just want to be able to enter a recovery mode on this device, to ensure no future issues and doubts upon the unfortunate events of a permanent brick. My idea is to flash this phablet with ParanoidAndroid; or cyanogenmod, and I could try doing this with a software reset, but then what if the ROM is incompatible, and totally bricks it? Then I have no way in hell to revive and reflash, because I can't access the recovery mode anyway.
I have came to the conclusion that it maybe due to the filesystem, potentially due to it's fbifs, that is the cause to no recovery mode, but what if it's ext4, does any of this make a difference.
Is there any way to make this device open the recovery menu while powering it on?
When I attempt to enter recovery mode while powering up with volume +, the device is basically a brick, until I press reset. It doesn't respond at all. The only way to enter recovery menu is by booting into android resetting the device into recovery mode via an app.
What's the deal with this, please can anyone guide me out of this noob pit, and make progress to this issue? Thank you.
Device Info -
Hardware : MT6572
Model : MT6572
Build number : ALPS.JB3.MP.V2.0
Build date UTC : 20131104-123514
Android v : 4.2.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V1, 2013/09/18 03:24
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #10 SMP Thu Dec 19 09:40:47 CST 2013
Uboot build v : -----
LCD Driver IC : 1-hsd070idw1
Scatter eMMC -
PRELOADER 0x0
MBR 0x600000
EBR1 0x680000
NODL_PRO_INFO 0x700000
NODL_NVRAM 0xa00000
NODL_PROTECT_F 0xf00000
NODL_PROTECT_S 0x1900000
NODL_SECCFG 0x2300000
UBOOT 0x2320000
BOOTIMG 0x2380000
RECOVERY 0x2980000
SEC_RO 0x2f80000
NODL_MISC 0x2fc0000
LOGO 0x3040000
NODL_EXPDB 0x3340000
ANDROID 0x3d40000
CACHE 0x2c740000
USRDATA 0x43f40000
NODL_FAT 0x96b40000
NODL_BMTPOOL 0xffff00a8
preloader 0x0000000000600000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000001d80000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0
sec_ro 0x0000000000040000 0x0000000002980000 2 /dev/block/mmcblk0
misc 0x0000000000080000 0x00000000029c0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000002a40000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000002d40000 2 /dev/block/mmcblk0
android 0x0000000028a00000 0x0000000003740000 2 /dev/block/mmcblk0p4
cache 0x0000000017800000 0x000000002c140000 2 /dev/block/mmcblk0p5
usrdata 0x0000000052c00000 0x0000000043940000 2 /dev/block/mmcblk0p6
fat 0x0000000051440000 0x0000000096540000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
Sorry for being such a noob, I don't know if any of this information is useful in the slightest.
device name???
hey tell your device name and brand.. and also do you have backup of your stock rom???
Sakthivel_Subbiah said:
hey tell your device name and brand.. and also do you have backup of your stock rom???
Click to expand...
Click to collapse
Alps MT6572
yes, I managed to backup my stock rom.
Use sp flash tools
Download Sp flash tools. Load scatter file MT6572_Android_scatter_emmc.txt from your backup. Uncheck all options except recovery dont click preloader because if you flash wrong preloader it will brick your device. then click download button and connect your phone without battery via USB now watch for red blue and yellow lines then finally a window with a green circle download ok. now you can remove usb plug and boot your phone into recovery..:good:
Note: You need mtk vcom preloader drivers before using sp flash tools. just connect the phone without battery your computer will detect it automatically and click install drivers automatically
Sakthivel_Subbiah said:
Download Sp flash tools. Load scatter file MT6572_Android_scatter_emmc.txt from your backup. Uncheck all options except recovery dont click preloader because if you flash wrong preloader it will brick your device. then click download button and connect your phone without battery via USB now watch for red blue and yellow lines then finally a window with a green circle download ok. now you can remove usb plug and boot your phone into recovery..:good:
Note: You need mtk vcom preloader drivers before using sp flash tools. just connect the phone without battery your computer will detect it automatically and click install drivers automatically
Click to expand...
Click to collapse
Thank you very much for explaining this solution, but the battery for my device is built in; sealed and I can't take the battery out, so does this mean I can't use SPflash?
CPUzX said:
Thank you very much for explaining this solution, but the battery for my device is built in; sealed and I can't take the battery out, so does this mean I can't use SPflash?
Click to expand...
Click to collapse
If you have reset button on your tab press it and you can connect usb by holding vol up button and releasing it after it is detected by sp flash tool(red bar) if you dont have reset button just switch off and keep it for 5 min and give a try... but make sure that you clicked only the recovery...
if sp flash tools doesnt recogonize your phone, just go into factory mode and keep it a side open minimal adb and fastboot or you can download from this thread http://forum.xda-developers.com/showthread.php?t=2317790 just copy your recovery.img from backup and paste into the folder where minimal adb and fastboot.exe is placed. now open minimal adb and fastboot now connect your phone via usb in factory mode now type:
adb reboot bootloader( now your phone reboots into a black screen)
type fastboot devices and see if there is any device id or name if it shows your device name then type
fastboot flash recovery recovery.img (make sure that you have copied recovery file named recovery.img in same folder)
now flashing will progress after done type fastboot reboot (Now your device will reboot)
then now switch it off again and go into recovery mode!!!
MT6572 teeamge e701
hello, I also have a similar phone to your rom to flash tool you create me, please, I need to restore my phone table. thanks
how did you find a solution to this?
I realise scatter files are different for every phone and manufacturer.
However, I'm really struggling to find out what each memory slot is actually used for.
Some are obvious but some don't make much sense to me......there doesn't seem to be any standard desciptions anywhere.
I checked my W8 Beyond scatter file and noticed that the "__NODL*" do not feature when you load a scatter file into Flash_tools.
Why is this ???? I can see each block follows the previous one.
I can only think that these are reserved blank memory allocations ?
PRELOADER 0x0
MBR 0x600000
EBR1 0x680000
__NODL_PMT 0x700000
__NODL_PRO_INFO 0xb00000
__NODL_NVRAM 0xe00000
__NODL_PROTECT_F 0x1300000
__NODL_PROTECT_S 0x1d00000
__NODL_SECCFG 0x2700000
UBOOT 0x2720000
BOOTIMG 0x2780000
RECOVERY 0x2d80000
SEC_RO 0x3380000
__NODL_MISC 0x3980000
LOGO 0x3a00000
EBR2 0x3d00000
__NODL_EXPDB 0x3d80000
ANDROID 0x4780000
CACHE 0x2d180000
USRDATA 0x34f80000
__NODL_FAT 0x134f80000
__NODL_BMTPOOL 0xFFFF00a8
_NODL flag indicates that those are protected blocks that shouldn't be touched (overwritten during firmware upgrade) because they
contain device specific info like IMEI, MAC addresses and other stuff.
(NODL as "no download")
C3C076 said:
_NODL flag indicates that those are protected blocks that shouldn't be touched (overwritten during firmware upgrade) because they
contain device specific info like IMEI, MAC addresses and other stuff.
(NODL as "no download")
Click to expand...
Click to collapse
Many many many thanks C3C076.
I made a mistake with the block sizes and ended up formatting the whole phone.
I flashed with the latest THL W8 beyond offical firmware and all good again!
Strangley the only thing that was missing was he IMEI numbers for each sim slot but I added them in ENG mode.
Maybe this is a question for another thread but I rooted and tried out the THL GPS fix but it doesn't seem to help much.
The stock w8 beyond rom doesn't seem to handle EPO.Why are the EPO options in the standard android settings greyed out and downloading EPO via the engineering menu fail ??
C3C.... if I could buy you a coffee it would be a large one !!
Hi!
My main aim is to root a china phone (symphony w67).
I made the scatter file, rom and stuffs. Now the problem I end up with is when I want to make the cwm recovery image using the Mtk Droid Tools. Here is the log:
--------------------------------------------------------------------------------------------------------------------------------------
--->>> Connect to device <<<--- --- The preservation folder on the computer: C:\Users\Adib\Desktop\MtkDroidTools v2.5.3\backups\W67_140811_ForFlashtoolFromReadBack _141029-124724\ --- scatter is write to the file:
C:\Users\Adib\Desktop\MtkDroidTools v2.5.3\backups\W67_140811_ForFlashtoolFromReadBack _141029-124724\MT6572_Android_scatter.txtcopying is complete
-- preloader.bin ...it is copied ... cut OK
-- MBR ...it is copied
-- EBR1 ...it is copied
-- pro_info ...it is copied
-- nvram.bin ...it is copied
-- protect_f ...it is copied
-- protect_s ...it is copied
-- seccfg ...it is copied
-- uboot.bin ...it is copied
-- boot.img ...it is copied
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
-- recovery.img ...it is copied
-- secro.img ...it is copied
-- misc ...it is copied
-- logo.bin ...it is copied
-- expdb ...it is copied
-- system.img ...it is copied
--- task is complete ---
------------------------------------------------------------------------------------------------------------------------------------------------
As u can see there are 2 errors:
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
and also no modified cwm recovery image is created in the backup folder. So may I please have some solution for this error? I became very desperate, been trying to root this device for 4 days.
Below are more details about the mobile if it helps in anyway:
Model number: W67
Android version: 4.4.2
Baseband version: MOLY.WR8.W1315.MD,WG.MP.V43, 2014/05/22 18:56
Kernel version: 3.4.67
Build number: W67_1_XXX_V01.0_V2.0_20140809
brother,,,
How to Root Symphony W67
i got the same error, maybe locked bootloader
Same error with a Mediatek D101_MB_V4
Android 4.4.2
Rocky oo7 said:
How to Root Symphony W67
Click to expand...
Click to collapse
Message me rocky, I can root w67
Adib254 said:
Hi!
My main aim is to root a china phone (symphony w67).
I made the scatter file, rom and stuffs. Now the problem I end up with is when I want to make the cwm recovery image using the Mtk Droid Tools. Here is the log:
--------------------------------------------------------------------------------------------------------------------------------------
--->>> Connect to device <<<--- --- The preservation folder on the computer: C:\Users\Adib\Desktop\MtkDroidTools v2.5.3\backups\W67_140811_ForFlashtoolFromReadBack _141029-124724\ --- scatter is write to the file:
C:\Users\Adib\Desktop\MtkDroidTools v2.5.3\backups\W67_140811_ForFlashtoolFromReadBack _141029-124724\MT6572_Android_scatter.txtcopying is complete
-- preloader.bin ...it is copied ... cut OK
-- MBR ...it is copied
-- EBR1 ...it is copied
-- pro_info ...it is copied
-- nvram.bin ...it is copied
-- protect_f ...it is copied
-- protect_s ...it is copied
-- seccfg ...it is copied
-- uboot.bin ...it is copied
-- boot.img ...it is copied
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
-- recovery.img ...it is copied
-- secro.img ...it is copied
-- misc ...it is copied
-- logo.bin ...it is copied
-- expdb ...it is copied
-- system.img ...it is copied
--- task is complete ---
------------------------------------------------------------------------------------------------------------------------------------------------
As u can see there are 2 errors:
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
and also no modified cwm recovery image is created in the backup folder. So may I please have some solution for this error? I became very desperate, been trying to root this device for 4 days.
Below are more details about the mobile if it helps in anyway:
Model number: W67
Android version: 4.4.2
Baseband version: MOLY.WR8.W1315.MD,WG.MP.V43, 2014/05/22 18:56
Kernel version: 3.4.67
Build number: W67_1_XXX_V01.0_V2.0_20140809
Click to expand...
Click to collapse
I have same problem
help with rooting and making cwm mtk6572
my phone is o+8.93 mtk6572 and was following this thread http://forum.xda-developers.com/showthread.php?t=2519432&page=2
but see this image here when using 1st step of droid root tool : i cant make scatter file why is this?
any help is much appreciated. i've been searching for rooting methods for a week a now
i have i9082 samsung duos mt6575 and it's restarting after show samsung logo continuosly.
i format it with miracle box but same. and after format i collect it's info that is below.
info:
Code:
Waiting for USB Port...
Set MediaTek PreLoader USB VCOM Port (COM6)
Please Hold "ON" to connect with the phone...
Connected to Phone.
CPU: MT6575 SW: E201 Ver: CB00
Downloading Boot8 ...
EMMC Size: 0x00E7000000
Flash Type: EMMC
INT/EXT RAM Size: 0x0+0x0
Reading infr(EMMC)...
PRELOADER BaseAddr:0x0 Size:0x40000
DSP_BL BaseAddr:0x40000 Size:0x5C0000
MBR BaseAddr:0x600000 Size:0x4000
EBR1 BaseAddr:0x604000 Size:0x5C000
__NODL_PMT BaseAddr:0x660000 Size:0x400000
__NODL_NVRAM BaseAddr:0xA60000 Size:0x300000
__NODL_SECCFG BaseAddr:0xD60000 Size:0x20000
UBOOT BaseAddr:0xD80000 Size:0x60000
BOOTIMG BaseAddr:0xDE0000 Size:0x600000
RECOVERY BaseAddr:0x13E0000 Size:0x600000
SEC_RO BaseAddr:0x19E0000 Size:0x600000
__NODL_MISC BaseAddr:0x1FE0000 Size:0x60000
LOGO BaseAddr:0x2040000 Size:0x300000
__NODL_EXPDB BaseAddr:0x2340000 Size:0xA0000
EBR2 BaseAddr:0x23E0000 Size:0x4000
ANDROID BaseAddr:0x23E4000 Size:0x20000000
CACHE BaseAddr:0x223E4000 Size:0x20000000
USRDATA BaseAddr:0x423E4000 Size:0x40000000
__NODL_FAT BaseAddr:0x823E4000 Size:0x6481C000
__NODL_BMTPOOL BaseAddr:0xFFFF0050 Size:0x0
>>Done.
emmc scartter info:
Code:
PRELOADER 0x0
{
}
DSP_BL 0x40000
{
}
MBR 0x600000
{
}
EBR1 0x604000
{
}
__NODL_PMT 0x660000
{
}
__NODL_NVRAM 0xA60000
{
}
__NODL_SECCFG 0xD60000
{
}
UBOOT 0xD80000
{
}
BOOTIMG 0xDE0000
{
}
RECOVERY 0x13E0000
{
}
SEC_RO 0x19E0000
{
}
__NODL_MISC 0x1FE0000
{
}
LOGO 0x2040000
{
}
__NODL_EXPDB 0x2340000
{
}
EBR2 0x23E0000
{
}
ANDROID 0x23E4000
{
}
CACHE 0x223E4000
{
}
USRDATA 0x423E4000
{
}
__NODL_FAT 0x823E4000
{
}
__NODL_BMTPOOL 0xFFFF0050
{
}
full flash scatter size is 885mb.
i need it's flash file or recovery file ........
thanks.
gsm city said:
i have i9082 samsung duos mt6575 and it's restarting after show samsung logo continuosly.
i format it with miracle box but same. and after format i collect it's info that is below.
info:
Code:
Waiting for USB Port...
Set MediaTek PreLoader USB VCOM Port (COM6)
Please Hold "ON" to connect with the phone...
Connected to Phone.
CPU: MT6575 SW: E201 Ver: CB00
Downloading Boot8 ...
EMMC Size: 0x00E7000000
Flash Type: EMMC
INT/EXT RAM Size: 0x0+0x0
Reading infr(EMMC)...
PRELOADER BaseAddr:0x0 Size:0x40000
DSP_BL BaseAddr:0x40000 Size:0x5C0000
MBR BaseAddr:0x600000 Size:0x4000
EBR1 BaseAddr:0x604000 Size:0x5C000
__NODL_PMT BaseAddr:0x660000 Size:0x400000
__NODL_NVRAM BaseAddr:0xA60000 Size:0x300000
__NODL_SECCFG BaseAddr:0xD60000 Size:0x20000
UBOOT BaseAddr:0xD80000 Size:0x60000
BOOTIMG BaseAddr:0xDE0000 Size:0x600000
RECOVERY BaseAddr:0x13E0000 Size:0x600000
SEC_RO BaseAddr:0x19E0000 Size:0x600000
__NODL_MISC BaseAddr:0x1FE0000 Size:0x60000
LOGO BaseAddr:0x2040000 Size:0x300000
__NODL_EXPDB BaseAddr:0x2340000 Size:0xA0000
EBR2 BaseAddr:0x23E0000 Size:0x4000
ANDROID BaseAddr:0x23E4000 Size:0x20000000
CACHE BaseAddr:0x223E4000 Size:0x20000000
USRDATA BaseAddr:0x423E4000 Size:0x40000000
__NODL_FAT BaseAddr:0x823E4000 Size:0x6481C000
__NODL_BMTPOOL BaseAddr:0xFFFF0050 Size:0x0
>>Done.
emmc scartter info:
Code:
PRELOADER 0x0
{
}
DSP_BL 0x40000
{
}
MBR 0x600000
{
}
EBR1 0x604000
{
}
__NODL_PMT 0x660000
{
}
__NODL_NVRAM 0xA60000
{
}
__NODL_SECCFG 0xD60000
{
}
UBOOT 0xD80000
{
}
BOOTIMG 0xDE0000
{
}
RECOVERY 0x13E0000
{
}
SEC_RO 0x19E0000
{
}
__NODL_MISC 0x1FE0000
{
}
LOGO 0x2040000
{
}
__NODL_EXPDB 0x2340000
{
}
EBR2 0x23E0000
{
}
ANDROID 0x23E4000
{
}
CACHE 0x223E4000
{
}
USRDATA 0x423E4000
{
}
__NODL_FAT 0x823E4000
{
}
__NODL_BMTPOOL 0xFFFF0050
{
}
full flash scatter size is 885mb.
i need it's flash file or recovery file ........
thanks.
Click to expand...
Click to collapse
If I understood you right, you need rom for recover with odin? Here it is samsung-updates(dot)com/device/?id=GT-I9082 . Replace (dot) with dot. I dont have more than 10 post and I cant post links.
zerocoolminja said:
If I understood you right, you need rom for recover with odin? Here it is samsung-updates(dot)com/device/?id=GT-I9082 . Replace (dot) with dot. I dont have more than 10 post and I cant post links.
Click to expand...
Click to collapse
hey it's not orignal samsung....it's clone cell made by china.....inside chip is mt6575.....do you understand now....
thanks for reply
gsm city said:
hey it's not orignal samsung....it's clone cell made by china.....inside chip is mt6575.....do you understand now....
thanks for reply
Click to expand...
Click to collapse
Sorry for bad information.
any solution from any expert or someone have file then share file here plzzzzzzzz.
need badly
never bacl to life to i9082 mnt6575-s01
i have this phone dead and i search all the world and no body coudlnt get baclk in life again.
i9082 mt6575-s01
this is not mt6575 and miracle and volcano info are all in mistake to show us bad info.
there is no factori rom to work with spflash tools and all are in error 3004 because our file are curepted and falls.
yesterday i found a cell same chip mt6575.....i read factory file from that and now i flash recovery and cache to the faulty cell but it is still hang on logo...........
now i have also factory file readed from working cell.
anybody tell me how to solve that cell....bcoz i have been dead two piece before....
thanks.
when try to upgrade firmware
brom error : s_da_nand_flash_not_found (3016)
[h/w] da didn't detect nand flash on the phone
[hint]:
1. it maybe a smt issue.
2. it maybe a nfi issue.
3. nand hasn't been validated.
please check "memory_validation_list_external.xl" or ask for help.
sp flash tool ver-5.15****
what is problem..........?
Make sure you got the latest SP Flash Tool, then google or search the forums from the SP Flashing Tool and lookup your chipset first...
they might have a Chipset related post with special tools for your device or instructions...
Also Google your error instead of asking directly, I couldn't believe you can't find anything when you google your chipset type and it's flash tool....