[Q] Want to install recovery image - GT540 Optimus General

Hi guys,
I am trying over 4 hours to flash a recovery image on my gt540.
I have installed a fastboot rom via kdz updater.
Then I turn on the device in fastboot mode to install the recovery using command prompt but in this stage my pc does not recognize the phone. It says "waiting for device".
I have tried every driver I found, but I cannot make it work.
I am running windows 7 x64.
Can anybody help me? I am confused, I don't know what to do.

hmm looks like you dont have the drivers installed. im also using windows 7 x64. i got my drivers by plunging in the phone and waiting for the computer to recognize it and install the drivers from windows update. You can try rebooting the PC then change USB ports. Give each port at most 5 mins to try recognize the phone if it fails then change ports sooner or later the computer will get the drivers
the driver for fastboot is called googlee fastboot interface or something liek that, maybe you can try these http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/

Man you are great! I was searching all day for this!
Thank you very very much!! I managed to flash a good rom!
Thanks again!

Related

usb drivers didn't work anymore

Hello,
I've installed VillainRom 5.5 since a long time, and I think that I've never try to use adb since that.
Yesterday, I try to connect my phone on my computer to install VillainRom 12 based on officiel 2.1, and it tells me that the hardware is not reconize, and adb command didn't work.
So I used the Power and return combination to reboot to bootloader and from that, I managed to used fastboot to boot on RA recovery.
But even now, with my VillaimRom 12, Windows XP doesn't reconize my phone anymore....I can use it for charge or mounting the sd card, but adb doesn't work anymore...
I try to download http://dl.google.com/android/android-sdk_r06-windows.zip and the update package "usb driver rc3", but it changes nothing... :-(
A idea?
Edit: It works thanks to http://www.crazyws.fr/blog/tutos/votre-htc-hero-en-modem-usb.html
Thanks

computer can't find phone in fastboot mode

Hi people
I've been trying to unlock the bootloader to root my nexus s 2.3.3 for 2 days now and have tried everything i can find in all the related threads but my computer wont see the phone when in fastboot mode.
Im getting really fed up as i do not know what to try next.
Anyone had this problem before?
Any help would be much appreciated.
Jon
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Andrew421 said:
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Click to expand...
Click to collapse
Yeah I've tried that too but computer does'nt see the phone in fastboot mode so i cannot update the drivers at all.
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
kenvan19 said:
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
Click to expand...
Click to collapse
Hi, when i put the phone in fastboot mode the computer doesnt see the phone in device manager but it does see it when not in fastboot mode. Im running windows 7 64.
Hey man, I had the same issues. It took me a total of 12 hours to root my phone and I tried everything . I was stuck trying to unlock the bootloader for hours. The problem for me was that the driver couldnt be found. I tried the pda net and it kept saying that the drivers were installed. Assuming your using windows, go to devices with the phone plugged in and you should see the device named something different with a yellow exclamation mark..... right click and hit update driver software. Then find the file pdanet and point it to update with that file. If this doesnt work, theres a file in there I believe its called android_usb or android_winusb and you push "have disk" and force install from that file . then it should see your phone. this was the only way i could get it to work was by pushing have disk and pointing it at the actual android 1.0 driver becuase the google usb package didnt have it (at least at the time). Im new to the forum, so bare with me if my directions aren't too great, just thought I'de try to help you out bc it was so frustrating!. Also, here is a good link in the xda forums for you to check out http://forum.xda-developers.com/showthread.php?t=875580
also,,,are you getting the "waiting for device" message when you type fastboot oem unlock? these instructions are for if you are experiencing that... Its basically not found becuase there is an android 1.0 driver that you have to force to update. good luck!
Thanks for the replies am now downloading the sdk onto the wifes laptop as hers is win 7 32 so hope there is less issues. fingers crossed.
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
mattdub1 said:
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
Click to expand...
Click to collapse
Have the same drivers installed but computer still doesn't see the phone when in fastboot mode. It worked perfectly on win7 32 on other laptop and I managed to root. still trying to get it to work on win7 64 as this is my main OS.
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
also, you did make sure to dowload the google usb package and get the right sdk version correct? I cant see any other reason that the phone wouldn't be recognized. I also believe you need usb debugging on
http://forum.xda-developers.com/showthread.php?t=878786 check out this post... VERY good guide and this is what helped me on the 64 bit 7. it sounds like your missing the fastboot driver which allows the computer to see the device in fastboot mode
mattdub1 said:
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
Click to expand...
Click to collapse
On win7 32 it was really easy once all the necessary programs and files were downloaded I first connected the phone switched on in normal mode with USB debug on and installed the drivers. Once in fastboot mode the path for the drivers was already there from the previous driver install I just selected the bootloader driver and the rest is history
Sent from my Nexus S using XDA Premium App
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
mattdub1 said:
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
Click to expand...
Click to collapse
it was the google usb drivers when i went update drivers on my system the path is
C:\android\android-sdk\extras\google\usb_driver.
Then go to option 'let me pick from a list of drivers on my computer' Which brings up three options:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Choose the Android Bootloader Interface hit next and yes to install.
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
noj78 said:
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
Click to expand...
Click to collapse
If you can see the phone in fastboot what else do you need?
deleted!!!!!!!!!!
I can see it in fastboot mode but not in device manager where it should be.
I can only see it in devices and printers where there are no driver options.
Okay, so put it in fastboot mode and try to run a fastboot devices real quick.

