Related
I have installed Kindle Utility and TWWP and succesfully loaded CM7
I then tried to restore a backup in TWWP but I changed the title of the backuo by adding KF to the end of the folder name.
TWWP said the Backup had loaded succesfully and I rebooted. I am now stuck on the yellow triangle screen.
My computer recognises the kindle being plugged in but about 5 seconds later it disappears.
The ADB status on KFU is offline.
can anyone identify the issue and how to solve it ?
I have looked all over XDA but can't find exactly the same issue.
You need to install TWRP I don't know where you got TWWP
Sorry I Meant TWRP
have you tried to cold-reset (hold pwr ~20sec) then power on again ?
tried that I'm afraid. I also tried getting it to normal mode via KFU by pressing the number in the 5 second window that the computer recognises the fire. KFU says it sent the command then the screen goes black momentarilly then back to the yellow triangle.
Any help would really be appreciated
first you can try to use kfu option 1 - set bootmode to normal
the same manual:
go to the tools directory of kfu and open an (elevated command prompt)
isue following commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
one of them should work
is your kf correctly recognised in device manager ?
normal boot mode -> android composite adb interface
fastboot mode -> android adb interface
if not you can try:
uninstall everything with kindle, adb or unknown device in device manager
click search new hardware and reinstall the drivers
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
Hi,
Thanks for your help I really appreciate people trying to help someone who is out of their depth.
I tried option 1 in the KFU. I did this in the 5 second window that the computer actually recognises the KF. It says it was telling the KF to do something and the KF screen momentarily goes black then back to the yellow triangle and nothing else happens.
I think my issue is that the computer recognises the Kindle fire for about 5 seconds then it disconnects. this happens three times and then it isn't recognised at all.
that says to me the drivers are there but for some reason the KF is breaking the connection. I will reinstall the drivers but if that doesn't work is there any other way to get the computer (running windows 7 if that makes any difference) to recognise the Kindle.
Also any idea of the official name for this fault (stuck on yellow triangle) as this will help me search for solutions.
first can you get into twrp by pressing the power button at startup repeatently till it gets orange ?
that sounds really like a driver issue - ther are a lot of ways
since it seems that your kf is recocnised for a short ammount of time and fastboot is really quick try following:
power down (hold pwr ~20sec) the kf and disconnect
go to the tools directory of kfu and open an (elevated command prompt)
isue following commands:
"fastboot -i 0x1949 oem idme bootmode 4000" if you want to normal boot
or
"fastboot -i 0x1949 oem idme bootmode 5001" if you want to recovery (twrp)
it will say <waiting for device>
connect kf without powering on (does it by itself)
at some point the fastboot command should be done and you can cold-reset the kf
nevertheless you should try to solve your driver issue
you can disconnect the kf and clean up your drivers:
http://support.microsoft.com/kb/315539/en-us
uninstall everything regarding kindle and adb
here is an alternate driver set:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
run install.bat and then update the driver
that's only a loose description that you see how it is done:
if you' asked for a driver:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
if you'r not asked and want to update the driver:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
to power down the computer and power up sometimes helps (no restart - the comp still thinks the kf is connected)
if your not able to figure this out you can try this:
http://forum.xda-developers.com/showthread.php?t=1430038
since it seems that your kf is recocnised for a short ammount of time and fastboot is really quick try following:
power down (hold pwr ~20sec) the kf and disconnect
go to the tools directory of kfu and open an (elevated command prompt)
isue following commands:
"fastboot -i 0x1949 oem idme bootmode 4000" if you want to normal boot
or
"fastboot -i 0x1949 oem idme bootmode 5001" if you want to recovery (twrp)
it will say <waiting for device>
connect kf without powering on (does it by itself)
at some point the fastboot command should be done and you can cold-reset the kf
Hi,
Thanks for taking the time to help me on this. If I ever get it sorted is there a way i can donate funds to you - or a charity of your choice.
I'm in the UK so at work and will try all this later but in the meantime could you clarify a few things (Sorry !)
i have tried holding down the power button until it goes yellow and it still stays at the yellow triangle (is this the same as pushing it constantly). If not I will try the other way
I've also tried using KFU option 1 in the 5 second window that the Kindle is connected and it says it has sent the command and the yellow triangle goes off momentarily and comes back - should I have cold reset the kindle at this point (how do I do that ?)
If KFU option1 doesn't work is there still a chance that the command line will work ? If so I will try it.
I will try and delete the drivers but the only time I see them is in the window of 5 seconds when the kindle connects. I will look on msn to see how else I can do this.
If I do all this succesfully and it still doesn't work then is my best bet your linux solution ?
Thanks for helping
wigsey said:
Thanks for taking the time to help me on this. If I ever get it sorted is there a way i can donate funds to you - or a charity of your choice.
Click to expand...
Click to collapse
no - i do this cause i like to help others if i can and what is xda for - thank's
i have tried holding down the power button until it goes yellow and it still stays at the yellow triangle (is this the same as pushing it constantly). If not I will try the other way
Click to expand...
Click to collapse
holding don't work for most people
I've also tried using KFU option 1 in the 5 second window that the Kindle is connected and it says it has sent the command and the yellow triangle goes off momentarily and comes back - should I have cold reset the kindle at this point (how do I do that ?)
Click to expand...
Click to collapse
you can start the kfu command - it says <waiting for device> and runs some minutes before timing out - cold reset is holding the power button till it turns off (~20 sec)
If KFU option1 doesn't work is there still a chance that the command line will work ? If so I will try it.
Click to expand...
Click to collapse
yes - because you have better control - i prefer to do things manually
I will try and delete the drivers but the only time I see them is in the window of 5 seconds when the kindle connects. I will look on msn to see how else I can do this.
Click to expand...
Click to collapse
read the microsoft article i provided in my last post - it's exactly how to do this
If I do all this succesfully and it still doesn't work then is my best bet your linux solution ?
Click to expand...
Click to collapse
if you can't get rid of the windows drivers - yes
I will try and delete the drivers but the only time I see them is in the window of 5 seconds when the kindle connects. I will look on msn to see how else I can do this.
read the microsoft article i provided in my last post - it's exactly how to do this
I read the article but it's for windows xp. I've been working on a windows 7 machine. is it the same for that.
If notthen I do have an XP machine I could try from scratch as it has no drivers on it (or if it has I can take them off with the articles help]. In that case will KFU run on a windows xp machine in the same way as on windows 7 [i.e paste the folder on the C drive]. That may be an easier option if so.
Finally so if the Fastboot says it's worked do I have to do the soft reset [ie wait for the fastboot to say it's sent then hold the power button in for 20 secs - which I haven't done yet] or will it automatically reset (which it hasn't done previously).
wigsey said:
I read the article but it's for windows xp. I've been working on a windows 7 machine. is it the same for that.
Click to expand...
Click to collapse
it should be the same for 7
If notthen I do have an XP machine I could try from scratch as it has no drivers on it (or if it has I can take them off with the articles help]. In that case will KFU run on a windows xp machine in the same way as on windows 7 [i.e paste the folder on the C drive]. That may be an easier option if so
Click to expand...
Click to collapse
xp will be the better choice cause you don't have to hassle with 32/64 bit drivers
and the uac (user access control) - means you don't have to run the shell as administrator
Finally so if the Fastboot says it's worked do I have to do the soft reset [ie wait for the fastboot to say it's sent then hold the power button in for 20 secs - which I haven't done yet] or will it automatically reset (which it hasn't done previously).
Click to expand...
Click to collapse
if you did with kfu it should automatically reset - look exactly at the output of kfu - anyway-a manual reset after a minute will not harm in this case
that is what i mean if i say i like to do things manually cause of better control ...
i doubt kfu is doing the command correctly ...
Tried all the above (except Linux which I'm now trying).
I managed to delete the drivers but couldn't reinstall any as the kindle is detected for 3 seconds then stops being detected.
Is there any way to put a driver in without the device being there ?
wigsey said:
Tried all the above (except Linux which I'm now trying).
I managed to delete the drivers but couldn't reinstall any as the kindle is detected for 3 seconds then stops being detected.
Is there any way to put a driver in without the device being there ?
Click to expand...
Click to collapse
that's not possible - what about the xp machine ?
On XP it shows as Unknown Device.
In XP I have run the Bat file but no adb seems to appear anywhere. When I try to install the kindle drivers it says that they are not suitable.
Any ideas on what I'm doing wrong.
There has been one slight change in that I ran the command prompt to go to recovery (before I deleted the driver) and now the Kindle is still stuck on the yellow triangle but the switch goes orange two seconds after turning on.
Could this means I have more than a fastboot issue and if so is Linux likely to fix it ?
if you used the alternative driver set the install.bat ensures only a correct adb_usb.ini in the .android folder
this is from post #6 and what to do now:
uninstall everything with kindle, adb or unknown device in device manager
click search new hardware and reinstall the drivers
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
Click to expand...
Click to collapse
if it tells the drivers are not signed -> install anyway
the kf has to be detected correctly in every bootmode, regardless if it's recovery, fastboot or normal
to have the necessary commands on the computer you have to copy KFU to something like c:\kfu - the commands (adb, fastboot) are in the tools folder
I will look at this tonight but can I clarify
1) What does "install.bat ensures only a correct adb_usb.ini in the .android folder" mean. Do I need to do this or is it not necessary. If I need to do it where does it appear in XP
2)Where do the commands come into it. This isn't a driver issue is it. Is this simply to know where to run them from in the command prompt ?
3) I didn't uninstall the unknown device. Do I need to do uninstall or can i just delete it ? If I uninstall does the Fire need to be unplugged.
4)Once I've done 3 do i Do i search new hardware, find the recently uninstalled unknown device and point it at the KFU DFrivers folder.
Many thanks
first:
1. if you used the drivers i provided they should be in "c:\kindle fire drivers"
2. the kindle fire utility should be in "c:\kfu"
1) What does "install.bat ensures only a correct adb_usb.ini in the .android folder" mean. Do I need to do this or is it not necessary. If I need to do it where does it appear in XP
Click to expand...
Click to collapse
the install.bat copies a correct adb_usb.ini to your .android folder under c:\documents and settins\username\. this folder with a correct ini file is necessary for adb to work - and yes you have to do this
then you have to install/update the drivers form "c:\kindle fire drivers"
the file responsible for driver installation is android_winusb.inf and has also all necessary entries
2)Where do the commands come into it. This isn't a driver issue is it. Is this simply to know where to run them from in the command prompt ?
Click to expand...
Click to collapse
in first place you have still a driver issue - if you did the above correctly then your kf is correctly recognised by your computer - if this is done then you think about any commands:
if you have kfu in c:\kfu then you can simply double click "run.bat" in "c:\kfu" and do option 1 and set bootmode to normal
or you can open a command promt and cd to "c:\kfu\tools" - there are all necessary commands - you can test to what your kf is responding (depends on the current bootmode of the kf)
"adb devices" - if it returns a number then you can work with adb commands:
"fastboot -i 0x1949 getvar product" - when it returns "kindle" then you can work with fastboot commands
tell me to what it is responding to know how to do further ...
3) I didn't uninstall the unknown device. Do I need to do uninstall or can i just delete it ? If I uninstall does the Fire need to be unplugged.
Click to expand...
Click to collapse
that's the same - and you don't need to unplug
4)Once I've done 3 do i Do i search new hardware, find the recently uninstalled unknown device and point it at the KFU DFrivers folder.
Click to expand...
Click to collapse
YES !!!
Got the drivers in but the Kindle still connects and then disconnects.
I used the kfu to tell it to go normal mode and now it sits with the green light on and yellow triangle stuck on screen.
If I tell it to go to to recovery through KFU it sits with the yellow light on the on off button and the yellow triangle stuck
I'm beginning to think I may have bigger issues here than fastboot. What do you think
I have very similar issue. I open KFU go to boot mode, then connect my kindle fire and press 1 (normal mode) very fast (it looks like the computer recognizes the device for a couple of seconds only) then triangle disappears and...... I see kindle fire words. I start jumping of joy (for 2 seconds maybe) then the triangle shows up again and nothing happens.
So sad
Following the steps from the thread http://forum.xda-developers.com/showthread.php?p=24124828#post24124828, I lost my device on fastboot command (I followed correctly all the steps).
The device freezes on the startup screen and the PC can't recognize it properly. So the next fastboot command stays awaiting the device indefinetly.
The Android ADB Interface still remains untouchable on devices panel, but as an unspecified device. So, Windows doesn't mount the internal storage and consequently it is apparently impossible to change the damages.
Does anyone know something that can be useful?
install the correct drivers for fastboot and go ahead:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
i had the same problem
used this link helped get my device up again
http://forum.xda-developers.com/showthread.php?t=1422832
After upgrading to Android 4.2.2, a new secure feature is introduced to adb. The first time a computer wants to connect to an Android device, a popup window will appear on the screen of the Android device.
I've already upgraded my /opt/android-sdk/platform-tools/adb and I mis-pressed the "No" button on the screen when the popup shows to let me confirm the RSA key! Now there are no more popup windows! No matter how I adb kill-server or even restart my computer and Nexus 7, the popup will not show for the second time, not giving me a second chance to confirm the RSA key...
I tried another Linux computer and the popup window shows correctly. How can I somhow edit the whitelist/blacklist file in Android and let the popup windows show for the second time for my computer? Where is the adb whitelist/blacklist file in Android?
If I recall correctly it doesn't have remember autolocked so it should show up again.
Maybe restart the machine itself or the device.
And this goes without saying but make sure USB debugging is on
There is a "remember" setting when choosing. I know a factory reset will fix it or flashing a new rom if rooted, but that might be a little extreme. But I cannot figure out what app would hold that data, so that might be your only choice if you need adb.
Hi everyone,
I have a Nexus 6P which simply refuses to connect via USB on my Mac (i.e. it doesn't show up as a valid device under adb devices or via Android File Transfer). I believe it was working at some point but it seems to have stopped now. Might be worth noting, I did try connecting it to my car's charger a few months ago but had the worst time with it, it would charge and disconnect every few seconds (may or may not be relevant in this case as it pertains to the USB). I tried a different charger and it works fine with it though.
I have tried a lot of different things (which I'll list below) but have had no luck getting my Nexus 6P being recognized as a device when I connect it to my Mac (or any other). I do have the Developer settings enabled and I am able to switch to MTP but I never get the prompt to change USB mode. Anytime I connect my device, adb devices doesn't list it at all. I tried ADB File transfer as well and that also says "Please connect your device".
Here are some of the things I have tried so far:
1. Used different cables - no luck
2. Used a different mac - no luck
3. Tried a different Nexus 6P with my cable, it works fine (so it is not a cable issue)
4. Tried a different Nexus 6P with my mac, it works fine (so my Mac seems to be OK too)
5. Restarted in recovery mode - no luck
6. Tried removing a bunch of apps in case there was something conflicting - no luck so far
7. Chatted up Google support - They couldn't tell me much outside of the last option - Factory Reset - I have been holding off on that since I want to be able to transfer my files out first but I really want to avoid having to try that before exhausting all other options. They did offer to replace with a refurb'ed device but I had to decline that.
I did create a bug report dump using the device to see if anything interesting showed up and the only thing noticeable there is an exception related to USB. I am putting that info here in case it is useful in helping with this.
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
Any help here is really appreciated! Thanks
desimunda42 said:
Code:
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Click to expand...
Click to collapse
That seems suspicious. Was this taken while the phone was connected to your mac?
Here's my phone's dump while NOT connected to a computer
Code:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
[COLOR="red"] Last key received: blahblahblahblah (not null)
User keys: blahblahblahblah (no exception)
[/COLOR] System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Here it is when connected to computer
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
[COLOR="red"] mConnected: true
mConfigured: true
[/COLOR] mUsbDataUnlocked: false
mCurrentAccessory: null
[COLOR="red"] Kernel state: CONFIGURED
[/COLOR] Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
[COLOR="Red"] Last key received: blahblahblahblah (not null)
User keys: blahblahblahblah (no exception)
[/COLOR] System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Are you on a custom rom? Do you get an authorization prompt if you call "adb device" after doing "Revoke USB debugging authorizations" from Develop options?
adotkdotjh said:
That seems suspicious. Was this taken while the phone was connected to your mac?
Are you on a custom rom? Do you get an authorization prompt if you call "adb device" after doing "Revoke USB debugging authorizations" from Develop options?
Click to expand...
Click to collapse
I wasn't connected to my Mac at the time I pulled the report (I confirmed by repeating it just now and still get that 'FileNotFoundException" in the logs for USB device. I don't have a custom rom, I have the standard OEM from the Google Store and didn't do anything else with it.
Also, I did revoke the USB debugging auth multiple times and inspite of that I never get any prompt when I connect.
I also got the report while connected to the Mac and am still seeing the same exception:
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
desimunda42 said:
Hi everyone,
I have a Nexus 6P which simply refuses to connect via USB on my Mac (i.e. it doesn't show up as a valid device under adb devices or via Android File Transfer). I believe it was working at some point but it seems to have stopped now. Might be worth noting, I did try connecting it to my car's charger a few months ago but had the worst time with it, it would charge and disconnect every few seconds (may or may not be relevant in this case as it pertains to the USB). I tried a different charger and it works fine with it though.
I have tried a lot of different things (which I'll list below) but have had no luck getting my Nexus 6P being recognized as a device when I connect it to my Mac (or any other). I do have the Developer settings enabled and I am able to switch to MTP but I never get the prompt to change USB mode. Anytime I connect my device, adb devices doesn't list it at all. I tried ADB File transfer as well and that also says "Please connect your device".
Here are some of the things I have tried so far:
1. Used different cables - no luck
2. Used a different mac - no luck
3. Tried a different Nexus 6P with my cable, it works fine (so it is not a cable issue)
4. Tried a different Nexus 6P with my mac, it works fine (so my Mac seems to be OK too)
5. Restarted in recovery mode - no luck
6. Tried removing a bunch of apps in case there was something conflicting - no luck so far
7. Chatted up Google support - They couldn't tell me much outside of the last option - Factory Reset - I have been holding off on that since I want to be able to transfer my files out first but I really want to avoid having to try that before exhausting all other options. They did offer to replace with a refurb'ed device but I had to decline that.
I did create a bug report dump using the device to see if anything interesting showed up and the only thing noticeable there is an exception related to USB. I am putting that info here in case it is useful in helping with this.
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
Any help here is really appreciated! Thanks
Click to expand...
Click to collapse
I usually only get the key prompt for ADB authorzation when I connect my device and type "adb devices"..... If worse comes to worse, You can restore your phone to factory settings without wiping your sd card. Then you could test that option with compromising your data. Just flash each image from the archive yourself when restoring the firmware as opposed to using the flash-all scipt, or resetting the phone from settings... DO NOT flash the "userdata.img" included in the factory firmware archive or issue the command "fastboot format userdata" during the restore process and all of your files will be fine. This may be an option as long as fastboot is still functional on your device. Ive come across so many different devices in so many different conditions over the years, as long as the device could power on and the usb port was functional, fasboot has worked time and time again.
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac. Youll have to pull up your terminal and and direct it to the folder containing adb and fastboot. Its usually ina a folder called "platform-tools" Which can be found in the dictory in whch you installed the Android SDK or SDK Tools packages... Now that I think about it, you have to download adb from the SDK package I just mentioned. After doing so, youll find the platform tools folder and it should contain what you need. As long as java is correctly installed on your mac then everything should work once you issue the "adb devices" command in a terminal session thats points at the "platform-tools" folder. YOU ALSO HAVE TO HAVE JDK INSTALLED in order for it to work with your device. I just looked at what you posted and it looks like youred missing JDK"...
If you havent done any of this yet the thats the problem. If everything I just typed seems confusing then you can try this which explains everything you need to do to set up adb a whole lot better than my attempt above lol buts its going to take some time to accomplish https://seo-michael.co.uk/how-to-setup-adb-on-os-x/
or
You can also install and configure adb a whole lot easier by issuing the following commands from within your mac terminal.... (This will install Brew on your Mac, if you arent familiar with what it is, Its a software distrobution platform. Sort of like git hub and linux software repos. When in doubt, do a little reading first. It'll solve all your problems....
-Install Brew - Copy and paste this command into a mac terminal and follow the prompts that show up.
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
-Once that finishes, next use this command
brew update && brew cask install java
-Once that is complete enter this last command
brew install android-platform-tools
Those 3 commands will do 99 percent of the work. When its done just find the platform tools folder and go from there. Hope this helps.
Sass86oh said:
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac. Youll have to pull up your terminal and and direct it to the folder containing adb and fastboot. Its usually ina a folder called "platform-tools" Which can be found in the dictory in whch you installed the Android SDK or SDK Tools packages... Now that I think about it, you have to download adb from the SDK package I just mentioned. After doing so, youll find the platform tools folder and it should contain what you need. As long as java is correctly installed on your mac then everything should work once you issue the "adb devices" command in a terminal session thats points at the "platform-tools" folder. YOU ALSO HAVE TO HAVE JDK INSTALLED in order for it to work with your device. I just looked at what you posted and it looks like youred missing JDK"...
Click to expand...
Click to collapse
He says he already tried adb devices which didn't list anything. That tells me adb is configured correctly. Otherwise it should've given errors. Plus, he also said another Nexus 6P worked on the same mac.
adotkdotjh said:
He says he already tried adb devices which didn't list anything. That tells me adb is configured correctly. Otherwise it should've given errors. Plus, he also said another Nexus 6P worked on the same mac.
Click to expand...
Click to collapse
Yep
Sass86oh said:
I usually only get the key prompt for ADB authorzation when I connect my device and type "adb devices"..... If worse comes to worse, You can restore your phone to factory settings without wiping your sd card. Then you could test that option with compromising your data. Just flash each image from the archive yourself when restoring the firmware as opposed to using the flash-all scipt, or resetting the phone from settings... DO NOT flash the "userdata.img" included in the factory firmware archive or issue the command "fastboot format userdata" during the restore process and all of your files will be fine. This may be an option as long as fastboot is still functional on your device. Ive come across so many different devices in so many different conditions over the years, as long as the device could power on and the usb port was functional, fasboot has worked time and time again.
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac.
Click to expand...
Click to collapse
Thanks for the detailed steps but like adotkdotjh mentioned, I already have a working adb (and it worked fine with a different Nexus 6P on the same mac). How would 'fastboot' work if the computer does not even see my device under list of devices? I've never done any image flashing before so that would be quite an unfamiliar territory but I'd be willing to explore. Where would I get these image files and how do I issue the command to the device while it is not being recognized? Thanks
desimunda42 said:
Yep
Thanks for the detailed steps but like adotkdotjh mentioned, I already have a working adb (and it worked fine with a different Nexus 6P on the same mac). How would 'fastboot' work if the computer does not even see my device under list of devices? I've never done any image flashing before so that would be quite an unfamiliar territory but I'd be willing to explore. Where would I get these image files and how do I issue the command to the device while it is not being recognized? Thanks
Click to expand...
Click to collapse
Fastboot (also refered to as "download mode") is a tool used to essentially reprogram your device in the event that you are unable to enter into recovery mode in oreder to fix whatever issue your device is having. Android devices have 3 working modes, normal function, recovery mode, and fastboot. Number one is obvious, recovery allows you to completely reset your device without using a computer if every other measure youve tried hasn't worked. When you use this feature everything on your device is erased and your phone is completely restored to factory settings. Its convienet becuase not everyone is computer savvy and its to the point. But say you were updating (system update) your phone and accidently dropped it causing the battery to fall out and the device to shut off in the middle of the update process. What will most likely happen is the system partition will become corrupt, causing the phone to stick at the initial boot screen. Usually if that happens you can still access recovery mode and just reset but if for some reason that didnt work you would go to the manufacturers website and download the latest firmware for your device. You put the phone into fastboot mode by holding volume down and then pressing and holding the power button at the same time (while the phone is off).The process varies bydevice, If done correctly you will see on your screen a bunch of info along with Andy (the Android) chillin with his hatch open. You connect your phone to your computer and as long as your computer is set up correctly with adb and fastboot, you now have the abailty to reprogram (flash) your device using a series of commands that are issued from either the command line (windows) or terminal (linux/mac).
YOUR BOOTLOADER NEEDS TO BE UNLOCKED BEFORE CONTINUING. IF YOU DONT SEE A LITTLE LOCK AT THE BOTTOM OF YOUR DEVICE UNDER THE GOOGLE LOGO WHEN YOU FIRST TURN IT ON THEN YOU NEED TO GO TO SETTINGS, ABOUT DEVICE, FIND BUILD NUMBER AND TAP IT RAPIDLY UNTIL YOU SEE A MESSAGE POP UP SAYING YOU UNLOCKED DEVELOPER OPTIONS. GO BACK TO THE SETTINGS MENU AND SELEC DEVELOPER OPTIONS WHICH SHOULD NOW BE THERE AND INSIDE THERES AN OPTION CALLED "ALLOW OEM UNLOCKING" TURN IT ON. AND CONTINUE
Eextract the firmware archive you downloaded which will produce a folder containing 2 ".img files" files, another ".tar" archive, and some script files that you can use to make the process pretty much automated.
There are two of them, one for Windows (flash-all.bat) and one for Linux and Mac (flash-all.sh)....
Open the folder that was extracted from the firmware archive... Hold shift then right click a blank area in the folder. Select "open command prompt here" (Windows)
or
Type in terminal : cd ~/downloads/xxx where "xxx" is the name of the folder that was extracted but make sure that folder is moved to your "downloads" directory first
Then type the following commands:
IF YOU HAVENT UNLOCkED YOUR BOOTLOADER BEFORE THEN THIS IS WHERE YOU WILL NEED TO:
For Mac/Linux type: ./fastboot flashing unlock **Make sure you use the ./ or the command wont be recognized**
For Windows type: fastboot flashing unlock
Select yes on the phone when it asks if youre sure..... BAM, unlocked bootloader.
Your phone is completely free of restrections if you want to install custom firmware now. If not you can relock it after flashing the stock firmare by enterning fastboot mode again and typing
fastboot flashing lock or ./fastboot flashing lock (mac/linux).....
Now we can proceed with flashing the device...
For Windows: flash-all.bat and hit enter. The computer will do the rest.
Linux/Mac: ./flash-all.sh Make sure you use the ./ or the command wont be recognized.
If youre feeling brave you can do the entire process yourself by extracting the files in that second archive that was produced and flash each of them individually using a series of command in a specific order.
The 2nd extracted archive will give you a folder with five .img files
boot.img
cache.img
system.img
recovery.img
userdata.img ***** DO NOT FLASH THIS IMAGE. FORGET ITS EVEN THERE****
Take all five and move them to the original folder that was extracted. There are 2 other .img files that were extracted from the first archive also like I mentioned above, one that says "BOOTLOADER.xxx.xx.img" and one that says "RADIO.xxx.xxx.img"... Rename RADIO.xxx.xxx.img to | radio.img |and the other to| bootloader.img |ALL LOWER CASE keep them in that folder along with the other five. Now you should have 7 total image files in one folder. (Its smart to use the folder that your command prompt or terminal was opened in, if you decide to use a different folder then you have to direct each fastboot command to the folder where the .img file is located.
from the command line you flash each img individually with the following commands.....
(Mac/Linux need to include ./ before every fastboot command begins like this: ./fastboot or it wont work.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader (phone will reboot then go back into fastboot mode, dont worry should only take seconds)
fastboot flash radio radio.img
fastboot reboot-bootloader (reboots again)
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot format userdata (this command takes place of the "userdata.img" file I told you to forget about)
fastboot reboot
As long as you see action on the screen and a "complete" after every command then youre in business. If you get an error check your spelling. THE COMMAND LINE IS CASE SENSETIVE. You might type the correct words but if one letter is capital the command wont work. If theres an extra space between words then the command wont work so check everything. Safe rule: Everything should be in lower case letters with 1 space after every word.... THIS S*** MATTERS
Its not as hard as it seems if you arent familiar with the process, but its also not something to mess with unless youve done your homework. Read up on it, there are so many good posts and people in here so you'll be able to find everything you need without any issue.
Fastboot can also be used to install a custom recovery like TWRP which would then allow you to install custom firmware (roms) on your device as long as theres support for it. Nexus devices are built for that very reason! They tend to have a huge selection of development within the Android community. They come with Android as Google intended it to be! No extra BS.... And its wicked easy to unlock the bootloader. That is why they are, in my opinion, the best Android devices available. But someone who doesnt really care much for things like modding and installing custom firmware might see the Nexus as plain device which lacks the bells and whistles included in other devices. Which is ok! I personally love the simplicity of pure Android and the whole philosophy behind the Nexus Program. To each is own! If you need anything else send me a message!
Have not read it all on here lol install this on your Mac https://www.android.com/filetransfer/ and see if it sees you 6p make sure you plug in them change from charging to file transfer on the phone then exit out of the app and reboot that will tell you if your Mac sees your phone
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.