What could be the problem?
Loading G1 in fastboot, connecting to pc, it says: unknown device, vid & pid only zeros. Loading OS, connecting to pc - everything ok, installing drivers.
OS installed RC29 now. Flashed custom recovery, after that - hboot-.33.2003AF-safe, still unkown device.
I want to flash new radio, boot and AOSP OTA 2.2 for HTC Dream.
Please help
Update your Google USB driver in the SDK, and install it. your USB driver is not correctly install (wrong driver)...
Related
Yes, I have searched... ALL OVER!
I have the new 1.6 sdk installed. I'm running the Cyanogen 4.1.999 ROM Donut/1.6. I have adb working. But, I can NOT get fastboot to recognize my device.
I have tried the following:
I have uninstalled the mass storage device - problem here is that Windows automatically installs the drivers again and I CAN'T stop it!
I have gone into the device manager/mass storage device and instructed it to update the drivers using the new 1.6 sdk. The message I received was that I was using the most up to date drivers.
I have found additional tips to solve this problem if I was running Linux. But, I can't find anything I haven't tried for Windows 64-bit....
You even title your question Q and don't post in the Q&A section?
Sorry, I didn't realize I was still in the Android Dev section when I started the thread. I was in a hurry.
If a Moderator will please move this to the Q&A section!
you are running fastboot from the SPL arent you...if not you need to boot up with (Cam+Power)
you need the engineering spl, hardspl, or haykuro spl for fastboot. you also need to make sure fastboot is active on the phone (make sure it says fastboot on it in the bootloader. if not, press the back button)
Yes, sir done all of the above. ADB works great. Boot into spl - shows Fastboot USB. I just get "waiting for device" in the command window. This should be a windows setting, driver install process, or something that either I am missing, doing wrong, or that I don't have installed. But, I have attempted everything I can find on the net. I worked at it for about three hours the other night. The wife was pissed b/c I was on the computer for so long.
Well is fastboot devices showing up under device manager?
it is most likely a driver error. note that if you have haykuro's spl, he has different drivers for it. you will need to get them from his google code page
ok I'm trying to get the PSGroove so what is fastboot? An app? Please explain
shaneaus said:
Yes, I have searched... ALL OVER!
I have the new 1.6 sdk installed. I'm running the Cyanogen 4.1.999 ROM Donut/1.6. I have adb working. But, I can NOT get fastboot to recognize my device.
I have tried the following:
I have uninstalled the mass storage device - problem here is that Windows automatically installs the drivers again and I CAN'T stop it!
I have gone into the device manager/mass storage device and instructed it to update the drivers using the new 1.6 sdk. The message I received was that I was using the most up to date drivers.
I have found additional tips to solve this problem if I was running Linux. But, I can't find anything I haven't tried for Windows 64-bit....
Click to expand...
Click to collapse
If you cannot get the sdk usb drivers to work for you when your entering into fastboot, try installing htc sync. It has additional drivers that may work. I have attached a driver pack that i use.
I needed help, after trying cooked rom Touch - it so I went back to the original version hspl lost, So far so good, I installed in the rom via bootloader 7.0.700.0, from this moment I will install multiple drivers sampre gives me error I connects to the zune and I can not update my HD7. How can I do?? Always tells me no drivers found, are desperately
Hi...i suggest you to install active sync if your pc is a XP,or "centro dispositivi wm" if in your pc runs vista/w7.than you can connect your phone in boot mode and reflash rspl/hspl to try flashing a new official or custom rom.In my phone the DeepShining rom works very well
Hello.
I recently tried to root my phone with the S3 Mini Toolkit. I have the GT-I8190 international version.
It said that I needed to Install the device drivers first (which is the v1.5.18.0).
So I did it as instructed in the command prompt. When it finished installing the driver, and I plugged my device as instructed, suddenly came an error message "Samsung Hardware ID is missing error", and my Mini became unrecognized all of a sudden. I couldn't access my device storage.
There was an error message too popped up in my device saying that It cannot find a driver in my PC for my device.
I tried to install KIES afterward, hoping that it can solve the problem. Thing is, it didn't. My device was still not recognized, and KIES couldn't recognize it either (Connecting.....for, like forever).
I then tried to Google the problem, and came by a forum, saying that it was the 1.5 USB Drivers that caused the problem (but the case being talked in the forum is for Galaxy S3). Said that my PC need to uninstall the 1.5 drivers, uninstall KIES, deactivate the automatic device installation by Windows, and install the 1.4 version.
Well, what I can find in the internet is the 1.3 USB Drivers, so I tried the instructions, and installed the version 1.3 USB Drivers, and my PC recognized my device again, and able to access the storage.
(also, the 1.3 drivers made Odin unable to recognize my phone too in download mode).
Does anybody here have ever experienced the same problem as mine? Or did I do something wrong?
I managed to root my Mini, being not recognized by the PC (but registered at the toolkit) in the whole process, and then did the whole uninstalling and re-install the USB drivers so that I can access my storage again.
Because it's rather a painful process if in the future I want to use the toolkit again with the newest drivers.
Note:
- before rooting, I did the latest OTA update.
My current device info is
Android version 4.1.2
Baseband version I8190DXAMA2
Build vnumber JZO54K.I8190DXAMA2
Region Indonesia
Thank you very much
Bumped. Can anybody gives me some enlightenment about this issue? Thanks
Hello everyone!
So I've been doing a lot of OS tests on my 2x, but this time I think i screwed it up.
The situation is the following: The phone only boots until the lg logo (have ICS bootloader) and can't boot on recovery (don't think he has recovery right now).
So it is completely empty besides the bootloader. Furthermore I don't have the proper drivers installed on my computer. When I turn the phone on and the windows trys to install it fails.
UPDATE: I've been able to boot it on S/W Upgrade to the computer and the windows installed the right drivers - I will try to smartflash a ROM
So I need to fix this situation...
What have I done:
I've downloaded the drivers from LG and LGMobile Support Tool - this last one cant recognize the phone in the current state.
I've downloaded AIO and installed NVFlash Recovery in order get the new Partition and unlocked bootloader (It's currently unlocked already) and put a new recovery image but i always get "USB device not found". I know this is because the drivers aren't there. But how can I install the drivers of the phone itself if I can't boot it up? (Note: I've already installed the lg drivers).
So... What exactly can I do?
Thank you for any help provided
If u can boot in s/w so u can smartflash a stock rom, or install apx drivers there are in aio somewhere it should work and next flash recovery 5.x.x.x so u can repair emmc for flashing roms copy zip to your phone and flash
This kinda worked.
So I tried the smartflash the baseband and ROM. But i got an error and the process was incomplete although i think it did installed at least the bb. After the error, windows started installing some nvidia drivers and I thought that the computer had recognized the phone. And so after that I've tried to change my recovery image and it worked well. The PC could connect through nvflash.
It is now fully operational!
Thank you very much
No problem bro )
Hey all i recently brought a htc one m7 that had viperone already installed, i`m quite computer savvy but phone rooting n flashing are all new to me , i had an issue where i could not hear incomming calls upon answering so i downloaded a hotfix .zip file from venom website, i was then stuck in a boot loop so decided to format and try to reinstal the os for a newer one, (viperone latest) , now im stuck on the Htc boot screen, thought id plug into computer to pass over the new rom only to find that the htc is not recognised bycomputer so i have a bit of a dilema any help appriciated
newb mark said:
Hey all i recently brought a htc one m7 that had viperone already installed, i`m quite computer savvy but phone rooting n flashing are all new to me , i had an issue where i could not hear incomming calls upon answering so i downloaded a hotfix .zip file from venom website, i was then stuck in a boot loop so decided to format and try to reinstal the os for a newer one, (viperone latest) , now im stuck on the Htc boot screen, thought id plug into computer to pass over the new rom only to find that the htc is not recognised bycomputer so i have a bit of a dilema any help appriciated
Click to expand...
Click to collapse
When you say it's not recognised by your computer. Can you elaborate please?
adb does not work in recovery?
fastboot does not work in bootloader?
Or drivers fail to install altogether?
Thanks for interest , i plug the phone in and the htc suite comes up but reports no phone connected , the phone comes up on pc as a cd drive then automatically tries to install htc mtp drivers for pc (win 7 64bit) it installs half way then fails htc suite reports that i need to unlock with a pin or to accept htc sync on phone (which is pinless), on phone i have access to twrp 2.6.3.3 have looked for a viperone rom on phone but i can`t find one when i try to boot to system it tells me that i have no os then it asks if i want to install supersu as my phone does not appear to be rooted, in the bootloader it states tampered , unlocked i select fastboot usb but always seem to go back to twrp , as i say i am brand new at all this and there is possibly a simple answer that i am overlooking, was told to download a stock three andriod but cant see how i can get the phone to read it , thanks again
newb mark said:
Thanks for interest , i plug the phone in and the htc suite comes up but reports no phone connected , the phone comes up on pc as a cd drive then automatically tries to install htc mtp drivers for pc (win 7 64bit) it installs half way then fails htc suite reports that i need to unlock with a pin or to accept htc sync on phone (which is pinless), on phone i have access to twrp 2.6.3.3 have looked for a viperone rom on phone but i can`t find one when i try to boot to system it tells me that i have no os then it asks if i want to install supersu as my phone does not appear to be rooted, in the bootloader it states tampered , unlocked i select fastboot usb but always seem to go back to twrp , as i say i am brand new at all this and there is possibly a simple answer that i am overlooking, was told to download a stock three andriod but cant see how i can get the phone to read it , thanks again
Click to expand...
Click to collapse
Ok after you see the driver install failed message do this
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install latest version. :good:
That should get your drivers working. Then can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting.
it`s under htc mtp device in device manager under portable devices it allows me to run htc mtp V 1.0.0.21 install or mtb usb device tried both and get an error on installation code 10 this device cannot start tried it in twrp and on htc
screen that it seems to be stuck on
newb mark said:
it`s under htc mtp device in device manager under portable devices it allows me to run htc mtp V 1.0.0.21 install or mtb usb device tried both and get an error on installation code 10 this device cannot start tried it in twrp and on htc
screen that it seems to be stuck on
Click to expand...
Click to collapse
Ok well I'm not a big user of Windows and that's about all I got for trouble shooting drivers.
You might try with Linux. No drivers needed. No drivers no problems
http://forum.xda-developers.com/showthread.php?p=54272479
Failed OTG Upgrade and Unlock Bootloader
I have a HTC One M7U Device PN07110 Cid: HTC__J15, Currently on Software Version 4.19.401.5 & bootloader 1.56.0000. I tried to upgrade OTA many times but it fails after the blue bar shows up. Then I repeatedly tried to unlock its bootloader as mentioned in htcdev website and XDA-Dev forums. All went well and the device rebooted after flashing unlock_code.bin and getting confirmation "Yes" in the prompt clean each time. But the bootloader is still showing locked on top of screen. Please help.
newb mark said:
it`s under htc mtp device in device manager under portable devices it allows me to run htc mtp V 1.0.0.21 install or mtb usb device tried both and get an error on installation code 10 this device cannot start tried it in twrp and on htc
screen that it seems to be stuck on
Click to expand...
Click to collapse
Can I ask which version of recovery your using ?
Ive just noticed with the latest version of TWRP recovery and my phone booted, when I plug it into the computer it comes up in device manager as MTP device also, and adb doesnt work, thankfully, adb and fastboot still work with the phone in the bootloader / recovery.