Related
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.
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.
A while ago I made a post about how I hardbricked my Wiko Lenny, and I finally decided to try the testpoint method. The problem is that I have absolutely no idea as to where that testpoint is on the PCB.
Can someone guide me? I attached some pictures with the PCB.
Okay, I found the testpoint. It's noted as KCOL0, and it's under the PCB, near the volume up button. I connected GND with KCOL0, but the phone is rapidly switching on and off. I can't flash it in this state.
After a few minutes of constant switching on and off, the phone decided to calm down and let the PC detect it.
In Device Manager it appears as "USB Serial Device (COM6)", and SP Flash Tools v5 detects it easily. But it can't flash it. It always spits out this: "S_FT_ENABLE_DRAM_FAIL" and stops.
Any ideas?
Come on, guys... Someone here must have at least a bit of experience with Mediatek phones...
Please tell me your status for now, also tell me how you got into this ??
I mean how you made a brick??
My phone has the habit of simply going into a bootloop once every few months. I always repair it by reflashing the ROM in SP Flash Tool, but last time I used a tool supplied by Wiko. Apparently the tool reflashed the entire phone instead of the Android partition, and managed to corrupt the preloader. As a result, the phone didn't turn on, vibrate, or even get recognized by the PC.
A while ago I made a post about this, but nobody wanted to help me. I researched the internet and found out that the phone can be repaired by META mode, by JTAG or by testpoint. META mode isn't available on MT6572 devices, so that didn't work. JTAG seems too complicated for me, so the last option was shortcircuiting the KCOL0 testpoint.
I opened up the phone's back, took the PCB out and soldered a copper wire that connected the groundpoint(GND) with the testpoint(KCOL0). After connecting it to the computer, the phone started turning off and on rapidly for around 10 minutes, then decided to stop, letting it be recognized by the PC. It appeared as "USB Serial Device", but it should be called "Mediatek MTK PRELOADER" or something similar. I thought it was the PC, so I continued.
Started SPFT, loaded a scatter that I backed up from the last flash, then clicked Download. After 30 seconds it stops and writes this: "BROM ERROR: S_FT_ENABLE_DRAM_FAIL (4032)". Tried resoldering and reflashing, but same result.
Any ideas?
DragonSky87 said:
Any ideas?
Click to expand...
Click to collapse
Error 4032
Message: BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail
Meaning: The firmware you're trying to flash is either not compatible with your device or you have selected the wrong flashing settings
Solution:
* Ensure that the file(s) you're trying to flash are actually for your exact phone model
* Ensure you tick the boxes for only the files present in the ROM you're about to flash
* Probably have the wrong driver installed. Uninstall vcom, preloader and MTK drivers using usb deview then manually re-install using forum.hovatek.com/thread-440.html
* Delete the sp flash tool folder then re-extract
* Ensure the phone is switched off (with battery still inside) before connecting to PC for flashing.
* If that doesn't work, keep holding down the volume decrease button just before connecting the phone to PC for flashing (you could try volume increase , power + volume decrease or power + volume increase).
* Consider using the latest version of Sp Flash tool
* Format the phone before trying to flash the file(s) again
Ti-am scris si un mesaj privat. Mi-ar place daca m-ai putea ajuta
VanCroft said:
Error 4032
Message: BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail
Meaning: The firmware you're trying to flash is either not compatible with your device or you have selected the wrong flashing settings
Solution:
* Ensure that the file(s) you're trying to flash are actually for your exact phone model
* Ensure you tick the boxes for only the files present in the ROM you're about to flash
* Probably have the wrong driver installed. Uninstall vcom, preloader and MTK drivers using usb deview then manually re-install using forum.hovatek.com/thread-440.html
* Delete the sp flash tool folder then re-extract
* Ensure the phone is switched off (with battery still inside) before connecting to PC for flashing.
* If that doesn't work, keep holding down the volume decrease button just before connecting the phone to PC for flashing (you could try volume increase , power + volume decrease or power + volume increase).
* Consider using the latest version of Sp Flash tool
* Format the phone before trying to flash the file(s) again
Ti-am scris si un mesaj privat. Mi-ar place daca m-ai putea ajuta
Click to expand...
Click to collapse
First : sorry for my bad english; I have wiko lenny too and after I dismantled the phone, and found KCOL0 TP, shorted it to Ground and connected USB cable and after that my phone is conecting and disconecting all the time. Not remain conected and can`t flash firmware.Please help me with any sugestions. Thanks in advance.
VanCroft said:
First : sorry for my bad english; I have wiko lenny too and after I dismantled the phone, and found KCOL0 TP, shorted it to Ground and connected USB cable and after that my phone is conecting and disconecting all the time. Not remain conected and can`t flash firmware.Please help me with any sugestions. Thanks in advance.
Click to expand...
Click to collapse
Nobody knows ?
VanCroft said:
Nobody knows ?
Click to expand...
Click to collapse
Sorry for my English.
I have one with the same "dead".
Make short between Kcolo point and GND.
Be sure battery is full.
Use V20 firmware.
Select firmware up-grade from Smart Phone Flash Tools.
Connect phone to PC with Volume + push
Don't forget to remove the jumper after flash
VirtualG said:
Sorry for my English.
I have one with the same "dead".
Make short between Kcolo point and GND.
Be sure battery is full.
Use V20 firmware.
Select firmware up-grade from Smart Phone Flash Tools.
Connect phone to PC with Volume + push
Don't forget to remove the jumper after flash
Click to expand...
Click to collapse
Thanks for reply! After short betwen Kcolo and GND I must insert the battery ? and then flash? First time
I thought the battery should be removed Ok! I will try now
VanCroft said:
Thanks for reply! After short betwen Kcolo and GND I must insert the battery ? and then flash? First time
I thought the battery should be removed Ok! I will try now
Click to expand...
Click to collapse
Thank you very much!!!!!!!!!
I managed to bring it to life:laugh:
Brother have you fixed or still need support ?
Let me know if you need something
Sent from my Lenovo IdeaTab S6000-H Using XDA Premium 5
maged.homaid said:
Brother have you fixed or still need support ?
Let me know if you need something
Sent from my Lenovo IdeaTab S6000-H Using XDA Premium 5
Click to expand...
Click to collapse
Thank you. I have done, my phone is working now.:laugh:
VanCroft said:
Thank you. I have done, my phone is working now.:laugh:
Click to expand...
Click to collapse
Good news brother
Congratulations..
Sent from my Lenovo IdeaTab S6000-H Using XDA Premium 5
I still didn't manage to repair it, as I may have made a mistake while soldering and shortcircuited the phone.
I may try again, though.
I have the same issue but my Wiko Lenny 3 is dead for a while (like 2-4 years). Until this time, I was trying to repair my device, but no luck occurred. But I can't find the KCOLO point, as I should. It is either on the main board / motherboard (I don't know how to call it) or under it. I'm of a smartphone repair noob...
I hope that I can finally manage to repair this device because I don't know what I should do with this device.
And added the image to see if you guys can find the KCOLO / KOLO / COLO point...
Hello everyone,
I have a situation that has around 4 months now, and I can't fix it even after reading every piece of information I could grab on this forum and google.
I'm usually the guy that prefers to play safe and not flash any kind of Android device to avoid this kind of headaches, but out of the blue (i believe it was a power grid failure), my box wouldn't boot past the logo. It's a Mini M8S II (S905X). I contacted the support at Gearbest (where I bought it) and they said it could not be fixed and refunded half the money. So no luck there.
After 4 months of research and testing and failing to unbrick this box, here are the conclusions I took:
- When I try to flash any firmware with USB Burning Tool it recognizes easily, but always stops at 7% (U-Boot/Send Command Error or something like that). Tried 2 cables, 2,0 and 3.0 USB ports, and different versions of USB Burning Tool (had time to try many combinations)
- When I try to flash any firmware with SD Card, it shows the cute and lovely android but ends up with a red cross on the end. (tried all kinds of combinations with the erasing flash option, all types of firmwares I could find for this box, etc)
- When I try to access the recovery without SD Card using the toothpick, nothing happens.
- I tried the "sd_MINIM8SII_rv102" extracted to the sd card, nothing happened.
- Tryed many firmwares with USB Burning Tool, rv109, rv112, and others for S905X...... nothing goes in this box =/
After some deeper research, I tried extracting the "update.zip" from "sd_MINIM8SII_rv102" to sd card and replacing the recovery.img with the one from TWRP for S905X v3.0.2. It boots successfully to TWRP asking if I want to keep the system read-only. (at this point I saw the light at the end of the tunnel) Tried right away to flash a firmware from it, failing with messages saying the are no mounting points for /data and no /system partition and what not. Then I noticed the internal memory says 0Mb, in the recovery. Is that the problem?
I've also seen stuff like dropping a u-boot.bin (tried botfap's u-boot.bin.sd.bin) and stopping u-boot to access u-boot shell. From there you can flash the recovery.img and dtb.img and stuff like that. Can't find much information on that and didn't had much luck with it either.
What am I missing? what can I do? I'm up for anything other than using this Box as a tall beer coaster.
How about the short circuit method? I'm lost.... I just want it working again =(
Here goes some images with the error from USB Burning Tool:
imgur.com/a/GFhJu
imgur.com/a/5LIn5
Have you tried starting usb tool flash and then plugging in the box after flashing already started in software? That worked for me. Found the fix on another forum.
Sent from my SM-G900V using Tapatalk
Koognod said:
Have you tried starting usb tool flash and then plugging in the box after flashing already started in software? That worked for me. Found the fix on another forum.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
If you mean pressing start on usb burning tool and then plug the USB cable. Then yes, tryed it several times with many diferent ROM's =( always the same output.
It was one of the many tricks/tips i've found. But still no difference..... thank you tho!
when u get error message at usb burning tool after press start, just continue with reconecting usb cable with and w/o press reset button..
actually last hour i get some trouble like you, error in usb burning tool because device disconected automaticly after 10 second maybe, but i just try recconect the usb cable, n viola, usb burning working n install my rom..
i think if your pc still recognizing ur tv box via usb cable, u still can doing flash with that usb burning..
clasie said:
when u get error message at usb burning tool after press start, just continue with reconecting usb cable with and w/o press reset button..
actually last hour i get some trouble like you, error in usb burning tool because device disconected automaticly after 10 second maybe, but i just try recconect the usb cable, n viola, usb burning working n install my rom..
i think if your pc still recognizing ur tv box via usb cable, u still can doing flash with that usb burning..
Click to expand...
Click to collapse
Thats what I thought, if the USB Burning Tool recognizes there is hope!! lol
but the truth is.... I keep hearing the "Keep trying" on several forum topics...... I try reconnecting and refreshing several times..... I tryed with several USB Burning Tool versions, I tryed with several combinations of installing drivers with and without the reset button when connecting...... several things....... the computer sometimes recognizes as "GX-CHIP" and sometimes as "Worldcup Device"........ would there be the problem? I keep hiting the 7% wall with the "UBOOT/Disk initialize/Send command/Error result" message..... very frustrating! =/
Here goes more information from the error log:
[20:04:54 876][HUB1-2][Inf]--Device is connected
[20:04:54 876][HUB1-2][Inf]--Close device handle 0x00000660
[20:04:54 938][HUB1-2][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#5&1003806&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x000008c0
[20:05:00 001][HUB1-2][Inf]--0-7-0-16
[20:05:00 002][HUB1-2][Inf]--CheckFileRunState succeed
[20:05:00 002][HUB1-2][Inf]-- low_power
[20:05:00 007][HUB1-2][Inf]--Send command success
[20:05:00 010][HUB1-2][Inf]--Read command status success
[20:05:00 010][HUB1-2][Inf]-------------Download meson1.dtb-----------
[20:05:00 012][HUB1-2][Inf]--0-7-0-16
[20:05:00 012][HUB1-2][Inf]-- download mem dtb normal 79872
[20:05:00 012][HUB1-2][Inf]--Send download command success
[20:05:00 025][HUB1-2][Inf]--Read command status success
[20:05:00 037][HUB1-2][Inf]--Transfer complete
[20:05:00 037][HUB1-2][Inf]--Send download get_status command succeed
[20:05:00 041][HUB1-2][Inf]--get_status success
[20:05:00 542][HUB1-2][Inf]-------------ERASE FLASH-----------
[20:05:00 542][HUB1-2][Inf]--disk_initial 1
[20:05:00 542][HUB1-2][Inf]--Send command success
[20:05:01 671][HUB1-2][Err]--failed:[20:05:01 671][HUB1-2][Err]--Check command return failed
[20:05:01 688][HUB1-2][Err]--[0x30201004]UBOOT/Disk initialize/Send command/Error result
have you ever managed to resolve this issue?
Hello.
Everything has gone terribly wrong for my phone and I desperately need your help.
I downloaded what was stated on needrom.com I made sure MTK vcom was installed properly and had the correct rom from needrom.com but I still got Brom Error: STATUS_BROM_CMD_SEND_DA_FAIL in SP flash when using MTK_AllInOne_da.bin.
I then tried DA_PL.bin and got another error. I tried to uncheck preloader and run Download through SP flash with DA_PL.bin which worked just fine. However now I'm stuck at the Bluboo logo screen and phone does not load into android.
I still get Brom Error: STATUS_BROM_CMD_SEND_DA_FAIL in SP Flash if I use MTK_AllInOne_da.bin but if I use DA_PL.bin now I get this error:
Chip mismatch!
Scatter:MT6757D
device: MT6757
Please help me, my phone is bricked until one of you help me. I'd be forever grateful!
Tomaskaos said:
Hello.
Everything has gone terribly wrong for my phone and I desperately need your help.
I downloaded what was stated on needrom.com I made sure MTK vcom was installed properly and had the correct rom from needrom.com but I still got Brom Error: STATUS_BROM_CMD_SEND_DA_FAIL in SP flash when using MTK_AllInOne_da.bin.
I then tried DA_PL.bin and got another error. I tried to uncheck preloader and run Download through SP flash with DA_PL.bin which worked just fine. However now I'm stuck at the Bluboo logo screen and phone does not load into android.
I still get Brom Error: STATUS_BROM_CMD_SEND_DA_FAIL in SP Flash if I use MTK_AllInOne_da.bin but if I use DA_PL.bin now I get this error:
Chip mismatch!
Scatter:MT6757D
device: MT6757
Please help me, my phone is bricked until one of you help me. I'd be forever grateful!
Click to expand...
Click to collapse
Don`t worry about that, first this is the link of the last update https://www.google.com/url?q=https:...ds-cse&usg=AFQjCNFJKeEcDClPU2MnxLJefaQ19GmQpQ
for more success put your folder of SPFlash Tool near to folder of your unpacked rom (for short transmission of data) and Bluboo S1 has a few different way to enter to other mtk cause battery it`s not removable like other just disconnect it and connect again; in this case connect cable usb to your device, prepare all the files in SPFlashTool and click download and now while pressing both volume + and - connect cord to pc till SPFlashTool begin to recognize files (red letters) and release now, SPFlashTool continues process till 100% in yellow progressing line
SubwayChamp said:
Don`t worry about that, first this is the link of the last update https://www.google.com/url?q=https:...ds-cse&usg=AFQjCNFJKeEcDClPU2MnxLJefaQ19GmQpQ
for more success put your folder of SPFlash Tool near to folder of your unpacked rom (for short transmission of data) and Bluboo S1 has a few different way to enter to other mtk cause battery it`s not removable like other just disconnect it and connect again; in this case connect cable usb to your device, prepare all the files in SPFlashTool and click download and now while pressing both volume + and - connect cord to pc till SPFlashTool begin to recognize files (red letters) and release now, SPFlashTool continues process till 100% in yellow progressing line
Click to expand...
Click to collapse
Thanks!!! It works!!!!
Just be very careful. The USB C connector port in the phone is very loose... so make sure you can hold the cable tight other wiser it will lose the connection and brick your phone. For me, I had to remove the Plastic cover to be able to hold the power cable tight!
Hi, could you help me please? I did your steps, but it is not working. Sp flash does all its job, shows the green sign, but the phone stills dead. What I noticed the usb connects with the phone, then it disconnects. I tried to install the drivers as the tutorials say like deactivating the driver signature enforcement, but nothig happens well.