what can i do?!
p.s.
i can get into download mode and recovery mode
Use flashtool and flash kdz on your phone
danial.aw said:
Use flashtool and flash kdz on your phone
Click to expand...
Click to collapse
can you explain me how? i'm new at this..
suchegi quickly
hi,
use adb sideload to push a rom on your sd and flash through your recovery.:
http://forum.xda-developers.com/showthread.php?t=2559200
or
info about kdz flashtool etc.... :
http://forum.xda-developers.com/showthread.php?t=2705259 (pined)
x10tom said:
hi,
use adb sideload to push a rom on your sd and flash through your recovery.:
http://forum.xda-developers.com/showthread.php?t=2559200 (pined)
Click to expand...
Click to collapse
thx alot, but i have some problem maybe you would know..i did all the stages but when i need to enter "adb usb"
i get
"* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found"
what can i do?
some lectmi
ok..
what i do:
my driver look like this (adb sideload activated Under twrp ):
type only "adb sideload rom.zip" in cmd
(rom.zip in the adb's folder)
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.
Since I coudn't find any rooting guide in this forum I followed the this guide: http://www.theandroidsoul.com/htc-u11-root-twrp-recovery-and-bootloader-unlock/
I successfully unlocked the bootloader. The next step is flashing TWRP and that's where my problem begins. I downloaded the latest TWRP image for my HTC U11 and issued fastboot flash recovery twrp-3.1.1-0-ocn.img.
When I tried to reboot into the recovery I only saw a screen with a smartphone showing a red sign with an exclamation mark. Seems something went wrong flashing the recovery.
Unfortunately since then adb doesn't seem to work any more. I managed to reboot the phone and everything is working but whenever I connect my phone to my windows laptop and issue adb devices I get the following error message:
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
That's the reason why I cannot flash the recovery again. What are your suggestions now?
Helped myself. Even though adb still gave me the very same error message in download mode I was able to issue the fastboot flash recovery command again (fastboot devices did list my phone). This time it worked and now I successfully booted into TWRP. Guess you've got to be in download mode when trying to flash the new recovery. Puh...
simu_lacrum said:
Since I coudn't find any rooting guide in this forum I followed the this guide: http://www.theandroidsoul.com/htc-u11-root-twrp-recovery-and-bootloader-unlock/
I successfully unlocked the bootloader. The next step is flashing TWRP and that's where my problem begins. I downloaded the latest TWRP image for my HTC U11 and issued fastboot flash recovery twrp-3.1.1-0-ocn.img.
When I tried to reboot into the recovery I only saw a screen with a smartphone showing a red sign with an exclamation mark. Seems something went wrong flashing the recovery.
Unfortunately since then adb doesn't seem to work any more. I managed to reboot the phone and everything is working but whenever I connect my phone to my windows laptop and issue adb devices I get the following error message:
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
That's the reason why I cannot flash the recovery again. What are your suggestions now?
Click to expand...
Click to collapse
Wait for a limited time and try again, if failed read this tutorial video:
https://www.youtube.com/watch?v=aOkDjaqspGQ
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.
Dear members,
I was running aokp_find5_nougat_unofficial_2017-01-26_1250 on my Oppo Find 5. Since installing it I had doubts about the LVM, because the Oppo complained about a shortage of space. Anyway, I read about the lower TWRP version 2.8.7.0 (find5-twrp-recovery-2.8.7.0-en-lvm-f2fs) and installed it. And because I wanted a clean start wiped everything I thought necessary.
The phone can come up (power up) and the only thing I see is the white Oppo letters.
I can boot into recovery = TWRP (2.8.7.0) most of the times but sometimes it shows me the newer, I think, 3.0.2.0.., version that I used before.
When I try to fastboot, I only see the letters fastboot... (no chinese characters).
I think I need to fastboot to connect to my computer with xubuntu 16.04 and adb and fastboot software installed.
When I connect the usb cable while Fastboot... is on screen, I can see it connects but only shows one sub-folder. When I try to move the zips into it only 12 bytes are transferred.
Most of the messages about the SDcard (built-in) mention a SDcard 0 bytes big?
I think the most urgent question is how to get fastboot to really connect with my computer?
Please advise,
pablo k
P.S.: I tried adb sideload - not really knowing what I was doing:
Downloads/OppoFind5$ adb sideload aokp_find5_nougat_unofficial_2017-05-22_1000.zip
loading: 'aokp_find5_nougat_unofficial_2017-05-22_1000.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
-------------
Please advise.