Database Users

ADB works but fastboot does NOT

I don't know what's going on, and I've been searching for an answer to this for the past 2 hours. I have the latest SDK installed. I'm running the cm7 alpha build, latest one. ADB seems to work just fine. I just typed
adb reboot bootloader
bam, my mt4g is in fastboot mode.
I then typed
fastboot flash splash1 splash.img
and fastboot is not a recognized internal or external command, operable or batch file.
Seriously getting frustrated. I'm gonna smoke a bowl and come back a little more calm. lol

http://dl.dropbox.com/u/11228290/fastboot
Put that in c:\windows\system32
then try your command again.
And then ship the bowl this way.

I'm about to try this. If it works I'm gonna kiss you. Its been hell and a half trying to find this answer. lol
Sent from my HTC Glacier using XDA App

No go. Still the same error.
Sent from my HTC Glacier using XDA App

/b/rotherJudas said:
No go. Still the same error.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
oh. My bad, thats the linux version. You need the windows version. I have a .bat for that.
Just run the file called adbonly.bat
and feel free to look through the file if you get scared that it asks for admin rights. Just needs to be elevated to write to system32. Then you can run your command from anywhere.
I actually made this as part of a seperate project, but it comes in handy if you need adb and fastboot quick and convenient like.

I finally figured this out. When the sdk updated (changing ADBs location from \sdk\tools\ to \sdk\platform-tools\ it didn't move fastboot.exe or any other files. All I had to do was cut all the files from \tools\ and paste to \platform-tools\
Hopefully this wont cause more problems down the line, which it ALWAYS does with winblows. Lol.
Sent from my HTC Glacier using XDA App

/b/rotherJudas said:
I finally figured this out. When the sdk updated (changing ADBs location from \sdk\tools\ to \sdk\platform-tools\ it didn't move fastboot.exe or any other files. All I had to do was cut all the files from \tools\ to \platform-tools\
Hopefully this wont cause more problems down the line, which it ALWAYS does with winblows. Lol.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yeah that happens. But I swear my .bat would have worked too. lol.

I'm sure it would have. After running your cm7 rom I have total faith. I just didn't want to edit too many system folders on this craptop. Its my 4 year old sisters. Lol.
Sent from my HTC Glacier using XDA App

Thank you so much. I spent an hour last night trying to get clockwork on my friends MT4G and had the same problem.
Looked at my comp when I read this post this morning and that was it, fastboot was still in the old tools folder.
Don't you love how "correcting" our state of mind can change how we see things.
Thanks again.
Sent from my HERO200 using XDA App

pdug said:
Thank you so much. I spent an hour last night trying to get clockwork on my friends MT4G and had the same problem.
Looked at my comp when I read this post this morning and that was it, fastboot was still in the old tools folder.
Don't you love how "correcting" our state of mind can change how we see things.
Thanks again.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Yeah, lol. I knew it would be something stupid like that. I'm not sure if my environmental variable was set up wrong or what. I have it set to C:\AndroidzSDK\
Should I set it to C:\AndroidSDK\tools\
Or maybe
C:\AndroidSDK\platform-tools\
?
Sent from my HTC Glacier using XDA App

Please post questions in Q&A section.

So I'm just now installing the SDK on my gf's computer and it puts ADB in /tools and Fastboot in /platform-tools. Fastboot refuses to run.
Code:
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.
What's this about?? I downloaded the sdk.zip (the installer exe wanted me to install the java jdk, which I definitely don't need) and extracted it to C:\android-sdk-windows. Then I ran the SDK manager and installed the platform tools. Should I copy the platform-tools contents into tools or the other way around?
And why would they give me an SDK with a non-working fastboot? Kinda pissed right now...
EDIT - Copied contents of \platform-tools into \tools (DID NOT REPLACE ANY FILES!) and now everything works.
I would still like to know what was going on with this, and is there any advantage to adding the environment variable? I'd like to be able to run commands from any directory if possible, instead of having to cd all over the place.

For those wanting to just root, here's some help

This is for those on ICS only. If you have upgraded to jellybean, this will not work.
There have been other posts, and this one is nothing new, in fact it's a remake of DebugfsRoot so that author gets all credit. I just made a couple of tweaks to help those that might be having a fuss with it. First, this is assuming you are using a windows PC. I don't work on MACs. Next, make sure you have ADB working properly on your PC. To do this:
Go to your start menu and open a command prompt, usually by typing "cmd" in the run blank.
Type adb
If you don't get a whole heap of feedback of how to use adb returned to you, and instead get an error, you don't have it set right. If you're sure you installed the development kit and you have ADB on your PC, do the following:
FIND IT... and add it to your system path variable. adb.exe comes with the root extract, so if you don't have the kit installed, you can use that instead, but seriously, if you want to root and enjoy this hobby to its fullest, install the android kit. The most common location is "C:\Program Files (x86)\Android\android-sdk-windows\platform-tools" - but hey, get this, did you know the asus sync software available from their site also includes it? I just now found that out haha...
To add whichever absolute path to your system path variable, start menu > control panel > system > advanced system settings > environment variables button > In the system variables window, scroll down to path, click it, click EDIT > move your cursor to the very end and add ; again that's (semi-colon) - you'll see other entries there which show you, just follow the pattern. Remember, you only need to do this if your original attempt at typing adb didn't work. Save your settings, return to that command window, and try adb again, you should have better results this time.
Now then, download the root package here:
https://dl.dropbox.com/u/33560221/DebugfsRoot_v1.8.exe
This is the original software with slight enhancements by me...those enhancements are all to the BAT file, and are as follows:
The EXE file is a self-extracting archive which will extract the contents to C:\tabletroot Please don't change this install location. You'll see why in a moment. the RootDebugfs.bat was edited as follows:
Within each push command, I preceeded the file name with C:\tabletroot so it knows exactly where to find what it needs. I found if you just pushed without it, it didn't like it too much.
Last, after each "wait-for-device" command, I added TIMEOUT 120 This forces the batch file to sleep for 2 minutes allowing plenty of time for your tablet to reboot. I found if you didn't do this, it would try to do the next commands way too soon causing failure. This should give enough time for you to get to your desktop before the next command is issued. If you find it's too long and you're ready to go, just press a key and that will kill the clock. If not long enough, edit the batch file with any text editor, and increase the timeout time.
All other files are what was originally found. I didn't update any of the apks or edit any other file than the main batch file. That's it. I used these exact files to root my tf300t on firmware version .30 with no issue of any kind. I hope this helps someone. If you run into trouble, not sure how much help I can be. I'm simply posting exactly what I did. I didn't author anything other than the edits mentioned above. Good luck.

Did the your_path thing and it didn't work.

Could you describe just a bit more which part you're having trouble with and what happened?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

I added ;<your_path> at the end of the path and it did not change anything in the CMD window after imputing adb, when nothing happened before.
I'm sure it's something that I did not do that went wrong.

The your path thing was just a descriptor. You need to replace that with the location of your adb.exe file so it would look like ;c:\program files\ ... and so on. I gave a sample path of where mine is but it could vary between systems.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Well if my previous answer doesn't prove I've never rooted anything...
Where do you DL the adb file from?

Couple Choices
10010110 said:
Well if my previous answer doesn't prove I've never rooted anything...
Where do you DL the adb file from?
Click to expand...
Click to collapse
OK, I will assume you do not have the android development kit installed, so you still have a couple of choices here:
ADB comes with the archive I directed you to download, so if you download it and run the EXE, you'll find ADB inside the newly created folder I mentioned, so using this method, you would add... ;C:\tabletroot
ADB also comes with the ASUS sync software found on the ASUS website. If you have / will download and install this software, the ADB file will be located here: C:\Program Files (x86)\ASUS\ASUS Sync or it might be in C:\Program Files\ASUS\ASUS Sync just depends on the type of system you have. I have a 64-bit OS, so I have a Program Files and a Program Files (x86) folder (the x86 is for 32-bit programs) - in this situation, you would want to add ;C:\Program Files (x86)\ASUS\ASUS Sync or ;C:\Program Files\ASUS\ASUS Sync
Remember if you go with option one, download the archive I provided and run it before you add / test to your path variable, because that's what puts ADB in place. Once you have that all done, just go run the BAT file - after you connect your tablet and can see it on your PC as a media device that is

Clarification
So using this method do we need the blob files or was that just for downgrading, and since we don't need to downgrade using this method, everything that we need is in that self extracting exe file? I'm not interested to unlock bootloader -for now-...just want a few tweaks and to install a few root apps
Sorry, I only have experience rooting a couple HTC devices and they were both 1 touch and rooted.

I hear you, and they are legit questions. This is for rooting only. This procedure doesn't unlock your bootloader, which is why i used it. All you need is in the archive.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Another question, do you have to put the tablet into any special mode in order for the batch file to work? If I remember correctly, the phones just had to be on, plugged in via usb (duh) and the batch files did the rest. The batch file has the 120 second pause, but it seems like it does the first part with -
1. waiting for device to be detected
2. daemon not started
3. daemon started successfully
then it just sits there, and its been longer than 2 minutes...what am I missing?

Only mode i know of is to put it in media mode mentioned above. Also I've read to turn off asus sync found in the sync section of settings.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

HandicapFailure said:
Another question, do you have to put the tablet into any special mode in order for the batch file to work? If I remember correctly, the phones just had to be on, plugged in via usb (duh) and the batch files did the rest. The batch file has the 120 second pause, but it seems like it does the first part with -
1. waiting for device to be detected
2. daemon not started
3. daemon started successfully
then it just sits there, and its been longer than 2 minutes...what am I missing?
Click to expand...
Click to collapse
Either unknown sources, or USB debugging might need to be on.

Ah yes forgot those. I'd do both thankya.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

FYI the batch file does not work with windows xp, I searched and seems timeout is not supported. Sucks having an old OS..
I ran the commands manually and the root worked, so thanks anyway!

rickc3k said:
FYI the batch file does not work with windows xp, I searched and seems timeout is not supported. Sucks having an old OS..
I ran the commands manually and the root worked, so thanks anyway!
Click to expand...
Click to collapse
Wow, I didn't know that. Thanks for the tip.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

[Q] HUGE problem! >:_(

Hi,
I was going to install a ROM on my Nexus, so I made a backup and wiped EVERYTHING. Including the SD card so now in clockworkmod
it can not mount the SD card, I cannot mount it to my computer... I am shaking and my hands are cold... I cant flash any rom HELP NOW!!!! ((((
thanks

No need to panic, its a nexus.
can you adb push a ROM zip to your sdcard?
if you can't then you can always flash a factory image with fastboot and you'll be back to normal in no time.
So take a deep breath and chill.
Sent from my Nexus 7 using xda premium

nodstuff said:
No need to panic, its a nexus.
can you adb push a ROM zip to your sdcard?
if you can't then you can always flash a factory image with fastboot and you'll be back to normal in no time.
So take a deep breath and chill.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have a factory image please tell me how'd I do that in fastboot! (only if they had a begging at knees thing)

ok i will write you some step by step functions to follow in order to get yourself a rom onto your device
Info that is Needed!
Do You Already Have ADB functioning on your Computer
If Yes - Skip to Step 2
If No Proceed from Step 1
----STEP 1----
install the ADB drivers for your device
im going to assume you have a windows machine here so the followthrough will be for windows (i use Win7 but it should be the same)
BOOT YOUR DEVICE INTO RECOVERY WHILE PLUGGED INTO YOUR PC BUT DO NOT CLICK ON ANYTHING
1. Download These Google Drivers for Nexus Devices http://www.themoviedb.org/movie/15092-crank-ii-high-voltage
2. extract the folder
3. press the start button
4. right click on "Comptuer" or "My Computer (XP)
5. Click on Manage
6. in the new window press "Device Manager" on the left
you should see in the tree on the right (a device with a yellow exclamation mark ! probably called nexus)
7. right click it and press update driver software
8. press browse my computer for driver software
9. press let me pick from a list of device drivers on my computer
10. press have disk
11. press browse
12. on the new window navigate to the folder you extracted earlier and select the android_winusb.inf
13. press ok
14. there will either be 1 or 2 options to choose - click Android Composite ADB Interface and then press next
15. tick always trust software from google inc. and then install
your device should now have ADB capablilities
Proceed to step 2
----STEP 2----
this will use adb to push a file to your device while it is in recovery mode which you can then flash
1. Download This - http://www.mediafire.com/?50baad8rykng2j0
these are adb & fastboot binaries which will allow your pc to send files to your nexus via ADB
2. extract the downloaded archive to somewhere easy to remember ( i suggest C:\fastboot )
3. rename your downloaded custom rom to rom.zip (for simplicity) and copy it to the extracted directory (the one with adb.exe & fastboot.exe)
4. bring a command prompt to this directory
- in the directory you extracted (c:\fastboot) hold shift and right click in a blank area of the main window
- click "open command window here"
or
- Windows Key & R
- in the new box type cmd then press enter
- type cd c:\fastboot (where c:\fastboot is the directory where you extracted)
now to push it over
5. in the cmd window type adb devices and make sure your device is listed
your should see something like
list of attached devices
XXXXXXXXXXXXXXXX Recovery
where XXXXX is your devices serial number
6. in your cmd window type adb push rom.zip /sdcard/
this will take a while to complete but once it is down go back to your device and try to install a rom as you usually would
you should see the file in your internal memory to install now

^^ I was too slow!
First install the android SDK (Google it) then you need to put fastboot in your path you need to open my computer, system properties, advanced system settings, environment variables button at the bottom, then in the bottom window scroll down til you see find path and edit it and add the path to the android SDK and in particular the platform-tools folder.
So if you download the android SDK to your C drive, the path you will be adding will be like ";C:\android-sdk\platform tools" (note the semi colon at the start, important to separate entries)
Once the path is set up you can use fast boot in cmd just by typing fastboot xxxxx rather than typing C:\android-sdk\platform-tools fastboot xxxxx every time.
So next thing is to extract the images to somewhere.
Inside the zip is another zip called image-nakasi-jzo54k,
unzip that til you have .IMG files, system.img, boot.img etc.
then once they are extracted you use cmd to CD to that folder where you have the images and you can start to flash them.
fastboot flash system system.img
fastboot flash boot boot.img
You could just use flash-all.bat but and that will flash them all automatically but will wipe your internal SD.
Sent from my Nexus 7 using xda premium

If you JUST read that, I figured it out, and if I can flash all the partitons correctly, I will punch the thanks button.

cburk01 said:
yay new problem
Ok, so I unzipped it, extracted the thing inside, but it was it a weird format Windows recognized as "file". So, I added .zip to the end. WinRAR opened it, I saw the files, began to extract when an error popped up about the archive being damaged. WTF.
Click to expand...
Click to collapse
What was the name of the file that you had problems with?
the first one is a .tgz file then .tar but the one with the images inside that is .zip (looking at it now)
use 7-zip instead of winzip
Sent from my Nexus 7 using xda premium

nodstuff said:
What was the name of the file that you had problems with?
the first one is a .tgz file then .tar but the one with the images inside that is .zip (looking at it now)
use 7-zip instead of winzip
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Now I REALLY DO have a problem. I flashed boot.img, system.img, userdata.img, everything to the right partitons and still have a problem. Boot loop. Sticks on Google logo. Why? I did everything right. I even tried fastboot boot boot.img, no luck. I saw some people having boot loop problems, too on 4.1.2. So now, until you reply, I am going to try a custom kernel. Scratch that I'm using ToolKit to download and install 4.1.1.

If you flashed userdata.img that means your internal SD is wiped.
did you run flash-all.bat that is in the folder?
It would be no harm to do that now since everything is wiped already.
no matter what its still recoverable so don't worry.
Sent from my Nexus 7 using xda premium

nodstuff said:
If you flashed userdata.img that means your internal SD is wiped.
did you run flash-all.bat that is in the folder?
It would be no harm to do that now since everything is wiped already.
no matter what its still recoverable so don't worry.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
*facepalm* with the SD I already wiped that before I flashed. And I didnt run flashall.bat or what ever its called so I am going in to try that. Ran flashall got some weird radio flashing error so now continuing with ToolKit.

Flash-all.bat just automatically flashes all the images by running one command, it simplifies the process.
It just isn't ideal if you wanna keep your SD contents.
that's why you flash images separately, so you don't flash userdata.img but since you already wiped it then you're good to go.
Sent from my Nexus 7 using xda premium

WOOT!!!!!!!!!!!!!!!!!!!! Although I don't know if my backup will work, my tablet is now booted up into Android 4.1.1. Now I am going to root it, install a ROM, restore my data partition from TWRP, and (hopefully) have what I have been waiting for. A updated, functioning Nexus 7. *mashes thanks button*

Hey, should I update to 4.1.2 THEN root or root on 4.1.1 THEN flash the ROM?

cburk01 said:
WOOT!!!!!!!!!!!!!!!!!!!! Although I don't know if my backup will work, my tablet is now booted up into Android 4.1.1. Now I am going to root it, install a ROM, restore my data partition from TWRP, and (hopefully) have what I have been waiting for. A updated, functioning Nexus 7. *mashes thanks button*
Click to expand...
Click to collapse
Your backup is most likely gone, its stored on the SD card and that is wiped. Unless you have it on your computer, then you are all good.
Glad its back to life and now you know how to fix it if anything goes wrong.
What you learned today is very valuable to know.
It's nearly impossible to kill a nexus device (from a software perspective)
Sent from my Nexus 7 using xda premium
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
cburk01 said:
Hey, should I update to 4.1.2 THEN root or root on 4.1.1 THEN flash the ROM?
Click to expand...
Click to collapse
Update first
Sent from my Nexus 7 using xda premium

Yes, I have my backup on my Macbook (running Windows 7). Thanks for all the useful advice. lol about the Nexus devices are hard to kill thing, I imagined a cockroach. And about the valuable lesson thing, I learned fastboot commands and adb stuff all when I was messing with (then soon after fixing) my HTC EVO 3D. Oh, I love XDA. Thanks again.
-cburk

Dev help needed- make stock image rooted and flashable

As the title states, I am looking for a straight forward tutorial on how to take a factory image and make it rooted and flashable. The image is currently a tgz. I unzipped and it had recovery and bootloader as well as a few other img's, but those 2 will need to be deleted correct?
Sent from my HTC One X using xda app-developers app

dan.kels.r said:
As the title states, I am looking for a straight forward tutorial on how to take a factory image and make it rooted and flashable. The image is currently a tgz. I unzipped and it had recovery and bootloader as well as a few other img's, but those 2 will need to be deleted correct?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
There's a flash-all batch file in the (latest) factory image from Google. If you have Android SDK installed, I imagine running the batch file "should" just work (only thing needed on your end is to put the tablet in bootloader mode, and to make sure the driver is installed, which can also be acquired from Android SDK).
If the batch file doesn't run adb or fastboot on it's own even with the SDK installed, you might have to add the SDK's executable folder to PATH. There's a guide somewhere that explains it pretty well.
The above applies to Windows though. OS X and Linux would run the flash-all.sh file, but I have no idea on what's needed on either OS for the script to work.

Thanks for the reply. I am tracking that i have to run the .sh for linux. but what i want to accomplish is basically making it a stock rooted rom i can flash through custom recovery.
espionage724 said:
There's a flash-all batch file in the (latest) factory image from Google. If you have Android SDK installed, I imagine running the batch file "should" just work (only thing needed on your end is to put the tablet in bootloader mode, and to make sure the driver is installed, which can also be acquired from Android SDK).
If the batch file doesn't run adb or fastboot on it's own even with the SDK installed, you might have to add the SDK's executable folder to PATH. There's a guide somewhere that explains it pretty well.
The above applies to Windows though. OS X and Linux would run the flash-all.sh file, but I have no idea on what's needed on either OS for the script to work.
Click to expand...
Click to collapse

[Q] Help - pushing a file to N4 via ADB on Ubuntu 13.04

Hello.
After quite a bit of searching, both on google, and xda, I was unable to find help for my question. I did the thing that everyone does at some point, and got myself into a bootloop. I cleared my storage of old rom files, downloaded a fresh one, and did a full wipe install. I thought i had a rom backup, but apparently i deleted it too, at some point.
So basically, heres where I stand.
I am on Ubuntu 13.04
My nexus is in recovery (TWRP)
I open up a terminal and navigate to the platform-tools folder.
I do an "adb devices" command and it comes up with one device (a long number ending in 'recovery') im assuming thats my N4
when I do "adb push PA MAKO-3.99-20130823.zip /sdcard/ (thats the rom I downloaded to my computer) however, it doesnt seem to succeed. I get pages and pages of gobbldygook instantly. And no file seems to transfer. (I can go into my file system in recovery and see that no new file exists)
What am I missing? I can post screenshots of the terminal if it would help.
Thanks!

The filename has a space in it. Try renaming it to something without a space like 'PA.zip' and try running the command again.
Sent using xda-developers app

Chromium_ said:
The filename has a space in it. Try renaming it to something without a space like 'PA.zip' and try running the command again.
Sent using xda-developers app
Click to expand...
Click to collapse
That worked! thanks.
I also had to move the file to the "platform-tools" folder using the gksudo nautilus file browser. Thats why it wasnt able to find the file or something... duh me