In SP Flash Tool (v3.1304.0.119, seemingly the latest I can find out there) I get the following, no matter which function I perform:
BROM ERROR: S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM Failed!
Err msg box pops up right after RED 100% (no subsequent yellow & green)
Is this likely a hardware failure or is there any possibility of rescuing via SW means.
Worse case scenario I'll have to send to back to CHN.
Thanks for any input you may offer.
i've same problem
help me too
I've got the same problem : I erased my preloader (I can't use "Preloader-->DA" any more to brush a ROM). Now, I'm looking how to boot on "ROM-->DA". On a MT6577, it's easy : you put the battery without power on the phone, you connect USB cable, you run your brush software ("SP flash tool" or "SP_MDT"), you remove the battery... and the brush begin. But on MT6589, it doesn't work
If someone has a solution...
@crkmanho: your phone got recognized as mt5xx preloader, so it isn't bricked. you`ll need to get the correct firmware for your device and make full download. did you made a backup of your running firmware? No? Haha. next time think about it before just flashing random FW to your device. also, check in your driver settings that you have assigned vcom port 1-16 to mt65xx preloader. sometimes preloader is recognized (vcom 7 or something) bt other device drivers are offset (27 or something) wich will work for connecting your device to PC, but not flashing through SP Flash Tool.
@ManuD_Linux: is your device recognized by your PC? if so, same thing. if it is completely dead, google for "mt65xx testpoint" or something similar. not every phone got one, but many. you can connect the testpoint to GND and the phone will "boot" into preloader. those devices are almost unbrickable.
Chrizzly92 said:
[...] @ManuD_Linux: is your device recognized by your PC? if so, same thing. if it is completely dead, google for "mt65xx testpoint" or something similar. not every phone got one, but many. you can connect the testpoint to GND and the phone will "boot" into preloader. those devices are almost unbrickable.
Click to expand...
Click to collapse
I find a solution !!! It certainly will help someone. If you totally brick your Lenovo A820 (no or bad preloader), simply brush (with "SP flash tool") this preloader : http://desvigne.org/divers/firmwares/Preloader_a820.7z
After, all become possible ! You can brush an original firmware with a flash tool, and bruch TWRP, install a custom firmware....
Hope it helps someone... (the Lenovo is really unbrickable ).
Manu
I bought a Cubot GT72 from the net - its basically a chinese knock-off with some very nice specs. And it was working great out of the box; but I had to experiment - right?
Edit: cannot post links; but if you got to www cubot net - you can find the phone easily. The stock ROM is also available.
I fired up MTK-Tools and rooted the phone - no problem there. Then I tried to create a custom CWM and install - that's when things starting going down the drain. It overwrote the recovery and boot partitions - so the phone stopped working. And since then I have been trying various ways to unbrick it.
Luckily, I have another phone with the exact same specs - and was able to download a backup using MTK-Tools and another one using SPFlash.
Problem - the phone is not switching on at all. When I connect it to the computer (after installing the MTK drivers) - nothing happens. When I connect without battery and keep the Up volume pressed - the computer detects an "MTK COM Port", installs it and within 5-10 seconds the port disappears, comes back after 5-10 seconds - and this cycle keeps repeating. I'm not able to connect to the phone using wither MTK-Tools or SPFlash.
When I connect the working phone - it shows up as "MTK VIA COM Port" and I can connect to it using SPFlash.
Have opened the phone and looked for test points - found one that switches on the phone and connects to the computer - but the result is the same as when I connect with the volume up pressed.
Please help - I'm at my wits end.
Drivers
dushyantahuja said:
I bought a Cubot GT72 from the net - its basically a chinese knock-off with some very nice specs. And it was working great out of the box; but I had to experiment - right?
Edit: cannot post links; but if you got to www cubot net - you can find the phone easily. The stock ROM is also available.
I fired up MTK-Tools and rooted the phone - no problem there. Then I tried to create a custom CWM and install - that's when things starting going down the drain. It overwrote the recovery and boot partitions - so the phone stopped working. And since then I have been trying various ways to unbrick it.
Luckily, I have another phone with the exact same specs - and was able to download a backup using MTK-Tools and another one using SPFlash.
Problem - the phone is not switching on at all. When I connect it to the computer (after installing the MTK drivers) - nothing happens. When I connect without battery and keep the Up volume pressed - the computer detects an "MTK COM Port", installs it and within 5-10 seconds the port disappears, comes back after 5-10 seconds - and this cycle keeps repeating. I'm not able to connect to the phone using wither MTK-Tools or SPFlash.
When I connect the working phone - it shows up as "MTK VIA COM Port" and I can connect to it using SPFlash.
Have opened the phone and looked for test points - found one that switches on the phone and connects to the computer - but the result is the same as when I connect with the volume up pressed.
Please help - I'm at my wits end.
Click to expand...
Click to collapse
Ok Google "mt6572 com port drivers" and look for ***.ftdichip.com/Drivers/VCP.***, install the software off that site and see if your computer recognizes the com port, hopefully you'll be able to flash the original rom back to it, let me know how you get on :good:
neosnake991 said:
Ok Google "mt6572 com port drivers" and look for ***.ftdichip.com/Drivers/VCP.***, install the software off that site and see if your computer recognizes the com port, hopefully you'll be able to flash the original rom back to it, let me know how you get on :good:
Click to expand...
Click to collapse
Thanks Neo, The driver is installed - the problem I'm facing is that the phone keeps going offline every 30-40 seconds and hence am unable to flash.
okies
OK thanks for the reply. Its obvious these MTxxxx devices wait for a signal when you plug them in.
1.Try going to the SDK folder and open a command prompt, type fastboot flash boot "boot.img" > point the boot.img to where you have downloaded the original boot.img for the device.
2.When the fastboot gives you the [waiting for device] prompt plug in your phone.
Let me know how you get on, i'm going to be working on a program to flash these phones from windows. :good:
p.s if the above works then flash your original recovery as well
neosnake991 said:
OK thanks for the reply. Its obvious these MTxxxx devices wait for a signal when you plug them in.
1.Try going to the SDK folder and open a command prompt, type fastboot flash boot "boot.img" > point the boot.img to where you have downloaded the original boot.img for the device.
2.When the fastboot gives you the [waiting for device] prompt plug in your phone.
Let me know how you get on, i'm going to be working on a program to flash these phones from windows. :good:
p.s if the above works then flash your original recovery as well
Click to expand...
Click to collapse
Hi Neo - tried. The phone gets detected, but fastboot remains stuck at [waiting for device]. Please see screenshot.
Also, I think the preloader is also gone
Diffrent Drivers
Ok i noticed on there website that there are a different set of drivers, where the ones you have installed emulates a com port the other ones gives you direct access to the USB port, go to adb and type adb devices so that your phone will show up in the device manager, uninstall those drivers and install these ones ftdichip.com/Drivers/D2XX.htm.
Then try and flash the preloader in the usual way, first type flash preloader {name of file} then connect your phone and hopefully you will be able to flash your phone again.
Let me know how you get on again :good:
neosnake991 said:
Ok i noticed on there website that there are a different set of drivers, where the ones you have installed emulates a com port the other ones gives you direct access to the USB port, go to adb and type adb devices so that your phone will show up in the device manager, uninstall those drivers and install these ones ftdichip.com/Drivers/D2XX.htm.
Then try and flash the preloader in the usual way, first type flash preloader {name of file} then connect your phone and hopefully you will be able to flash your phone again.
Let me know how you get on again :good:
Click to expand...
Click to collapse
Apologies for the late reply - tried your method - the phone gets detected as MediaTek DA USB VCOM port - but fastboot or SP flash are unable to detect.
Also, now I have managed to brick the other phone also. Was trying to upgrade the ROM from cubot's website. And even that one is bricked
Really frustrated here.
dushyantahuja said:
Apologies for the late reply - tried your method - the phone gets detected as MediaTek DA USB VCOM port - but fastboot or SP flash are unable to detect.
Also, now I have managed to brick the other phone also. Was trying to upgrade the ROM from cubot's website. And even that one is bricked
Really frustrated here.
Click to expand...
Click to collapse
Also, is there a way I can create a scatter file from the ROM I downloaded using SP Flash?
dushyantahuja said:
Also, is there a way I can create a scatter file from the ROM I downloaded using SP Flash?
Click to expand...
Click to collapse
The full ROM dump has been uploaded here - is there any way I can simply flash the entire dump back into the phone.
http://www.4shared.com/file/wtNcfbRu/ROM_0.html
hi, did you manage to work out anything? i have the exact same problem with my GT72, and i'm out of ideas.
I finally gave up and sent it for repairing. The vendor has been trying to repair it for the last 2 weeks and has given up too. The problem with my phones is that they are not original cubot - the seller on aliexpress is selling fake cubot phones - and we're unable to find the correct files to write to the phone.
Now if only I could find a way to write back the ROM0 file without the scatter files - I had though that would be easy, but am unable to do anything about it
megariffer said:
hi, did you manage to work out anything? i have the exact same problem with my GT72, and i'm out of ideas.
Click to expand...
Click to collapse
dushyantahuja said:
I finally gave up and sent it for repairing. The vendor has been trying to repair it for the last 2 weeks and has given up too. The problem with my phones is that they are not original cubot - the seller on aliexpress is selling fake cubot phones - and we're unable to find the correct files to write to the phone.
Now if only I could find a way to write back the ROM0 file without the scatter files - I had though that would be easy, but am unable to do anything about it
Click to expand...
Click to collapse
maybe i have a fake one, too then. wierd stuff, that is. faking a $60 phone...
anyway, i'm guessing you can only use that ROM_0 file to create a proper preloader.bin for the phone, but you need a working one for that.
you could do that in MTK droid root & tools, but since our phones doens't get detected, we're stumped.
i think having the right preloader could push us to the right direction, but i'm not planning to order a new phone to revive my dead one
anyway, if you make any progress, let us know!
megariffer said:
anyway, i'm guessing you can only use that ROM_0 file to create a proper preloader.bin for the phone, but you need a working one for that.
Click to expand...
Click to collapse
I backed up the ROM_0 file from a working phone (had 2 - broke both); have uploaded it and shared in this thread. So, if you can create the preloader.bin from it - please be my guest.
dushyantahuja said:
I backed up the ROM_0 file from a working phone (had 2 - broke both); have uploaded it and shared in this thread. So, if you can create the preloader.bin from it - please be my guest.
Click to expand...
Click to collapse
i know you uploaded it, but the problem is that i can't do anything with it in MTK droid root & tools, since it only works if there is a working phone connected to the pc.
megariffer said:
i know you uploaded it, but the problem is that i can't do anything with it in MTK droid root & tools, since it only works if there is a working phone connected to the pc.
Click to expand...
Click to collapse
I had even created a scatter file using MTK Droid - the only problem is the scatter doesn't work with the phone. See if it helps you.
dushyantahuja said:
I had even created a scatter file using MTK Droid - the only problem is the scatter doesn't work with the phone. See if it helps you.
Click to expand...
Click to collapse
here's my "progress":
i was able to salvage a preloader.bin from your dump, this was the only one i could get flash tool to start preparing flashing.
i ran into numerous errors after that, but i managed to build a seemingly flashable rom, but it just does not work.
i could format the nand with it, but when i try to flash, it says that the bootlader exceeds partition boundary, whatever that means.
so i'm pretty much stuck at this point, but i'll attach the preloader for you, maybe it will work with your scatter.
the scatter btw did not work for me, since the addresses were wrong (i guess that scatter is for 512MB version, too).
so i built a scatter from scratch with notepad++ it's in the zip, too.
now i just wish there would be someone with a 256MB version able to make a backup with mtk droid and share with us.
megariffer said:
but i'll attach the preloader for you, maybe it will work with your scatter.
Click to expand...
Click to collapse
Thanks - let me try to flash the preloader this weekend and see how things go...
dushyantahuja said:
Thanks - let me try to flash the preloader this weekend and see how things go...
Click to expand...
Click to collapse
how's it going?
arsenal3008 said:
how's it going?
Click to expand...
Click to collapse
Didn't get any time last weekend - will update this weekend.
Wrong firmware.
dushyantahuja said:
Didn't get any time last weekend - will update this weekend.
Click to expand...
Click to collapse
Hi, the same problem, have you figured it out? Thanks for your help ...
I tried to install a new rom on Amoi a862w, and installed it, but when I turn it on I got only black-and-white screen, tried to go again, but again the same thing. I have connected a it on a computer via a USB cable, the phone is formatted by himself, now not even that works, when I connect to the computer, PC recognize the phone as "Qualcomm HS-USB QDLoader 9008" qualcomm download mode, so there is no system on it, is there a program that could use to put on a new system, I've tried over the flash tool, but when I want to throw in a scatter file writes me that scatter file is wrong. Please people help me because I love my cell phone. Sorry for my bad English. I hope that someone will understand
A quick search did not come up with much for your particular Device. There was one thread, but it does not have much ( thread link below ) . I would suggest posting your question in Android Q&A, Help & Troubleshooting. Best of luck .
EDIT:
Additionally, you may want to try a fresh Clean flash of the Rom you have. Making sure to verify the MD5 Checksum before flashing the Rom zip file. There is a good guide HERE on how to Flash a Rom.
[Help] Rooting Amoi N820
Hi there,
I somehow hard bricked my Jiayu F1 WCDMA smartphone (MTK6572) by flashing a wrong ROM (event though it was supposed to be good).
Now, I can connect the phone to the PC and it get's recognised (the bell rings), but I can't flash anything (nor format) through SP Flash Tool, which keeps bumping the "Enable DRAM FAILED" annoying error, no matter what ROM I'm trying to feed it.
I really could use some help, or at least getting a working scatter file, preloader, etc, just to rule out a fault on the flashed files' side.
Thanks a lot.
barbas66 said:
Hi there,
I somehow hard bricked my Jiayu F1 WCDMA smartphone (MTK6572) by flashing a wrong ROM (event though it was supposed to be good).
Now, I can connect the phone to the PC and it get's recognised (the bell rings), but I can't flash anything (nor format) through SP Flash Tool, which keeps bumping the "Enable DRAM FAILED" annoying error, no matter what ROM I'm trying to feed it.
I really could use some help, or at least getting a working scatter file, preloader, etc, just to rule out a fault on the flashed files' side.
Thanks a lot.
Click to expand...
Click to collapse
1. Uninstall all vcom,preloader and MTK drivers using USBdeview then manually install vcom drivers (you can see how to manually install MT65xx (MediaTek) USB VCOM drivers on Windows if you need help doing this)
2. Once you have vcom drivers installed, delete the SP flash tool folder then re-extract a fresh copy
3. I believe you should have go the correct backup now so go ahead and flash it using sp flash tool. you can try meta mode (flash without battery while holding volume up button) if you're still getting the error
My problem is my phone is a piece of **** now......it is currently hard bricked.......
i'm trying to flash my stock rom but whenever i download it, sp flash tool not passing by in the com port of my device (mtk usb port) which i need to be in mtk preloader vcom....
i need your suggestion guyz........
:crying:
TA_MiMo said:
My problem is my phone is a piece of **** now......it is currently hard bricked.......
i'm trying to flash my stock rom but whenever i download it, sp flash tool not passing by in the com port of my device (mtk usb port) which i need to be in mtk preloader vcom....
i need your suggestion guyz........
:crying:
Click to expand...
Click to collapse
Hi,
please provide us the more details to be able to direct you to the right place for help.
Vivek_Neel said:
Hi,
please provide us the more details to be able to direct you to the right place for help.
Click to expand...
Click to collapse
Sir,
I port rom cm 12.1 on my MT6582 Lenovo A328 device. As i power it off, it takes time to open and few seconds TWRP appears and i reboot the system and suddenly stucks on the cm logo and i removed the battery and open again and try and try again and it does not open. I thought that my phone is hard bricked so i connect the device without a battery to the computer via usb cable. Open the sp flash tool and open my scatter file and download....but sp flash tool download progress is color red which means connection on port problem. I open device manager and saw ports....MTK USB Port appears to be the kind of my driver's device and I think that it should be MTK Preloader VCom to be able to flash the stock rom.......Hope you understand and thank you so much for your time.....:crying:
Hi,
Try posting your question here:
Android Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!