Related
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
petoxxx said:
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
Click to expand...
Click to collapse
mine is not working i think mine is bricked completly
bricked my mobile...Help!!!!
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
sivakarthick said:
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
Click to expand...
Click to collapse
The thread called 'Problem with huawei vision' still seems to be active. You may want to try asking your question over there.
Huawei (u8850) unbricked
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
how to turn off huawei u8850 completely
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
bikeshrt said:
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
Click to expand...
Click to collapse
it's actually not difficult to remove the battery...
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Anyone here interested in developing a 3.x kernel? seems other phones with msm8255 have successfully got one...
u8850 power off
btsimonh said:
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Click to expand...
Click to collapse
now i have tried it, and no success.
However, what i have found to work - if your non-boot is actually booting the kernel, but failing to initialise the phone, then you can still use adb with it... I ran adb shell, and then used 'poweroff' to power off my phone, which then meant i could boot into CWM recovery....
i HAVE THE SAME PROBLEME? PLEASE CAN U HELP ME TO SOLVE IT BY GIVING ME DETAILS.
it is working, thank you bro
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
it is working thanks bro
Stock rom download plz.
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
HOLY GOD! F**K ME!!! I finally did it! THANKS A LOT, BRO! YOU'RE AWESOME!!!
Hi!
I had a problem yesterday with my Amoi N828 cell phone. During a contact list or messages searching, my phone was automaticly restarted. My idea was to make a system restore using option available on the power on/off button. After that I saw chinesse menu which is not understoded for me I pressed some button and after that such process was started and stopped during 15 min. My decision was to a phone restart. And right now, during system initialization I'm seeing only Amoi logo and phone is stoped.
My next step was to flash system again. I found some drivers MT6589, additionally firmware and "SP flash tool"
When I'm connecting phone without battery by USB cable to the system (Win7 32 and 64 bit) is detected and looking the drivers. And now is a problem. my device is visible for the moment and after that is disappears and again - see link below:
youtube.com/watch?v=Wg47gdlB7YU
the question is why? When the drivers are installed, the problem is still same like before - nothing changed
PLEASE HELP ME! I'm woeful ((((
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
This might be a long situp to write this, but i've experienced that a lot of the excelvan users do not really know, where to get support for their device. I've bought this device because the price was low. And so is the quality. It is assembled with a JTY mt10 smarphone mainboard, connected to a 10,1'' touch display.
I've bricked the device and getting help to retrieve it back to life was a pain. No support from excelvan, so I've experimented with it, to find the best possible solutions. In order to help you save time on rechearching this issue, I'll now post this, hoping it helps you getting the tablet back to life and running.
Notice: this is for excelvan mt 10 tablet only. I have no idea, if this works for any other product, so don't ask me, just look around the forum to find help. If the real hardware is bricked, this won't work either, your device should be repaired by qualified service persons to proceed with this.
1 setup your pc to get started.
I've installed the following software on my windows 10 desktop pc:
- The MTK Droid tools, links are supplied by this forum
- The MTK Sp Flash tool, you'll find links for that in this forum or get it from mediatek
- Philz recovery, use google to find it
- Kingo Root, you'll find it at the kingo root home page
- The Mediatek VCOM USB Drivers for Windows 10 (As for my PC) at Mediatek.
- The stock rom for excelvan mt10 tablet, you'll find it on needrom, download for registered users only
Installation of the software on your pc is straight forward, just follow the on-screen installation instructions and you'll be good to go.
Probably your device is bricked already, so no further action needs to be taken on your device.
The first thing you'll have to do is to see, if your drivers can connect to the device. To achieve this, follow the procedure below.
1. After setting up the drivers package, connect the device to your PC, using original USB cable. There are a lot of cables around there, but please use the original provided cable, as it is not sure, that other cables have all pins connected for this, so do yourself a favour...
2 Go to the device manager in your pc and look for your phone's name or the mediatek VCOM driver to run. If the device is booted up, you'll find them, if your device is bricked, you'll have to initiate the META mode of the 6572, to establish the connection. Luckily, the device has a reset button, so if it is bricked, you'll need to connect it to your PC, open up the device manager and press the reset button. (I've opened the device the very first time, to unsolder the battery leads, but I didn't know then, that there was a reset button...) The reset button is located between the micro USB and the Headset connectors on the right upper side of the device, the little hole there, use an insulated papar clamp to press it. In the device manager, you will see the driver popping up and after a short time, shut down. This is normal operation, sometimes it starts reconnecting over and over again, but that's allright.
3. First, you should try to get the preloader back on the system. This is very useful, many devices are bricked by shooting off the preloader. Open up SP Flash Tool, load the scatter file from the unzipped stock rom image for the device. You'll see the used blocks and partitions used by the software in the right pane of the flashtools program. Uncheck all blocks first, then click the checkbox at the 'Preloader', the first entry in the right pane..
4. Now connect your device with the USB cable to the pc. Yes, this comes first. Now press the 'Download' button, the dropdown bar should tell you 'Download Only'. If not, please select this from the dropdown and press download. Now the program waits for the connection, so press the reset button of your device. If all is setup correctly, your device will connect and download will start. First, you'll see a red bar running at the bottom part of the programs's screen, shortly followed by a yellow bar, showing progress of the download. If the download was successfull, you'll be notified accordingly. Disconnect your device and wait 10 seconds, then reconnect it to the pc. If your download was successfull, your phone will be recognised and stay connected, please look in your device manager on your pc, to see connection startup. You'll see the battery charging icon on your device, so it shows, that it is recovered back into it's life.
5. Now it comes to flash the rest of the firmware, so go back to SP Flash Tools, select the scatter file again, check all blocks EXCEPT the preloader and flash it to the device the same way, you've flashed the preloader. Now that you've selected more blocks to flash, you'll see that this takes much more time to download. So please be patient, do not tamper with anything, go ahead, get yourself a coffee or a beer and relax. If everything is okay, flashtools will inform you if the download of the firmware is successfull. If yes, you are good to go, for the first startup of your device.
Disconnect the device from your pc and power it on. If all is right, it will boot up android and you're ready to install and customize it for you.
But sometimes things just don't work this way, what can you do ?
Well, in my case, I've shot my preloader at the first try to flash the stock rom. Yes, I did not obey the rule that I should not tamper with this preloader, so it was checked also. This was a big mistake, after unsuccessfull download, the device did not react any more. The second time (I've bricked it again, because I would like to know, how to restore a bricked file system). So I've formatted all partitions, reinstalled everything and it worked fine. You can do this with the SP Flash Tools also.
I was tired of the 'Factory Recovery Mode', a standard piece of software, which seems to be some sort of rudimentary, so I'd like to install a CWM recovery for that. It would let me install a ZIP Update from the SD card, so it seems more usefull than that rudimentary factory recovery, but how to establish that ?
Searched the web for a long time. Used MTK Droid Tools for that, but this didn't work on the device. It could not create the recovery because of two errors:
- No found kernel GZ
- No found split boot image.
The search for the solution to these both errors resulted in just one thing: There seems not to be a solution for that.
If I can find the time, I will try to solve this but in this moment....
In this case, you'll have just one option left, install Philz Recovery. It brings touch capab8illity also, so it just seems ideal to have that. Besides the fact, that you can use the touch interface, the software brings a ton of usefull options with it, so it is the best choise for your device. I've extracted the ZIP file and dropped all items on my desktop to have a quick access to it.
This can only be done on a routed device, so you'll need to root it before continuing. Not rooting the tablet will result in hanging up the recovery program, so no use. I've rooted the device using kingo root. It runs on my pc and the only things installed on my device are the kingo root super user module and the kingo link module, for connectivity. The latter installations are done by kingo root and your PC, so you'll not have to do this yourself.
Rooting the device will take some time, so be patient. My device is connected as a JTY MT 10 Smartphone, when kingo root recognises it. It can take up to an hour to root. Probably there are other rooting programs out there, which could do the same, but I've tested a few of them, nothing else worked properly. I'll be using kingo root for this device in the future. Be aware, that the rooting with kingo root is session dependable, so after rebooting your device, you'll have to root it again.
You may now run the setup program for philz recovery. It can take more times starting up the program to successfully install the recovery on your device. I had to start the program 5 times, to get it installed completely, so if it is not working the first time, don't panic and start it over again.
The standard recovery image from the stock rom is not the same size as the recovery from philz. The program warns you for getting IMEI lost, so if you don't want this to happen, quit installation here. If you know what you do AND you have a backup of IMEI (NVRAM folders of the device) just go ahead. If installation of the recovery was successfull, you'll be notified by the program running on your pc. Now you can boot your device into recovery, by hitting the apropriate button presented by philz recovery setup program on your pc. To do this on the device itselft, power it off, wait 20 seconds, press the VOL + button and hold this while then pressing the power button. Hold these untill your screen lights up and select 'Recovery' from the menu, use VOL + for selecting, use VOL - to confirm. If the program starts, you'll notice, that it is 'Upside-Down'. That should not bother you, for this little inconvenience you get paid with a superb recovery.
In the next section of this post, I'll cover the backup and restore issues, using MTK Droid Tools, explain how to reinstall an IMEI, how to install a new MAC adress on the device. So stay tuned...
Joshi
Does anyone has custom recovery for Excelvan MT10?
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES
FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004)
Follow the following steps:
1. Get SP flash tools (Latest version)
2. Download your phone's firmware (from manufacturer site or needrom.com etc) and extract it.
3. install Mediatek Preloader drivers as per your OS version (win x7 , 8 10 etc) and architecture (32/64bit).
4. Run Flash tools with admin as administrator
5. select the scatter file from the firmware folder you downloaded and wait for it to load. (Do not connect your phone yet and leave the battery inserted)
6. Select Download Only
7. Hit the download button
8. Now plug in the micro/type C usb end of your cable to your phone but dont plug to PC. yet
9. While hold down both volume buttons i.e up and down buttons, (Do not press the power button), Insert the Usb cable end to your PCs usb port (Please choose a port thats very reliable).
10. After a while, P Flash tool will begin to upgrade your phone, dont release the buttons yet, let it lapse about 2mins then release them, the firmware upgrade will still continue and it will display a tick pop-up when done (this may take between 5-10mins).
Now unplug your phone, remove and re-insert the battery and power-up your phone. You phone is now unbricked.
Note that the first boot will longer than a regular boot.
This saved me
Oh my god. I was searching for hours and hours for a solution. This post saved my back side.
Perfect Solution for ZTE Blade A520
Thank you very much. This worked like a charm. Very helpful
adisa said:
FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004)
Follow the following steps:
1. Get SP flash tools (Latest version)
2. Download your phone's firmware (from manufacturer site or needrom.com etc) and extract it.
3. install Mediatek Preloader drivers as per your OS version (win x7 , 8 10 etc) and architecture (32/64bit).
4. Run Flash tools with admin as administrator
5. select the scatter file from the firmware folder you downloaded and wait for it to load. (Do not connect your phone yet and leave the battery inserted)
6. Select Download Only
7. Hit the download button
8. Now plug in the micro/type C usb end of your cable to your phone but dont plug to PC. yet
9. While hold down both volume buttons i.e up and down buttons, (Do not press the power button), Insert the Usb cable end to your PCs usb port (Please choose a port thats very reliable).
10. After a while, P Flash tool will begin to upgrade your phone, dont release the buttons yet, let it lapse about 2mins then release them, the firmware upgrade will still continue and it will display a tick pop-up when done (this may take between 5-10mins).
Now unplug your phone, remove and re-insert the battery and power-up your phone. You phone is now unbricked.
Note that the first boot will longer than a regular boot.
Click to expand...
Click to collapse
Thank you very much Sir, you are awesome!
Thank you very much Sir, you are awesome! I have made my dead phone alive following your post. You are the Life Saver of my phone. I have no word to thank you. I salute your hard work. Thank you very much. I want to share your post to everyone who are seeking solution like me.
mohidulhaq said:
Thank you very much Sir, you are awesome! I have made my dead phone alive following your post. You are the Life Saver of my phone. I have no word to thank you. I salute your hard work. Thank you very much. I want to share your post to everyone who are seeking solution like me.
Click to expand...
Click to collapse
New Error Now-
Error : S_AUTH_HANDLE_IS_NOT_READY(5000)
i have this error "Failed to Connect DA: S_AUTH_HANDLE_IS_NOT_READY". i dont know how i do
Ndanou jean-claude said:
i have this error "Failed to Connect DA: S_AUTH_HANDLE_IS_NOT_READY". i dont know how i do
Click to expand...
Click to collapse
Hi!
You should watch this video and tutorial, it was helpful for me too.
https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/