Database Info

[Completed] Symphony w 92 MTK 6589 Hard Bricked

My phone was ok. I installed cwm recovery by mtk dorid tool. But , I wanted to install TWRP recovery by a pc software- during installation a warning message appeared and I clicked ok (something formatted – I did not remember). Then I lost my mobile network signal, null imei and null baseband. Then I install N9500_MTK6589_Miui_Revolution_4.5.23_Cwm via CWM recovery (2 times, but system closed automatically. But, third time after installation phone totally bricked ). Basically phone starts with startup sound, but with crushing screen. I was able to connect mtk dorid tool and it says Model: N9500- null baseband-null imei, then I tried to Install CWM recovery. Then phone totally bricked without starting. I tried everything from google to solve. Then I was able to firmware upgrade – stock rom (Only one time). Now, stock rom is not downloading. I used all sp flash tools. All the times one error appears –Brom Error: S_FT_Enable_DARM_Fail (4032).
Please anyone help me. (My Pc Detect My Phone as preloader usb vcom port, I am using windows 8.1 64 bit, no issue with driver software and sp flash tool)
Device Name: Symphony w 92, MTK 6589 , 1.2 GHz ,Quad Core , 4 GB rom . 512 Ram, 5 inch Capacitive Full Touch, (854*480),8MP Primary (Flash light) + 2MP Secondary.
Please Help me to solve .

Duplicate thread.
http://forum.xda-developers.com/general/xda-assist/how-install-preloader-mtk-6589-bricked-t2969643

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

[TB-8504X] No WiFi or Sim card after restoring stock rom with Lenovo Rescue and Smart Assistant

Hello There,
I was trying out LineageOS 17.1 on Lenovo Tab4 8, 8504X, 8MP Rear camera model. Everything was fine except the very low volume during audio playback. I was trying to follow the volume fix guides and while in adb shell, device kept crashing. So I tried restoring the factory image using Lenovo Rescue and Smart Assistant. It downloaded and flashed the firmware image, but I saw afterwards, wifi was not working. After a few more attempts, the SIM card also stopped working. Now the device has no connectivity.
I did an oem lock after flashing the stock firmware, now I am not able to use fastboot to flash images. QFIL tool works. The stock firmware version flashed by the tool is TB_8504X_USR_S001024_1909061423_Q12000_ROW_SVC. I am not sure if this is the correct one. Does anyone have the same device with stock ROM? Or can someone please point me to the stock ROM image where things work? The region is India.
Thanks in advance,

Checking further, the baseband version is shown as unknown. Is there an image file that can be flashed to fix this ?
EDIT: Now I understand the QCN needs a restore Does anyone have a copy ?

I wanted to update on the thread on how I managed to fix this. I tried the whole thing again, so that I can make sure.
Using the same QFIL tool, I flashed TB_8504X_USR_S001024_1909061423_Q12000_ROW_SVC firmware. This helped booting back to the system. This also enabled diag mode and adb by default on the tablet. That was a big relief. I noticed that wifi is not working and not turning on during the initial setup. I completed the setup and did
Code:
adb reboot bootloader
Once in fastboot mode, I did
Code:
fastboot flash persist persist.img
I used the persist.img from the same firmware folder. Once I turned on the device, WiFi and Bluetooth were working. Since diag port was already on, I used the backup and restore QCN option in QFIL to flash TB-8504X[MPSS.JO.2.0.c1-00151-8937_GENNS_PACK-1].qcn.
I tried may QCN rebuilder tools, but this QCN file seems to be not conforming to the format they expect and they kept gaving error. So I flashed the QCN as it is, rebooted the device and then used a tool named "WriteDualIMEI-W-G-eMMC" to program the IMEI number. This worked perfectly and I have network back.
When I was trying to do this again, for some reason, Sahara errors kept popping up and none of the tools were able to access the device. I found that was because of the driver I used. It wasn't the same ones I used first time. But I used the QDL tool from Linaro in linux and flashed the images with it. It worked perfectly.
I wasn't able to restore the tablet serial number though. Couldn't find a way to do that.

[SOLVED] Unbrick hard-bricked OP 8T

Hello people, unfortunately, I bricked my phone and am stuck trying to unbrick it.
How the bricking happened:
I bricked my OP 8T when I tried to update my OS from Lineage OS 18.1 (Android 11) to 19.1 (Android 12) following this guide: Official Upgrade Guide, I installed the firmware according to Firmware Upgrade Guide.
I can access neither recovery mode nor fast boot mode, adb doesn't work anymore, and I can't boot into Lineage either.
So the bricking occurred at step 7 in the first guide when rebooting to recovery. Note: I was surprised that the guide does not mention also flashing the recovery image in step 6 (it is an .img file not .zip). So I didn't flash the 19.1 recovery image but only the Lineage OS. Maybe that was a mistake.
Unbricking steps I tried:
I followed this guide for the unbricking procedure and this guide for installing the Qualcomm driver.
In the device manager, my device is correctly shown under ports as Qualcomm HS-USB QLoader 9008 (COM3).
I put my phone into EDL mode and it says connected in the MSMDownload Tool. When I now press "start" it says "Open Serial Device Failed". Edit: after rebooting pressing the start button now gets me "Sahara Communication Failed, Please try again after power off phone (PBL:6)"
I tried different versions of the MSM Download tool (the Europe versions, the global versions, and even the newer one of the TMobile versions from the above link), all with the same error message "Open Serial Device Failed".
I tried many different USB ports USB 2 and 3 under Windows 10.
Now I'm out of ideas on what to try.
Can anyone help me?
Cheers,
Alex

Yeah, that happened to me too. Obviously the LOS guides are missing something.
The only way out is to abandon all the data and Msm to stock...
You don't have to try different versions of MsmTools, you can only use the one which matches your hardware.
Pick yours from these:
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
[OP8T][OOS TMO KB09CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
About your Sahara error, try these steps:
1. Uninstall any driver completely you've installed manually;
2. Plug-in your device while it's under EDL mode, and ask Windows to check for update;
3. Install the driver from Windows update from "Advance Options" - "Optional Updates";
(Or from here [ https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ])
4. Press phone power button for over 1 minute and try to reboot it into EDL mode again;
5. Try EDL flash again.

My phone is now unbricked again. I used a friend's computer and followed some scattered hints. I used another USB cable, a USB 2 slot on a 64bit Windows with an Intel processor. There the MSM Download tool worked without a problem.