(2014-07-07, 17:22)foppen Wrote: [ -> ]same here u9592
(2014-06-20, 04:25)messiah2505 Wrote: [ -> ]i have a ulefone u692 mtk6592 chip, which is throwing up keyboard errors and a google process error, so i am trying to flash the latest firmware to resolve it.
i have installed the latest pdanet adb drivers, mtkdroid tools and mtk flash latest version.
mtk droid can see the phone when it is turned on and connected, it happily pulls the state and details of the phone.
pda net also establishes a connection to the phone when it is on.
when trying to run the flash tool to flash the firmware try as i like i can't get the flash tool to pick up the phone it just sits and waits for the phone.
i have tried taking the battery out and leaving it out and running the download and firmware upgrade ways and nothing,
i have also tried holding the down button button and running with no connection
i have also tried holding the power button and the vol up button to connect,
but the flash tool still wont connect to the phone.
can someone help me work out what i am doing wrong.
regards
craig
The Brom error comes from not right installed drivers or a broken image. Unzip your rom or unzip a new fresh sp flash tools. That helped me with my e5.
if flash tools dont rekognised the phone, put out the usb and the battery. Plug in the usb in pc and smartphone.Then put in fast the battery. If you have a driver prob, windows will pop up a info. if driver is ok, he should start.
if nothing help, also open a fresh downloadet flash tools.
The new chipsets are very freaky and work not always correctly with the flashtools.
I am attempting to install a new ROM and was successful in using MTKDroidtools to backup the existing one before proceeding.
When I follow the procedure to install the new one using the supplied SP_Flash_Tool_v3.1328.0.183, all I see is searching when I initiate the update.
The device is seen by windows and I can use adb to see the phone.
When I press the volume down button and the power button and then insert the battery (as per the instructions), the phone enters factory mode.
I even used adb at this point with the command adb reboot bootloader but still the tools are stuck on searching.
Any ideas?
Update:
I solved the problem.
When using it on Windows 7, it was fine but not in Windows 8.
I downloaded Usbdeview, uninstalled all of the current MTK drivers, downloaded SP_Drivers_v1.4, then after connecting the phone in bootloader mode, installed the new drivers (after disabling enforced driver signing in Windows).
Windows 8.1 was then able to see the phone for flashing again using sptools.
hello can you please tell me how to solve the DRAM problem..
even im getting the same error... im trying to flash my phone with stock rom.. but its not happening
@Gizbeat
Please add these to your OP (maybe just beneath the change usb cable):
-Sometimes you need to change from a usb2.0 to a usb3.0 port to have it work. This may have to do with the somewhat stronger powersupply of a usb 3.0 port.
-Try restarting (which in this case means: power-off and remove the powercable, reconnect it and reboot) the pc. Sometimes the usb powerchips get "confused" when there are many connect/disconnect sequences. Removing the pc's powercable ensures the usb controllers loose their power and thus get reinitialized the right way on reconnect. Normally a pc keeps the power on the usb bus even in shutdown state.
-Try flashing with the battery or without it. You may need to change the option in flashtools from automatic to with or without battery (which may even differ from what is really the case, I've seen flashtools work with the option set to no-battery but with the battery actually inserted.
Hope this helps some with their problems.
(2014-07-21, 10:09)Bluesmanuk Wrote: [ -> ]I am attempting to install a new ROM and was successful in using MTKDroidtools to backup the existing one before proceeding.
When I follow the procedure to install the new one using the supplied SP_Flash_Tool_v3.1328.0.183, all I see is searching when I initiate the update.
The device is seen by windows and I can use adb to see the phone.
When I press the volume down button and the power button and then insert the battery (as per the instructions), the phone enters factory mode.
I even used adb at this point with the command adb reboot bootloader but still the tools are stuck on searching.
Any ideas?
Update:
I solved the problem.
When using it on Windows 7, it was fine but not in Windows 8.
I downloaded Usbdeview, uninstalled all of the current MTK drivers, downloaded SP_Drivers_v1.4, then after connecting the phone in bootloader mode, installed the new drivers (after disabling enforced driver signing in Windows).
Windows 8.1 was then able to see the phone for flashing again using sptools.
Sounds similar to the problem I am having. MTK Droid Tools can communicate with my phone, did a backup. Tried to flash the backup using SP Flash Tool v3.1344.0.212 and SP Flash Tool v5.1352.01 but with both the program greys out and stays that way doing nothing saying searching.
I am on Windows 7 by the way.
Trying your suggestion of uninstalling USB drivers using the tool you suggest.
I m Having Brom error 5007 on mtk 6589 device
s_not_enough_storage_space 1011 pls helpppp???????[/size]
whenever i try to flash my mmx a110q with mtk 6589 i get error 5069 no space what to do??
tried every method on this site...
i am not able to flash it ..my phone is not starting up..it completely bricked!!!what to do???
(2014-04-30, 09:01)mongkolc Wrote: [ -> ] (2014-04-25, 19:14)mir_shahzad Wrote: [ -> ]image preloader failed appears in a window after completion of red and purple meter, help plz
my phone zte v972m (MT6589) is dead
I tried to flash backup rom to my phone with sp flash tool
I found error
BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to Download DA to Baseband chip's internal SRAM!
How can i solve this problem
please help me
Hi , did you manage to fix this , stuck with same problem
I have a Samsung galaxy s5 clone(m6589 SM-G900H)...First of all everything goes right but while clicking the readback button a **** error pops up it is like
BROM ERROR:S_CHIP_TYPE_NOT_MATCH(3168)
Any solution?