Hi guys I'm a noobie at this Stuff... But I make my Struggle, even trying it
I have a M4tel model SS1060 from Telcel, the phone was Ok, just one day it freezed , I removed the battery and when I put it back to the phone it get sttucked at M4 logo
So, I found at the web that with SPflashtool I could make it boot up correctly again, loading again the correct ROM or FIRMWARE with it:
I was making this procedure on a laptop with Windows 8.1pro 64bits.
1.- I get the firmware from MTK page I found
2.- I installed the mtk VCOM preloader drivers succesfully
3.- Extracted the RAR file of the Firmware.
4.- Opened Flashtool, I selected the respective scatter.txt file for my device, put the icon on "Donwload Only".
5.- I unpluged the battery, and conect it via USB, the program started to send the file . After a few secconds a error ocurred saying that the PMT was wrong. So i Try it again a few times, even with other version of SPflashtool, and different firmwares for the M4 ss1060 (diferent mobile operators ROMs) without good results.
At this point the phone was in the same condition... I could boot it into recovery normaly, but when triyng to boot it up it keeps stucked at M4's Logo.
I found that this issue was supposed to be fixed setting the program on "Firmware Upgrade" instead of "Download Only". So I make the same process changing it to Firmware Upgrade.....
7.- The progam started succesfully, and loaded the file completly with no errors, after eight minutes the "ok " icon" was shown .
I unplugged the phone from the PC, insert the battery and nothing happened ANYTHING. I think that my mistake was to put "Firmware Upgrade".....
The phone keeps OFF I plug the Charger and it does not turns even the screen to Say "I'm Charging" I can't even get it into recovery mode, no logo screens. BUT.... When I plug the USB from the PC to the Phone I see that the Device Manager detects the phone with the Vcom Preloader of Mediatek.
So I tried to load the firmware again with SPflashtool on Download mode, the program send the file correctly, and it takes long as ten minutes showing the "OK" icon. But the phone keeps OFF, it makes nothing....
So I wonder If someone knows what to do, I was thinking on install a custom recovery, having on that the problem may be that I damaged the recovery of my phone making it unaviable to boot up. But I'm not shure, and I haven't found information about it.
I just knows that my phone has a MT6572 Chipset, I wonder if some one knows what to do.
Thanks.
Related
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 ((((
Lets get one thing straight at the start:
If you have the real Goophone i5c and it is not starting up BUT showing up in Windows (ie. you hear the Windows sound for device attachment), you CAN revive your dead phone.
if your phone doesn't show up then I can't help you - sorry!
I have done my utmost though to kill my phone and as someone on another thread said, its virtually impossible to kill it by just flashing roms to it.
What I have learned by reading on the web is that most people struggle to get the sp tool and other flashing tools to work once they have bricked their phone.
I had the same issue but figured it out after trying various solutions and failing.
First of all download the latest version of sp tools. if you haven't already done so, download the MT65xx_USB_Driver from the link below. You can also get the sp tools from there but it might not be the latest version though it will work.
You need to download the goophone rom from here: https://docs.google.com/file/d/0B5nKOG8KS1D3bjZPUGNrUDNRX1U/edit
Unpack all of them start the sptools and load the scatter file as shown here: http://mychinesephone.com/viewtopic.php?f=44&t=352
Plug in your dead phone. if it shows up as a vcom usb device, all is well. If it doesn't (mine initially showed up as a Alcatel device) you need to force the driver by doing update driver and choosing the driver manually then pointing it to the usb driver folder you unpacked before and choosing the android_winusb.inf file. It will then allow you to choose the MTK USB device.
Once you have this, unplug the phone and replug it to make sure its showing up as the usb device.
At this stage, click Firmware Upgrade. As most people have found nothing happens. Now hold Menu and Power on your phone for a few seconds and then release. You should hear the Windows device attach sound and a few seconds later flashing should commence. If all goes well, you should see the success notice after a few minutes (on this rom the whole process takes under three minutes, on others it takes longer).
If you see an error message, its likely you have a different version of the phone (kuphone etc.) and need the appropriate rom.
Hope this helps someone, there seems to be very little information for fixing these phones out there.
My Google Drive link is below with the files I've mentioned and a few other versions of the flashing tools which may also work for some if the one mentioned above doesn't work for you.
https://drive.google.com/folderview?id=0B1KaW-uz7M9dOVNBT3AzMy15blk&usp=sharing
GOOD LUCK!
Once the phone has finished flashing, you need to unplug it and give it a minute or so. press and hold the power button for a second and you should be greeted with the Goophone logo.
If it doesn't switch on, hold Menu and Power together and release then try again.
Once you have the phone booted you may notice that your IMEI number is showing invalid. This number should be on the back of your phone and you can fix this by pressing *#8002# on you dial pad and on the menu that appears, choose GPRS and enter the number under the SIM1. Click the Menu button to exit and then reboot. you can check if this has worked by dialling *#06# on the dial pad. It should display your IMEI number.
If you want to replace the Goophone logo with the Apple one, simply type *#8000# on your dial pad and reboot!
Sorry, Menu button is of course the Home button, the big round button in the middle!
Can someone let me kmow if this worked for them?
Thanks
Deleted
Zophone i6 unbricking
I did exactly what you told... I got a Zophone I6 with the original ROM.
After forcing the driver, it started to flash (red bargraph 100%)..... then nothing...
The phone is now detected as DA Vcom usb driver but nothing happens if i connect flash tools...
Any idea ???
Hi!
I have bricked a MT6575 Star B79 phone. I know that is a very old-fashioned platform, but maybe someone can help me anyway.
I flashed it many times in the past without issues, but this time something was wrong.
Before brick, it had REVO 4.0.4-SGS4 firmware working for many time. The phone became bricked trying to flash stock 4.0.3 firmware PULID_B79(三码电脑升级)-20120707.
Actual state of phone is: Battery charging ok on power-off; at power-on phone shows the first Android image and then shows a black screen (back-light on; no sound, no starting “video”). In this state (power-on), if I connect to PC, the Device Manager of Windows shows a “Linux storage drive” (or some like that) and other “/F” device.
I can boot in recovery mode by it is stock recovery (<3e> version) and shows “failed to mount /cache”.
Preloader seams connect OK to PC when phone is connected without battery. But apparently, SP Flashtool can’t write to the phone.
I tried to flash with different versions of SP Flashtool, many different ROMS but always I got the same result.
SPFT shows the flashing advance bars and the green circle, but apparently, file is not write to the phone. I tried to flash a cwm-recovery, SPFT showed ok but stock recovery stayed in the phone.
I tried by changing drivers, but resulting state was the same. I also tried by “test point” method by disassemble the phone, same result (all OK in SPFT but nothing changed in the phone).
It seems like internal memory of phone is in read-only mode…
Someone could help me with this issue?
I apologize because of my poor english.
Regards.
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
Hello everyone;
I was trying to load a CM recovery file on my cell by using SP Flash tools and somehow bricked my Acer Z410 phone (carrier: Fido, 2 sim card slot) I do not know why afterwards, the cell turns white with a yellow strip down the middle. I have been able to have my computer recognize it after numerous attempts to flash firmware versions that I was not quite sure was the original. I had tried your site to load the firmware that seem to correlate to my cell configurations, but all of the links are dead. I ended up flashing with SP Flash tools firware version AVOKO 1.015, but it still can't boot in to see anything on cell. So as of today, I got my computer to recognize the phone and I can actually see the files on my phone and sd card inside. How can I boot into this puppy? I have tried within ABS and the command function to view adb devices, but it does not show up? I get an error : device 0123456789ABCDEF Unauthorized. In my device manager it shows up as ACER phone , and under the Ports section it does show Mediatek Preloader USB VCOM driver (COM 5). I hope I have given enough information to start diagnosing the problem.
Any suggestions how to go about this problem from here?
breezin123