Database Info

[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.

Note 5 Pro dead by Note 6 Pro ROM, stuck in EDL. Help plzzzzzzzzz

I was on Masik X 4.1. Phone was working just fine.
I downloaded Masik X 5, installed it over 4.1. Flashing goes very well but at the end phone become dead.
No response on USB, No Driver on PC at all. Phone is complete dead.
Just noticed that I mistakenly downloaded "Masik P Tulip.zip" and flashed it blindly. There was no warning regarding File Mismatch in TWRP.
Very very bad luck.
I manged to bring phone into EDL Mode by testpoint method. Phone flashed successfully with both Qfil and Miflash.
Flashed many many times, tried all files available on different threads but phone is now permanently stuck in EDL mode and dont reboot after successful flashing.
Phone flashed successfully every time but I cant get rid of EDL Mode aka Qdloader 9008.
Plz help me to get my phone out of Qdloader 9008 mode.
Anybody please help me.................................

press power button for more than 30 seconds to get out of edl mode.

yawarniazi said:
I was on Masik X 4.1. Phone was working just fine.
I downloaded Masik X 5, installed it over 4.1. Flashing goes very well but at the end phone become dead.
No response on USB, No Driver on PC at all. Phone is complete dead.
Just noticed that I mistakenly downloaded "Masik P Tulip.zip" and flashed it blindly. There was no warning regarding File Mismatch in TWRP.
Very very bad luck.
I manged to bring phone into EDL Mode by testpoint method. Phone flashed successfully with both Qfil and Miflash.
Flashed many many times, tried all files available on different threads but phone is now permanently stuck in EDL mode and dont reboot after successful flashing.
Phone flashed successfully every time but I cant get rid of EDL Mode aka Qdloader 9008.
Plz help me to get my phone out of Qdloader 9008 mode.
Anybody please help me.................................
Click to expand...
Click to collapse
AFAIK , there's no such things as "automatically reboot after successfully flashed the device"
I was also in this condition but with different phone (it was Redmi 4 Prime (markw)), and all I did is just disconnect the battery form the circuit and then replug it, then I can boot to the system successfully
Hope it helps, but if it isn't then maybe something wrong

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.

Question [SOLVED] OP9 MSM Tool not working. Phone possibly hard bricked.

So i tried to flash some firmware for a custom rom with enhanced fastboot. afterwards the phone booted into EDL mode and only EDL mode. i cant get bootloader, fastboot, recovery, or even system boot. before when this has happened msm tool worked well, but now ive tried 4 diff msm tool repacks, 2 diff versions of QFIL. MSM tool gets stuck on "start download firehose binary". then errors out to "sahara communication failed". QFIL errors to "qdssloader fail" or "924 sahara protocol error" and " qsahara server fail". the github edl utility reports "sahara in unknown mode, resetting". ive tried many cmd utilities, python utilities, qualcomm utilities, etc. idk if its completely gone or if there is a way to save it such as switching boot slots without fastboot? i have tried the EDL python utility and it says process completed on boot slot switching but still the same EDL only boot and unresponsive flashing attempts. i have tried like 30 different methods and 2 OSes to try and remedy this issue. i also have telegram and discord for one on one help: @rivapeeva riva!#0451

Have you tried the Indian MSM tool? I thought I was boned when I was messing with my phone a couple of weeks ago, and that was the only thing that worked for me.

riva! said:
So i tried to flash some firmware for a custom rom with enhanced fastboot. afterwards the phone booted into EDL mode and only EDL mode. i cant get bootloader, fastboot, recovery, or even system boot. before when this has happened msm tool worked well, but now ive tried 4 diff msm tool repacks, 2 diff versions of QFIL. MSM tool gets stuck on "start download firehose binary". then errors out to "sahara communication failed". QFIL errors to "qdssloader fail" or "924 sahara protocol error" and " qsahara server fail". the github edl utility reports "sahara in unknown mode, resetting". ive tried many cmd utilities, python utilities, qualcomm utilities, etc. idk if its completely gone or if there is a way to save it such as switching boot slots without fastboot? i have tried the EDL python utility and it says process completed on boot slot switching but still the same EDL only boot and unresponsive flashing attempts. i have tried like 30 different methods and 2 OSes to try and remedy this issue. i also have telegram and discord for one on one help: @rivapeeva riva!#0451
Click to expand...
Click to collapse
Are you TMobile or global 9?

Frosthaxx said:
Are you TMobile or global 9?
Click to expand...
Click to collapse
tmobile

posar said:
Have you tried the Indian MSM tool? I thought I was boned when I was messing with my phone a couple of weeks ago, and that was the only thing that worked for me.
Click to expand...
Click to collapse
i tried the UE tool, the indian tool, the na tool, the tmobile tool, and the conversion tool.

riva! said:
i tried the UE tool, the indian tool, the na tool, the tmobile tool, and the conversion tool.
Click to expand...
Click to collapse
Indian msm tool works on lite Firehose. Then use TMobile India mod and you can from there do what you need to do. Caution however. Doing the Indian trick makes your bootloader to the Indian bootloader but all functions will still work. You just can't use normal msms anymore

Unfortunately the bricking your describing is what happened to me because I goofed something. But I was able to get back using this to TMobile India after Indian. Then using the bootloader unlock guide in TMobile.a few update scenarios, then eventually evolution x. Unless someone has a better way there's not much written about this situation. I had to figure it out myself

IF ANYONE needs info on how i managed to fix this, please dm me or add my socials. If you flashed the wrong xbl/xbl_config files and now your sahara/firehose doesnt work, feel free to reach out. it took me 4 days straight of surfing and downloading and trial and error.

Unfortunately I don't think my issue can be fixed. There isn't anything specifically on fixing Indian region bootloader. Once that's done I think it's sol but it still works normal. I had to however because my brick also wasn't reading the USB either. It was a very odd situation. And I've modded and given advice on multiple phones. I'm glad you got yours working though. Doesn't bother me though

Phone works and the India mod get me back where needed. But others that haven't flashed the Indian msm tool could benefit from your find