Hi, Guest! Login / Register
Giveaway: Free Hovatek T-shirts, Hoodies & Cufflinks.. I WANT ONE! (Nov 25, 2017)
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Phone not starting after unsuccessful flashing

#11

(09-14-2014, 08:52 PM)hovatek Wrote:
(09-14-2014, 06:45 PM)Androhelp Wrote: I just tested thoroughly and below is the submission with snapshots (pls co-relate)--

1) When I insert the USB cord in the USB port of PC, the Device Manager blinks (refreshed) and the 'Alcatel Single RNDIS Interface #2' listed in the network adapters in Device Manager (without any exclamation sign) as shown in 'DevMgr_1.png'.
2) Just within 4-5 seconds (instantly), Device Manager again blinks (refreshed) and come to the stage as shown in 'DevMgr_2.png' attached. Alcatel adapter is now having Exclamation sign.
3) The point 1 and point 2 told above go into an endless loop until I remove the phone USB cord from the computer
4) When phone is not attached to computer, the device manager looks like 'When_phone_not_plugged_in.png' attached.

Please go through the snapshots and advice further. Thanks.

I would've suspected a loose contact between the USB cord and the phone jack but something below caught my attention. Did you noticed that under Port, all Mediatek / MTK ports have exclamation / error sign with or without the phone connected? This is possibly where the No Com Port detected issue is coming from. Right-click on each one then uninstall. After Uninstalling, restart the PC. Back in device manager, Click Action at the top then scan for Hardware changes. You can then manually Install Vcom drivers using http://forum.hovatek.com/thread-440.html . forget PdaNet. You would need a working phone of the same model to install MT drivers using PdaNet and that you don't have

Thanks for the reply. I have followed the link and uninstall all the port drivers and reinstall them manually after restarted the PC. But, still the problem is there. Snapshot 'Driver_reinstall.png' attached.

The SP Flash logs still shows like --

09/15/2014 10:17:09.981 FlashTool[6476][7636][D]: USBSetting::SearchUSBPortPool(): Scaning USB port failed!(..\QT_FlashTool_Refactor\Conn\USBSetting.cpp,195)
09/15/2014 10:17:25.923 FlashTool[6476][7480][D]: OptionDialog::InitUARTInfo(): No com port detected.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,416)
09/15/2014 10:17:25.933 FlashTool[6476][7480][D]: OptionDialog::InitUARTInfo(): No com port detected.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,416)

Please advice.



Attached Files
.png   Driver_reinstall.png (Size: 10.5 KB / Downloads: 90)
Reply
#12
Right click on one of the MTK Ports>>Properties. And lets see the error msg..
Reply
#13
(09-15-2014, 09:28 AM)Slimzzy Wrote: Right click on one of the MTK Ports>>Properties. And lets see the error msg..
Thanks Slimzzy. The properties of the 'MediaTek PreLoader USB VCOM (Android)' shows that 'This device cannot start. (Code 10)'. In all the MTK Ports, it is same..
Reply
#14
(This post was last modified: 09-15-2014, 12:32 PM by hovatek. )
(09-15-2014, 10:09 AM)Androhelp Wrote: Thanks Slimzzy. The properties of the 'MediaTek PreLoader USB VCOM (Android)' shows that 'This device cannot start. (Code 10)'. In all the MTK Ports, it is same..

A Code 10 error is generated in Device Manager in
one of the following situations:

* Device Manager can't start the device.
* One of the drivers that the device needs does not
start.
* Device Manager has insufficient information to
recognize the error that is bubbled up by the
device driver.

Note In this situation, the Code 10 error can be a
very generic message that indicates some kind
of unspecified driver or device problem.
Need further assistance? Speak with a Hovatek Representative:
Working Hours: Mondays - Saturdays ; 09:00 - 18:00 (GMT +1:00)
Reply
#15
(09-15-2014, 12:31 PM)hovatek Wrote:
(09-15-2014, 10:09 AM)Androhelp Wrote: Thanks Slimzzy. The properties of the 'MediaTek PreLoader USB VCOM (Android)' shows that 'This device cannot start. (Code 10)'. In all the MTK Ports, it is same..

A Code 10 error is generated in Device Manager in
one of the following situations:

* Device Manager can't start the device.
* One of the drivers that the device needs does not
start.
* Device Manager has insufficient information to
recognize the error that is bubbled up by the
device driver.

Note In this situation, the Code 10 error can be a
very generic message that indicates some kind
of unspecified driver or device problem.

Ok noted, but in our given situation,how to address the issue and get the phone in working condition? Can you advice some way forward to test with?

