Hi guys, I have read several threads on here already so just to let you know Im not just making a thread at the first sign of trouble.
Heres my predicament:
I used a tool kit ( nexus 1 click toolkit for mac) to try and root my phone, which after diving in and pressing enter, found that they seem to be the work of the devil. So it unlocks the bootloader no problem but it cant push the su file to the nexus and comes up with this text :
Pushing UPDATE-SuperSU-v1.45.zip...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
after this it installed cwm, but obviously the su file isn't there so I can't install zip from sd card.
I've tried formatting personal data (which cwm says cant mount sdcard/android_secure, skipping format) and formatting the dalvik cache and rebooting with no avail.
I'm running a mac but can get access to a pc if absolutely necessary, at the moment I don't mind if I don't have root, having my phone back is priority!
Thanks for you help in advance.
dont use toolkits, do it the right way.
fastboot oem unlock via fastboot, fastboot flash a custom recovery, flash the latest supersu in you new custom recovery, reboot. thats it.
simms22 said:
dont use toolkits, do it the right way.
fastboot oem unlock via fastboot, fastboot flash a custom recovery, flash the latest supersu in you new custom recovery, reboot. thats it.
Click to expand...
Click to collapse
Hi thanks for putting me on the right track, when i put in ./fastboot devices
0042642ea095831a fastboot
it does come up with the serial number but when i put in ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
the list of devices attached is blank, any ideas? leading me to think i don't have debugging on
is there a way of turning debugging on from terminal?
Jack_R8 said:
Hi thanks for putting me on the right track, when i put in ./fastboot devices
0042642ea095831a fastboot
it does come up with the serial number but when i put in ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
the list of devices attached is blank, any ideas? leading me to think i don't have debugging on
Click to expand...
Click to collapse
its fastboot, adb doesnt work in fastboot.
simms22 said:
its fastboot, adb doesnt work in fastboot.
Click to expand...
Click to collapse
Just to let you know i got it fixed, thanks a lot :good:
Hey there.
I´ve been following this guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Stuck at this point already:
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
Click to expand...
Click to collapse
I made a few screenshots to show what I´ve done / got so far:
imgur: android SDK manager, installed packages
imgur: windows 10 being up to date and rough system specs
imgur: nexus 6p bootloader screen
imgur: developer options, oem unlocking & usb debugging both enabled
imgur: installation path including command line results
So what am I doing wrong? Couldn´t find a reason yet, other than it being my drivers but then again I´ve deinstalled and reinstalled the newest drivers using the SDK manager multiple times already. Not sure what else to do.
Kind regards,
Chrotesque
Your device is connected via ADB not FASTBOOT (what it shows on the last pic).
Try using : adb reboot bootloader
and then, after the phone reboots, go on and : fastboot devices
kauemelhado said:
Your device is connected via ADB not FASTBOOT (what it shows on the last pic).
Try using : adb reboot bootloader
and then, after the phone reboots, go on and : fastboot devices
Click to expand...
Click to collapse
Hey and thanks for the reply, however I´ve done that, to be specific I´ve done it in two different ways.
1. shut down the nexus and then loaded up the bootloader via pressing power & volume down button
2. while having the nexus connected via usb to the pc I used the command "adb reboot bootloader" from the command line interface, the nexus rebooted directly into the bootloader and still the same result.
Using "fastboot devices" after using "adb reboot bootloader" didn´t help at all - if necessary I can screenshot that as well ofc.
Go to device manager and see if an error shows up for the phone. YOu may need to install drivers. Right click on android and install drivers, look up drivers, a samsung driver should show up, install it twice. That should help your fastboot bootloader.
Try doing what I said, without booting into bootloader.
>Power on your device (system)
>Enable Usb Debugging
>adb devices
>adb reboot bootloader
>wait for the device to boot up
>fastboot devices
kauemelhado said:
Try doing what I said, without booting into bootloader.
>Power on your device (system)
>Enable Usb Debugging
>adb devices
>adb reboot bootloader
>wait for the device to boot up
>fastboot devices
Click to expand...
Click to collapse
Did that, result is this here: [cant link stuff]imgur.com/6KT3vxZ
Go to device manager and see if an error shows up for the phone. You may need to install drivers. Right click on android and install drivers, look up drivers, a samsung driver should show up, install it twice. That should help your fastboot bootloader.
Click to expand...
Click to collapse
Result: [cant link stuff]imgur.com/P5SelUM
I was able to get fastboot devices to work ONLY when I used this driver: [I cant post links]software.intel.com/en-us/blogs/2015/08/18/intel-usb-driver-for-android-devices-that-support-windows-10-is-here
This one didn't work at all: [I cant post links]developer.samsung.com/technical-doc/view.do?v=T000000117
EDIT:
is it correct that adb devices does not work when I am on the bootloader?
C:\SDK\android-sdk-windows\platform-tools>adb version
Android Debug Bridge version 1.0.32
Revision 09a0d98bebce-android
C:\SDK\android-sdk-windows\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
CVH7N15B11000407 device
C:\SDK\android-sdk-windows\platform-tools>adb reboot bootloader
*reboots into bootloader*
C:\SDK\android-sdk-windows\platform-tools>fastboot devices
CVH7N15B11000407 fastboot
C:\SDK\android-sdk-windows\platform-tools>adb devices
List of devices attached
At this point I`d expect the device again but I am currently in the bootloader, is that the "issue" and not an issue at all at this point?
EDIT 2:
seems like everything worked out, seems like the intel usb driver did the trick
Thanks for your help so far!
Chrotesque said:
Did that, result is this here: [cant link stuff]imgur.com/6KT3vxZ
Result: [cant link stuff]imgur.com/P5SelUM
I was able to get fastboot devices to work ONLY when I used this driver: [I cant post links]software.intel.com/en-us/blogs/2015/08/18/intel-usb-driver-for-android-devices-that-support-windows-10-is-here
This one didn't work at all: [I cant post links]developer.samsung.com/technical-doc/view.do?v=T000000117
EDIT:
is it correct that adb devices does not work when I am on the bootloader?
C:\SDK\android-sdk-windows\platform-tools>adb version
Android Debug Bridge version 1.0.32
Revision 09a0d98bebce-android
C:\SDK\android-sdk-windows\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
CVH7N15B11000407 device
C:\SDK\android-sdk-windows\platform-tools>adb reboot bootloader
*reboots into bootloader*
C:\SDK\android-sdk-windows\platform-tools>fastboot devices
CVH7N15B11000407 fastboot
C:\SDK\android-sdk-windows\platform-tools>adb devices
List of devices attached
At this point I`d expect the device again but I am currently in the bootloader, is that the "issue" and not an issue at all at this point?
EDIT 2:
seems like everything worked out, seems like the intel usb driver did the trick
Thanks for your help so far!
Click to expand...
Click to collapse
Eidit: Nevermind I see you're all set
Chrotesque said:
Did that, result is this here: [cant link stuff]imgur.com/6KT3vxZ
Result: [cant link stuff]imgur.com/P5SelUM
I was able to get fastboot devices to work ONLY when I used this driver: [I cant post links]software.intel.com/en-us/blogs/2015/08/18/intel-usb-driver-for-android-devices-that-support-windows-10-is-here
This one didn't work at all: [I cant post links]developer.samsung.com/technical-doc/view.do?v=T000000117
EDIT:
is it correct that adb devices does not work when I am on the bootloader?
C:\SDK\android-sdk-windows\platform-tools>adb version
Android Debug Bridge version 1.0.32
Revision 09a0d98bebce-android
C:\SDK\android-sdk-windows\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
CVH7N15B11000407 device
C:\SDK\android-sdk-windows\platform-tools>adb reboot bootloader
*reboots into bootloader*
C:\SDK\android-sdk-windows\platform-tools>fastboot devices
CVH7N15B11000407 fastboot
C:\SDK\android-sdk-windows\platform-tools>adb devices
List of devices attached
At this point I`d expect the device again but I am currently in the bootloader, is that the "issue" and not an issue at all at this point?
EDIT 2:
seems like everything worked out, seems like the intel usb driver did the trick
Thanks for your help so far!
Click to expand...
Click to collapse
so i installed the intel driver onto my pc, the fastboot devices doesnt work. help?
TechMillz93 said:
so i installed the intel driver onto my pc, the fastboot devices doesnt work. help?
Click to expand...
Click to collapse
I reckon you should open your own thread and provide a sufficient amount of details to your own situation in order to get help, it´s near impossible to help you with the information that you provided so far, having installed the intel drivers and these "not working".
Simply go through the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and start your own thread as soon as you start having issues and list exactly what you´ve done, what error messages you get, et cetera.
Chrotesque said:
I reckon you should open your own thread and provide a sufficient amount of details to your own situation in order to get help, it´s near impossible to help you with the information that you provided so far, having installed the intel drivers and these "not working".
Simply go through the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and start your own thread as soon as you start having issues and list exactly what you´ve done, what error messages you get, et cetera.
Click to expand...
Click to collapse
Never mind I got it ha
Sent from my Nexus 6P using Tapatalk
Thanks
Chrotesque said:
Did that, result is this here: [cant link stuff]imgur.com/6KT3vxZ
Result: [cant link stuff]imgur.com/P5SelUM
I was able to get fastboot devices to work ONLY when I used this driver: [I cant post links]software.intel.com/en-us/blogs/2015/08/18/intel-usb-driver-for-android-devices-that-support-windows-10-is-here
This one didn't work at all: [I cant post links]developer.samsung.com/technical-doc/view.do?v=T000000117
EDIT:
is it correct that adb devices does not work when I am on the bootloader?
C:\SDK\android-sdk-windows\platform-tools>adb version
Android Debug Bridge version 1.0.32
Revision 09a0d98bebce-android
C:\SDK\android-sdk-windows\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
CVH7N15B11000407 device
C:\SDK\android-sdk-windows\platform-tools>adb reboot bootloader
*reboots into bootloader*
C:\SDK\android-sdk-windows\platform-tools>fastboot devices
CVH7N15B11000407 fastboot
C:\SDK\android-sdk-windows\platform-tools>adb devices
List of devices attached
At this point I`d expect the device again but I am currently in the bootloader, is that the "issue" and not an issue at all at this point?
EDIT 2:
seems like everything worked out, seems like the intel usb driver did the trick
Thanks for your help so far!
Click to expand...
Click to collapse
Thank you. I was stuck in the same problem. Installing the intel drivers for windows 10 in the above link solved my issue.
Windows 10 Home on host computer, and ADB tools installed.
USB debug mode on and host computer allowed.
USB PTP mode.
LG Unified Driver installed.
I opened command prompt, locate adb platform-tools. Ran the following commands
Code:
adb reboot bootloader.
The phone rebooted to bootloader.
On the bootloader mode on the phone, I typed
Code:
fastboot reboot
The phone rebooted properly
Does it work right?
Currently the phone is not ready to unlock bootloader until there's no problem, especially speaker problem, found.
Help
i've tried everything, different pc's, different drivers, i just can't get my phone to connect with adb
fastboot devices works
Code:
adb>fastboot devices
4TE7N16B26004380 fastboot
adb devices doesn't
Code:
adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
If you phone works. Turn on USB debbuging.
phone doesn't work
meezo said:
Help
i've tried everything, different pc's, different drivers, i just can't get my phone to connect with adb
fastboot devices works
adb devices doesn't
Click to expand...
Click to collapse
ADB is to connect working system to PC for debugging (and other good stuff).
Since your phone can't boot, you need to make it boot. dload method or fastboot flash system and boot partitions should be your next step.
Hi, I formatted my phone with Msm tool and fastboot isn't working properly since.
The device is detected both in adb and fastboot, but in fastboot it shows a double output, an ordinary device id and a series of question marks.
Also, adb cannot boot bootloader for some reason.
I tried formatting from device, formatting again through msm, i checked all drivers and tools, I changed cables and port. No dice.
Any suggestions?
Thanks
use " adb devices -l " commands so it will tell what devices model ...