Hello,
after a few days I successfully unrooted & unbricked my LG-D605. I read a lot of articles and asked lot of questions and tried a lot of unsuccessfull ways. Here is my successfull solution.
My PC configuration
HP 650 (2,4 GHZ, 4 GB RAM, 500 GB drive)
OS openSUSE 13.2 64bit - software.opensuse.org
Oracle Virtualbox from oracle official repository - www.virtualbox.org
Downloaded Windows 7 home premium EN 32bit (very important - it was unsuccessfull with xp / 8.1 and czech localization xp / 7 / 8.1) - Windows 7 32-bit Home Premium x86 English on techverse.net
LG-D605 preparation - HARD RESET (form off-state Vol- & Power, when prompted Power, when prompted Power), next off
Needed downloads - tested
LG mobile drivers - attachment
LG Flash tool - attachment
ROM in .bin and LGUP_L9II.dll (extracted from kdz file) - file in google drive
Install process
Unpack and install LG mobile drivers
Unpack and install LG Flash Tool without run it
Overwrite file c:\\lg\lgfllashtool\megalock.dll with file megalock.dll in archive lg-flash-tool.zip
Connect phone in download mode (remove battery - connect phone to usb -> hold Vol+ -> insert battery)
After phone detection and installation in PC run Windows Device Manager and set LG device to port COM41
Run LG Flash Tool
Mark checkbox "Manual" and set in Model Config path to LGUP_L9II.dll and *.tot file (archive extracted kdz)
Click on OK
In PortSetting window leave marked only port 1
Click on Right Arrow
If you see in small window Port 1 "Ready", disconnect phone on 5sec and reconnect (if you on virtualbox, remember on reactivation usb port)
Done
hi, other flash metod is turn phone in download mode, and flash the kdz file with KDZ_FW_UPD.exe.
also downgrade or upgrade firmware very easy, open the software, select tipe 3gqtc, mode diag, open te kdz file, conect the phone in download mode and launch software update.
Note: in windows device manager disable lg modem device.
no problem in win xp.
sorry for my english.
I tried this metod but it gets stuck at 54%, jumps to 100 and it gives me a download failed error. What could it be?
Thanks man! It worked for me.
I had a slightly different configuration though...
Host OS: Fedora 21 64bit
Oracle VirtualBox 5.0
Guest OS: Windows 7 Professional EN 64bit with corresponding VirtualBox Additions installed
Installation of LG drivers and Flash Tool went well. But after connecting phone in Download Mode it took long time time install drivers which ultimately ended with fail - "drivers were not successfully installed" in yellow bubble. But the phone was shown in device manager so I continued.
Another thing is that I do not have enabled reactivation on usb port so I quickly pluged it in manually after phone rebooted. It worked too.
Only bad thing is that now I have Android 4.1 and have to upgrade back to 4.4. But this is much better situation than bricked phone so thanks again.
When I click right arrow, nothing is happening
Related
Hi guys, your forum is set so that i cant make a new account to reply to important posts in the developer section so here is my reply for http://forum.xda-developers.com/showpost.php?p=16702026&postcount=204
DarkAgent said:
Originally Posted by Ruwin
Yes, i am using XP 32bits. My guess it is a connection problem. Any other phone, including other p500 connects smoothly with the pc. This one connects but not all drivers match. I can connect the phone in Emergency Mode to kdz only if i remove the sd, sim and battery.
the error is: "upgrade error WParam : 100 LParam : 502"
By the way, the reason i need to flash the original ROM is to try and get dir of the start-up Emergency Mode error. Meaning, if i shut down the phone, and turn it on it gets intro Emergency Mode. I have to pull the battery out for like 15 - 20 minutes to boot again normal. You can imagine this is annoyng. Once booting, the phone runs perfect...
Click to expand...
Click to collapse
Maybe you have some opinion on this one?
Thanks!
Did you ever figure it out? I am having the exact same issue (phone goes to Emergency Mode) and the exact same error when trying to flash with Kdz.
Click to expand...
Click to collapse
I had the same
Code:
upgrade error WParam : 100 LParam : 502
on a Windows 7x64 fresh install I think its caused by a bad ROM flash which happens to clash with drivers.
KDZ->Read Phone Info always gave device not known errors then crashed.
I chose to use another PC to make sure driver issues were gone (PPL say that win7 works but I changed to a Vista laptop for a better result) Here is what i did:
**Use a Windows XP 32-bit PC for best results**
1. Use the LG Support tool Run as administrator to DL latest drivers
-
2. Reinstall 3 drivers in order from C:\LGP500\USB_Driver and C:\LGP500\USB_Driver\LG_SmartPhone.
-a. LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.1.exe (version will vary)
-b. LGWindowsMobile_USBDriver_WHQL_ML_Ver_1.0.exe
-c. LGSmartPhone_ModemlinkDUNDrive_WHQL_ML_Ver_1.0.exe
Restart if required
-
3. Download crecked's Original LG Firmware.exe and get your .KDZ
-
4. Download Software update KDZ and install msxml.msi as administrator
-
5. Remove Sim, MicroSD, and battery.
-
6. Connect the phone and boot it in emergency mode (still no battery)
-
7. Goto device manager and disable Modems->AndroidModem
*MUST RESTART PC HERE!*
-
8. Check ALL modems are disabled in task manager and then set KDZ_FW_UPD.exe to always run in compatibility mode for Windows XP SP2
-
9. Ensure Phone is in yellow emergency mode and no battery... (USB connect noise as soon as plugged in)
-a. Run KDZ_FW_UPD.exe as administrator (MUST be XP SP2 compatible) and set type: 3GQCT and PhoneMode: EMERGENCY.
-b. Select your previously downloaded KDZ file from using the program in step 3, and Launch!
-
10. If finished then wait 2-3mins and turn on phone (if not already booting), Insert battery, and close KDZ. Initial startup may take 10 mins
**Again, Win7x64 did not work for me (even in XPSP2 compatibility mode which is a MUST) so I used Vista 32-bit but XP 32-bit is preferable**
Thanks guys, this forum was amazingly helpful and a huge learning experience for me, mods can feel free to delete this post, or even move it to where it should be I just wanted user DarkAgent, and RUwin to know, and to have the result searchable so others can receive the same amazing tips I had!
Hicsy said:
Hi guys, your forum is set so that i cant make a new account to reply to important posts in the developer section so here is my reply for http://forum.xda-developers.com/showpost.php?p=16702026&postcount=204
I had the same
Code:
upgrade error WParam : 100 LParam : 502
on a Windows 7x64 fresh install I think its caused by a bad ROM flash which happens to clash with drivers.
KDZ->Read Phone Info always gave device not known errors then crashed.
I chose to use another PC to make sure driver issues were gone (PPL say that win7 works but I changed to a Vista laptop for a better result) Here is what i did:
**Use a Windows XP 32-bit PC for best results**
1. Use the LG Support tool Run as administrator to DL latest drivers
-
2. Reinstall 3 drivers in order from C:\LGP500\USB_Driver and C:\LGP500\USB_Driver\LG_SmartPhone.
-a. LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.1.exe (version will vary)
-b. LGWindowsMobile_USBDriver_WHQL_ML_Ver_1.0.exe
-c. LGSmartPhone_ModemlinkDUNDrive_WHQL_ML_Ver_1.0.exe
Restart if required
-
3. Download crecked's Original LG Firmware.exe and get your .KDZ
-
4. Download Software update KDZ and install msxml.msi as administrator
-
5. Remove Sim, MicroSD, and battery.
-
6. Connect the phone and boot it in emergency mode (still no battery)
-
7. Goto device manager and disable Modems->AndroidModem
*MUST RESTART PC HERE!*
-
8. Check ALL modems are disabled in task manager and then set KDZ_FW_UPD.exe to always run in compatibility mode for Windows XP SP2
-
9. Ensure Phone is in yellow emergency mode and no battery... (USB connect noise as soon as plugged in)
-a. Run KDZ_FW_UPD.exe as administrator (MUST be XP SP2 compatible) and set type: 3GQCT and PhoneMode: EMERGENCY.
-b. Select your previously downloaded KDZ file from using the program in step 3, and Launch!
-
10. If finished then wait 2-3mins and turn on phone (if not already booting), Insert battery, and close KDZ. Initial startup may take 10 mins
**Again, Win7x64 did not work for me (even in XPSP2 compatibility mode which is a MUST) so I used Vista 32-bit but XP 32-bit is preferable**
Thanks guys, this forum was amazingly helpful and a huge learning experience for me, mods can feel free to delete this post, or even move it to where it should be I just wanted user DarkAgent, and RUwin to know, and to have the result searchable so others can receive the same amazing tips I had!
Click to expand...
Click to collapse
I hear a humor that when the phone is in emergency mode and it's conected to pc and the pc is not recognizes it you have to shake you phone to get it working... see if it is true...
Having searched for a long time for a solution in using Odin under Mac OSX environment, I've finally found a solution! A lot of people say can't , but here it is...
1. Load up VirtualBox's Windows session
2. Download the Samsung USB drivers in Windows from the attachment and extract in a folder.
3. Closes the Windows session
4. Go to the USB setting of the Windows session
3. Reboot SGS2 in download mode
4. Plug in the phone to USB
5. Add a new USB filter <SAMSUNG Gadget Serial [021B]>
- Note: There could be a error box showing up, ignore it
6. Unplug USB
7. Load up Windows session again
8. Once loaded, plug in the phone again and wait for new hardware prompt
9. Add the required drivers from the downloaded file
10. Unplug USB
11. Load Odin
After Odin is loaded inside the Windows session and the phone is plugged in, the COM box will turn yellow and you can flash whatever you want!
My setup is like this:
Mac OS: 10.7.2 Lion
Win OS: Win XP SP3 32 bit
VirtualBox: 4.1.6 (with USB extension pack)
For those who are using difference OS versions, please report the results and help others! I'll try to generate a list from the feedback.
Thanks, I've been looking for a way to do this forever.
Working on my setup:
OSX (Host) - 10.7.2
Win (Guest) - XP SP3 32bit
VBox - 4.1.8 (USB extention pack)
Virtualbox Odin crash
I actually managed to work out who to get as far as getting Odin to recognise my phone (after ages of fiddling, i found the usb filters in virtual box).
HOWEVER, when I START odin to flash a rom, it reboots my VM. Anyone got any ideas what might cause this?
FYI:
I am trying to flash a previous rom version onto my Galaxy Note (LA4 back down to KKA [United Kingdom]) so that I can run the one-click CF-Root.
NB:
Running OSX Lion
Virtualbox version 4.1.8
Windows XP with service pack 3
davidgood89 said:
I actually managed to work out who to get as far as getting Odin to recognise my phone (after ages of fiddling, i found the usb filters in virtual box).
HOWEVER, when I START odin to flash a rom, it reboots my VM. Anyone got any ideas what might cause this?
FYI:
I am trying to flash a previous rom version onto my Galaxy Note (LA4 back down to KKA [United Kingdom]) so that I can run the one-click CF-Root.
NB:
Running OSX Lion
Virtualbox version 4.1.8
Windows XP with service pack 3
Click to expand...
Click to collapse
check the "enable usb 2.0 (ehci) controller" into machine configuration. that solves the OS reboot for me.
May have to try this cause it sure isn't working with VMWare
You legend
I have been looking for the samsung device drivers for ages. Working great with virtual box. Good bye boot camp, you were only there for odin these days anyway! Thank you.
Thank you !!!
Thank you very much !!!
Thanks!
dj_ghosie = gentleman + scholar
wow. awesome find here.
this worked for me as well. however, I used the drivers and odin and recovery files found here in the 2nd post:
http://forum.xda-developers.com/showthread.php?t=1275031
(drivers http://devphone.org/files/gtab7/Sprint_P100_Samsung_GALAXY_Tab_USB_Drivers.msi)
OSX 10.8.2
WindowsXP SP2
VirtualBox 4.2.4
THANK YOU SO MUCH!!!
OKAY, very interested in this.
I have the Galaxy s3. Would I download this..
http://download.virtualbox.org/virtualbox/4.2.6/VirtualBox-4.2.6-82870-OSX.dmg
and then follow the directions listed in OP?
Want to eventually do this...
http://forum.xda-developers.com/showthread.php?t=2046439
Good stuff!!!
Works in my setup:
Mac OS: 10.8.3
Win OS: Win XP SP3 32 bit
VirtualBox: 4.2.10 (with extension pack)
Stuck at last step when I boot into Odin
Hi,
Thanks for the awesome guide. I'm on a Mac (10.7.5) using VirtualBox with Win7. I installed all the drives and Odin and VirtualBox has no trouble picking up my phone (GS3) when I plug in in BEFORE going to Odin mode.
Then I follow the last set of instructions (unplug USB, boot into Odin, plug phone back in) and then VirtualBox won't find the phone. Any ideas? I've Googled all over the place and haven't found anyone with this exact issue yet.
Wrong forum. Post in S3 Q&A/similar.
Experience with os Mavericks and windows xp virtualized in vmware
dj_ghosie said:
Having searched for a long time for a solution in using Odin under Mac OSX environment, I've finally found a solution! A lot of people say can't , but here it is...
1. Load up VirtualBox's Windows session
2. Download the Samsung USB drivers in Windows from the attachment and extract in a folder.
3. Closes the Windows session
4. Go to the USB setting of the Windows session
3. Reboot SGS2 in download mode
4. Plug in the phone to USB
5. Add a new USB filter <SAMSUNG Gadget Serial [021B]>
- Note: There could be a error box showing up, ignore it
6. Unplug USB
7. Load up Windows session again
8. Once loaded, plug in the phone again and wait for new hardware prompt
9. Add the required drivers from the downloaded file
10. Unplug USB
11. Load Odin
After Odin is loaded inside the Windows session and the phone is plugged in, the COM box will turn yellow and you can flash whatever you want!
My setup is like this:
Mac OS: 10.7.2 Lion
Win OS: Win XP SP3 32 bit
VirtualBox: 4.1.6 (with USB extension pack)
For those who are using difference OS versions, please report the results and help others! I'll try to generate a list from the feedback.
Click to expand...
Click to collapse
just my experience:
Mac os Mavericks, vmware, windows xp virtualized in vmware, last version of samsung kies installed inside the windows xp virtualized machine. install Odin3 3.10, put your phone in download mode, connect the usb cable and when operating system ask for connection with osx or vmware obviosly choose vmware, Odin3 recognize immediatly the phone and you can update everything you want. I have updated my bootloader e my CMW and after installed the rom "android revolution hd" without any problem
Method still works. macOS Big Sur host, Windows 10 guest.
You need to make sure you have VirtualBox Extension Pack installed, otherwise in VB USB settings you'll only see USB 1.1 controller.
May need to create different filters for connecting your phone in normal mode vs download/adb/whatever.
Also I didn't need any Samsung drivers (for my S10e Exynos). Everything "just worked".
Hi Everyone,
I know there are stupid people out there like myself that bought a crapy chineese tablet with model msm7227 shown that would like to know how to root the phone. Installing the Gingerbreak apk file and running it seems to do the trick.
I tried to take it a step further and upgrade the android version from 2.2.2 to 2.3.3 following instructions from a russian site that I translated.
Russian site link:
ublaze.ru/forum/ftopic1158.html
I translated the instructions in the website below. Refer to pdf attachment for instruction and pics:
Unfortunately I only managed to go as far as Step 3 G. Click Start to update ARM9.
Your tablet will automatically reboot after the upgrade.
For me after I click start the status changes indicating that it is Changing the Phone to Download Mode
It then switches off the unit and loses the com connection to the phone and the status changes to "Attempting to run Flash Programmer"
It fails then with the status "Software Download Aborted" Error "Could Not Communicate with Flash Programmer". I try an restablish the connection during the status "Attempting to run Flash Programmer" but it makes no difference.
So I have pretty much left it there. If any one else is game to give it a go and have better luck good luck. My unit still works after I reset it but its still on Android 2.2.2.
INSTRUCTIONS
Характеристики QUALCOMM MSM7227 FFA 3g
Код: Выделить всё
QUALCOMM MSM7227-1 Tablet PC with Mobile Phone function
Android 2.3 OS
512MB RAM +4GB Flash Memory
7 inch capacitive multi-touch screen
Built in 3G module and WiFi and bluetoothBuilt in GPS navigation
Built in 2.0MP/0.3 CMOS dual cameras
Support phone call and flash10.1 playing
ID устройства:
USB\Vid_05c6&Pid_9018&Rev_0226&MI_00
USB\Vid_05c6&Pid_9018&Rev_0226&MI_01
USB\Vid_05c6&Pid_9018&Rev_0226&MI_02
The firmware consists of 4 steps.
Step 1. Zhelateono have a PC running Windows XP, but I probyval and Windows 7 32-bit also works.
Step 2. Installing the USB driver
рис. 1
If the popup window does not appear automatically, go to the Device Manager> Other Devices
and click the right mouse button on the label Qualcomm HSUSB Device and select> Update Driver
pointing the way to the drivers for each Qualcomm HSUSB Device (see Fig. 2) as follows (see Fig. 1)
рис. 2
Step 3. update ARM9
A. Turn the tablet and connect it to your computer.
B. Go to Device Manager and check that, if the operating system your computer has defined the tablet (see Figure 3.)
рис. 3
C. Installing the program QPST.
рис. 4
D. Click Start, and then click the QPST Configuration. Add all the ports that are able to find (see Fig. 5)
рис. 5
Navigate to the Software Download tab and remove the check mark from C Auto Backup/Restore
рис. 6
рис. 7
Click Start clients and select Software Download, and then click Multi-image.
Click Browse and specify the correct path to the image (image).
Код: Выделить всё
...\Reflash Software\ARM9\image
Click Advanced, select the AMSS Apps Boot Ldr Hearder and AMMS Apps Boot Loader, then click OK
рис. 8
The tab Multi-image, uncheck Auto Backup / Restore
рис. 9
G. Click Start to update ARM9.
Your tablet will automatically reboot after the upgrade.
Step 4. update ARM11
A. Make sure your tablet is connected to your computer via USB-cable.
B. Open ... \ Reflash Software \ Android_Download_tools \ Arm11 V1.7_20110418 \ Android_download.exe
C. Click Connect and verify that the displayed fastboot device
D. Press the volume (Volume) and the power button, and then click the Reset button (Reset)
E. Hold down the volume (Volume) and the (what exactly, the instructions are not written - most likely the trigger) and then, in the program, click Connect again.
And then start flashing.
F. Click Run and wait for as long as see the word Done!!!
рис. 10
G. In this update is completed.
Note. If your tablet does not flash, as I have, in some cases, do the following:
1. Take the sd card and dump the sd card to the root of the archive here: update.zip
2. Insert the sd card into the tablet.
3. Hold the power button and press vol -.
4. Without releasing the two buttons we press on reset clip (located just below the buttons vol -)
Next tablet should enter into recovery mode, that's how it looks:
5. Next, we need to press the Home button (Home)
6. C Use the "vol +" and "Vol -" go to the inscription:
code: Выделить всё
apply sdcard:update.zip
and press the touch button with the four squares (just below the button home)
7. Upgrade process will start. At the end of reset the unit.
Download the firmware for Ipad QUALCOMM MSM7227 FFA 3g
Скачать прошивку для Ipad QUALCOMM MSM7227 FFA 3g
Use this tool to root it : http://www.only4download.com/2012/05/download-superoneclick-android-software.html
Don't forget the THANKS button
You Biscuit!!!!
Thanks guys for helping me to flash my device!!! Running 2.3 with full marketplace. WOO HOO!!!
Ok I had managed to root it before finding your post. ( I think it was UnversalAndroot if memory serves me right - tried so many! )
Used Chrome to translate the original Russian page to English. The USB drivers and the quickboot drivers are all in the file listed on that site. (2.3 software ) I used a Windows XP workstation to connect the device and load the drivers.
To get the device into fastboot:
turn on while holding the Volume UP + button. You should see the android robot.
Connect to PC and install the ADB driver.
Run the Android_download.exe and let it do it's magic. The device will reboot twice and will show a new logo on rebooting. ( at this point I installed the standard USB drivers )
The device will default to Chinese language. Find the settings icon ( blue rings on black ) and look for the icon with an "A" on it.
The network does not work - I assume its because of my region ( South Africa GSM 900 / 1800 / 2100 ) and something is missing in the drivers. It no longer detects a SIM or network.
At least I have a device that resembles a proper Android device now! Time will tell if it's any more stable than the brickware it came with.
Please don't ask me too many technical questions - I'm not a pro by any means!
Thanks
Finally
Finally found the time to get around to trying the flashing to Android 2.3.3 again.
It all worked great this time round. The issue I was having with installing the ARM 9 update was that everytime it changed the unit to download mode and rebooted it, the COM port would change and lose connecitvity after the reboot. But once I used the browse button in the QPST Configuration application and changed the port to match the new port allocated after the reboot it successfuly transfered the software across without the error.
Its so great now that the unit has Android 2.3.3 as now all the following things have been fixed and verified working
1) 3G data works properly now with Telstra
2) Phone and messaging works with Telsta
3) I dont get face book error in the news read section
Theres still a few android apps that are not compatible with the device like, Adobe Flash player but there are suitable alternatives.
But now its a nice workable unit. Very Happy :>
Some error has been solved
saintlypaul said:
Finally found the time to get around to trying the flashing to Android 2.3.3 again.
It all worked great this time round. The issue I was having with installing the ARM 9 update was that everytime it changed the unit to download mode and rebooted it, the COM port would change and lose connecitvity after the reboot. But once I used the browse button in the QPST Configuration application and changed the port to match the new port allocated after the reboot it successfuly transfered the software across without the error.
Its so great now that the unit has Android 2.3.3 as now all the following things have been fixed and verified working
1) 3G data works properly now with Telstra
2) Phone and messaging works with Telsta
3) I dont get face book error in the news read section
Theres still a few android apps that are not compatible with the device like, Adobe Flash player but there are suitable alternatives.
But now its a nice workable unit. Very Happy :>
Click to expand...
Click to collapse
I have solved some error when update rom for it. I attached it from file word
HELP ERROR update ARM9
Hi, I have a problem when star the process appear in red NAK: Invalid Address
I have read the manual 6 times and nothing, please how I can fix this error
Same Error
Hi
I am getting the same error as yours.
Where you able to move ahead an upgrade the tablet to 2.3 ?
Hi, frist post here.
I'm from Venezyela, sorry for my english first to all.
My problem is that: I want the ClockRecoveryMod for my Samsung Galaxy 550, but I can with Odin, because my PC (Windows 8.1) dont run the Drivers on the "Downloading Mode", The Kies recognizes the phone and I made the Root with SuperOneClick, but with DonloadMode the PC just say me "Windows dont recognizes" so, Odin dont recognizes it too.
If someone can help me or maybe know another way to install a RecoveryMod to the Phone, I will be grateful
Waiting for your help, bye bye.
Google "Samsung drivers", download them and then right-click the (driver's) installer and go to properties -> compability and select windows 7. Finally, install them.
That should do it.
Sent from my GT-I5500 [CM11]
AdriaMRios,
This is the link to download for drivers.
http://d-h.st/iPk
As you use windows 8.1 then you will have to extract the file you download from the link above and then right click on the .exe file and go to 'properties', in that go to 'compatibility' and in that choose your operating system as "WINDOWS 7" and check the option below 'always run as administrator' and there you go. Double click on .exe file and follow steps. Install drivers. No need to restart the pc also. (if your phone also do not detect after installing these drivers only then restart). These are the most stable and perfect drivers I have found.
If these drivers Don't work...! Then...read below.
Windows 8.1 has a bug in the Microsoft USB stack affecting many devices using Qualcomm chipsets. The bug prevents the OS from being able to enumerate any of these devices in download mode (fastboot, Odin, Sony flashtool - they're all buggy).
You can downgrade your PC to Windows 8.0, flash on another PC, or wait for Microsoft to release the fix. See here:
http://blogs.msdn.com/b/usbcoreblog...ode-43.aspx?CommentPosted=true#commentmessage
Don't spam their comments section. They have the information needed to fix the Galaxy 5 already, so just be patient.
Hello,
*I have a problem with accessing phone PreLoader on Virtual COM port.*
I have NO PROBLEM with ADB driver and access. I can also access phone as a Device in Windows.
*But I want to create backup of my phone ROM.*
I want to read the ROM with SP Flash Tool to make backup.
(I cannot post links, so see full links in .txt file attached)
Phone: Alcatel IDOL One Touch Mini
Phone model code: 6012X
Full phone specs: gsmarena.com/alcatel_one_touch_idol_mini-5669.php
Chipset: Mediatek 6572
USB driver link page: developer.android.com/sdk/win-usb.html
Driver direct link: dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
OS: Windows 7, 64 bit
What I do:
------------
- I turn phone off. (Cannot remove battery - phone can not be opened=battery is not removaable)
- Connect to Windows
- Windows popup message for a device connected !
- Browse... choose driver for Win7,64bit,..... (only first time Windows wants driver)
- In Device Manager this device appear for a second, and then disappears: [PreLoader USB VCOM Port (COM_X)]
=== Result: Phone is not visible and cannot be accessed/shown in SP Flash Tool. Tried in versions 3.1224.01 (older)
and 3.1352.01 (newer interface).
What I tried to troubleshoot:
---------------------------------
- Used USBDeview.exe (64 bit), runned as administrator. Performed manual Uninstall for all old virtual COM ports.
- Tried another USB cable.
- Tried another USB port; Tried another USB port on another insernal USB hub; Tried on extranal USB hub.
- Tried another drivers, which I have found on fourms.
- Started Device Manager as admin, show hidden devices. Now I can see m phone as a light gray device.
Every time I plug phone, Windows creates a new VCOM port. I have to uninstall them manually with UsbDeview.
When I click properties on VCOM with/without currently phone attached windows says:
"Device status: Currently this hardware device is not connected to the computer. (Code 45)".
See screenshot: postimg.org/image/o3h86dbzt/
- Googled many times for Code 45 but cannot solve this problem.
- Obviously windows can see MediaTek chipset at least for a while. Tried to connect on turned off phone. Or with
phone started in Recovery mode (Meta mode?) - Power+Volume up. No luck here too.
=== Result: Failed to succeed. Nothing of above can help.
Please, help!