troubleshoot your excelvan mt10 tablet - Android Q&A, Help & Troubleshooting

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?

Related

[Q] Odys Genesis bricked after cyanogenMod7 custom rom for odys genesis update?

Hello,
I've tried updating the Odys Genesis to the custom firmware cyanogenMod7 custom rom for odys genesis.
I think i did it the wrong way. I've searched for hours on the internet how to do it, and then i cam across a post that said i just needed to put it on the device and then android would pop up and say: "A new update is available" and i just would have to tap that. So, i did.
The device rebooted and started updating all kinds of stuff in a dos-like enviroment. But now it's only a black screen and saying ANDROID in white letters. I've kept it like that for an hour, and then i tried resetting it (behind the device, hard reset button). I see the Odys brand screen, but then it's back at the black screen with android on it again.
Is there any hope left? Can i do something to fix it?
I've tried searching for hours on the internet, and i came up with absolutly nothing. Any help would be greatly appreciated!
Thanks in advance!
I found out a little bit more:
- My problem is called a boot-loop. It seems like it anyway, i only see a tiny white text saying 'android'.
- I can't find anywhere on the internet if there's a recovery mode for the Odys Genesis.
- The device will turn on with any button-combination, except when i press menu+power or power+reset.
I have been looking at Odin, cause that should be a unbrick-program for android phones. But it seems you need specific firmware for your model. Can i just use the original firmware update from the website of the manufacturer?
Or am i just totally ****ed? Just a reaction alone would be appreciated !
Solution
And somebody can close this topic!
I'm extremely happy, cause by a little accident i discovered how i could flash back to the normal firmware.
For somebody who has the same problem, here my solution:
When the device is on the screen only saying android do the following:
- Press the hard reset button (on the back, the tiny hole) and the menu button at the same time.
- The android screen should now go away, and it should like the device is off (although it isn't).
- Plug in the usb cable and connect it to your pc.
- If you had your device previously plugged in to your pc before, the pc will falsly recognize it as 2 hdd's while there isn't any shown in this computer.
To fix that:
- Go to device manager (This computer (right click) -> properties -> device manager)
- Uninstall the falsly drivers, (so there is no driver anymore).
- Disconnect the usb cable and connect it again.
- Windows should now say (or say in device manager) that an unknown device is connected.
- Download the Pc Update Tool and original firmware from the manufacturer website: (can't post url's here, so google Odys Genesis and you will get there)
- At the driver installation window choose you would like to point where the drivers are.
- Choose the dir from the pc update tool, and choose the driver map according to your processor and windows.
- The device should now be installed as a RK2.... something device.
- Start the Pc Update Tool
- The first box below should be green, indicating it sees the device and is ready to flash.
- At the box image, choose the original image downloaded from Odys website.
- Click Upgrade.
All should work well now, the box (log) should keep you informed. It could take a little while.
When it's done, it will tell you in the window. The device should now restart and Boot recovery should start and the device, formatting everything, resetting again and then installing everything. It all could take some while, so be patient.
And that's it.... then everything is working again ! ~!
Please let me know where you downloaded the CM7 ROM from... can't get it from the link in other post
Thanks
sleuteltje said:
And somebody can close this topic!
I'm extremely happy, cause by a little accident i discovered how i could flash back to the normal firmware.
For somebody who has the same problem, here my solution:
When the device is on the screen only saying android do the following:
- Press the hard reset button (on the back, the tiny hole) and the menu button at the same time.
- The android screen should now go away, and it should like the device is off (although it isn't).
- Plug in the usb cable and connect it to your pc.
- If you had your device previously plugged in to your pc before, the pc will falsly recognize it as 2 hdd's while there isn't any shown in this computer.
To fix that:
- Go to device manager (This computer (right click) -> properties -> device manager)
- Uninstall the falsly drivers, (so there is no driver anymore).
- Disconnect the usb cable and connect it again.
- Windows should now say (or say in device manager) that an unknown device is connected.
- Download the Pc Update Tool and original firmware from the manufacturer website: (can't post url's here, so google Odys Genesis and you will get there)
- At the driver installation window choose you would like to point where the drivers are.
- Choose the dir from the pc update tool, and choose the driver map according to your processor and windows.
- The device should now be installed as a RK2.... something device.
- Start the Pc Update Tool
- The first box below should be green, indicating it sees the device and is ready to flash.
- At the box image, choose the original image downloaded from Odys website.
- Click Upgrade.
All should work well now, the box (log) should keep you informed. It could take a little while.
When it's done, it will tell you in the window. The device should now restart and Boot recovery should start and the device, formatting everything, resetting again and then installing everything. It all could take some while, so be patient.
And that's it.... then everything is working again ! ~!
Click to expand...
Click to collapse
I have the same issue, but I have a 64bit Win7 and it just won't work. Windows will not install the original drivers. Any other way to go around it?
I only need make a hard reset, any help??? I don't remember unlock code
I've tried to download original firmware but i can't find it.

[Q] Huawei Vision (U8850) bricked

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!!!

Goophone i5c Bricked? Relax..help is at hand!

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 ???

Android phone 'bricked' yet with signs of life

Our phone has apparently bricked after a manufacturer supplied, firmware upgrade from SD card. :crying:
Current symptons are:-
Phone still powers on but the display is massively corrupted in all cases (save for the manufacturer logo at power on).
Booting into Recovery mode (PWRBTN+VOL-DOWN) works (of sorts) but booting to fastboot/system recovery (PWRBTN+VOL-UP) doesn't. In the former case, it's impossible to go further without the display although it responds to the adb tool when connected to a Windows PC.
Booting into normal mode, it is possible to remove the screenlock and even make out & set some options for the USB mode.
Whilst a pain, the whole thing doesn't seem totally without hope.
Is it possible to recover this device without sending it back to the factory (it's a second-user one so we're likely to be charged)? If so, what should the next step be?
Thanks.
xanda-escuyer said:
Our phone has apparently bricked after a manufacturer supplied, firmware upgrade from SD card. :crying:
Current symptons are:-
Phone still powers on but the display is massively corrupted in all cases (save for the manufacturer logo at power on).
Booting into Recovery mode (PWRBTN+VOL-DOWN) works (of sorts) but booting to fastboot/system recovery (PWRBTN+VOL-UP) doesn't. In the former case, it's impossible to go further without the display although it responds to the adb tool when connected to a Windows PC.
Booting into normal mode, it is possible to remove the screenlock and even make out & set some options for the USB mode.
Whilst a pain, the whole thing doesn't seem totally without hope.
Is it possible to recover this device without sending it back to the factory (it's a second-user one so we're likely to be charged)? If so, what should the next step be?
Thanks.
Click to expand...
Click to collapse
Depends on what tablet you have...
es0tericcha0s said:
Depends on what tablet you have...
Click to expand...
Click to collapse
Cubot P9 in my case.
xanda-escuyer said:
Cubot P9 in my case.
Click to expand...
Click to collapse
Might want to check out here:
http://www.needrom.com/category/cubot/p9/
and see if one of those might get you back on track.
You must try to format ur phone factory CWM mode may be its solve ur problem
Bhavik Kumar
SOLVED: Courtesy manufacture support.
Thanks for the reply.
We see a lot of references to the needrom site (amongst others) but are uncomfortable drawing from a source which has no apparent verification in terms of authenticity.
In the meantime, we were able to recover the device with the aid of the manufacturer.
For the benefit of anyone else in the same boat and thinking that their device is beyond all repair, here's what you need to do (assuming Windows PC):-
i) Get a copy the MediaTek SP Flash Tool (at this time, there is no official download site for this available outside their developer portal).
ii) Device ROM package/archive with the scatter file for the specific device. (Ask your mfr first).
iii) MediaTek USB driver (ditto point one).
The whole fix doesn't take very long and is semi-automatic. In short, here's what to do:-
- Start by removing the phone battery and connecting to the PC.
- Install the USB drivers next.
- Run the SP Flash Tool (it's a portable app so no installation required) and load the binary & scatter files.
- Insert the battery to the phone; this will automatically put the phone into a serial connection mode which the SP Flash Tool will immediately detect; followed by automatic downloading of the firmware to the device.
That's it - reboot the device and it should all just work...
HTH

Kingroot - what a disaster - Blu Studio XL bricked

I made the serious mistake of installing Kingroot which failed installing the first time, then it said try again, then it worked but totally took over every aspect of my phone with no apparent way to delete any of the new "features". It didn't seem to be as much about installing root as it was interested in installing some apps they force you to install which totally takes over your phone. (Side note - it is a shame that this is sold as a rooting software, it should be in reality named a virus or malware and avoided. Too bad for BLU users there doesn't seem to be any other way to attempt a root)
Then installing supersu-me created more havoc, then trying to re-install Kingroot completely locked my phone and put it in a boot loop.
Now upon first attempt, I can't seem to make SP Flash Tool or MTK Droid talk to the phone (first time trying now). I installed all the drivers that came with the forced install .exe (which installs the drivers even when no "unknown device" ever appears in device manager) but I have not yet found any "unknown device" in the Device Manager before or after installing these drivers.
When there is no data cable connected, the recovery menu must be used as the only method to power down the phone because it loops on and on with an attempted power up until the battery runs down. However after using the green on black background recovery menu (hold in VolUp and Power), and making the selection to power down, the phone finally powers down. Unfortunately, as soon as the data cable is inserted into the phone, it begins the boot loop again which makes the laptop ding-dong indicating USB driver loading/unloading over and over.
There are options on the green/black recovery menu to load from SD card and to enable ADB but I can't figure out what driver to use and which option on the green/black recovery to attempt. Of course the factory restore option did nothing and the options for ADB, Fastboot and load from SD card seem promising but all I can find for an image is a RAR file which appears as the format of someone's SP Flash Tool dump, and includes the scatter file MT6582_Android_scatter.txt plus other *.img and *.bin files.
With no way to get into my phone, I don't know how to attempt to load this image which I believe is the extraction from the SP Flash tool. I have installed CDC/ACM driver install package, Google Inc USB, Media Tek usbser from 2011 & 2007, usbvcom and Usbvcom_brom.
Any ideas? Thanks!
Just saying, whenever you root your phone you gotta make sure to have a stock firmware in case of emergencies... It's no one's fault.
hi all,
does anyone have a solution to installing a custom rom on blu studio xl (lte)? the stock rom is on Android 5.1 and its laggy as all hell.
thanks much in advance,
ak
Install mtk v com drivers.
Similar thing happened to me on a mtk phone, I have all software and drivers etc on my home pc, not here. Send me a message tomorrow to remind me and I'll Google drive them and give you a link, with instructions. It can be fixed! Don't panic! I assume you have stock firmware? If not, get that ready and downloaded ready. Also, a few different versions of SPflash tools, some don't work on some phones, even the same phones. And different USB leads also.

Categories

Resources