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:
Related
Hello,
When I do this command I see the device in the list:
adb devices.
The the next step is to go in fastboot, witch I do with BACK button + POWER on. The fastboot mode is on, but I couldn't see the device anymore. So the next command doesn't work at all:
fastboot boot recovery-new.img
Do I have to put on the phone again, because that is not written in the manual.
Greetz,
Dries
Droned said:
Hello,
When I do this command I see the device in the list:
adb devices.
The the next step is to go in fastboot, witch I do with BACK button + POWER on. The fastboot mode is on, but I couldn't see the device anymore. So the next command doesn't work at all:
fastboot boot recovery-new.img
Do I have to put on the phone again, because that is not written in the manual.
Greetz,
Dries
Click to expand...
Click to collapse
Windows vista for example tries to install the incorrect drivers. Adb drivers are not recognized for it in fastboot mode, or will install different drivers.
Use usbdeview to delete all the HTC or android drivers. Go into fastboot mode connect phone, manually install your drivers from the sdk/tools/usb drivers folders. Boot the recovery, backup, then flash the recover. Feel free to PM and I will try to help.
when your in fastboot its
fastboot devices rather than adb devices
make sure your phone is connected and in fastboot mode
as well as make sure it reads
"fastboot USB"
minogue has the correct information listed for you (assuming that you have the USB drivers installed for "fastboot" mode as well.
I had the exact same problem as you, but after typing in "fastboot devices"... bingo, there it was.
OK, I went in the control panel of vista and delete the device, plugged in the phone and installed the correct drivers and it works.
Thanks
Droned said:
OK, I went in the control panel of vista and delete the device, plugged in the phone and installed the correct drivers and it works.
Thanks
Click to expand...
Click to collapse
Sounds like I was correct.
How do you know when its rooted? ive got 2 partitions (Fat32 and Ext2) i can seee them in paragon partition manager but when i look on sd settings on my g2 it says under secondary storage unknown?
bonesy said:
How do you know when its rooted? ive got 2 partitions (Fat32 and Ext2) i can seee them in paragon partition manager but when i look on sd settings on my g2 it says under secondary storage unknown?
Click to expand...
Click to collapse
Terminal immulator type $ su
if it changes to # you have root.
Also, adb shell, # you have root.
Brilliant thanks. So what abiout it not showing on my phone? Says "SD Secondary storage" But under says unknown?
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
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
simms22 said:
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
Click to expand...
Click to collapse
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
simms22 said:
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
Click to expand...
Click to collapse
Revise it, I can use adb push/ pull etc...
you explained that to someone long ago
rootSU said:
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
Click to expand...
Click to collapse
I'm using TWRP. My problems with drivers keeps increasing it seems :\
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
you can go to device manager and update the driver, choose Browse my computer, Let me pick from a list of device drivers, and choose one that says adb.
rootSU said:
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
Click to expand...
Click to collapse
GUGUITOMTG4 said:
Revise it, I can use adb push/ pull etc...
you explained that to someone long ago
Click to expand...
Click to collapse
right.
was concentrating on work. i messed up
simms22 said:
right.
was concentrating on work. i messed up
Click to expand...
Click to collapse
We all do it
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
OK as you said you have followed the steps in the linked post. I will assume you have already downloaded and extracted the latest_usb_driver_windows.zip.
I Use windows 8 but the procedure should be the same for Vista / 7 / 8
Here is what to do.
1. Put your phone in recovery.
2. Plug into PC
3. Go To Device Manager
4. Right click "AOSP on hammerhead".
5. Choose "Update Driver Software..."
6. Click "Browse my computer for driver software"
7. Click "Let me pick from a list of device drivers on my computer"
8. Click "Have Disk..."
9. Click "Browse..."
10. Navigate to the extracted Driver you downloaded. (in my case V:\Downloads\latest_usb_driver_windows\usb_driver\)
11. Double click on android_winusb.inf
12. Click "OK"
13. Click "Android Composite ADB Interface" and press Next. (If it is not in the list, untick the "Show compatible hardware button at the top)
Your driver will now install and you should be able to use ADB normally in recovery
To make adb works in recovery you need the naked usb drivers
Tapatalk-kal küldve az én Nexus 5-el
You don't need the naked USB drivers at all.
I use the Google USB drivers and they work fine in recovery.
The problem he is having is that windows has automatically installed a different driver than what is needed for adb to work.
Manually updating the driver to the Google adb driver as shown in my previous post will get the op running without having to download anything extra
Sent from my Nexus 5 using xda app-developers app
Alex240188 said:
OK as you said you have followed the steps in the linked post. I will assume you have already downloaded and extracted the latest_usb_driver_windows.zip.
I Use windows 8 but the procedure should be the same for Vista / 7 / 8
Here is what to do.
1. Put your phone in recovery.
2. Plug into PC
3. Go To Device Manager
4. Right click "AOSP on hammerhead".
5. Choose "Update Driver Software..."
6. Click "Browse my computer for driver software"
7. Click "Let me pick from a list of device drivers on my computer"
8. Click "Have Disk..."
9. Click "Browse..."
10. Navigate to the extracted Driver you downloaded. (in my case V:\Downloads\latest_usb_driver_windows\usb_driver\)
11. Double click on android_winusb.inf
12. Click "OK"
13. Click "Android Composite ADB Interface" and press Next. (If it is not in the list, untick the "Show compatible hardware button at the top)
Your driver will now install and you should be able to use ADB normally in recovery
Click to expand...
Click to collapse
Can you check if you can use adb remount when the phone is fully booted? I'm using naked drivers and everything works except this command. Adb root doesn't work also.
This has nothing to do with the drivers. The kernel you use has to be built with the ro.secure=0 flag for remount to work
Sent from my Nexus 5 using xda app-developers app
I was in recovery and accidentaly wiped everything and now i m stuck in recovery and can connect to pc to transfer a new rom.
What do i do now??
DimitrisN5 said:
I was in recovery and accidentaly wiped everything and now i m stuck in recovery and can connect to pc to transfer a new rom.
What do i do now??
Click to expand...
Click to collapse
Now you must work out how to connect to PC to transfer new rom. You can use adb. Loads of guides for adb push about
rootSU said:
Now you must work out how to connect to PC to transfer new rom. You can use adb. Loads of guides for adb push about
Click to expand...
Click to collapse
When i go to mount option i twrp there is a list that says system data etc.but under these there isn't an option to mount
DimitrisN5 said:
When i go to mount option i twrp there is a list that says system data etc.but under these there isn't an option to mount
Click to expand...
Click to collapse
http://lmgtfy.com/?q=adb+push
Is there any chance i cant connect my device to my pc and permanently damage the device??
DimitrisN5 said:
Is there any chance i cant connect my device to my pc and permanently damage the device??
Click to expand...
Click to collapse
Not whilst adb puhsing, no.
If you were fastboot flashing something like a bootloader or radio and disconnected it during teh flash, you could brick your device - but you're not doing that.
adb push is just copying files from your PC to your device.
lets say you have rom.zip on your computer c drive
Code:
adb push c:\rom.zip /sdcard
is all you'd need to do.
Ok, I have a Nexus 5. I have been trying to port (Zip style, not Source) the CM11S build for the OnePlus One. I used the 20140615 CM11 nightly build as the base, but it keeps getting stuck at the boot animation. My issues are that I need to know how to activate ADB Debugging through the build.prop so I can get a logcat on first boot (while it's stuck on the boot animation). Also, once I can get a logcat, I would love some help debugging my port. I will upload a copy of my Zip in it's current form, if anyone has any advice, feel free to pass along some advice.
My CM11S Port (AndroidFileHost)
Don't think you can do it in build prop.. You would need use sqlite3 to write it to settings.db
Sent from my Nexus 5 using Tapatalk
rootSU said:
Don't think you can do it in build prop.. You would need use sqlite3 to write it to settings.db
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Can this be done without the ROM booting fully?
TekGadgt said:
Can this be done without the ROM booting fully?
Click to expand...
Click to collapse
Yeah you can adb pull the db and use sqllite to edit it on a pc and push it back
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yeah you can adb pull the db and use sqllite to edit it on a pc and push it back
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am having issues with adb over recovery, my device in device manager appears as 'AOSP on Hammerhead' and does not recognize adb interface. I have tried CWM, TWRP, and Philz.
TekGadgt said:
I am having issues with adb over recovery, my device in device manager appears as 'AOSP on Hammerhead' and does not recognize adb interface. I have tried CWM, TWRP, and Philz.
Click to expand...
Click to collapse
search on google for: xda naked usb drivers 0.73, download it and install those drivers in device manager for AOSP on hammerhead device. If you are running running win 8 or 8.1 then you have to turn off the driver signature enforcement.
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
search on google for: xda naked usb drivers 0.73, download it and install those drivers in device manager for AOSP on hammerhead device. If you are running running win 8 or 8.1 then you have to turn off the driver signature enforcement.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
I got the adb over recovery issue sorted out, now I just need to figure out why when I use adb logcat, I get /sbin/sh: exec: line 1: logcat: not found
Any ideas? Thanks in advance. Also, if I try to save the logcat to a file, adb logcat -v long > logcat.txt, I get Access is denied.