Related
Okay, this guide is for users with less experience and want to overclock their Kindle Fire. This is for Windows.
This section is if you haven't installed ADB yet
1) You need to download the Android SDK
Android SDK: http://developer.android.com/sdk/index.html
2) Open the SDK Manager and install the SDK Tools and SDK Platform Tools
3) You need to add the ADB path. First find where you installed the Android SDK.The default is in C:\Program Files\Android\Android-sdk or C:\Program Files (x86)\Android\Android-sdk, you can check in the SDK Manager at the top, it will tell you your path. Then click on the start button, and right click on my computer and hit properties. Then on the left click Advanced System Settings In the next box at the bottom is Environment Variables click on this. Under System Variables find the variable that says Path DO NOT DELETE THIS VARIABLE! Hit Edit and at the the end put:
;YOUR ANDROID SDK PATH\tools;YOUR ANDROID SDK PATH\platform-tools
Then hit OK.
ADB install tutorial is now finished
4)Now we want to add the correct drivers. There are a couple of ways to do this, this is the way I do it. Again right click on My Computer, and click properties. Now in the top left corner is Device Manager click on this. Now find where it says Kindle and right click it. Click the drivers tab and then Update Drivers and then browse my computer for driver software. Then click, let me choose from a list on my computer and click adb interface, and then either a ADB Testing Interface, or fastboot Interface, both work for what we are doing.
5) The next thing you want is a kernel so download and put in the \platform-tools folder.
IntersectRaven's: http://forum.xda-developers.com/showthread.php?t=1382999
DoomLord's: http://forum.xda-developers.com/showthread.php?t=1372625
6) Plug your Kindle Fire into your computer
7) Open a CMD window. Hit start and run CMD.exe or search for CMD. Then type into cmd:
adb shell
idme bootmode 4002
reboot
8) Open another CMD and type cd YOUR ANDROID SDK PATH \platform-tools. Then type:
fastboot boot NAME OF KERNEL.img
9) Now your Kindle will reboot, make sure it boots! Now that you have verified that it works we are ready to flash it.
10) Shutdown your Kindle Fire.
11) Use your old CMD with fastboot, and type:
fastboot flash boot NAME OF KERNEL.img
12) It will probably get stuck in booting at this point. With the fastboot CMD type:
fastboot oem idme bootmode 4000
it will say waiting for device, do not close this CMD!
13) Now hold down the power button until your device turns off. Then turn it on again, and the command will register.
14) Let your Kindle Fire boot and enjoy your new kernel!
If this doesn't work please leave a comment, or if I forgot anything, I am kind of tired while writing this. I may add pictures later. Thanks!
All this does is boots the custom kernel a single time (which you MUST do to test it). You still need to flash it.
Sent from my Gingervolt-ed VS910 4G using xda premium
Sorry, I will add the rest soon, slipped my tired mind.
do we really need the whole android and java sdk ?
the only commands used is adb and fastboot.
woud'nt the tools directory of KFU be enough since it contains the necessary commands ?
furthermore the driver installation is a essential part for correct operation of adb and fastboot
and don't forget so say your how-to is for windows
I haven't looked at the KFU much yet, so I don't know. I added that it is for windows and removed the java sdk. And added how to flash the kernel.
Accessory mode suppot
Are any Fire kernels available that support Accessory Mode aka ADK.
The changes that need to be made to the kernel are available from Google. They are in the main 3.x kernel source tree and in the samsung source tree of the 2.6.35 kernel.
i'm VERY new to all of this, and i promise i tried my hardest to find an answer in existing threads and google, but haven't found anything to help with my prob:
I tried (?) to root kindle fire [android police thingy], not sure if I succeeded or not (had a lot of "device not found" at the beginning) and tried to install RTL languages support at the same time.
I haven't installed any "TWRP" or "firefirefire" or anything like it.
after the reboot at the end of the RTL, the kindle got stuck on "kindle fire". I tried 20 second power button for several times, on and off power.
kindle fire utlity ("run") says:
adb status: online
adb rooted: no
boot status: 4000
when trying to root through this (temp root), i get: adbd cannot run as root in production builds.
I get the same phrase trying to do anything on the utiility.
Can I do anything to save this from being a 200$ coaster?
THANKS!
you can try to install fff and twrp with kfu (option 5)
then copy one of the prerooted stock images to sdcard:
http://forum.xda-developers.com/showthread.php?t=1402440
would recommend the secure one
and install with twrp:
http://forum.xda-developers.com/showpost.php?p=20543289&postcount=47
imageshack. us/photo/my-images/515/brickc.jpg/
(delete spaces)
i get about the same thing for every option i choose.
any other option?
(and THANK YOU for answering so quickly)
open an (elevated) command prompt in the tools directory of kfu and type in:
adb shell
copy and paste what you get back
b63 said:
open an (elevated) command prompt in the tools directory of kfu and type in:
adb shell
copy and paste what you get back
Click to expand...
Click to collapse
$ sign.. (waiting does nothing, "enter" produces yet another $ sign :X )
that is very good - you did not mess up your shell !!!
ok - what version of kfu do you have ?
would recommend the newest one - 0.9.2 - extract it to c:\ and rename the folder to "kfu" so that it looks c:\kfu
then give it a retry with option 3 and then 5
please copy and paste the output that i can see what it is doing
b63 said:
that is very good - you did not mess up your shell !!!
ok - what version of kfu do you have ?
would recommend the newest one - 0.9.2 - extract it to c:\ and rename the folder to "kfu" so that it looks c:\kfu
then give it a retry with option 3 and then 5
please copy and paste the output that i can see what it is doing
Click to expand...
Click to collapse
the kf is on 6.2.1 and the kfu is 0.9.2.
img521.imageshack .us/slideshow/webplayer.php?id=brick2m.jpg
(again, delete space)
on the first attempt with no. 5, it started downloading something but my internet went bad and the dl stayed on 52%. I manually downloaded the file and named it "recovery" (in the correct folder). after that, i got the message in "brick 3"
and another thing - even though i keep getting "adb rooted: no", after each time i "root", the device reboots, but it doesn't reboot after the "installation" of the twrp.
that with the recovery was right - it has to be recovery\recovery.img
the file should be ~10mb - maybe we have to do it manually
the problem is that burritoroot is allready installed and kfu can't gain root
you did not install burritoroot with kfu ? (kfu has a special version)
therefor we get the message "... can not run on production builds"
now we can look where the file is located and install with kfu or
install fff and twrp manually
i think in this case it will be easier to install manually:
first fff 1.2 manuell:
•download from here:
http://forum.xda-developers.com/attachment.php?attachmentid=850008&d=1326179460
•extract to the folder where adb.exe & fastboot.exe is located
•"adb shell idme bootmode 4002" & "adb reboot"
•flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
second twrp manuell:
•copy recovery.img which you downloaded and renamed to the folder where adb.exe & fastboot.exe is located
•install with "fastboot -i 0x1949 boot recovery.img"
now we reboot into recovery:
•"fastboot -i 0x1949 oem idme bootmode 5001"
•"fastboot -i 0x1949 reboot"
now we should have the recovery system installed ...
b63 said:
i think in this case it will be easier to install manually:
first fff 1.2 manuell:
•download from here:
http://forum.xda-developers.com/attachment.php?attachmentid=850008&d=1326179460
•extract to the folder where adb.exe & fastboot.exe is located
•"adb shell idme bootmode 4002" & "adb reboot"
•flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
Click to expand...
Click to collapse
itmw,
"adb shell idme bootmode 4002" (in c:\KFU\tools)
gave me:
"<idme> invalid permission"
(and thank you again for all the help)
RYuval said:
itmw,
"adb shell idme bootmode 4002" (in c:\KFU\tools)
gave me:
"<idme> invalid permission"
(and thank you again for all the help)
Click to expand...
Click to collapse
looks like you have messed up the permissions !
ok - then we use this to get into fastboot:
download this and extract in the tools folder:
http://forum.xda-developers.com/attachment.php?attachmentid=833582&d=1325144494
then:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
now we should continue the steps above
b63 said:
looks like you have messed up the permissions !
ok - then we use this to get into fastboot:
download this and extract in the tools folder:
http://forum.xda-developers.com/attachment.php?attachmentid=833582&d=1325144494
then:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
now we should continue the steps above
Click to expand...
Click to collapse
those steps went fine.
but now we're back to "error: device not found"
reinstalled the drivers, shut down, restarted and reinstalling again to see if it helps. (maybe it's just me, but it feels like anything that can go bad, does. )
RYuval said:
those steps went fine.
but now we're back to "error: device not found"
reinstalled the drivers, shut down, restarted and reinstalling again to see if it helps. (maybe it's just me, but it feels like anything that can go bad, does. )
Click to expand...
Click to collapse
that's quite normal
what say your device manager about adb or kindle ?
b63 said:
that's quite normal
what say your device manager about adb or kindle ?
Click to expand...
Click to collapse
until recently, "adb android device" or something like that..
now it says the driver does not suit 64bit... (currently: unknown USB device)
it should say "android adb interface"
update the driver with the one from c:\kfu\drivers - they can 64bit
if it does'nt work you can run install_drivers.bat from c:\kfu - maybe 2 times
for information in device manager:
normal boot (4000) -> android composite adb interface
fastboot (4002) -> android adb interface
b63 said:
it should say "android adb interface"
update the driver with the one from c:\kfu\drivers - they can 64bit
if it does'nt work you can run install_drivers.bat from c:\kfu - maybe 2 times
Click to expand...
Click to collapse
for some reason, that still doesn't work..
and the driver was properly installed earlier..
RYuval said:
for some reason, that still doesn't work..
and the driver was properly installed earlier..
Click to expand...
Click to collapse
for normal boot - have you ever been/worked in/with fastboot mode ?
we have to get the right drivers for every mode working
i just switched my kf to fastboot and return to normal boot to verify
try to update the driver manually (select manually)
alternately you can delete every driver with kindle or adb and then unplug and replug the kf
that' only a loose description that you see how it is done:
if you' asked
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select okay and okay
just in case you'r not asked:
-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 okay and okay
will be updated (drivers installed.) the name's without "composite"
if you have a 32 bit pc - that's the better choice
what os is it ? xp 7 or ?
on the 32 bit you can try an alternate set
download it from this post:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
and run the included batch and then install the driver
b63 said:
if you have a 32 bit pc - that's the better choice
what os is it ? xp 7 or ?
on the 32 bit you can try an alternate set
download it from this post:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
and run the included batch and then install the driver
Click to expand...
Click to collapse
i have 32bit win7 (and 64 on win7)
it identified as an "adb interface device" but still "device not found" on cmd..
RYuval said:
i have 32bit win7 (and 64 on win7)
it identified as an "adb interface device" but still "device not found" on cmd..
Click to expand...
Click to collapse
device not found on what command ?
your on an elevated command prompt (as administrator) ?
fastboot -i 0x1949 getvar product
it should return "kindle"
Ok, so I did something stupid, I tried to install a slider lock theme on my kindle and probably screwed up the Framework-Res. I did not have TWRP or a backup of any kind.
Now the kindle just sits at the boot splash screen.
The device was running on 6.2.2 and most tutorials seem to be made for 6.2.1
I have tried a few manual commands but remount is just say "Operation Not Permitted" (I cant figure out how to fix this either.
Running automated programs like Unbrick Utility just don't work, it says it has completed but you can see a bunch of errors saying it could not copy or not permitted etc...
At this point I just want my kindle fire back even if that means a complete restore, can someone please try to help or point me in the right direction I am about to go insane.
Added Info: To be more exact, I tried to use metamorph to install a slider lock theme, nothing seemed to happen so I closed the app. I thought everything was fine so I put the kindle to sleep, but I could not wake it up. I tried restarting it and that's how I got to were I am now.
Update:
Thanks to b63 I was able to get this fixed, I cant thank him enough.
Ok here is how I got it fixed
First I followed the directions given to me below by b63
he told me to refer to this http://forum.xda-developers.com/show...8&postcount=29 which I did, however When I got to 8 I did something different, I did not need to re install the whole Rom because I had only messed up the Framework-res.apk
So instead I pulled the Framework-res.apk from /system/framework in the official kindle 6.2.2 update.zip
I then used these commands to replace the broken apk on the device and restart in normal boot mode.
4. "adb remount"
5. "adb push framework-res.apk /system/framework/framework-res.apk"
6. "adb shell chown root /system/framework/framework-res.apk"
7. "adb shell chmod 644 /system/framework/framework-res.apk"
8. "adb shell idme bootmode 4000"
9. "adb reboot"
I know that this explanation is not super descriptive but most of what you need can be found below in the thread.
This problem is rather specific to my situation so if you are having the same problem and you can't figure it out send me a PM or reply to this thread.
Anyone? I'm starting to think i should just try to return it.
would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?
b63 said:
would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?
Click to expand...
Click to collapse
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB
Damieok said:
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB
Click to expand...
Click to collapse
ok i see a lot out of this - thanks
would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693
b63 said:
I would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693
Click to expand...
Click to collapse
Ok so I renamed the "Kindle Fire Utility" folder to "kfu" moved it to C:\
(if this is incorrect please let me know.)
And good news, adb shell responds with $, were should I go next. (also I have access to my normal computer now)
Thanks again for helping me out with this.
great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there
b63 said:
great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there
Click to expand...
Click to collapse
Im a little confused at this guide are the commands being entered into adb or in kfu? Were does kfu come into play?
Sorry the guide is a little hard to understand
it' not so complicated as it sounds ...
open a elevated command prompt and cd to c:\kfu\tools
here are all commands you need and where kfu comes in play
- you don't need kfu itself - only the tools folder
- leave the command window open all the time
Issue has been solved see last posts
For some reason when I run "KFU" it says windows cannot find tool/wget and when kfu loads up everything i click says it cannot find path specified. I have tried moving it to C:\ and using cmd... I have also tried earlier versions of kfu but to no avail. i found this http://forum.xda-developers.com/showthread.php?t=1473212 but nothing there helped I dont know what to do can someone please help me..
Sidenote, I have a kindle with 6.2.2 and im using windows 7.
I have rooted a kindle before with kfu and it worked almost flawlessly and that was around kfu 2...
espacially on win7 it seems to be be important to move and rename kfu that it is c:\kfu - it don't like spaces in pathname
check the tools folder of kfu - there should be wget.exe along with all other needed commands - it not -> redownload
i don't double click on run.bat - i use to open a (elevated) command prompt, cd to c:\kfu and enter run.bat
hope this helps ...
That is exactly what i have done it is in c:\kfu no spaces i have used cmd and typed exactly what you said before but when kfu loads it says "adb status offline""adb rooted no""boot status unknown"
I have also redownloaded it multiple times i tried the 9.2 kfu and patched it but that didnt works either i have even tried two different win7 computers and on the other win 7 i tried using kfu 8 but it said adb status offline
what does the device manager say under "android phone" ?
kf is in normal boot mode ?
allready tried a hard reset ? (holding pwr button ~20sec till it turns off - pwr on again)
some other ideas:
restarting adb on pc by issuing "adb kill-server" from the tools directory
checking with "adb devices"
check if you have c:\windows\system32 in your path ("path" at a command prompt)
android adb interface under android phone...
i hit normal boot manually power off and on the KF and the utility is stuck at waiting for device...
kill server goes through but list of devices shows nothing
and path on cmd shows up as c:\users\jamil>
i saw another post that said type set into cmd but that seems to not have done anything
thanks again for helping
this is what path shows
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\jamil>path
PATH=C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Program Files (x86)\AMD APP\bi
n\x86;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System3
2\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-S
tatic
C:\Users\jamil>
Okay so i figured it out no when i right-click run.bat with admin rights it get the windows cant find tool.... but i noticed that when my other kindle gets connected it considers itself to be adb composite device when this one considers it self to be adb interface device or something like that i deleted both of the devices drivers and then i connected the one i am working with now and installed the drivers afterwards and voila... i got it too work thank you very much b63 for all the help
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
b63 said:
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Click to expand...
Click to collapse
I have done what he did and mine still gives the same error
its in C:\kfu
Please note, I can only speak with any degree of certainty about devices bought from Play / Moto. I cannot attest to the accuracy of this information for US carrier versions etc. Anything you do is at your own risk
Contents / Thread overview
Introduction
What is Fastboot?
What is adb?
How to install adb and fastboot
How to test adb and fastboot work
OK Gimme some useful fastboot commands please!
OK Gimme some useful adb commands please!
A little more about using Windows command prompt
Myth Busters
Introduction
adb and fastboot are very useful command line tools. They can be used from Windows, Linux or Mac to carry out tasks on your android device, such as moving and backing up files, rooting and restoring your phone to it's factory state. Understanding how to use these tools could save your phone when you get yourself in trouble. This is especially true of rooted users. Particularly those of you who are "new to the scene". You definitely should read and understand this thread before you do ANYTHING root related.
This thread is not intended to be a non-exhausted reference. It is merely here to give an overview of the most basic of basics
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is fastboot?
Fastboot comprises of 2 components.
1) Fastboot mode on the phone (The Bootloader)
2) Fastboot tool on your computer
Fastboot is a small command line tool that you can use from your computer whilst the phone is connected via USB and you are booted into the bootloader. The most common uses for fastboot are:
Unlocking the bootloader - needed as part of the rooting process
Flashing a custom recovery to the device - needed as part of the rooting process
Flashing factory images - used for saving / trestoring your device back to stock
Being able to do these 3 things are essential before rooting. Many new users skip learning these and use a toolkit to root. As a result, when they mess up and we try to explain what they need to do to fix their issues, it becomes very difficult for us to help as fastboot is not understood. It is YOUR responsibility to understand these things BEFORE you mess up.
What is adb?
adb is another small command line tool that stands for "Android Debugging Bridge". Again, it can be used from a computer connected via USB to your android device. It can be used whilst the device is booted into Android or (if you have a custom recovery), it can be used in recovery too, unlike fastboot (yes, adb and fastboot are NOT the same thing) which can only be used in the bootloader.
adb can be used to push files to (or pull files from) your phone. It can also be used to execute many of the commands available in Linux terminals (Or Android terminal emulators) on the device itself. We're not here to cover all these commands however. We just want to cover the basics.
How to install adb and fastboot
adb and fastboot are very easy to install and can be installed on Windows, Linux and MAC computers. The Windows install can be a little bit more complicated than the other 2 and may need additional drivers installing too.
Windows.
There is a very handy tool that can install adb and fastboot in 15 seconds. It is recommended that you use this to install adb and fastboot. Please see the link immediately below for that tool:
ADB, Fastboot and Drivers - 15 seconds ADB Installer - Really quick and easy way to install adb and fastboot (by @Snoop05). Download links are at the bottom of post 1.
This tool asks if you want to install adb and fastboot (to which you should answer Y) and then creates c:\adb\adb.exe and c:\adb\fastboot.exe
It then asks if you want to install it system wide .. This is asking to install for all windows users. < 15 second installer needs updating to SDK 23, which is required for latest Android versions.
Download the latest SDK (adb and fastboot) versions here: https://developer.android.com/sdk/index.html (Scroll down to SDK tools only) then download the Windows *Installer*.
Open the installer and select "Platform-tools" and install the packages. This should create "C:\Program Files (x86)\Android\android-sdk\platform-tools"
Now we want to set this path as a Windows Environment variable PATH to make the executables work system wide:
right-click computer > properties > advanced > environment variables.
under system variables click "path" and click "edit"
at the end of the line, add the below:
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Please note, the semi-colon ; is VERY important.
You may also need to install drivers.
Here is a link to the Google USB Driver: DOWNLOAD THIS
Code:
To install on Windows 7:
- Ensure existing drivers are uninstalled first*
- Extract the zip to c:\adb (created earlier by the installer)
- Right-click "Computer" > Manage in windows and choose "Device Manager"
- Boot the Nexus 6 to the bootloader (Volume down + Power) and connect the USB Cable
- Watch for any new devices with exclamation marks appearing
- Right-Click the new device > Update driver software
- Choose the "browse" method and browse to c:\adb, find teh folder you extracted then follow the wizard to the end - using amd6 64 if you're on a 64 bit system and i386 if you're on a 32 bit system.
*To uninstall existing drivers, boot into Android and connect the USB cable. Monitor device manager for the device showing up. To uninstall the device, right-click it to uninstall it. At the prompt, ensure you also choose to delete the driver. Repeat this for bootloader and recovery.
Code:
To Install on Windows 8, you may need to additionally disable driver enforcement
- From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the - -- pop-out bar to appear, then click the Gear icon).
- Click ‘More PC Settings’.
- Click ‘General’.
- Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
- Wait a bit.
- Click ‘Troubleshoot’.
- Click ‘Advanced Options’
- Click ‘Windows Startup Settings’
- Click Restart.
Once that is done, your Windows computer is configured for adb and fastboot.
In device manager, the device should show up as below, depending whether you are booted into recovery or bootloader...
Recovery - Android Device > Google Nexus 4 ADB Interface
Bootloader - Android Device > Google Nexus 4 Bootloader Interface
If it shows as something different, either you have existing drivers in the way or something went wrong.
Linux and Mac
Here is a really simple tool to install adb and fastboot on the above OS. The only expectation is you know how to open and run a terminal command. Please see the link immediately below:
Nexus Tools 2.2 (Featured by XDA) - adb and fastboot installer for Linux and Mac (by @corbin052198)
Once you have installed adb and fastboot from the above link, you're ready to go.
How to test adb and fastboot work
As previously mentioned, adb and fastboot are both command line tools. That means you must run these tools from command prompt (cmd in Windows) or Terminal (Linux and Mac).
Remember earlier, I mentioned that fastboot can only be used in bootloader? and adb can only be used in Android (or custom recovery - lets cover that later)? We can use the command "fastboot devices" and "adb devices to see if we have adb and fastboot working correctly.
Lets try it.
Boot your phone into android
Connect it to your computer via USB
Open cmd (start > type "cmd" on Windows) or Terminal (Mac/ Linux
Type in the windows "adb devices" and press enter
Here is what we don't want to see:
Notice how there is nothing underneath where it says "List of attached devices" That means it cannot see any device
Here is what we DO want to see:
We can see that there is now a device listed.
OK lets test fastboot. Unplug the USB and turn off the phone. When it is off, hold down Volume down + power until you feel the vibrate. You will now be in the bootloader. Reconnect the USB cable.
In the same window (cmd or terminal) we're going to now type "fastboot devices".
Again, here is an example of what we don't and do want to see:
If in both modes, you can see your devices "Serial Number", then you know they are both working.
Please note that if you cannot get adb and fastboot to work "system wide", you can open the command prompt to the location of the adb and fastboot executables exist and try from there.
OK Gimme some useful fastboot commands please!
Here are some of the most useful fastboot commands you will come across. Fastboot is used mostly for flashing images to the devices partitions on the internal memory.
Code:
fastboot oem unlock
This unlocks your bootloader and allows you to flash a recovery to root. WARNING, this will wipe your device. Rooting the N6 is essentially unlocking the bootloader, flashing a recovery and then putting the SuperSU zip on your sdcard and flashing it via the recovery. This thread covers rooting: [HOW-TO] The Nexus 6 All-In-One Beginner's Guide by @xBeerdroiDx
Code:
fastboot flash recovery recovery.img
This will flash a recovery.img to the recovery partition. The command is broken down into "fastboot flash" (what to do) "recovery" (where to flash to) "recovery.img" what to flash there. In the terminal or command prompt, you cannot just type "recovery.img" though. It has to be the path to where the recovery image is. For example, if my recovery image is on my desktop, I would have to type:
Code:
fastboot flash recovery c:\users\rootsu\desktop\recovery.img
It is worth noting, that it IS case sensitive, meaning if your file is called Recovery.img, you must type the capital R...
Other things you would flash:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
These will flash the system image (ROM) and boot image (kernel) as you would if you were returning to stock.
A full guide to returning to stock can be found here: [TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot || Relock bootloader by @Mr hOaX
You can also boot into a recovery.img without flashing it...
Code:
fastboot boot c:\users\rootsu\desktop\recovery.img
which is "fastboot boot" (what to do) "c:\users\rootsu\desktop\recovery.img" what to do it with. As you may have noticed, we did not define the recovery partition in this command, that's because we're not flashing it....
OK Gimme some useful adb commands please!
At the moment, we are going to assume you have a custom recovery and you have booted into recovery. The reason for this is using adb in recovery can be much simpler.
Here are some useful scenarios for using adb.
Backup your sdcard to your PC
Code:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
**Please note, some recoveries may "mount data" automatically on boot, so don't be disheartened if you get an error stating device or resource busy. This probably just means you can't mount what is already mounted**
/data/media/0 is the real location of /sdcard for your information. Also referred to as "The mount point". What we have done here is "adb pull" (what to do) "data/media/0" (what to move) "c:\MyBackup" (where to move it to)
Push a zip file from your PC to your sdcard (useful if you wiped your sdcard and rom)
Code:
adb shell
mount data
exit
adb push c:\rom.zip data/media/0
What we have done here is "adb push" (what to do) "c:\rom.zip" (what to move) "data/media/0" (where to move it to)
You can of course also use adb to push and pull files to and from /system too. You just need to:
Code:
adb shell
mount system
exit
I mentioned earlier that using custom recovery is much easier for adb than whilst booted into Android. You need to ensure you have a kernel that allows insecure adb before you do anything with system and data partitions. You also need to ensure that USB debugging has been enabled in developer options.
For example, to mount system to pull files whilst android is running you have to:
Code:
adb root
adb shell
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
...which is clearly a little bit more involved, so I recommend you use recovery for adb push and pull. You can find more detailed information on adb here: http://developer.android.com/tools/help/adb.html
A little more about using Windows command prompt
One thing to understand is that like Windows, command prompt (cmd.exe) works with directories (or folders if you like). The Linux and Mac terminals are the same, but most linux users, we expect you would already know this.
Here you will see I have downloaded a recovery image that I want to flash using fastboot.
As you can see, the recovery.img is located in C:\users\rootSU\Desktop
Usually when you open the command prompt from the start menu, or run command, the command prompt will default to your user location as seen below:
So lets try and fastboot flash recovery recovery.img...
It fails with a not-too-accurate error message. It has failed because you have not told it where the recovery image is. It assumes it is in the directory as listed in the prompt
So, how do we deal with this? Well, there are 3 ways.
1) We tell the command prompt where the recovery.img actully is in the command itself
Success! As you can see, we have told the command that the location for the file is Desktop\recovery.img
2) We can change the directory in command prompt to the directory where the file is. In this example, we change directory to "Desktop". The change directory command is "cd " or in this case "cd Desktop"
3) ...and possibly the simplest method. We hold shift whilst we right-click on the folder we want to change directory to, and directly open a command prompt there:
Another point to make with command prompt or terminals, is if you do a particular command, it is "pre-programmed" to "expect" a particular format of that command.
For example, we know that adb push as a command expects after it . This means the command is actually
Code:
adb push
BUT if you put something AFTER , for example -
Code:
adb push somethingelse
, it will assume that the "somethingelse" is a bad parameter, and the command will fail. It will probably display (or "print" which is the technical term in a terminal) a helpful guide of how the command should be used instead of trying to run the command which it does not understand.
You're probably wondering why I am telling you this. Well quite simply, it is a warning about folder names. Imagine you have c:\users\rootSU\My Documents as a folder. You assume the command is then
Code:
adb pull /data/media/0 c:\users\rootSU\My Documents
but it is not... There is a space in between My and Documents. What you have actually done is
Code:
adb pull Documents
because it uses a space to signify the end of a command or parameter. It is best to avoid using folders with spaces in them. Avoid as much as you can. In the event it is unavoidable (Although when is it ever>) then please surround the path with quotation marks,
Code:
adb pull /data/media/0 "c:\users\rootSU\My Documents"
so that way, it sees everything between the " " as a single parameter.
Myth Busters
Myth 1: You need USB debugging on to use adb and fastboot
If you cannot boot into Android, it doesn't matter. You DO NOT need USB Debugging turned on to use adb outside of android. USB Debugging is an Android ONLY setting. Fastboot obviously also does not need debugging either as this too is outside of Android
Myth 2: to adb push or fastboot flash files, they must be in the same folder as adb or fastboot executables. Sorry but this is rubbish. You can pass the full path of the image you're flashing or file you're pushing in the command and fastboot / adb can be called system wide if you've set them as an environment variable or used the 15 second installer
thanks(im out of thanks). but ill be back to leave one here!!!!!
simms22 said:
thanks(im out of thanks). but ill be back to leave one here!!!!!
Click to expand...
Click to collapse
No worries. Just putting it here for info. It's not a new work, just a slightly amended version of my N5 thread. No need for thanks
rootSU said:
No worries. Just putting it here for info. It's not a new work, just a slightly amended version of my N5 thread. No need for thanks
Click to expand...
Click to collapse
it was up in the n5 threads before, and was needed here. but its here now as well, so thank you
Good guide. Needs to be a sticky. In fact, I think every device general forum should have a sticky like this. Would have saved me a lot of grief back when....
Excellent update.
Very good to see. I'm sure lots of people will be sending noobs here for the basics.
Up to your usual helpful, good work I see.
rootSU said:
This tool asks if you want to install adb and fastboot (to which you should answer Y) and then creates c:\adb\adb.exe and c:\adb\fastboot.exe
It then asks if you want to install it system wide (to which again, you should answer Y)... This then allows you to type adb commands in the command prompt without having to open a particular directory first. You may or may not understand what I mean when I say that, but take it from me, its much more convenient and easier to use this way.
Click to expand...
Click to collapse
Y option = System-wide = install to "C:\adb" and add path for system variable - This mean you can use it by any account on your pc.
N option = Current user only = install to "C:\Users\[YOUR USERNAME]\adb" and add path for user only - Only user account used for installation can actually use it.
So if you say Y or N you will be still able to use it from any directory with cmd.
rootSU said:
It will also ask if you want to install device drivers. Actually, say N to this as we're going to cover that next, using the google USB drivers
Here is a link to the Google USB Driver: DOWNLOAD THIS
Click to expand...
Click to collapse
Drivers in my installer are the one from the link you posted here. I'm not using any modified drivers, just the one that come with SDK. And they are also digitally signed.
I hope you will fix these But still nice work, beginners should understand it :good:
Snoop05 said:
Y option = System-wide = install to "C:\adb" and add path for system variable - This mean you can use it by any account on your pc.
N option = Current user only = install to "C:\Users\[YOUR USERNAME]\adb" and add path for user only - Only user account used for installation can actually use it.
So if you say Y or N you will be still able to use it from any directory with cmd.
Drivers in my installer are the one from the link you posted here. I'm not using any modified drivers, just the one that come with SDK. And they are also digitally signed.
I hope you will fix these But still nice work, beginners should understand it :good:
Click to expand...
Click to collapse
Thanks for the info. I thought system wide meant it was putting it as a path environment variable. Reason I didmt use the drivers from your tool originally is (well I wrote this thread for N5 originally) they didnt work so had to install the universal naked driver. But if yours are the same as the ones linked, I can update that.
rootSU said:
Thanks for the info. I thought system wide meant it was putting it as a path environment variable. Reason I didmt use the drivers from your tool originally is (well I wrote this thread for N5 originally) they didnt work so had to install the universal naked driver. But if yours are the same as the ones linked, I can update that.
Click to expand...
Click to collapse
Path is added in both cases.
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
papeshfoo said:
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
Click to expand...
Click to collapse
Can you be very specific with your issue please?
papeshfoo said:
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
Click to expand...
Click to collapse
Android M no like root, you'll either have to live with stock or wait for chainfire to do his thing.
This all worked well until I had to find my device in the cmd prompt. It listed no devices when I typed in "ADB Devices". The issue I found was with the ADB Interface Driver. I uninstalled it and reinstalled it thinking it might've been a driver issue, but it still wouldn't work. I tried the "Uninstall driver" then "scan for hardware changes" but that didn't work. Finally I found the universal ADB driver and tried using that. STILL nothing. I figured that, because I don't have my device's driver installed, it might've been that, so I tried to DL it and yet again, nothing. I have a Kyocera Hydro Life, if that helps. Also, I tried looking through the "update driver manually" in order to update the driver software by looking through the different ADB interfaces that it had but my Kyocera driver wasn't there. Is it supposed to be there or do I just use one of the ones provided?
I checked my programs and apps and it says that the Kyocera usb driver was installed. Did I do something wrong?
ScottyChaos said:
This all worked well until I had to find my device in the cmd prompt. It listed no devices when I typed in "ADB Devices". The issue I found was with the ADB Interface Driver. I uninstalled it and reinstalled it thinking it might've been a driver issue, but it still wouldn't work. I tried the "Uninstall driver" then "scan for hardware changes" but that didn't work. Finally I found the universal ADB driver and tried using that. STILL nothing. I figured that, because I don't have my device's driver installed, it might've been that, so I tried to DL it and yet again, nothing. I have a Kyocera Hydro Life, if that helps. Also, I tried looking through the "update driver manually" in order to update the driver software by looking through the different ADB interfaces that it had but my Kyocera driver wasn't there. Is it supposed to be there or do I just use one of the ones provided?
I checked my programs and apps and it says that the Kyocera usb driver was installed. Did I do something wrong?
Click to expand...
Click to collapse
Try a different USB port. If that doesn't work try a different USB cable. If that also doesn't work, you could try disabling driver signature checking for Windows.
If those don't work, try this thread > http://forum.xda-developers.com/showthread.php?t=1583801
cam30era said:
Try a different USB port. If that doesn't work try a different USB cable. If that also doesn't work, you could try disabling driver signature checking for Windows.
If those don't work, try this thread > http://forum.xda-developers.com/showthread.php?t=1583801
Click to expand...
Click to collapse
EDIT: I also forgot to mention that the error code that came up while I was in the dev manager was compatibility error code (28) when I clicked on "Device ADB interface".
ScottyChaos said:
EDIT: I also forgot to mention that the error code that came up while I was in the dev manager was compatibility error code (28) when I clicked on "Device ADB interface".
Click to expand...
Click to collapse
Error 28 means drivers not installed. Try the driver help thread that I linked above.
---------- Post added at 12:33 PM ---------- Previous post was at 12:04 PM ----------
cam30era said:
Error 28 means drivers not installed. Try the driver help thread that I linked above.
Click to expand...
Click to collapse
@ScottyChaos,
Just a fundamental question: I assume you have enabled "Developer Options" in Settings, and then checked "enable USB debugging"?
---------- Post added at 12:39 PM ---------- Previous post was at 12:33 PM ----------
[/COLOR @ScottyChaos,
Here is a thread that you might find interesting > http://forum.xda-developers.com/android/help/metro-pcs-kyocera-hydro-life-rooted-t2870678
Windows 10 device driver management is even more locked down then windows 8. I got two of the three drivers loaded but when going into adb mode on the phone through recovery it just disappeared out of the device manager. I had to unplug and plug in while in that mode to trigger a unloaded driver in the device manager. Once there I had to force the adb driver manually with the nasty windows driver warning and all. Once I did that I could see the device in adb mode and sideload my marshmallow OTA. woot!
I decided to drop a thanks bomb...
ADB is good.
But that fastboot.
Seriously, its ONE command. OK, a few different arguments to use.... But it is so easy, and so powerful. People are afraid to mess up on command line, but its actually way harder to type the wrong thing out then to click the wrong thing.
LEARN IT. Forget your toolkit.
You can fix almost anything, Its not too hard for you. It may be new... YOU CAN DO IT.
Also, I have to say it... Its not going to help anyone, but it will keep me from punching something. ADB and Fastboot... Not the same. You don't ADB a new system image....