So i feel pretty stupid as i have spent so long trying to work out the problem and i have no been successful... without even a glimmer of hope
So i have read this article and followed the last users advice and downloaded drivers for a phone which is not my model.
Anyway the problem:
When i plug my phone into the machine whilst booted normally the only thing that comes up in the device manager is: USBC - USB Mass Storage Device
I get nothing whilst in fastboot
Things i have:
I have installed LGMobile update manager
LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.1
Android SDK
Windows 7 64-bit
My Mobile has:
1.6 standard rom
Device manager:
I have been told to follow these but i have no such things in my device manager (device name or anything in 'other') it is just completely blank.
Now any tips? i really hope somebody has had a similar problem and i am being a bit slow. I have spent the last 3 days not working and just trying to get this thing to detect itself in my computer... grr silly windows 7
[TUTORIAL] How to Flash an Android ROM
MY ADVICE, UNISTALL THE WHOLE THING, AND FOLLOW THIS:
THIS TUTORIAL BELONGS TO CHKRLY FROM TARINGA!, i just added and quit some parts, translated and attached files...
WARNING: Any of these methods can brick your phone, im not responsible if that happens. READ ALL THE TUTORIAL FIRST. If your phone gets unresponsive DO NOT PANIC! we are here for HELP!
FIRST PART
(Flash from 1.6 to 2.1 with fastboot)
In this part we are going to flash an european ROM that comes with fastboot with the purpose of flash other ROMs that needs fastboot later...
1. Create a folder, download the KDZ Updater , the European ROM and the drivers for our LG GT540 and unzip them all in the same folder. Install the drivers:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WINDOWS7 users: Right clic>> Run as administrator.
Also is very important you install the drivers inside the LG_SmartPhone folder:
2. On to the phone go to: SETTINGS >> APPLICATIONS >> DEVELOPMENT and activate the mode USB debugging , also check out this:
SETTINGS >> SD CARD AND PHONE MEMORY >> EXTERNAL ONLY MEMORY (not SECRET_, remove if), then plug you phone to the computer
3. Close all applications you do not need on the computer & deactivate your antivirus/firewall and run the KDZ_FW_UPD.exe (Windows 7 users: right clic>>start as Administrator)
4. Once in the program select from the TYPE list the 3GQTC option and then clic in the folder icon and select the European ROM(KDZ file) from the folder where you unziped, then press the button Launch Software Update
NOTE: It is important mention that while in the process dot not interrupt the program, unplug the phone or shutdown the computer
*If it stops in any of the processes and doesn't finish (processes doesn't get stuck for long), then unplug your phone, close the program, open it again plug your phone, and run it again.
*If that doesn't help eather, remove the battery, close the program, plug your phone to the computer, start the program and run the process again.
NOTE: various problems in the following procedure to update can occur if non of the above tips helped then try this:
Go to Device Manager in your computer>> right click on the LG Modem Android>> DISABLE / Modem>> LGE Virtual Modem>> DISABLE and then try FLASHING AGAIN
THE WHOLE PROCESS SHOULD TAKE 10 MINUTES
Once the program has loaded the ROM to the phone it will appear a leyend FINISHED, after that the phone will reboot and boot android 2.1 with fastboot.
SECOND PART
(Flash from stock 2.1+fastboot to custom 2.1/2.2/2.3...)
1. Download the following files:
- Google SDK tools, then run the .exe, install in C:\ drive and rename the folder to sdk-android.
- Drivers for your computer recognize the phone in fastboot mode. Unzip and put the files of folder in C:\sdk-android
INSTALL WITH YOUR PHONE PLUGGED:
... then next and it will install the drivers.
- Clockwork recovery (latest version) and place it in C:\sdk-android
- Download the ROM you want to flash for FASTBOOT NOT RECOVERY, UNZIP and place the .IMG FILES in C:\sdk-android
2. Shutdown your phone and Start it in fastboot mode (CAMERA+POWER BUTTON) hold the camera for 1 sec then add the power button . Wait few second you will see LG's logo then the screen will turn dark, CLEAN DARK SCREEN, just in that moment you are in FASTBOOT mode.
3. Plug your phone to the computer and open a CMD terminal and type:
cd C:\sdk-android
4. Once inside the folder type ONE by ONE:
fastboot flash recovery recovery_clockwork_3.0.2.4_swift.img
fastboot -w
fastboot erase system
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot -w
fastboot reboot
THAT MY FRIEND IS A CLEAN INSTALL...
5. Once is rebooting fast login to recovery pressing POWER+HOME. Inside recovery select wipe data/factoryreset for reset the phone. Then select reboot, and that's it YOUR DONE!
6. Set your phone as you like install all your apps and once you done reboot into recovery and go to backup & restore>> backup for create a backup of your entire phone.
One more thing to add.
Dont forget to backup the rom after installing the clockwork recovery
Sent from my GT540 using XDA App
Go into Settings and choose SDCard & Phone Storage, Untick "Mass Storage Only" This fixed my problem with ADB not working when I first got mine. Also,you don't need to reflash your ROM to fix driver problems.
Hope it helps,
Jack
lavero.burgos said:
MY ADVICE, UNISTALL THE WHOLE THING, AND FOLLOW THIS:
THIS TUTORIAL BELONGS TO CHKRLY FROM TARINGA!, i just added and quit some parts, translated and attached files...
FIRST PART
(Flash from 1.6 to 2.1 with fastboot)
In this part we are going to flash an european ROM that comes with fastboot with the purpose of flash other ROMs that needs fastboot later...
1. Create a folder, download the KDZ Updater , the European ROM and the drivers for our LG GT540 and unzip them all in the same folder. Install the drivers
2. In to the phone go to: SETTINGS >> APPLICATIONS >> DEVELOPMENT and activate the mode USB debugging , then plug you phone to the computer
3. Deactivate your antivirus/firewall and run the KDZ_FW_UPD.exe (Windows 7 users: right clic>>start as Administrator)
4. Once in the program select from the TYPE list the 3GQTC option and then clic in the folder icon and select the European ROM(KDZ file) from the folder where you unziped, then press the button Launch Software Update
NOTE: It is important mention that while in the process dot not interrupt the program, unplug the phone or shutdown the computer
If it stops in any of the processes and doesn't finish (processes doesn't get stuck for long), then unplug your phone, close the program, open it again plug your phone, and run it again.
If that doesn't help eather, remove the battery, close the program, plug your phone to the computer, start the program and run the process again.
THE WHOLE PROCESS SHOULD TAKE 10 MINUTES
Once the program has loaded the ROM to the phone it will appear a leyend FINISHED, after that the phone will reboot and boot android 2.1 with fastboot.
SECOND PART
(Flash from stock 2.1+fastboot to custom 2.1/2.2/2.3...)
1. Download the following files:
- Google SDK tools, then run the .exe, install in C:\ drive and rename the folder to sdk-android.
- Drivers for your computer recognize the phone in fastboot mode. Unzip and put the files of folder in C:\sdk-android
INSTALL WITH YOUR PHONE PLUGGED:
... then next and it will install the drivers.
- Clockwork recovery (latest version) and place it in C:\sdk-android
- The ROM you want to flash and place it in C:\sdk-android
2. Shutdown and Start the phone in fastboot mode (CAMERA+POWER BUTTON) hold the camera for 1 sec then add the power button . Wait few second you will see LG's logo then the screen will turn dark, CLEAN DARK SCREEN, just in that moment you are in FASTBOOT mode.
3. Plug your phone to the computer and open a CMD terminal and type:
cd C:\sdk-android
4. Once inside the folder type ONE by ONE:
fastboot flash recovery recovery_clockwork_3.0.2.4_swift.img
fastboot -w
fastboot erase system
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot -w
fastboot reboot
THAT MY FRIEND IS A CLEAN INSTALL...
5. Once is rebooting fast login to recovery pressing POWER+HOME. Inside recovery select wipe data/factoryreset for reset the phone. Then select reboot, and that's it YOUR DONE!
Click to expand...
Click to collapse
He can't reflash the rom because his PC wont detect the phone.
cheers for the replies dude yup jack you are right comp won't detect it. Still uninstalling everything and disabling everything did get me a step closer i feel.
I have attached the problems i seem to be getting now.
[update]
So it appears to be working now... what did i do to get it showing up? Uninstalled everything and just installed one driver: LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0
and then i think the key difference and for what reason this works i am not sure but turning the phone off (as well as having usb debugging on and turning off sd storage) and plugging it into the pc from an off state!
O yes and i uninstalled the android SDK as well.
so like in the last post i said things were getting better i do believe they are here is where i get stuck each time now
Step Complete: DLOAD change
I have attached both my log file and a print screen of my device manager... umm just so you guys know thanks for helping out again
Code:
[21:40:22:051] : =============================================
[21:40:22:051] : Log is started on 10.04.2011, at 21:40:22:051,
executable: C:\Users\Hutber\My Phone\gt540\KDZ\KDZ_FW_UPD.exe (ProcID: 0x00001c18),
compile time : Sep 8 2010 17:19:53
[21:40:22:052] : Version :
[21:40:22:053] : strFilename1 = eur
[21:40:22:055] : m_DlMode = 4, m_strBinaryPath = C:\ProgramData\LGMOBILEAX\Phone\europen+fastboot.dz, m_nSelectedImages= 70787108
[21:40:28:035] : Start Web Downloading
[21:40:28:035] : Get Usb Port
[21:40:28:039] : rsi.strFriendlyName=Communications Port (COM1)
[21:40:28:039] : Remove Communications Port (COM1)
[21:40:28:039] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM4)
[21:40:28:040] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[21:40:28:040] : rsi.strFriendlyName=LGE Android Platform USB GPS NMEA Port (COM5)
[21:40:28:040] : Remove LGE Android Platform USB GPS NMEA Port (COM5)
[21:40:28:040] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 1 - COM4
[21:40:28:040] : Port = COM4
[21:40:28:040] : Clear
[21:40:28:040] : Clear
[21:40:28:051] : >> DIAG_STATUS_F FAILED
[21:40:28:056] : >>Get Model Name [DIAG_VERNO_F]
[21:40:28:056] : Clear
[21:40:28:057] : strModel = GT540
[21:40:28:057] : Read NV item: 71 NV ITEM 71 [71]
[21:40:28:057] : Clear
[21:40:28:068] : CSW
[21:40:28:068] : Banner : CSW
[21:40:28:068] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 0 - GT540
[21:40:28:068] : >>Get Mobile SW [DIAG_EXT_BUILD_ID_F]
[21:40:28:068] : Clear
[21:40:28:069] : GT540-M76XX-V10c-JUL-15-2010-XX
[21:40:28:069] : strFilename = GT540-M76XX-V10c-JUL-15-2010-XX
[21:40:28:069] : strFilename = V10
[21:40:28:069] : Flag_Phone_BIN_Donut = TRUE
[21:40:28:069] : Clear
[21:40:28:080] : Write NV item:9028 NV ITEM 9028
[21:40:28:080] : 9028 - NV_DONE_S Item
[21:40:28:180] : _DloadMode()
[21:40:28:180] : ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_CHANGE_DLOAD 4
[21:40:28:180] : >>Change Offline Mode [DIAG_CONTROL_F/Mode = 1]
[21:40:28:180] : Clear
[21:40:28:182] : >>Change Dload Mode [DIAG_DLOAD_F]
[21:40:28:182] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - DLOAD
[21:40:28:182] : Clear
[21:40:28:182] : 2_DIAG_DLOAD_F DLOAD_RESET_F do not wait for response
[21:40:28:182] : #ifdef FEATURE_L4
[21:40:28:182] : Clear
[21:40:28:182] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - Close Port
[21:40:28:182] : Close Port<<
[21:47:08:185] : OPEN_PORT_FAIL
[21:47:08:185] : TYPE_WPARAM_UPGRADE_ERROR
[21:47:08:185] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 6
[21:47:08:280] : Log finished
oh i see, it seems you have just installed 1 driver but here i show you:
*Install first the LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0.msi and then LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0.exe AS ADMINISTRATOR (all of them) just in case and then the bluetooth driver if you want, also is very important you install the drivers inside the LG_SmartPhone folder:
*Unzip the and install them , if you dont have all this drivers then download from here:
http://www.mediafire.com/?ltebjhq24f462lp
THANKS ARE WELCOMED!
cheers dude, well apparently LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0.msi won't installed on windows 7 64-bit. I have the same problem at home and now at work... :s the installer opens up and instantly closes. I have tried compatibility mode but all of the options are greyed out. I may give xp a try via a WM.
I have posted this in another thread so maybe this is naughty butttt.....
"So my pc detects the phone, i can boot in all modes but sadly my screen just won't turn on.
Put it into fastboot mode it vibrates and i plug it into the machine and windows detects it i can happily do a KDZ in emergency mode and that finishes. I go to re-set the phone, it vibrates but i get no logo's and nothing else happens.
I can also flash my system using the fastboot stuff.... Any ideas or more info needed :\
x"
Also to now when trying to use fastboot it will just wait for the device even though maybe 2 hours ago it was working :s maybe since i have tried the emergency KDZ rom it has stopped this working?
Clutching at straws?
jamiehutber said:
cheers dude, well apparently LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0.msi won't installed on windows 7 64-bit. I have the same problem at home and now at work... :s the installer opens up and instantly closes. I have tried compatibility mode but all of the options are greyed out. I may give xp a try via a WM.
Click to expand...
Click to collapse
well did you try to install as administrator dont forget the other drivers. i have windows 7 64 bits too in my laptop and it work great
jamiehutber said:
I have posted this in another thread so maybe this is naughty butttt.....
"So my pc detects the phone, i can boot in all modes but sadly my screen just won't turn on.
Put it into fastboot mode it vibrates and i plug it into the machine and windows detects it i can happily do a KDZ in emergency mode and that finishes. I go to re-set the phone, it vibrates but i get no logo's and nothing else happens.
I can also flash my system using the fastboot stuff.... Any ideas or more info needed :\
x"
Also to now when trying to use fastboot it will just wait for the device even though maybe 2 hours ago it was working :s maybe since i have tried the emergency KDZ rom it has stopped this working?
Clutching at straws?
Click to expand...
Click to collapse
I dont understand what is the problem then you say windows recognize it and you can use KDZ, fastboot state is that way no logo no nothing, just a dark clean screen, so thats is NORMAL. And for fastboot for the "waiting for the device" make sure you have all the neccesary drivers installed as i explained in the tutorial. There are other drivers for your pc to recognize you phone in fastboot mode.
lavero.burgos said:
well did you try to install as administrator dont forget the other drivers. i have windows 7 64 bits too in my laptop and it work great
Click to expand...
Click to collapse
oddly i can't run as admin at home or at work :s but... it didn't appear to be a problem as i got 2.1 installed. But i have no bricked my phone whilst trying to load system.img... i ran system.img from android 11 in the sdk folders... ooo how stupid am i
Any ideas on getting the phone un bricked
Cheers again for the help i've been thanksing
lavero.burgos said:
I dont understand what is the problem then you say windows recognize it and you can use KDZ, fastboot state is that way no logo no nothing, just a dark clean screen, so thats is NORMAL. And for fastboot for the "waiting for the device" make sure you have all the neccesary drivers installed as i explained in the tutorial. There are other drivers for your pc to recognize you phone in fastboot mode.
Click to expand...
Click to collapse
Ye the problem is that it says finished... and then i go to re-set the phone and it just vibrates and nothing else... nothing what-so-ever on the screen. This has happened, i have use kdz many times and each time it has said finished successfully and i reset the phone and same problem.
All the drivers are installed as i have already used the fastboot to flash it eariler, but i obviously did something wrong there
jamiehutber said:
Ye the problem is that it says finished... and then i go to re-set the phone and it just vibrates and nothing else... nothing what-so-ever on the screen. This has happened, i have use kdz many times and each time it has said finished successfully and i reset the phone and same problem.
All the drivers are installed as i have already used the fastboot to flash it eariler, but i obviously did something wrong there
Click to expand...
Click to collapse
hmmm ok are you flashing a KDZ in specific or you have tried with many of them?
jamiehutber said:
oddly i can't run as admin at home or at work :s but... it didn't appear to be a problem as i got 2.1 installed. But i have no bricked my phone whilst trying to load system.img... i ran system.img from android 11 in the sdk folders... ooo how stupid am i
Any ideas on getting the phone un bricked
Cheers again for the help i've been thanksing
Click to expand...
Click to collapse
I see you talk about flash KDZ and system.img apart ... what are you trying to do? dont play that way with your phone from KDZ to fastboot flash and viceversa many times cause you will brick your phone. there is more chances to brick if you want to go back from custom 2.1/2.2/2.3 to stock 2.1(flashed by KDZ).
So ok if you can access to fastboot (means you have flashed a ROM with fastboot) and flash from there succesfully try erasing everything you have posibly flashed in your phone to clean it all and lets see it if gets successful
fastboot erase recovery
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
now install custom 2.1/2.2/2.3 ROM. Stop flashing with KDZ . i recommend superfast froyo rom
fastboot flash boot.img
fastboot flash system.img (both .img should be inside C:\*SDK\tools folder)
fastboot reboot
sorry for the confusion dude...
I cannot use fastboot it still says wait for device, but i know i have the correct drivers. KDZ does detect the phone and also gets all the way through on the update on the euro+fast.
O yes and when it says finished and i take the battery out and try to start the phone it just vibrates and nothing else.
Have i tried any other kdz's? No i don't have a clue of where to download them from :\
Cheers again
Then the kdz you are using is the problem. There is a new post about rom 20E that is good in performance and works well. Download and flash it
Sent from my GT540 using XDA App
I'm about to sleep now. Catch u a bit later. Flash Cis version. With this will check if your phone is not the problem
Sent from my GT540 using XDA App
lavero.burgos said:
Then the kdz you are using is the problem. There is a new post about rom 20E that is good in performance and works well. Download and flash it
Click to expand...
Click to collapse
Ye cheers dude, only thing i can't download this at work... any ideas on any other kdz's? Just trying to get the phone back so i can then installed fastboot rom onto the phone. Unless now i have ruined it with kdz i'll only be able to use the kdz's?
Related
Helo,
I've got a big proplem, my GT540 doesn't boot anymore it always freezes when the LG sign appears. I have this proplem since I'd tried to change the statusbar font into whiteby changing the services.jar. Hardreset and KDZ Updater aren't working. And I also tried to change the new services.jar to the old with adb but I don't get root permissions.
My phone runs with 2.1 Eclair.
Thanks for your help,
Lucas
Wait, arent the status bar white by defoult ?
No i don't mean the bar I mean the clock, but do you have any ideas to solve my proplem?
Do The Hard Reset With Press The
Vol Up + Search Key (on the right side of the phome) + home button
When I Trie to do the hardreset it Happens nothing! Is there no other possibillity to reset?
You could try fresh install with KDZ updater, that worked for me when I broked the radio and my network didn't worked. If you have troubles geting in to download mode you could try removing the battery and press volume up + camera + power button Just be carefull! Good luck
Sent from my GT540 using XDA App
I tried this too, but it crashed always after I choose the kdz file
Here is the log file of KDZ Updater, rename it to Fail.log
Luc-As said:
I tried this too, but it crashed always after I choose the kdz file
Here is the log file of KDZ Updater, rename it to Fail.log
Click to expand...
Click to collapse
OK, you could try this :
If you have problems with KDZ_FW_UPD - Download and install from Microsoft two files "MSXML 4.0 SP3 Parser" and "VisualC Redist"
1 LG_Android_Driver Ver 1.0 must be installed
2 In the Device Manager disable LGE Android USB Modem
3 Run Windows Enabler (on Windows 7 as administrator) and left click on the icon in System tray ( it should be ON )
4 Run "KDZ_FW_UPD.exe" (on Windows 7 as administrator)
5 In the "Type" select "3GQCT", then choose the firmware file
6 Expand the window of the KZD flasher ( more options will emerge )
7 In the "PhoneMode" section choose "CS_EMERGENCY"
DIAG - standard flashing mode of ON state
EMERGENCY - in extreme cases!
CS_EMERGENCY - the same thing, CS - crash systems
8 Click "Start update" will process the firmware
You could also disable your anti virus and use only the back USB ports of your PC. Good luck !
Oh THANKS! I love you guy, I thought I killed my brand new mobile!
Luc-As said:
Oh THANKS! I love you guy, I thought I killed my brand new mobile!
Click to expand...
Click to collapse
You are welcomed
hi all!
my phone was root, instant a2sd, then it work very slow, i was factory reset, it worked.
but when i reset it again, and it can not log on. stop at "android" screen log on. In " download mode" ,i update rom again (v20B_00 and CIS V20B_00), some time, done, but not change, it can not log on. stand by at "android" screen.
any body help me? what can i do? any way to factory reset by window? script? els..
ps: it not hard reset, "Volume up + HOME + SEARCH" buttons not work, maybe my phone GT made by LG vietnamese.
IMEI :352***-04-31***3-1
tks for read!
GT540 does not boot
I have followed
I tried this too, but it crashed always after I choose the kdz file
Here is the log file of KDZ Updater, rename it to Fail.log
OK, you could try this :
If you have problems with KDZ_FW_UPD - Download and install from Microsoft two files "MSXML 4.0 SP3 Parser" and "VisualC Redist"
1 LG_Android_Driver Ver 1.0 must be installed
2 In the Device Manager disable LGE Android USB Modem
3 Run Windows Enabler (on Windows 7 as administrator) and left click on the icon in System tray ( it should be ON )
4 Run "KDZ_FW_UPD.exe" (on Windows 7 as administrator)
5 In the "Type" select "3GQCT", then choose the firmware file
6 Expand the window of the KZD flasher ( more options will emerge )
7 In the "PhoneMode" section choose "CS_EMERGENCY"
DIAG - standard flashing mode of ON state
EMERGENCY - in extreme cases!
CS_EMERGENCY - the same thing, CS - crash systems
8 Click "Start update" will process the firmware
BUT I get error:
Upgrade error
Wparam:100
lparam: 4008
try booting and then when it is stuck at the lg logo plug it in to your pc and begin the upgrade in diag mode.
It worked for me when i wiped my phone.
Cant get it to start reloading the firmware
Can you please tell me from where to get the file KDZ_FW_UPD.exe in english I have it in Russian.
I have tried in DIAG mode but failed...
Please help..
The upgrade does not start...
Very GOOD now it did it like this.
Start your phone in recovery. Volume down+camera+power, see if the pc sees the device. Start the update tool max it and select emergency and flash again.
This fixed...
Now I need to add spanish to it. Do you know how??
cmora22 said:
Can you please tell me from where to get the file KDZ_FW_UPD.exe in english I have it in Russian.
I have tried in DIAG mode but failed...
Please help..
Click to expand...
Click to collapse
Download this file http://forum.xda-developers.com/showthread.php?t=812308
and in folder u see the "updater" file. doubleclick and u have the english KDZ version.
Oh. I need this Fail.rar too.
I have the same Problem. Can anybody reupload?
THX
The Updater allways tells me, that the Phone is not found. What should I do?
I have all the drivers installed.
tehbone
tehbone said:
The Updater allways tells me, that the Phone is not found. What should I do?
I have all the drivers installed.
tehbone
Click to expand...
Click to collapse
yeah, i've got the same problem, i don't know what i can do...
Pleaz help us =(
My PC don't see my phone, my phone stay on 'lg' boot, and can't boot on emergency or hard reset... =/
EDIT: i did it!
You only need to desactivate the LG Android USB Modem (i didn't saw 'Modem' on Device Manager, so i could not desactivate it).
If like me you don't see Modem, you will see it during the period of time during which the device is recognized mod download, ie for about 5 seconds after you plugged in...
I hope it will help someone
PS: Sorry for my english..
Look under modem and you see your phone
At property under tab look your com number remember it
Take teraterm create a connection with your phone you can connect it normally
When you are connected write
AT
( if you see nothing go to setting general and activate ''echo typed only'' )
If your getting OK
AT%FRST%
and the phone does a factory reset
( i'm french so i'm sorry for my english )
Sent from my GT540 using XDA App
This is my first thread ever ok, i need help unbricking my gt540. i turn it on and i just get the LG logo. it will go in download mode but what do i do from there?
If you did it with kdz updater than:
pull out battery, sim and sd
connect phone with computer, make sure you use the usb port on the back of the computer, yes it makes a diferent.
disable lg modem in the device manager
flash a rom with fastboot
go in fastboot by camara+power
connect to computer
type 'fastboot -w' and 'fastboot reboot' in cmd
then flash the rom you want to use.
That should help
Joost
joostvhoek said:
If you did it with kdz updater than:
pull out battery, sim and sd
connect phone with computer
disable lg modem in the device manager
flash a rom with fastboot
go in fastboot by camara+power
connect to computer
type 'fastboot -w' and 'fastboot reboot' in cmd
That should help
Joost
Click to expand...
Click to collapse
edit: then u have to flash the rom that u want to use.
i bricked my gt540 a few days ago.
i saved it with this method
darkfield said:
edit: then u have to flash the rom that u want to use.
i bricked my gt540 a few days ago.
i saved it with this method
Click to expand...
Click to collapse
Me too. Saved my 'life'.
Joost
when u say "make sure you use the usb port on the back of the computer". i am using a laptop so what should i do?
joshyylgg said:
when u say "make sure you use the usb port on the back of the computer". i am using a laptop so what should i do?
Click to expand...
Click to collapse
I have a laptop with 2 on the left and two on the back, use the one on the back
Joost
ok, i get up to the flash with fastboot, it does its thing that i get ERROR!
WPARAM : 100
LPARAM : 4008
joshyylgg said:
ok, i get up to the flash with fastboot, it does its thing that i get ERROR!
WPARAM : 100
LPARAM : 4008
Click to expand...
Click to collapse
Did you pull out the battery?
Joost
Sent from my GT540 using XDA App
joostvhoek said:
If you did it with kdz updater than:
pull out battery, sim and sd
connect phone with computer, make sure you use the usb port on the back of the computer, yes it makes a diferent.
disable lg modem in the device manager
flash a rom with fastboot
go in fastboot by camara+power
connect to computer
type 'fastboot -w' and 'fastboot reboot' in cmd
then flash the rom you want to use.
That should help
Joost
Click to expand...
Click to collapse
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Just to ask how will we flash the ROM with fastboot?
The phone is currently dead, once plug into the usb port (at the back) only the LG logo apprears blink once then the LG logo remains unless plug-out. So I'm having hard time to understand how can I go to fastboot mode. Doing your instruction - holding the power+camera button - before pluging-in and keeping it press down until the LG logo apprears yields no desirable result.
I have fastboot.exe and the adb.dlls, how ever if runned it just display "waiting for device".
Ive use the KDZ updater using emergency mode but fail
>>>>>> current error displays:
>>>>>> WPARAM 100, LPARAM 500
I understand the LPARAM 4800 error appears if the modem was not disable.
Any suggestion?
just to bump the thread and also ask a question of my own
So my pc detects the phone, i can boot in all modes but sadly my screen just won't turn on.
Put it into fastboot mode it vibrates and i plug it into the machine and windows detects it i can happily do a KDZ in emergency mode and that finishes. I go to re-set the phone, it vibrates but i get no logo's and nothing else happens.
I can also flash my system using the fastboot stuff.... Any ideas or more info needed :\
x
What if the phone doesn't react to anything (computer USB, wall charge), isn't recognized by computer (although drivers are installed) and so isn't recognized by any program on the computer....
Doesn't turn on nothing just dead!
is there anything that can be done?
send a service-request to lg:
ht*p://www.lg.com/us/support/contact/support-message.jsp
PLEASE ALL THE USERS THAT HAVE BRICKED THEIR PHONES OR NEED ANY OTHER USEFULL INFORMATION GO TO THE FAQ| LG GT540 Reference Thread (the link is in my signature) !!!
there you can find many how-to's and tutorials, faq (VERY USEFUL INFORMATION) that will help you not to mess up with your phone.
NOW FOR YOUR SPECIFIC PROBLEM PLEASE CLIC ON THE LINK:
http://forum.xda-developers.com/showpost.php?p=13205397&postcount=26
Veronica
My Lg Gt540 Is Bricked
I have just upgraded to 2.3 but my phone is not loading boot animation so i flash my phone with KDZ updater with french v2o rom then out.kdz then
my phone doesn t turn on
hi guys.. could you help me with my problem.!
I have an LG GT540 android 1.6 firmware version(stock)
So here are my problems:
1. I tried to upgrade it from 1.6 to 2.1 using this tutorial http://forum.xda-developers.com/show...27&postcount=3 thanks to lavero.burgos for posting it, I was successful at first part, but I cant follow the next because my device wont go to fast boot,, I tried putting it off, then camera+poweron but it doesnt do anything. It doesn't light, no lg logo appears, just nothing although the computer can read the drive when I connect it through usb. So I cannot flash it to 2.3,2.3 because it just wont go to fastboot.
2. When I turn it on normally, It takes long before it response like after 30sec to light, but just light, no lg logo appears although it wasnt bricked because I can use it normally after just waiting to on.(annoying)
3. Since I upgraded it to 2.1, I lost all 3rd party application and the internal apps were the only left, so I copied all my saved apps (.apk) to my sd card but the problem is there is no saved app on my phone to read and install those apps from my sd card.(irritating)
4. My device wont read my sim card, when I start it it says "sim card unprovisioned" so basically I cant connect to mobile networks here in the philippines(im using globe telecom). I feel that Im stucked in the middle of nowhere since I cannot contact and txt all my family and friends.
5. I cant connect to wifi,, when my device detects wi-fi, I try to connect to it but from the log it only try to connect but doesn't obtain the ip address. Even when the wi-fi signal is strong, it does the same thing.
So please help me guys,,I want to hear from my fellow xda-developers badly,,,
PS. also those who have problems with their LG GT540 pls feel free to post and share it with us here... thank you all guys in advance....
hi so let me get it right the phone is working (can turn on and use but cant call) yes? hmmmmm..... try this
MUST DOWNLOAD THIS DRIVERS!!!!
http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Step one!
1.turn off phone.
2.hold the POWER button till you feel the beep.
3.let go of the POWER button when you feel the beep and hold onto the CAMERA button only.
4.hopefully it turns on to a blackscreen and nothing else(fastboot)
5.unzip this CLICK ME!! to desktop and open the flash all no wipe file
or......
1.turn on your phone.
2.go to settings>applications>development>tick the usb debugging
3.connect phone to computer (make sure phone is on)
4.unzip this CLICK ME!! to desktop and open the flash all no wipe file
5. phone should boot into blackscreen like the one above......
Click to expand...
Click to collapse
Step 2!
both should flash a recovery image. Next
1.make sure the phone is off
2.press POWER button
3.when you feel the beep let go of POWER button and press the HOME button only.
4.phone should boot into recovery mode.
5.take out battery again
6. download a rom into the sdcard using computer
7.go to recovery again using the steps above (steps 1 to 4)
8.select wipe all data factory reset or something like that....
9.install zip from sdcard
10.select from sdcard
11.choose the file you downloaded
12.finish flash and reboot phone.
Click to expand...
Click to collapse
excellent guide! big thanx
bs828 said:
hi so let me get it right the phone is working (can turn on and use but cant call) yes? hmmmmm..... try this
MUST DOWNLOAD THIS DRIVERS!!!!
http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Click to expand...
Click to collapse
Thanks,, Ive tried the 2nd option on step one and i think my phone successfully got to fastboot(just clean blank screen) so the cmd automatically run and states
C:\Desktop\adb rebootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: protocol fault <no status>
C:\Desktop\fastboot flash recovery recovery.img
< waiting for device >
Did I miss something???
ok try again this time with the phone turned on. and then run the script and did you install the drivers?
bs828 said:
ok try again this time with the phone turned on. and then run the script and did you install the drivers?
Click to expand...
Click to collapse
yeah I installed the drivers...
hmmm maybe there are no fastboot drivers(main suspect....) there are a few ways to get it but for mine i just plug my phone in to my pc (windows 7 64bit) it just recognize it and tries to get the "google fastboot interface" drivers from windows update...
Try Volume Up+Search Key+Power to go into Fast boot Mode, There's different keys to activate Fastboot Mode (There is different versions of Fastboot)
Sent from my LG GT540 CM9 PreRC Polish Blood using xda premium
Your phone is/was bricked
Hey, I'm sorry to bing back such an old thread, but I just wanted to say this for posterity: your phone has/had a soft-brick. This means: you can't see Android nor LG boot logos, can't enter Recovery and (maybe) can't access Fastboot, but I'm not too sure on that last one. Besides that, the phone works "okay", but you should try to fix it.
Basically this soft-brick is almost always caught when upgrading from 1.6 to 2.1, so everyone should have it, including me. It took me a whole year to realize how to friggin' fix it lol, but here goes what I did:
Thanks for your help everyone, I came to a solution after a full year lol. Here's my enlightenment, from another Thread:
------------------------------------------------------------------------------------------
Just wanted to leave my 2 cents here, I've been trying to do my best since around august 2014, no success. 2 days ago I retried this, and I DID IT! I will tell everyone what I did very shortly:
My problem that I solved: I can boot, device works like a charm. But: no boot logos, no recovery.
My solution for TL;DR: UNINSTALL ALL DRIVERS FROM DEVICE MANAGER 1ST, then reinstall. After that, flash a fastboot ROM and use it to WIPE ALL THE DATA IN YOUR PHONE! THIS was what I needed and was never explained: you had to WIPE the old data in order to get the boot screens back.
IN THIS ORDER (THANK YOU to those people from previous replies, gathering all your info was of great value):
Uninstall all of your phone drivers from your PC!!! This is what made most of my headaches go away, just use Device Manager and uninstall anything from LGE. After that, plug in your device in your USB ports (always BACK ports, not front ports, important). It should detect all drivers and download them.
IF it fails (it generally does with LGE USB Modem), you can go to Device Manager > Unknown Device (the one that wasn't recognized) > Right Click and Update > Choose 2nd option, then choose "choose from a list of local controllers" (or whatever the button says). After that, scroll down to LG Electronics, Inc. and install what didn't install.
I also found these drivers, but I did not test them: http://www.mediafire.com/download/p693hcz6kkouh19/USB_Driver_LG_GT540.zip
Huzzah!
Now you're set to begin:
FIRST thing you wanna do is a factory reset, this is something I'd forgotten with time, don't make the same mistake as I did. You can do it by turning your phone on and pressing Volume +/- & Home & Quick Search buttons all together for 5 seconds (it works, be patient and wait for it, even if you open the camera or any other stuff).
Download this Google SDK Tools (unzip and put the folder in C:\ drive) and this Fastboot drivers for GT540 (unzip and put the files inside the folder in C:\android-sdk).
Skip this next line if you know your ROM has fastboot.
Now, if you don't have a ROM with fastboot, I recommend you use either European Open+Fastboot or V20C Orange France Fastboot ROM.
Click to expand...
Click to collapse
Since you have Fastboot enabled, now all you need to do is turn off your device (all this with its battery on it, no weird things) and hold the Camera button before turning it back on. This should take you either to a black screen, or simply to no display, like me. Either one will work anyways.
Now press the Windows key > Type cmd and open it with Right Click > Run as Administrator.
In it, type all this, command by command (you can paste by right clicking):
cd C:\android-sdk
fastboot -w
fastboot erase boot
fastboot erase system
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
And now it's go time! Do what everyone else says in here: Take out your phone's battery, SD and SIM cards, fire KDZ Updater up as Administrator (If your KDZ freezes, then it's either faulty or you did not install msxml, look for a good KDZ that comes with that file and delete your current one), choose CS_Emergency PhoneMode and:
1-Plug your phone while holding the volume DOWN button (don't worry! My phone didn't show "Download Mode" either, if you hear the Windows "Somethingpluggedin" Bump noise, it's ok).
2-Flash French V20A
3-Unplug your phone once KDZ says "==FINISHED==".
4-Plug it once again, holding the volume DOWN button.
5-Flash out.kdz (remember! it's CS_Emergency).
Click to expand...
Click to collapse
THANK YOU XDA!
--------------------------------------------------------------------------------------
Also, if you look in here you'll find how to flash an awesome ROM, Cyanogen Mod 10 (should say "Final Version#2).
*** I've been receiving many requests and PMs from members asking to help them unbrick their device. Please note that I no longer own this device (and even if I did I would not purposely brick it just to reproduce your problem), therefore I am unable to help out beyond this tutorial. ***
Hello,
First some background and credits:
There are a few ways to brick a phone. Sometimes it's lack of experience, sometimes it's an accidental thing, sometimes there just isn't an explanation for what went wrong... (share your experience here, if you wish). For me, I owned my OPO for about 4 hours before things went wrong. First thing I did was I rooted it and installed TWRP. After creating a nandroid backup of the stock image I installed my favorite custom ROM and restored all my apps with TiBu. Everything was great and configured just the way I wanted it. I then wiped my old phone (Nexus 4), installed a new ROM and got it all ready for my wife. She was so excited to get rid of her GNex and move up to the N4. But then, for whatever reason, I opened an app on my OPO that I used to manage, download, and install kernels with. It came up with "there is a new kernel update!" and I instinctively clicked on "Install". 10 seconds later my phone was bricked. Nothing came on the screen, no fastboot, no recovery, nothing to boot to, no way to send data to and from it. The second the screen went black and the phone became lifeless I got that wretched feeling in my gut as I realized I just flashed a N4 kernel on my new OPO. Restoring the kernel management app with TiBu made it act like it's still running on my old phone, and in my excitement I didn't take a second to think things through...
I received a bit of consolation when a quick XDA search revealed that I am not the only dumbass to brick his phone this very way. I joined forces with some pretty smart and desperate people and tried different things, all described in the following thread: http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696. Unfortunately it took us what seemed like many long weeks to figure it all out. Well, in the end a solution was found and I documented it in the the following post: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136.
This was a few months ago, but I recently noticed many people continue to search for these directions and have problems finding them hidden among many pages and other threads, so I've decided to put this stand alone thread with these, now updated, directions.
Let me get one more thing straight, for the record. I did not find the way to unbrick the OPO. In fact I wasn't even the very first one to do it. It was a collective effort of few people who tried many different approaches and ideas, and I eventually documented these steps for others to follow. Being said, the following people deserve credit as well: @os_man, @rezor92, @Mnt-XDA. If I am forgetting other significant names and efforts, I apologize.
***CAUTION***
The following instructions are for hardware bricked devices ONLY and will not work on soft bricked devices. To determine whether your device is soft or hard bricked, click the button below:
Hardware brick
A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB. You might have a bricked OPO as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.
Software brick
Please do not attempt to use these directions if your phone is soft bricked. A software bricked OPO is one that might be stuck in a bootloop, but has a working bootloader, recovery partition, fastboot, or adb. If you press the power button and images appear on the screen and you are able to enter fastboot mode (Power + VolUP) or recovery (Power + VolDOWN) then your device is soft bricked. This thread does not encompass soft brick recovery, the instructions below do not apply and will not work on these phones. Consult other threads for help on soft bricked devices.
If based on the above explanation of differences between soft and hard bricks you determined your device is hard bricked, here's what you will need to do...
1:
Download Color.zip from (mirror needed).
After downloading, unzip the archive on your computer.
2:
Next, you need proper Windows drivers. There are architectural differences between Windows XP and Windows 7/8, so follow the directions below that pertain to you. One quick note about the drivers: the installation and process is very simple and straightforward on Windows XP (I also tested successfully on Windows 2003), but proves to be quite a challenge when running on Windows 7 or 8. Over and over people report issues when attempting the unbrick procedure on Windows 7/8, some have more luck than others. Being said, if you have access to a Windows XP computer, I highly recommend that you use that. If you have no choice but to use a Windows 7 or 8 computer and have problems, please share them here and read others' experiences.
So first, by now you probably tried a few different things to fix your phone and you've already installed some drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried so far and use the ones listed below. Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted. Then:
2a:
Windows XP users:
You are in luck, driver installation is straightforward. Go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through the prompts.
2b:
Windows 7 and Windows 8:
These operating systems block unsigned driver installations by default. Follow these steps (thanks @nag4pl for testing these):
Download and extract these Qualcomm 2012 drivers: (mirror needed).
Connect your bricked phone and let Windows do its thing.
Now something very essential you need to do here is to execute two commands to allow you to install unsigned drivers for QHUSB_BULK. Click on Start Menu > Type cmd.exe > Right Click and Run as Administrator.
In the CMD window type in the following commands (hit enter after each):
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Code:
bcdedit.exe -set TESTSIGNING ON
After both the commands should run successfully, restart your computer.
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software. For driver software location provide the path where you have extracted Qualcomm 2012 drivers you downloaded and make sure 'Include Subfolders' is checked. Proceed through all the installation prompts ignoring any warnings.
3:
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.
Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.
4:
Optional Steps:
Your phone is no longer bricked. You now have a few options to get back to stock. The easiest way is to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can flash an image manually by following directions from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541. Download the proper image zip and after extracting it, run the following commands in fastboot mode:
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue.
Good luck! Share your experience here and let me know if I can improve this thread.
Please click the Thanks button if you found the above guide useful.
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
did this and it finally worked but still i have unknown baseband and no imei.........flashed coloros using the msm tool and rom goes into a bootloop......tried all the ways with no luck....even flashed the persist.img......still no luck.......my last hope is claiming warranty and act like a noob in service center.......will they get to know taht i unlocked the bootloader?
mysterio619 said:
did this and it finally worked but still i have unknown baseband and no imei.........flashed coloros using the msm tool and rom goes into a bootloop......tried all the ways with no luck....even flashed the persist.img......still no luck.......my last hope is claiming warranty and act like a noob in service center.......will they get to know taht i unlocked the bootloader?
Click to expand...
Click to collapse
You should be able to boot to fastboot now. From there flash the cm11s image. I believe that "fastboot flash sbl1 sbl1.mbn" will fix the imei issue.
Also, unlocking bootloader does not void your warranty. Not with OPO.
netbuzz said:
You should be able to boot to fastboot now. From there flash the cm11s image. I believe that "fastboot flash sbl1 sbl1.mbn" will fix the imei issue.
Also, unlocking bootloader does not void your warranty. Not with OPO.
Click to expand...
Click to collapse
Tried it......still no imei
mysterio619 said:
Tried it......still no imei
Click to expand...
Click to collapse
Just to give one last try, flash color os modded zip from relic, i used 2.0.43 purezip and it gave me back my imei. Had the same issue as you last week. Be sure to flash TWRP 2.8.4.1 first and then flash color os.
Legit method.
Worked for me 2 weeks ago!
unbrick oneplus one, oppo 7
Hi there my friend, i had many works about unbricking solutions, a few of you know that, i have much easier and faster ways now, tested many times before i decided to share with you, it will be a long topic ( and my brain is messed up to sum them up clearly), as soon i can think clearly again, i start to write them, till then,
greetings from Istanbul to all geeks around thw world.
Ps: including restoring imei's if they got lost during this process.
Ps2: just a quick info abou imei, if your imei is "invalid" , this means your modem.bin (NON-HLOS.bin, baseband) is not inadaptable with your rom, just try flashing the right modem ( from fastboot), your imei will be back.
Ps3 : This will lead us to unbrick many Snapdragon's out there , not only oneplus one's or oppo's.
I had to use this tutorial some days ago.
There is also a modified .zip where the tool from OPO flashed CM11s instead of ColorOS.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I had many driver problems and i had to use this driver from qualcomm so my win7 could recognize the phone.
Tutorial to install the driver:
1. Open your device manager (Start - right click on computer - properties - devices manager)
2. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
3. Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
michaeldepotter said:
I had to use this tutorial some days ago.
There is also a modified .zip where the tool from OPO flashed CM11s instead of ColorOS.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I had many driver problems and i had to use this driver from qualcomm so my win7 could recognize the phone.
Tutorial to install the driver:
1. Open your device manager (Start - right click on computer - properties - devices manager)
2. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
3. Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
Click to expand...
Click to collapse
Hi, Dropbox link for drivers seems to be wrong.. could you please update correct one.. I am in very much need of it! pls!!
nag4pl said:
Hi, Dropbox link for drivers seems to be wrong.. could you please update correct one.. I am in very much need of it! pls!!
Click to expand...
Click to collapse
Sorry. Here is the link:
https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
Sent from my A0001 using XDA Free mobile app
michaeldepotter said:
Sorry. Here is the link:
https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you.. Troubleshooting my phone now..
may i ?
http://www.androidbrick.com/?wpdmdl=2599
Back from Brick!!
First of all Thanks a lot to @netbuzz(for such a life saver guide on unbricking 1+1) and @michaeldepotter for providing link to download appropriate drivers.
Here is some good news by my findings and can be a quick help for those who do not have or can't get XP. You can use Windows 7 itself for the process mentioned by @netbuzz
All you need to do is:
1. Download drivers from link provided by @michaeldepotter : https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
2. Extract to some folder under C: or whichever drive you prefer.
3. Connect your bricked phone after pressing Volume Up and Power key (make sure phone vibrates once)
4. Now that QHUSB_BULK should be detected and Windows will eventually try to download drivers from update, which you can skip and close the window.
Now something very essential you need to do here is to execute some commands so that you will be able to install unsigned drivers for QHUSB_BULK.
4a. Click On Start Menu > Type cmd.exe > Right Click and Run as Administrator (make sure you are running cmd as admin)
4b. Now type below command
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
>hit Enter
bcdedit.exe -set TESTSIGNING ON
> hit Enter again
4c. Both the commands should run successfully, then restart your computer.
These steps are to disable driver sign verification. You must proceed to next steps only after above steps executed successfully.
After machine booted back to desktop
5. Now Open Device Manager by Start > Run > type "devmgmt.msc" and hit enter
6. You should be seeing ugly yellow warning under other devices for QHUSB_BULK.
7. Right click on the same > Update Driver Software > Browse my Computer for driver software
8. Now under driver software location, provide the path where you have extracted drivers which you downloaded from step 1. For me it was:
"C:\Users\Arjun\Downloads\Qualcomm 2012\fre\Windows7" - Remember to provide path only till windows 7 and make sure 'Include Subfolders' is checked.
9. Click next, and it should install driver for QHUSB_BULK. Click on Install Driver if you get any warnings.
Now your driver set-up for QHUSB_BULK in Windows 7 is complete and now you may proceed with the steps to run Msm8974DownloadTool as provided by netbuzz.
I have attached the screenshots for the same just for confirmation.
SuccessfullDriver - showing successful installation of driver
FlashInProgress - showing tool flashing the system image
FlashSuccess - showing green row indicating successful flash.
Once again, thanks a lot for all the guide and help. Hope this quick guide helps some one in need!!
nag4pl said:
First of all Thanks a lot to @netbuzz(for such a life saver guide on unbricking 1+1) and @michaeldepotter for providing link to download appropriate drivers.
Here is some good news by my findings and can be a quick help for those who do not have or can't get XP. You can use Windows 7 itself for the process mentioned by @netbuzz
All you need to do is:
1. Download drivers from link provided by @michaeldepotter : https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
2. Extract to some folder under C: or whichever drive you prefer.
3. Connect your bricked phone after pressing Volume Up and Power key (make sure phone vibrates once)
4. Now that QHUSB_BULK should be detected and Windows will eventually try to download drivers from update, which you can skip and close the window.
Now something very essential you need to do here is to execute some commands so that you will be able to install unsigned drivers for QHUSB_BULK.
4a. Click On Start Menu > Type cmd.exe > Right Click and Run as Administrator (make sure you are running cmd as admin)
4b. Now type below command
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
>hit Enter
bcdedit.exe -set TESTSIGNING ON
> hit Enter again
4c. Both the commands should run successfully, then restart your computer.
These steps are to disable driver sign verification. You must proceed to next steps only after above steps executed successfully.
After machine booted back to desktop
5. Now Open Device Manager by Start > Run > type "devmgmt.msc" and hit enter
6. You should be seeing ugly yellow warning under other devices for QHUSB_BULK.
7. Right click on the same > Update Driver Software > Browse my Computer for driver software
8. Now under driver software location, provide the path where you have extracted drivers which you downloaded from step 1. For me it was:
"C:\Users\Arjun\Downloads\Qualcomm 2012\fre\Windows7" - Remember to provide path only till windows 7 and make sure 'Include Subfolders' is checked.
9. Click next, and it should install driver for QHUSB_BULK. Click on Install Driver if you get any warnings.
Now your driver set-up for QHUSB_BULK in Windows 7 is complete and now you may proceed with the steps to run Msm8974DownloadTool as provided by netbuzz.
I have attached the screenshots for the same just for confirmation.
SuccessfullDriver - showing successful installation of driver
FlashInProgress - showing tool flashing the system image
FlashSuccess - showing green row indicating successful flash.
Once again, thanks a lot for all the guide and help. Hope this quick guide helps some one in need!!
Click to expand...
Click to collapse
Thanks for this Win7/8 workaround. I'll be adding your info to the OP.
Finally Unbricked mine...Drivers resolved on Win 7
netbuzz said:
Second note about drivers is that I had the worst time trying to get things to work on my Windows 7 computers. Both Windows 7 and 8 block unsigned driver installations by default. I've tried overwriting these settings in Windows and spent half a day messing with it, and I never got things to work properly. At first all looked good to go, but then latter steps were failing. You might have a better luck getting drivers to work on Windows 7 or 8 (I've heard some people did it), but if you have access to a Windows XP or 2003 machine, try it first, it should save you some major headache.
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Click to expand...
Click to collapse
I have used the override tool for certificates: DSEO - Driver signature enforcement overrider
to allow the unsigned drivers to be used and it worked like charm on windows 7 64 bit.
Also, I used the additional Qualcomm 2012 drivers and not sure which one might got picked in that mess :cyclops::cyclops:
Thanks!!
:good::good::angel::angel:
nevermind!
Well I managed to hardbrick my phone. I am download the ColorOS file from Mega at the moment. It's downloading at 30KB/s and will take around 6.5 hours. Is there any other source to download it from ? Thanks !
Also, about the driver ...
While I wait on the colorOS to download I want to clarify one more thing about the driver.
According to the screenshot of @nag4pl the driver should show as Qualcomm USB diagnostic 9006, while for me it shows as Qualcomm HS-USB QDloader 9008. Is this going to be an issue ?
This is what I did. I uninstalled the default driver that came with windows 7. After that it failed to install the driver provided in this forum because it kept saying that device descriptor failed. I rebooted the phone several times and changed the USB ports and eventually windows detected it but AGAIN with the windows driver even though I had checked the option to delete the original driver while uninstalling it. Through the update driver option I managed to force it to install the unsigned driver.
Now I can see both the drivers under the update drivers option. Interestingly the default driver is a version ahead of the unsigned driver provided in this forum.
My only concern is that I see a different driver name compared to the one posted by @nag4pl
Thanks! Very useful for me!
That shouldn't be a problem. Not sure if that is specific to region, mine is India version phone.. Can some one clarify on this?
It's been years for you to hear this problem (hard brick)
I have a hard bricked yureka .I have gone through the thread which have posted in in xda and yu forums
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
http://forums.yuplaygod.com/threads/project-reviving-hard-bricked-yu-qloader-9008-mode.10236/
my problem is different form the cases that I read in these threads
In my case the mobile
* is not deducting in Windows*
*it goes to fastboot mode*
*it gets rebooting when connected to windows or charger*
*stable when connected to Windows in fastboot mode*
*during normal start up it goes to fastboot mode and starts rebooting *
*when connected to Windows in fastboot mode the device manager shows it as unknown device under USB*
anyone plz guide me to understand brick my yu....
plz help me .....I'm ineeded of help
I have attached the picture and videos for ur consideration
the link of the Google drive
https://drive.google.com/folderview?id=0B3JWgilAzvw0TjZRb0ZyZDB1Qkk
Install drivers
solution for unknown device
Install adb drivers for fastboot mode and try flashing with signed fastboot flash files
Santhosh Rasa said:
It's been years for you to hear this problem (hard brick)
I have a hard bricked yureka .I have gone through the thread which have posted in in xda and yu forums
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
http://forums.yuplaygod.com/threads/project-reviving-hard-bricked-yu-qloader-9008-mode.10236/
my problem is different form the cases that I read in these threads
In my case the mobile
* is not deducting in Windows*
*it goes to fastboot mode*
*it gets rebooting when connected to windows or charger*
*stable when connected to Windows in fastboot mode*
*during normal start up it goes to fastboot mode and starts rebooting *
*when connected to Windows in fastboot mode the device manager shows it as unknown device under USB*
anyone plz guide me to understand brick my yu....
plz help me .....I'm ineeded of help
I have attached the picture and videos for ur consideration
the link of the Google drive
https://drive.google.com/folderview?id=0B3JWgilAzvw0TjZRb0ZyZDB1Qkk
Click to expand...
Click to collapse
Parkadhe Anna said:
solution for unknown device
Install adb drivers for fastboot mode and try flashing with signed fastboot flash files
Click to expand...
Click to collapse
thanks ... I will try and reply the results ...
Parkadhe Anna said:
solution for unknown device
Install adb drivers for fastboot mode and try flashing with signed fastboot flash files
Click to expand...
Click to collapse
thanks ... I will try and reply the results ...
Hy bro.
I m having same problems two days ago.
I found the solution which issuccessfully working for me. First : downloade the universal necked driver (google it mostly found on google nexus 5 thread).
Second : change ur phone's battery. Get a new battery.
Third : remove ur batterry. Reinsert ur battery. Press volume down & connect USB cable u see the fastboot mode release volume down. Then go to device manager in ur computer and search unknown driver. Right click on it and select update driver update it manually ( google it how to manually update driver) browse the necked driver & select winusnb.inf then select Asus fastboot interface ur device got connect. Now flash official stock cm11 firmware through ygdp tool. That's it. Sorry for my bad English.