hello,
i have this old Samsung galaxy young GT-S6312 Running JB 4.1.2 . i was using it as my secondary phone. and yesterday it just stopped Working. when i pulled it out my pocket it was switched off and when i tried to on it, it would go to the very beginning of Samsung animation(i could only see animation for like a half of second ) and then it would crash. i tried to boot into recovery but it crashed there too and then then it stopped Working.
phone is just dead now, no display no charging animation(Battery is fine i checked it on another phone) power & Vol buttons does nothing.
Now When i connect it To my PC with battery Nothing happens however when i connect it without battery i can hear a loop of plugin and plugout sound (windows 7) and in device manager i can see qualcomm hs-usb qdloader 9008 (com10) and device manager keeps on refreshing like a device is being plugged in and plugged out.
is it HardBrick or the phone is just dead?
--edit--
phone is rooted
CWM recovery & Xposed Framwork is installed
r2dak said:
hello,
i have this old Samsung galaxy young GT-S6312 Running JB 4.1.2 . i was using it as my secondary phone. and yesterday it just stopped Working. when i pulled it out my pocket it was switched off and when i tried to on it, it would go to the very beginning of Samsung animation(i could only see animation for like a half of second ) and then it would crash. i tried to boot into recovery but it crashed there too and then then it stopped Working.
phone is just dead now, no display no charging animation(Battery is fine i checked it on another phone) power & Vol buttons does nothing.
Now When i connect it To my PC with battery Nothing happens however when i connect it without battery i can hear a loop of plugin and plugout sound (windows 7) and in device manager i can see qualcomm hs-usb qdloader 9008 (com10) and device manager keeps on refreshing like a device is being plugged in and plugged out.
is it HardBrick or the phone is just dead?
--edit--
phone is rooted
CWM recovery & Xposed Framwork is installed
Click to expand...
Click to collapse
x.ak**** said:
Like all my comments above to encourage me to help you.
Okay so first of all I will let you know why a phone gets bricked-
>Corrupted Rom
>Some system files got deleted
>Rooting
>Modding
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
MY CASE
I always keep two phones with me like one for my experiments and one as a backup. In this case I'll be talking about my LYF WIND 3 that got bricked.
>Actually I was trying to install TWRP onto that phone but first I had to root it, and due to the upgraded android security, I wasn't able to do via KingoRoot so I tried I-ROOT and it did the job but instead of kingo-superuser I got some ****ty superuser so i tried granting permission to the actual SUPERUSER and while doing so I accidentally double rooted my phone (First with I-ROOT and then with KingoRoot), which was kinda stupid, so it just deleted some system files and my phone wouldn't boot after that. It just got stuck on the boot logo.
>The second time I was trying to replace the boot animation and logo but did something wrong so the same situation arose again.
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
CURE
So my phone uses a Qualcomm CPU so i just guessed I'll flash it again.
*After Intense Googling*
I found this software QFIL (Qualcomm Flash Image Loader)
I downloaded this file and the drivers for my device. *Google it you'll find for yours too*
Then I downloaded the Stock Rom for my device *Google it again*
Now I just went over to Flat Build in that software and loaded the firehose file and the rawprogram.0 and Patch.0
Now I had just put my device in Download Mode (Volume Keys and Power Key)
Connected via USB and it detected it and then just clicked on DOWNLOAD
It takes about 5 minutes.
After this your phone gets good as new (Unroot, Full Reset)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Click to expand...
Click to collapse
Drop a like on my replies and Download the correct QPST drivers along with the correct firmware for your device.
Sent from my One Plus 5T using XDA-Developers Legacy app
x.ak**** said:
Drop a like on my replies and Download the correct QPST drivers along with the correct firmware for your device.
Sent from my One Plus 5T using XDA-Developers Legacy app
Click to expand...
Click to collapse
hello i was also looking for a solution when i found QFIL Method already tried it. there are two problems im having with it
1. phone is unresponsive so i cant boot into download mode
2. phone just keeps on plugin and unpluging itself so QFIL can not put a lock on it and gives following error
Code:
2018-04-14 23:53:13.007 23:53:12: ERROR: function: rx_data:247 Error occurred while reading from COM port
2018-04-14 23:53:13.007
2018-04-14 23:53:13.007 23:53:12: ERROR: function: sahara_main:924 Sahara protocol error
2018-04-14 23:53:13.015
2018-04-14 23:53:13.015 23:53:12: ERROR: function: main:303 Uploading Image using Sahara protocol failed
2018-04-14 23:53:13.015
2018-04-14 23:53:13.015
2018-04-14 23:53:13.015 Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
2018-04-14 23:53:13.023 Finish Download
Related
Hello all,
I have a rooted Micromax A58 which was perfectly working. I did a full nandroid backup of it 2 days ago. On yesterday, I was moving some system app (google maps, play store etc) to SD with some software) so that I could increase the internal memory and install some other softwares. But, unfortunately, after that modification, the phone stopped working properly (it was stucking up when the BOLT logo was reached). So, I started it in recovery and do a wipe cache and factory reset. After that, the phone is always going to Factory Mode.
Then I tried to Flash the Stock ROM using Flash Tool but was unsuccessful multiple times. After the scatter file selected, when I clicked the 'Download' (or even firmware upgrade), all time time, the phone was disconnecting/reconnecting every now and then and nothing happened after (even though I already installed the Vcom and PdaNet driver in the PC). So, I had to quit. I am attaching herewith the logs of the Flash Tool lastly tried.
Now, when I am starting the phone power button, nothing is happening.. NOTHING but black screen...
I am a bit worried.. your help very much appreciated. Please let me know for any information needed. Thanks.
'No com port detected' error
I tried another time and the problem still there.. When in SP Flash Tool, I select scatter file, click 'Download' and connect the phone to PC, the process doesn't progress further. So, I have to finally click 'Stop' to quit. In the logs, it shows--
"No com port detected.."
Attaching the trace logs file herewith.
Please advice how to resolve the issue.. I am totally stuck now. Thanks.
Androhelp said:
Hello all,
I have a rooted Micromax A58 which was perfectly working. I did a full nandroid backup of it 2 days ago. On yesterday, I was moving some system app (google maps, play store etc) to SD with some software) so that I could increase the internal memory and install some other softwares. But, unfortunately, after that modification, the phone stopped working properly (it was stucking up when the BOLT logo was reached). So, I started it in recovery and do a wipe cache and factory reset. After that, the phone is always going to Factory Mode.
Then I tried to Flash the Stock ROM using Flash Tool but was unsuccessful multiple times. After the scatter file selected, when I clicked the 'Download' (or even firmware upgrade), all time time, the phone was disconnecting/reconnecting every now and then and nothing happened after (even though I already installed the Vcom and PdaNet driver in the PC). So, I had to quit. I am attaching herewith the logs of the Flash Tool lastly tried.
Now, when I am starting the phone power button, nothing is happening.. NOTHING but black screen...
I am a bit worried.. your help very much appreciated. Please let me know for any information needed. Thanks.
Click to expand...
Click to collapse
Try changing the ports, Cable etc or better off try on a different computer .
Port/Cable/PC change didn't help
kapil_dheer said:
Try changing the ports, Cable etc or better off try on a different computer .
Click to expand...
Click to collapse
Hello Kapil,
Thanks for the response. Yesterday I tried with separate laptop, but the same problem was there. Today, I tried with the different USB port.. but didn't help.
It seems that the driver can not recognize the device and when I connect the phone, it is just in a loop of disconnecting/re-connecting. Please advice further. Thanks.
Only option now seems is Service Centre.
The guys are pretty dumb. I've tested samsung motorola etc.....they don't even know what root is.
Maybe they'll be unable to identify what you tried to do.
You can give any reason for it not functioning.
Good luck.
kapil_dheer said:
Only option now seems is Service Centre.
The guys are pretty dumb. I've tested samsung motorola etc.....they don't even know what root is.
Maybe they'll be unable to identify what you tried to do.
You can give any reason for it not functioning.
Good luck.
Click to expand...
Click to collapse
Thank you Kapil for the advice. As Micromax service centre is not having a good reputation regarding these, so I would go for that option as the last resort.
Before that, can I please ask the other members for giving further advice if there is any option to try with.. Thanks for your help.
Managed to get phone reconized in PC usb-pls help further
Androhelp said:
Thank you Kapil for the advice. As Micromax service centre is not having a good reputation regarding these, so I would go for that option as the last resort.
Before that, can I please ask the other members for giving further advice if there is any option to try with.. Thanks for your help.
Click to expand...
Click to collapse
I have managed to get the phone recognized by PC usb now. But, when I try try the SP Flash utility to either Format or Download or Firmware update etc, it is throwing error like below--
09/16/2014 09:56:32.640 FlashTool[2212][3912][D]: APCore::Connection::ConnectDA(): Failed to Connect DA: S_FT_ENABLE_DRAM_FAIL(..\QT_FlashTool_Refactor\Conn\Connection.cpp,126)
09/16/2014 09:56:38.140 FlashTool[2212][3912][D]: BackgroundWorker::run(): BROM Exception! ( BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded.)((APCore::Connection::ConnectDA,..\QT_FlashTool_Refactor\Conn\Connection.cpp,127))(..\QT_FlashTool_Refactor\UI\src\BackgroundWorker.cpp,94)
09/16/2014 09:56:58.765 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:56:59.750 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:57:33.828 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:57:34.812 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:58:08.890 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:58:10.375 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
I tried the above multiple times but everytime same error as above.
When tried to connect the phone (without battery) it is disconnect/reconnect in an endless loop.
When try to connect with battery, the disconnect/reconnect loop is gone (i.e.-stable) but sometime it can not identity phone ('Unknown Device').
Also tried to press volume down button along with battery inside, but showing 'Unknown Device' and Flash tool getting hanged.
I used the Stock Rom downloaded from xda site for my phone detailed below---
Android 4.2.2
Model Micromax A58
BaseBand version- MOLY.WR8.W1315.MD.WG.MP.V1.P11 2013/09/04 15:51
Kernel 3.4.5 [email protected] #1
Build Number Micromax A58_T09
I also have the good nandroid backup (if it could be of any use) but phone is dead now. Confused how to go forward. Please help.
Download in SP Flash Tool successful
Androhelp said:
I have managed to get the phone recognized by PC usb now. But, when I try try the SP Flash utility to either Format or Download or Firmware update etc, it is throwing error like below--
09/16/2014 09:56:32.640 FlashTool[2212][3912][D]: APCore::Connection::ConnectDA(): Failed to Connect DA: S_FT_ENABLE_DRAM_FAIL(..\QT_FlashTool_Refactor\Conn\Connection.cpp,126)
09/16/2014 09:56:38.140 FlashTool[2212][3912][D]: BackgroundWorker::run(): BROM Exception! ( BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded.)((APCore::Connection::ConnectDA,..\QT_FlashTool_Refactor\Conn\Connection.cpp,127))(..\QT_FlashTool_Refactor\UI\src\BackgroundWorker.cpp,94)
09/16/2014 09:56:58.765 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:56:59.750 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:57:33.828 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:57:34.812 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:58:08.890 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:58:10.375 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
I tried the above multiple times but everytime same error as above.
When tried to connect the phone (without battery) it is disconnect/reconnect in an endless loop.
When try to connect with battery, the disconnect/reconnect loop is gone (i.e.-stable) but sometime it can not identity phone ('Unknown Device').
Also tried to press volume down button along with battery inside, but showing 'Unknown Device' and Flash tool getting hanged.
I used the Stock Rom downloaded from xda site for my phone detailed below---
Android 4.2.2
Model Micromax A58
BaseBand version- MOLY.WR8.W1315.MD.WG.MP.V1.P11 2013/09/04 15:51
Kernel 3.4.5 [email protected] #1
Build Number Micromax A58_T09
I also have the good nandroid backup (if it could be of any use) but phone is dead now. Confused how to go forward. Please help.
Click to expand...
Click to collapse
In the meanwhile, when trying to resolve the issue, I tried the following steps and after that, I lastly managed to 'download' the Stock ROM successfully in my phone (using the Windows XP OS)--
1) As I was always getting the SP Flash Tool error 4032 for last couple of days and which was clearly describing 'please check your load matches your target which is to be downloaded', so was investigating the root cause in details. Upon searching in the internet, I downloaded multiple version of Stock ROMs for my Micromax A58 model from different sources to give a try. When trying to 'Download' (in SP Flash Tool), the 'T_09' ROM (link given by 'alanvmathew') in the below mentioned URL worked for me.
http://forum.xda-developers.com/showthread.php?t=2610046&page=2
It is to be noted from the link that Micromax A58 model have 2 different Stock ROMs (i.e.- 'T_07' and 'T_09') which info I was missing all the time.
2) After identifying the scatter file in the SP Flash Tool and clicking the 'Download' option, I inserted battery in the phone and pressing the 'Power + Volume down' button, connected the device into the PC USB. Upon connected, the 'DA USB VCOM PORT' driver automatically installed and the 'Download' started and flashing of ROM went smooth. Finally, it ended up with green 'Download OK' message. Also attaching the snapshots herewith.
Will check the mobile and its performance further and revert back accordingly.
Hello everyone,
I really need help. A friend asked me to fix his tablet because it had malwares, so I rooted the device, and deleted the bad files, but then i got error messages, and at the end it went off. Now when i turn it on, it's stuck on the ACER logo, MT65xx goes on and off, I install all the drives but still goes on and off. I sent through adb sideload the stock firmware Acer_AV0K0_A3-A20_1.018.00_WW_GEN1_DCC thinking that i was going to unbrick the device but it didn't work. I tried smart phone flash with the 1.018.00 firmware but I keep getting BROM ERROR (2004). I checked the list of errors, and I changed the compatibility, and ran sp with administrator, but still error 2004. What can I do to unbrick it? By the way, I am following this xda thread to fix it, but I can't (http://forum.xda-developers.com/showpost.php?p=59693904&postcount=480) Thank you everyone!
acer iconia a3 a20 error sp flash fix
fmarino09 said:
Hello everyone,
I really need help. A friend asked me to fix his tablet because it had malwares, so I rooted the device, and deleted the bad files, but then i got error messages, and at the end it went off. Now when i turn it on, it's stuck on the ACER logo, MT65xx goes on and off, I install all the drives but still goes on and off. I sent through adb sideload the stock firmware Acer_AV0K0_A3-A20_1.018.00_WW_GEN1_DCC thinking that i was going to unbrick the device but it didn't work. I tried smart phone flash with the 1.018.00 firmware but I keep getting BROM ERROR (2004). I checked the list of errors, and I changed the compatibility, and ran sp with administrator, but still error 2004. What can I do to unbrick it? By the way, I am following this xda thread to fix it, but I can't (http://forum.xda-developers.com/showpost.php?p=59693904&postcount=480) Thank you everyone!
Click to expand...
Click to collapse
---------- Post added at 11:26 AM ---------- Previous post was at 11:21 AM ----------
fmarino09 said:
Hello everyone,
I really need help. A friend asked me to fix his tablet because it had malwares, so I rooted the device, and deleted the bad files, but then i got error messages, and at the end it went off. Now when i turn it on, it's stuck on the ACER logo, MT65xx goes on and off, I install all the drives but still goes on and off. I sent through adb sideload the stock firmware Acer_AV0K0_A3-A20_1.018.00_WW_GEN1_DCC thinking that i was going to unbrick the device but it didn't work. I tried smart phone flash with the 1.018.00 firmware but I keep getting BROM ERROR (2004). I checked the list of errors, and I changed the compatibility, and ran sp with administrator, but still error 2004. What can I do to unbrick it? By the way, I am following this xda thread to fix it, but I can't (http://forum.xda-developers.com/showpost.php?p=59693904&postcount=480) Thank you everyone!
Click to expand...
Click to collapse
hy friend use this sp flash tools v5.1515.00
this link download https://doc-0c-bc-docs.googleuserco...046/*/0B7XGoy6u4PgeX3ByYUNyWlpjZmc?e=download
go in sp flash tools then select scatter file where you download the rom on directory then check all,pres download ,now pres vol down and connect the usb to computer and tablet still press vol down,see the mtk usb on bar sp flash tools ,relese vol down and wait ,red bar,purple bar,yellow bar, ok circle , done ,now disconect the tablet and press power ,or check if have logo charger reput usb to computer.100 % tets by me work
I have a similar problem, but no error message...it just seems the computer can't see the tablet. I tried my Windows 10 machine and an old Windows XP machine I have lying around. I've installed several versions of drivers, and nothing. I'm so frustrated right now. @paulktm I tried your file, but there's nothing there. I don't get any kind of error message, the Win10 machine just acts like it sees the tablet for a second, then doesn't anymore. The XP machine sees it, but fails to install any drivers for it...even when I manually install them, they don't seem to do any good.
I'm so frustrated right now!!!
This is an old thread but maybe some poor soul finds it like I did and manages to get his device back as well.
I've had a lot of trouble with an Acer Iconia A3 A20 FHD that was stuck at the first logo screen. Powered off and connected to the charger it only showed the battery logo with the flash but no animation any more. Booting into recovery (Pwr+VolDn) worked but mounting the system partition didn't work.
SP Flash always aborted with the dreaded "BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL (0x7D4)" / "BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL (2004)" although cabling and drivers were perfectly all right. Obviously Acer patched the preloader in order to lock out SP Flash's download agent - that's customer support - thank you [email protected]#%&!!!
Solution: Power off, start SP Flash download/readback/whatever, press VolUp *and* VolDn simultaneously and plug in the usb cable. This way the download agent should be able to do it's job. I also plugged out the battery all the time and this seems to be necessary.
Flashing worked as it should and the tablet booted nicely and I didn't even loose my apps and data since I excluded the USRDATA partition from flashing.
Good luck!
Hi
same problem, tablet bricked after installing custom recovery and on boot loop
tried to unbrik with but SPF tools, com port is working but the firmware won't upload...
I waited for ages.. nothing...
Hi guys, I recently purchased a Homtom HT3 for my mother, when it arrived to me I charged it and checked it out a bit just to make sure everything was fine which it was.
She collected it from me the next day and told me she'd start to use it the day after, she calls me up the next day and tells me there's some problems with it and a few people at her workplace tried to fix it for her to no avail. I pick the phone back up and I notice that everytime I power it on, it gets stuck on the "homtom" logo.
As I don't know too much about fixing phones I only took the following steps before asking for advice here; I went into recovery mode by holding up volume and power button, the android guy with the red triangle appeared so I tapped up + power button to get into the recovery(?) menu. I wiped the phone to factory settings and deleted the cache in there but it hasn't fixed the problem.
I assume I need to flash a firmware or something to potentially fix this, but I'm unable to find an official firmware from doogee/homtom's site for the HT3. I've found a firmware that I downloaded from "chinagadgetsreviews" but I'm a bit weary to try and flash with that rom because it isn't from the manufacturer. (even if I knew how to - the only experience I have is rooting my own phone but that's when I actually had access to a working phone, not one thats stuck on a boot logo).
Sorry for the long post but could anyone guide me in the right direction here? TIA
I'm not opposed to not using official firmware, I think I use cyanogen mod(?) on my own phone. I'd just like the problem fixed in the easiest way possible.
Trying to fix it myself by flashing a rom via SP flash tools but I've ran into another problem which is stopping any kind of progress - the phone isn't detected in Windows, I can't enable usb debugging because I can't get passed the boot loop, I've tried installing the ADB driver manually which didn't seem to work (just said it didn't install correctly and left me with a yellow exclamation mark) and I tried to install it automatically via ADB driver installer but it just throws up an error that the device isn't detected.
Any help would be greatly appreciated.
Hello. I bought a Homtom HT3 and next day a done an update with sp flash tool. all gone ok, but phone now wont to turn on. I contact homtom and got all drivers and room to fix it. Now i have a problem , i hit download on flash tool , take off battery + pres volume down + conect phone on usb cable. My computer detect it as USB MTK PORT sp flash tool load only the first red line but not detecting phone info, then after 1 minute i get
s_ft_da_no_response(4001) da didn't send response data to flash tool.
I changed drivers port even to MTK preloader, but i get same error.
NOTE....... All drivers and rom i got original from HOMTOM.
Thanks to all who can help me.
I can show a screenshot if need.
Same here - any solution for this problem?
Kleos89 said:
Hello. I bought a Homtom HT3 and next day a done an update with sp flash tool. all gone ok, but phone now wont to turn on. I contact homtom and got all drivers and room to fix it. Now i have a problem , i hit download on flash tool , take off battery + pres volume down + conect phone on usb cable. My computer detect it as USB MTK PORT sp flash tool load only the first red line but not detecting phone info, then after 1 minute i get
s_ft_da_no_response(4001) da didn't send response data to flash tool.
I changed drivers port even to MTK preloader, but i get same error.
NOTE....... All drivers and rom i got original from HOMTOM.
Thanks to all who can help me.
I can show a screenshot if need.
Click to expand...
Click to collapse
Lately during the morning after having my P9000 charged overnight it suddenly shut down and after that was completely unresponsive:
I tried powering it back on but it wouldn't (neither by pressing the power button nor in combination with volume+ or any other button).
I tried charging it again but the LED isn't lighting up so I'm guessing it's not actually charging either.
Then I tried to reanimate it with SPFT but realized that the phone wasn't recognized by the pc. When I pressed the volume+ button it was recognized as "MediaTek USB Port (COM3)" for some seconds but then disappeared again.
Despite of that I tried to flash the stock ROM 20160810 (as well as others - no difference). Every time I get the same error:
BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)
Also I tried to flash preloader only, without any difference.
Then I opened the cover, removed the battery and tried again - nothing changed: The pc recognizes my phone only when I'm pressing volume+ but throws the error above when trying to flash.
Next I shortened the GND point on the phone's mainboard to any test points, but couldn't bring the pc to recognize the phone.
Any ideas...? Does someone know what the error message means? I know that DA stands for "download agent".
You haven’t said much about as to what you had done with this phone prior to your issue, whether you have left your P9000 as standard with OTA updates or perhaps you have rooted, flashed a different Rom or changed its Kernel ?
It’s hard for anyone to give help easily without some background from you.
You're right, I bought it two weeks ago as a used part. To my knowledge it was left as standard (previous owner didn't seem to be skilled too much since some of his folders remained on the phone) and as far as I remember the installed ROM was 20160810, although I'm not 100% sure since I'm also new to android / not experienced with ROM versions and didn't write it down. At the end I believe the phone had never been rooted or changed kernel.
Maybe worth mentioning: The last two days before failure I noticed that the phone restarted one or two times per day.
@brager
There are two possibilities (or more)
1. It's hard bricked, so Google for a mtk hard unbrick guide
2. It's a battery related problem
Keep it two days plugged, or replace it
Keep in mind that the newest mtk software has to be installed on your computer
And try another cable first of all
1. It's hard bricked, so Google for a mtk hard unbrick guide
Click to expand...
Click to collapse
I've already performed all the steps in these mtk hard unbrick guides. I'm able to enter META mode but when I try to flash the preloader I get the error described above [BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)]
2. It's a battery related problem
Keep it two days plugged, or replace it
Click to expand...
Click to collapse
As far as I understand it flashing can/should be done without battery.
Keep in mind that the newest mtk software has to be installed on your computer
Click to expand...
Click to collapse
I was using SPFT 5.1524.00, now updated to SPFT 5.1628 and get nearly the same error: BROM ERROR: STATUS_DA_HASH_MISMATCH (0xC0070004)
And try another cable first of all
Click to expand...
Click to collapse
...didn't change anything.
I think the phone has a hardware problem and went to heaven.
Brom error: Status_da_hash_mismatch
brager said:
Lately during the morning after having my P9000 charged overnight it suddenly shut down and after that was completely unresponsive:
I tried powering it back on but it wouldn't (neither by pressing the power button nor in combination with volume+ or any other button).
I tried charging it again but the LED isn't lighting up so I'm guessing it's not actually charging either.
Then I tried to reanimate it with SPFT but realized that the phone wasn't recognized by the pc. When I pressed the volume+ button it was recognized as "MediaTek USB Port (COM3)" for some seconds but then disappeared again.
Despite of that I tried to flash the stock ROM 20160810 (as well as others - no difference). Every time I get the same error:
BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)
Also I tried to flash preloader only, without any difference.
Then I opened the cover, removed the battery and tried again - nothing changed: The pc recognizes my phone only when I'm pressing volume+ but throws the error above when trying to flash.
Next I shortened the GND point on the phone's mainboard to any test points, but couldn't bring the pc to recognize the phone.
Any ideas...? Does someone know what the error message means? I know that DA stands for "download agent".
Click to expand...
Click to collapse
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Help,I have the same problem
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
It has been 2 days that i try to fix this problem,because i thought it was a driver problem i formatted my windows 7 and reinstalled everything.
This issue still persists and my phone is brand new.
Hi there!
I have purchased a LENOVO L38111 smartphone which had its default ROM that I was trying to replace with another one. I've opened the Bootloader then I put TWRP on it. I've made a full backup with the TWRP in case an issue comes up, I could switch back to original system. I've installed Pixel Experience ROM following the instructions which was pretty pleasing to me, I've used it for a while. However, once I started the Waze app then I realised that the GPS is not working. I thought I have a full backup in the TWRP, a restore which was running appropriately, it got displayed that restoring was successful, restart.
Since then, it does not turn on, the screen is black. I've tried to restore my phone with the Qualcomm QPST program. I've installed QPST on PC, I've installed Qualcomm driver as well. If I connect the phone to PC with an USB cable, the USB Qdloader 9008 (COM8) driver gets displayed in tool manager, once I start QPST Configuration, then it says Q/QCP-XXX at the Active phone, however, in State, the progress signal goes up to approximately 20%. When I start QFIL, I choose the port (HS-USB Qdloader 9008 (COM8)), then the files from the default ROM but it says:
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Is it because the opened bootloader?
Do you have any idea what I can do?
Thank you in advance!