[Q] [HELP] Ulefone N9589 (MT6589) Fully Bricked - General Questions and Answers

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

Related

[Q] How can I unbrick my replica for SGS3 H600 H640_77v01.01b01 ( MT6577 ) ?

Hello,
I have phone H600 H640_77v01.01b01 replica for SGS3 (MT6577),but it is briked,when I connect it at my computer,only what can I see it is MTK USB Port (COM 28) in "Manage" ,no light,nothing else!
When I try to flash it with SP Flash tool I got some error after red line,only what can I do it is format.
What can I do to recognize it like MT65xx preloader? I need to press some buttons when I connect it to my computer?
Sorry for my little english!
are you sure this is an MT6577 based smartphone? how do you managed to brick it? flashed wrong firmware? we need some more inforamtions here. "some error" is something i cannot build onto. make a photo of the back of your device (without the battery) to identify your device. you`ll need to get a proper firmware for your device or it will be dead forever.
edit: found this software, this one MAYBE will work: http://4shared.com/file/IAkoq9Z5/
i didn`t looked into it, but is suggest you have to flash it using SP flash tool.

[Q] Jiayu F1 bricked - What do I do?

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

[Completed] [Q] [HELP] Lenovo A606 bricked, now I am stuck

Hello,
I have a new Lenovo A606, that came with a strange ROM (IMEI not recognized, some weird WIFI setup) from 2014. I was able to set it up and correct the problems (thanks to google), but I still had some language issues (the Lenovo Apps including dialer, contacts, sms, etc… were English only). I was able to root it fine, and no working problem.
I decided to install a clean stock ROM, ROW: the A606_USR_S036_1502271022_V3_MP_ROW that is more recent and fully supports multilanguage.
I took a PC with Windows XP, and installed the latest SP Flash Tool, following a tutorial.
I was able to install android adb drivers and the MTK driver from the ROM image. The phone was showing in the devices, then was disappearing, then showing again… I had an error, but then I tried again with the option to update the firmware, and the Flash Tool reached the end and said it flashed succesfully.
Problem: after that, the phone was totally bricked. It would not start at all. When I plug it on the PC, it shows sporadically a device called "VENDOR 0E8D - communication" that disappears very quickly. I cannot flash it again. I just lost my brand new phone…
I tried with SP Flash Tool, and Flash SPMDT, with different ROMs, CN only, ROW, different versions… But nothing. It always says that Flash failed. Even when the phone is not plugged, I have an error with Flash SPMDT, with all ROMs, saying that (1)COM ports number is repetitive or invalid, or (2) Brom and preloader have the same comport number! and it asks me to modify them in INI file or scan again. Of course, scan fails, when I plug the phone pressing vol up + vol down (only way to make the phone recognized by the computer without a battery), the progress goes to 100% then either stays stuck there, or says it failed. SP Flash Tools gives this error: 'BROM ERROR s_ft_enable_dram_fail (4032)'
I tried several drivers, to clean drivers with usbdview, I tried several versions of SP Flash Tools… I don't know what to do anymore. I hope that Lenovo has a warranty and that they could flash it back to normal.
I don't know if it is a problem accessing the META mode on the phone, or bad roms… I tried on one computer with XP, and another with Windows 8.1, and the problem is the same.
ANY HELP would be appreciated, thank you!
Hi, thank you for using XDA Assist. It sounds like you've tried everything possible. Since it sporadically shows up on your pc try a different USB cable. If that doesn't work then I think it is bricked and you'll have to check with whomever you purchased the device from to see if they can fix it.
Thread closed.

MTK Preloader disconnecting after a few seconds

Device : LUA-L22 - Honor Bee 2/Huawei Y3ii (4g ver.)
So I'm trying to root my device and I just want to create a backup before doing anything to not screw anything up.
I'm using miracle box, everything is fine till I connect the phone, when it's connected miracle box gives a "Downloading boot" message then it stops and the phone restarts.
I found out from device manager that the phone gets into preloader mode for sometime and then disconnects. I really don't think this is a driver issue.
So is there any way for me to make the phone stay in preloader mode or am I doing anything wrong?
Also is there any other way to backup the phone's firmware?
I just tried using SP Flash Tool but it's giving "brom error s_brom_download_da_fail (2004)"
Maybe I have the wrong DA file but I did try the ones that came with SP Flash Tool as well as a few custom ones.
Have the same issue with the LUA-L21 device. Any update so far?

LG W41 (LM-K610IM) dead bricked by my stupidity. Could it be somehow revived?

Greetings everyone. I didn’t find a thread for this specific phone model. So I am putting it up here. Few days back I decided to unlock the bootloader of my LG W41 (LM-K610IM) and upgrade to a custom ROM. So, I used fastboot mode to unlock the bootloader and up until now everything went like a dream. Problems started when I couldn't get a TWRP recovery for my specific model. I downloaded a generic one and first tried to push it to my recovery partition. That's when I learned my phone doesn't have a recovery partition. I don't know what came to me then I used fastboot flash command to flash the TWRP image to my boot partition. It was successful but my phone won't start after that. It was a softbrick. Only the LG logo started bootlooping. But the worse was still not over. In an attempt to restore my device I searched everywhere for the stock ROM as the official website is down, but couldn't find any. At last, I zeroed in on a similar device by the same manufacturer LG K52. It had the ditto hardware like LG W41. Even the model number was similar. So, I downloaded the KDZ file. Extracted the dz from the kdz and the boot.img from the dz using LG KDZ extractor . Made a scatter file using a Hovatek instruction and using WWR MTK tool and formatted my device using SP flash tool and flashed everything. Till now my device was detected by the Windows 11 PC as a LGE device. Anyways the SP tool successfully flashed everything but after that my won't turn on any more. It's total dead. It won't power on, pc won't recognize it. I have tried connecting using USB and all possible hardware key combinations. It is dead bricked I think. All because of my stupidity. Now my question is, does it have any hope left or should I throw it away and buy a new device? I am keeping my fingers crossed and hope to find a superhero
Edit 1: SP Flash tool doesn't see my device any more. I have all the specific drivers installed. From LG and from Mediatek.
Try LG Bridge or check lg-firmwares.com
or
buy/borrow second device and 1:1 clone with mtkclient
Thanks for the quick response, but I have already tried LG Bridge, LGUP . After soft brick LGUP was seeing device as "unknown at COM Port 9". After hard brick it doesn't see it any more. Actually my PC won't see the device anymore
The firmware is not available at LG-firmwares.com but I have requested for it there. Keeping fingers
you should be able to repair preloader from bootrom mode (BROM)
How to enter bootrom mode. I am sorry if it is a noob question
Soumyadip999 said:
How to enter bootrom mode. I am sorry if it is a noob question
Click to expand...
Click to collapse
XRed_CubeX said:
To put your device in BRom mode you may need a different key combination or a test point, find out on the internet how to put the device in BRom mode or ask various devs of that device
Click to expand...
Click to collapse
find KCOL0 test point and short to GND
https://forum.hovatek.com/thread-11802.html
Okay let me ask and I will follow up. Thank you for the amazing guidance. Let's see if the poor device could be saved
you should poll lsusb in linux while trying to connect usb with both vol keys pressed. disconnect battery from pcb if possible to ensure phone is off.

Categories

Resources