Related
hi, i face a problem on windows 8 . all drivers is correcly nstalled on windows 8, ADB is located and correctly mounted but when i restart the One s on bootloader to get it in fastboot USB then its not recognize and the computer said USB not recognize ..
any possible idea ??
thank you in advance
Will972 said:
hi, i face a problem on windows 8 . all drivers is correcly nstalled on windows 8, ADB is located and correctly mounted but when i restart the One s on bootloader to get it in fastboot USB then its not recognize and the computer said USB not recognize ..
any possible idea ??
thank you in advance
Click to expand...
Click to collapse
Works fine here.
Look inside the Device Manager while the phone is connected. Is anything not-recognized there?
khan.orak said:
Works fine here.
Look inside the Device Manager while the phone is connected. Is anything not-recognized there?
Click to expand...
Click to collapse
everything is recognized but the fastboot usb is recognized only the restarting of the computer, after that windows 8 start and the fastboot usb mode disappear ..
Will972 said:
everything is recognized but the fastboot usb is recognized only the restarting of the computer, after that windows 8 start and the fastboot usb mode disappear ..
Click to expand...
Click to collapse
Try plugging it into USB 2.0 ports. May not work with USB 3.0.
khan.orak said:
Try plugging it into USB 2.0 ports. May not work with USB 3.0.
Click to expand...
Click to collapse
i'm not using the USB 3.0 i only use USB 2
I got win8 and the fastboot works fine. I did install the htc manager and after I got the drivers, I stop the htm manager from loading at boot. See if the htc manager is loading at boot. That could interfere with fastboot.
beyond fla
i either recommend cheeking windows firewall to be off . latest version of ' htc sync manager' or ' htc sync' softwares . for checking this , you can go to device manager of windows and connect your phone.it must create a new device recognition and add its schematic between current devices .
So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!
AIndoria said:
So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!
Click to expand...
Click to collapse
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium
Taha Haq said:
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium
Click to expand...
Click to collapse
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
install htc drivers and make dure you cleared the all registry and files from your previous installation and connect your device
open cmd and go to the folder where you placed adb and type command
adb kill-server =>it will close all adb processes running at that time
adb start-server => it will start new adb process
adb devices=> to reconize your device
if it shows your device then through fastboot command flash the recovery
but make sure you have all neccessary binary files in that folder for adb and fastboot
hit thanks if helped
AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
You can try installing the newer Drivers.
Else your usb port may be broken. that is also a possiblity
Installing Cyanmod on N5
When following instructions from wiki
Place the CyanogenMod rom .zip file on the root of the SD card using adb:
Transfer your file(s): adb push YOURROMZIP.zip /sdcard/
Click to expand...
Click to collapse
I get error:device cannot be found.
fastboot device command lists my serial number, adb kill/resume server commands work fine.
Is the wiki missing something?
I have also attempted this step.
On some devices, the zip file can be copied to the device using standard USB Mass Storage or MTP support. Boot the device normally and transfer the file to it.
Click to expand...
Click to collapse
However after following the steps given in the Cyanmod wiki CWM version 6.04 installs the latest nightly and boots to a never ending load screen.
Any help much appreciated,
Cheers.
Are you booted into cwm recovery when using adb?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
No the wiki states to boot back into recovery mode once the .img has been moved over to the sdcard so I am in fastboot mode when issuing the push command.
I did try this while in CWM recovery however Windows 7 looses the Android Bootloader Interface drivers and looses the device altogether. I then have the yellow exclamation mark over Android in Device manager.
Did you wipe data, cache and dalvik in cwm before flashing the zip?
chdgzgfbzc said:
No the wiki states to boot back into recovery mode once the .img has been moved over to the sdcard so I am in fastboot mode when issuing the push command.
I did try this while in CWM recovery however Windows 7 looses the Android Bootloader Interface drivers and looses the device altogether. I then have the yellow exclamation mark over Android in Device manager.
Click to expand...
Click to collapse
You can only adb push in recovery or android. Not fastboot. Plus unless you have a custom kernel with insecure adb support, you can't use android either.
Your recovery issue seems you have a windows driver issue.
I had similar issues with cwm. I had to install drivers using mskip's toolkit. I normally would never advocate using a toolkit but for me it was the only way to get cwm recognised in windows
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Yeah no doubt its a driver issue, but it is strange the USB drivers provided by google are not sufficient, unless the issue is with CWM.
I can install drivers from device manager whilst in CWM recovery, but I have so far found no source that states what drivers you need.
But yeah all cache etc wiped before install.
chdgzgfbzc said:
Yeah no doubt its a driver issue, but it is strange the USB drivers provided by google are not sufficient, unless the issue is with CWM.
I can install drivers from device manager whilst in CWM recovery, but I have so far found no source that states what drivers you need.
But yeah all cache etc wiped before install.
Click to expand...
Click to collapse
I also had a similar issue where drivers for fastboot worked fine but I couldn't get adb to work. What worked for me where the android naked usb drivers.
jd1639 said:
I also had a similar issue where drivers for fastboot worked fine but I couldn't get adb to work. What worked for me where the android naked usb drivers.
Click to expand...
Click to collapse
Cheers man, will give them a try.
jd1639 said:
I also had a similar issue where drivers for fastboot worked fine but I couldn't get adb to work. What worked for me where the android naked usb drivers.
Click to expand...
Click to collapse
for me too. universal naked driver v.0.73. i did not need to install them beforehand either. i unzipped it on desktop, when got the warning that device can not be found, went to device manager, sure enough yellow icon on nexus 5. update driver, pointed to unzipped folder on desktop, done.
akmsr said:
for me too. universal naked driver v.0.73. i did not need to install them beforehand either. i unzipped it on desktop, when got the warning that device can not be found, went to device manager, sure enough yellow icon on nexus 5. update driver, pointed to unzipped folder on desktop, done.
Click to expand...
Click to collapse
Yip the drivers worked sure enough for issuing commands in recovery.
Now after install and restart cyanogenmod is frozen on the boot screen.
Windows device manager shows Portable Device>Nexus 5 with yellow exclamation mark and "This device cannot start. (Code 10)" under properties.
OH WELL.
using
cm-11-20131229-NIGHTLY-hammerhead
hi.
i have question that bothered me now and then.
how do you mount internal storage in pc. for example i wipe out everything, including internal storage (read as sd ext in recovery), evrytime i go in to recovery pick mount usb. it doesnt show any activities in my windows explorer. i go to my computer --> properties --> device manager there is icon nexus 5 with yellow warning on it. try to update driver but return in fail "windows was unable to instal nexus 5"
is there because linux partition on internal storage? so windows cannot load it? or i got wrong version of "usb driver"? or do you have better method? i'd like to know
now everytime i'm flashing rom wipe all data + cache + sd ext, reboot system, after to home screen or my device is on, my pc can transfer files, after done with transferring i reboot to recovery again and then apply rom
This phone doesn't support USB mass storage. Instead there is MTP, but this can only be used while the phone is booted into android. Therefore the only way to copy files to the device while in recovery is to use adb push.
Sent from my HTC Desire using xda app-developers app
Chromium said:
This phone doesn't support USB mass storage. Instead there is MTP, but this can only be used while the phone is booted into android. Therefore the only way to copy files to the device while in recovery is to use adb push.
Click to expand...
Click to collapse
yes i's trying using method adb push, but my nexus doesnt recognize by pc when phone is turn off or in recovery mode, my pc or adb push only work if my nexus is turn on or booted up.
any sugestions?
Private.Indo said:
yes i's trying using method adb push, but my nexus doesnt recognize by pc when phone is turn off or in recovery mode, my pc or adb push only work if my nexus is turn on or booted up.
any sugestions?
Click to expand...
Click to collapse
Search for this on google: naked usb driver 0.73 xda
Click on the first search resault then download the driver.
If you have windows 8 or 8.1 turn off driver signature enforcement.
Open device manager and install the driver for the unknown android device.
Tapatalk-kal küldve az én Nexus 5-el
Private.Indo said:
yes i's trying using method adb push, but my nexus doesnt recognize by pc when phone is turn off or in recovery mode, my pc or adb push only work if my nexus is turn on or booted up.
any sugestions?
Click to expand...
Click to collapse
Did you see this thread at the top of the Q&A section?
http://forum.xda-developers.com/showthread.php?t=2514396
bitdomo said:
Search for this on google: naked usb driver 0.73 xda
Click on the first search resault then download the driver.
If you have windows 8 or 8.1 turn off driver signature enforcement.
Open device manager and install the driver for the unknown android device.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
wow, thx, work like a charm
i knew it i just need correct usb driver package
:victory:
Hi Guys, I just want to ask if there will be a possible solution on how I will be able to use my phone again. I accidentally deleted the OS and the backup of my OS. When I tried to connect my phone to a pc, the pc wont read my phone. Any possible solution on how will I connect it or any solutions for my problem. I also dont have the custom rom zip on my sdcard anymore.
dxlevel81 said:
Hi Guys, I just want to ask if there will be a possible solution on how I will be able to use my phone again. I accidentally deleted the OS and the backup of my OS. When I tried to connect my phone to a pc, the pc wont read my phone. Any possible solution on how will I connect it or any solutions for my problem. I also dont have the custom rom zip on my sdcard anymore.
Click to expand...
Click to collapse
Can you boot into fastboot or recovery?
Mr.Ak said:
Can you boot into fastboot or recovery?
Click to expand...
Click to collapse
yes I can boot into TWRP, but can't connect to pc.
dxlevel81 said:
yes I can boot into TWRP, but can't connect to pc.
Click to expand...
Click to collapse
Ahh..
Just boot into Twrp,connect your device to Pc and transfer any ROM and flash it.Gee,twrp supports mtp,which means you can transfer stuff.Alternatively,if mtp is not working for any reason,you can use usb otg as well.
Mr.Ak said:
Ahh..
Just boot into Twrp,connect your device to Pc and transfer any ROM and flash it.Gee,twrp supports mtp,which means you can transfer stuff.Alternatively,if mtp is not working for any reason,you can use usb otg as well.
Click to expand...
Click to collapse
The pc wont read my phone anymore, I installed adb drivers already. But I'll try to use an otg usb.
dxlevel81 said:
The pc wont read my phone anymore, I installed adb drivers already. But I'll try to use an otg usb.
Click to expand...
Click to collapse
I forgot to mention you can use adb sideload as well.
Since you've adb drivers installed,boot into twrp,go to advanced and enable adb sideload,connect to PC.Copy the ROM zip in your adb folder(where adb files are situated),press shift and simultaneously hit right button on your mouse,select open cmd here.Now write command "adb devices"(obviously without quotes), if all goes well,you'll see your device Id there,proceed and write command "adb sideload ROM name.zip" (where ROM name= exact name of file you're trying to flash).The flashing progress should start now.
Mr.Ak said:
I forgot to mention you can use adb sideload as well.
Since you've adb drivers installed,boot into twrp,go to advanced and enable adb sideload,connect to PC.Copy the ROM zip in your adb folder(where adb files are situated),press shift and simultaneously hit right button on your mouse,select open cmd here.Now write command "adb devices"(obviously without quotes), if all goes well,you'll see your device Id there,proceed and write command "adb sideload ROM name.zip" (where ROM name= exact name of file you're trying to flash).The flashing progress should start now.
Click to expand...
Click to collapse
Do you have links on working adb drivers? That is my problem now. My pc is unable to read my oneplus
dxlevel81 said:
Do you have links on working adb drivers? That is my problem now. My pc is unable to read my oneplus
Click to expand...
Click to collapse
Device doesn't get detected even after enabling adb sideload in Twrp? What does it shows in Device Manager?
https://forum.xda-developers.com/showthread.php?t=2588979
Mr.Ak said:
Device doesn't get detected even after enabling adb sideload in Twrp? What does it shows in Device Manager?
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
It does'nt show in the device manager.