As told, I have already tried the various drivers but system couldn't identify the device..we are stuck there now.
Reply
#16
(09-15-2014, 12:59 PM)Androhelp Wrote: Ok noted, but in our given situation,how to address the issue and get the phone in working condition? Can you advice some way forward to test with?

As told, I have already tried the various drivers but system couldn't identify the device..we are stuck there now.

Read this article on how to fix code 10 error @ http://forum.hovatek.com/thread-596.html . Its most likely an incompatible driver issue.
Need further assistance? Speak with a Hovatek Representative:
Working Hours: Mondays - Saturdays ; 09:00 - 18:00 (GMT +1:00)
Reply
#17
(09-15-2014, 01:38 PM)hovatek Wrote:
(09-15-2014, 12:59 PM)Androhelp Wrote: Ok noted, but in our given situation,how to address the issue and get the phone in working condition? Can you advice some way forward to test with?

As told, I have already tried the various drivers but system couldn't identify the device..we are stuck there now.

Read this article on how to fix code 10 error @ http://forum.hovatek.com/thread-596.html . Its most likely an incompatible driver issue.

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 a 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 got the Stock Rom from xda site and downloaded for that phone model only.. FYI.
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.

Thanks.
Reply
#18
(09-16-2014, 06:43 AM)Androhelp Wrote:
(09-15-2014, 01:38 PM)hovatek Wrote:
(09-15-2014, 12:59 PM)Androhelp Wrote: Ok noted, but in our given situation,how to address the issue and get the phone in working condition? Can you advice some way forward to test with?

As told, I have already tried the various drivers but system couldn't identify the device..we are stuck there now.

Read this article on how to fix code 10 error @ http://forum.hovatek.com/thread-596.html . Its most likely an incompatible driver issue.

I have managed to get the phone recognized by PC usb now.
HOW DID U GO ABT GETTING IT TO COMMUNICATE? I HAVE SAME PROBLEM ON WINDOWS 7 -32bit. . BEEN TRYING TO GET THIS STUBBORN TECNO M7 UNBRICKED AND AM STUCK AT TRYING TO MAKE IT COMMUNICATE WITH PC..
Reply
#19
(09-16-2014, 09:36 AM)Slimzzy Wrote:
(09-16-2014, 06:43 AM)Androhelp Wrote:
(09-15-2014, 01:38 PM)hovatek Wrote:
(09-15-2014, 12:59 PM)Androhelp Wrote: Ok noted, but in our given situation,how to address the issue and get the phone in working condition? Can you advice some way forward to test with?

As told, I have already tried the various drivers but system couldn't identify the device..we are stuck there now.

Read this article on how to fix code 10 error @ http://forum.hovatek.com/thread-596.html . Its most likely an incompatible driver issue.

I have managed to get the phone recognized by PC usb now.
HOW DID U GO ABT GETTING IT TO COMMUNICATE? I HAVE SAME PROBLEM ON WINDOWS 7 -32bit. . BEEN TRYING TO GET THIS STUBBORN TECNO M7 UNBRICKED AND AM STUCK AT TRYING TO MAKE IT COMMUNICATE WITH PC..

yesterday, I was trying many things to get my phone alive.. that time I inserted it another PC (fresh) after doing some system restoration etc in windows XP... when inserted the phone without battery, it suddenly got identified. But, my main problem is still not yet resolved, tried all permutation and combination of driver installation, computer restart etc.. don't know what is missing here.

The Flashing ROM may be a 10-15 minutes job, but it took almost 3 days to just got the phone identified.. what a situation..
Reply
#20
(09-16-2014, 10:50 AM)Androhelp Wrote: yesterday, I was trying many things to get my phone alive.. that time I inserted it another PC (fresh) after doing some system restoration etc in windows XP... when inserted the phone without battery, it suddenly got identified. But, my main problem is still not yet resolved, tried all permutation and combination of driver installation, computer restart etc.. don't know what is missing here.

The Flashing ROM may be a 10-15 minutes job, but it took almost 3 days to just got the phone identified.. what a situation..

The error 4032 you're getting means that SP flash believes that the ROM you downloaded is not meant for your phone, but this is often corrected by formatting the phone than using firmware upgrade or download (preloader.bin alone first before other files) . You said it gives you the same error during format and that is really weird. Please, confirm this and also, lets know what version(s) of Sp flash tool you used
Need further assistance? Speak with a Hovatek Representative:
Working Hours: Mondays - Saturdays ; 09:00 - 18:00 (GMT +1:00)
Reply










Users browsing this thread:
1 Guest(s)