Hi
Sorry to bother, but i just got a new Star B92M but im having a rough time trying to update it and flash it with SP Flash Tool
So far, i have tried this
To flash with the SP_Flash_Tool_v3.1224.01 (i get BROM 3013 error)
To flash with the SP_Flash_Tool_v3.1224.0.sn85 ( i get the 8038 error)
I have tried to run each of them as administrator
I have tried to click on Firmware-> Upgrade as someone suggested on a post
I have installed the preloader drivers
I have tried by taking our the battery and plugging in then put the battery on
But i havent been able to flash it. The phone is not bricked, it runs as nothing has happened, i do think although, that recovery is messed after so many tries since there is the red triangle when i try it.
I dont know if it is normal, but everytime i plug the phone when its off for flashing, is like it gets connected by usb for 2 seconds then disconnected, but its weird because when the phone is on, the usb works like charms, no problems on computer ports either or the usb cable, it just happens when i connect it when the phone is off (preloader i guess), yet i have installed the proper drivers read in many tutorials
Is there any other way to flash it? or any solution to this problem? Sorry for the bad english
Thanks in advance.
Related
Hi all,
I have a Star/Bluebo B6000 phone which I believe is based on the MediaTek 6589T.
I followed the procedure here: http://forum.xda-developers.com/showthread.php?t=2206421
to set up a new ROM for the phone.
I seemed to have gotten it all done properly, but the phone only stays connected for about 2 seconds. The SP Flash tool moves into the red progress bar and then just fails.
Luckily, there isn't any software damage on the phone (from the look of it).
I'm trying to put in a new ROM to actually fix a previous issue where my phone remains on but when I press the home button or the power button the screen stays blank. Think a new ROM/fresh start may solve this.
But the core issue is that I am unable to put in a new ROM because the phone doesn't remain connected long enough.
Is there a solution to this? Or is there another way to install ROMS?
Thanks.
There are several things the issue could be.
Try running SP Flash Tools as Admin.
Try a different USB cable.
Try uninstalling current drivers and using PDANet VCOM USB drivers
Try a different PC
Try MTK Flash Tool as opposed to SP Flash Tool.
Make sure the scatter is correct. Create a new scatter with MTK Droid Tools
None of them work.
I've tried 4 different cables. MTK and SP tools.
It seems as though something is wrong with my preloader. When I try to 'restore factory settings' or even try to restart in recovery mode, the phone doesn't do anything. It's almost as though these modes don't exist or are bugged/busted.
EDIT: Yes, it seems to be some kind of preloader issue. When the phone is OFF, I connect the USB (which the computer recognises) and the within 2 seconds the 'disconnect' sound comes up. Within 2 seconds after that the battery charging shows up on the phone.
I say this because when the phone is ON, I am able to transfer files onto the phone and treat the phone as a normal connection. Something within the phone's software is causing SP Tools/MTK Tools/Other drivers not connect to it. I have a feeling I may have a corrupt/broken preloader/recovery system.
Thanks for the help. Please do advise as to what I can do.
Anyone?
Really could use some help.
vika09 said:
Anyone?
Really could use some help.
Click to expand...
Click to collapse
Hi, did you manage to get this sorted?
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
FLASHED 2.DUMP_ROM [SPFT][ROOTED] FROM All About CherryMobile Flare 4 AFTER IT SAYS FLASHING IS DONE 100% WITH CHECK MARK THEN MY PHONE DIDNT RESTART I WAITED FOR ABOUT 15 MINUTES TO SEE IF THERE'S SOMETHING MIGHT HAPPEN BUT NOTHING ONLY BLACK..
SO I PULLED THE USB CONNECTOR, THEN PLUG IT BACK. THE ONLY THING THAT I SAW IS UNRECOGNIZED USB. NO CHARGING LOGO OR ANDROID OR ANYTHING EVEN THE LED INDICATION OF CHARGING IS NOT BLINKING.
I HOPE SOMEONE CAN HELP ME :crying::crying::crying::crying::crying::crying::crying:
UP
I also had the same problem and I also cried. Your phone have MediaTek MT6753 Chipset. I have MT6582. You flashed ROM via recovery and looks like ROM have conflict with bootloader.
SP Flash Tool can flash shutdown MTK devices via USB. Your computer show "UNRECOGNIZED USB". SP Flash Tool need special ROM and driver to find your phone. Not sure, that SP Flash Tool can help you, but it helped me.
How I decided problem:
I waited some time (I went sleep, it was night)
Found stock ROM for Flashtool. This ROM contain all data for device and have more size.
Install driver for my phone.
Pulled out battery.
Connect with computer via USB.
Put in battery and computer detected phone as "MediatekDevice". SP Flash tool also detected phone
Started flashing.
Good luck!
AlexanderBabansky said:
I also had the same problem and I also cried. Your phone have MediaTek MT6753 Chipset. I have MT6582. You flashed ROM via recovery and looks like ROM have conflict with bootloader.
SP Flash Tool can flash shutdown MTK devices via USB. Your computer show "UNRECOGNIZED USB". SP Flash Tool need special ROM and driver to find your phone. Not sure, that SP Flash Tool can help you, but it helped me.
How I decided problem:
I waited some time (I went sleep, it was night)
Found stock ROM for Flashtool. This ROM contain all data for device and have more size.
Install driver for my phone.
Pulled out battery.
Connect with computer via USB.
Put in battery and computer detected phone as "MediatekDevice". SP Flash tool also detected phone
Started flashing.
Good luck!
Click to expand...
Click to collapse
thanks bro.
now it show dram fail (4032)
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.