[Q] Device doesn't show up in adb

Ok, I'm having a problem here. I'm buzy on a ROM, and I have made something that I want to test. But when I try to access my phone via adb, it doesn't show up in adb devices. Just nothing. I reïnstalled adb, the drivers, rebooted the phone and computer, put on debugging mode, everything. The phone is showing in (windows) devices, but adb just don't recognize him. I'm on Windows 7 Home Premium. And on my phone Swiftdroid M5 (with ClockworkMod Recovery 3.2.0.1, which is working properly). Anyone knows what to do?
Anyone?
Sent from my GT540 using Tapatalk
Heres my solution ^^ adb worked for me some weeks ago but now i had your problem too lol:
first uninstall all the adb drivers from:
Start>devicemanager
then get this :
http://www.junefabrics.com/bin2/LGDriver.exe
original LG drivers
and install
then plug your phone(debugging on of course)
then it will show 7 (i think) installations
5 of them will be done fast but 2 won't finish installation
so just go to devices and printer
rightclick on android sooner single adb interface and select troubleshooting( marked with a yellow triangle)
then just let is solve the error
the last of the 7 drivers wont install but thats not a problem
EDIT: make sure u know on which port u were doing this
Oh of course you should reinstall the adb drivers. Btw i'm in linux you can use linux for building rom. What are you using?
Sadronis said:
Oh of course you should reinstall the adb drivers. Btw i'm in linux you can use linux for building rom. What are you using?
Click to expand...
Click to collapse
Windows 7 + Ubuntu 11.10
Sent from my GT540 using Tapatalk
is fastboot working now ?. and installed properly in device manager.
regisol said:
is fastboot working now ?. and installed properly in device manager.
Click to expand...
Click to collapse
Wrong topic
Sent from my GT540 using Tapatalk
Hello, I tried all of the above but my device still doesn't get recognized. Is there any other way to fix this? Thanks.
I've been in the same situation like this before. My phone wasn't recognized by adb. I though it was a driver problem so I reinstall the driver million times but it doesn't help. I tried on many other computer with various OS as well but adb still can't recoginized it. At last I flash another ROM and adb can recognized my phone again. so the problem is the SDSL ROM
I see. Thanks for the info ^_^

Fastboot trouble windows 8 x64

Hi guys,
I want to go back to stock since 4.4 is coming. However, when I try to flash the stock rom+ with Nexus Root Toolkit 1.7.3, I get stuck at the whole fastboot part. Fastboot IS working on my Nexus, but the drivers cause a lot of trouble. Installing the drivers when my device is running normally ( so no fastboot mode or whatsoever) works fine.
I have followed the Full driver installation guide where I tried options 1 till 4 but they all get stuck at the point where my device reboots into fastboot mode. At this point, my computer doesn't recognize my device and gives me an error. My nexus is shown in the device manager as unknown device and updating the drivers manually by redirecting my computer to the NRT drivers does not work. It says it cannot find drivers for the device. Does anyone know what I might have done wrong?
Or is it possible to flash a stock rom through twrp? like this one? http://forum.xda-developers.com/showthread.php?t=2376881
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
issak42 said:
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
Click to expand...
Click to collapse
Yeah, I tried the same things you did, including disabling driver signature verification but it won't work. I'll try a windows 7 machine.
Thanks for your answer!

Huge mistake

Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Pedrau said:
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Click to expand...
Click to collapse
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
zaclimon said:
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
Click to expand...
Click to collapse
Yes I can acces to bootloader and TRWP. Tried another USB port, another USB cable, using manual commands it says " <waiting for device>" and nothing happen..
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
venu123 said:
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
Click to expand...
Click to collapse
Thanks buddy , but my drivers were fine before all this. And now i can't reinstall it that way since my nexus isn't even showing up on device manager, I used another method from NRT. Gonna test on w7..
EDIT: Problem solved using windows 7. There seems to have problem with drivers on windows 8.1
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
venu123 said:
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
Click to expand...
Click to collapse
I didn't have to on Windows 8.1.

Categories

Resources