[Q] Adb is not recognized as an intern or extern command - G2 and Desire Z Q&A, Help & Troubleshooting

Hi, so i'm very new to Android and while attempting to do the gfree permaroot for my desire Z, i came across a problem. When I type the commands, it says that adb is not and intern or extern command. I have adb file in platform-tools (400ko). When i open it, it make a cmd screen for about 2 seconds then shuts down. Can someone help me with this problem
I just installed HTC sync and my computer cannot find any device attached. It says: the htc vision htc port does not repons.
Thanks
Vince

are you doing CD C:/location of adb/adb?
You must direct your command line to the directory of adb.
also run cmd as administrator if you're on vista or win7.
If you're not a command line pro I suggest you just rename your folder to whatever you want in C:/folderhere
For example heres the folder renamed to "android"
then just do CD C:/android
Then type "adb" and hit enter
{
"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"
}
and boom! you're in adb!
Hope this helps
I'm no adb pro but I'm ok at cmd. Maybe I should make a video or something on the basics to getting adb running if there isn't one already?

Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it

Vincethedevil said:
Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it
Click to expand...
Click to collapse
Nah, you still aren't getting it
How did you install ADB? If you search in Windows for the file "adb.exe" what does it tell you?

it's in the platform tools folder in the sdk

Vincethedevil said:
Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it
Click to expand...
Click to collapse
I'm not quite sure what you mean by this, I wonder if you're doing something wrong. Have you followed this guide ? http://forum.xda-developers.com/showthread.php?t=865685
If you have added the correct folders to your path, as explained in the guide, it should find adb ok.
If it's finding adb ok, then if you run "adb devices", is that not showing your phone ? Are you using the original HTC cable to connect to your phone ? Third-party ones sometimes will not work.

Yeah i'm using the original Htc cable. I have downloaded Htc Sync and it appears as "my htc" in device manager. Although, Htc sync doesn't recognize any plugged in phone.
For adb, i go in cmd, change the path with cd to the path where is the adb.exe, then type adb. A series of text follow. Then, i switch to the folder where is gfree (with cd) and type the first line for temp root. That when it says that adb is not recognized as an intern or extern command

Since adb.exe is not located in your gfree directory, it's not a recognized command. You either need to run the commands directly from your platform tools directory (and use the full directory paths for the gfree commands) or place the path for adb in your environment variables so that adb can be called from any directory (step four in the ADB for noobies linked earlier). This is the easier method.

I tried it but it's not working. I'll take pictures tomorrow so my obvious noob error can be spotted

Adding adb to your path
Hey there,
Here's a quick guide to fix your problem (basically, you don't have adb added to your path). Btw, this guide was made on Windows 7, but the principle should be the same for Vista and XP (though the steps are different).
Step 1: Right click "Computer" or "My Computer"
Step 2: On the left side find "Advanced system settings" and click it.
Step 3: On the Advanced tab, click "Environment variables"
Step 4: In the bottom part of the window, scroll until you find the row that starts with "Path" and click "Edit"
Step 5: At the end of the existing line, add a semicolon ( ; ) and the path to your android toolkit. If the path contains spaces, don't forget to enclose it in quote marks ( "C:\path to adb\tools\" )

Vincethedevil said:
For adb, i go in cmd, change the path with cd to the path where is the adb.exe, then type adb. A series of text follow. Then, i switch to the folder where is gfree (with cd) and type the first line for temp root. That when it says that adb is not recognized as an intern or extern command
Click to expand...
Click to collapse
You haven't set the Path up so that it can find adb, as has been said, and that's all covered in the guide that I previously linked to. But the previous poster has provided you with an excellent step-by-step solution.

Thanks alot, my adb problem is now solved! I just have one more question, when i plug my phone, htc sync cannot recognize it. Although, when i write adb devices in cmd, my phone appear. Am I still gonna be able to permaroot or should i mess with the drivers.
Thx
Vince

It's not a driver problem, it's an HTC Sync problem. Your phone has to be in Sync mode and you have to wait a few minutes (mine takes up to 20 mins) for HTC Sync to recognize it.

sounds like you'll be able to root just fine if it recognizes and responds to adb.
Not sure about htc sync, I don't even know what that is...lol

not able to root
i am using this procedure
http://forum.xda-developers.com/showthread.php?t=1601038
as i am running runme.bat i am getting this screen please help

Need to set up adb, there are tons of guides on xda and the web to do this properly, follow one of them and then try your whatever you're doing again
Sent from my Nexus 7 using xda premium

demkantor said:
Need to set up adb, there are tons of guides on xda and the web to do this properly, follow one of them and then try your whatever you're doing again
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
thanx for reply/..
not able to to set up adb.. please help if you can
should i uninstall existing drivers and again install it

You may need to reinstall drivers but first make sure you have the right ones as well as adb.exe download from the sdk or whereever you get it
See the third post. In this thread
http://forum.xda-developers.com/showthread.php?p=31899577
If you're still having issues let me know and ill help ya
Sent from my MyTouch 4G Slide using xda premium

Related

[HOWTO]- Performing a Nandroid Restore Manually using ADB

[HOW TO] Perform a Nandroid Restore via the Android Debug Bridge (ADB)
(This guide assums that you have already installed and set up adb tools on you PC)
1. Start phone in recovery mode, by turning it on while holding "Home" and "Power" buttons.
2. Plug the phone into the PC with a USB cable
3. Start Windows Command Prompt on your PC, by pressing Start on your PC and typing CMD into the run or search bar depending on your operating system. Then selecting Command Prompt.
4. Within the command prompt window, change the directory to the one your adb tools are by typing the following:
cd c:\sdk\tools
Click to expand...
Click to collapse
The path you put in may be different to this example, as it depends where on your PC your adb tools are kept.
5. Then type:
adb shell
Click to expand...
Click to collapse
6. Now type:
mount /sdcard
Click to expand...
Click to collapse
7. Now you need to change directory again to the one holding your nandroid back-up data, so first type
cd /sdcard
Click to expand...
Click to collapse
8. Then type:
cd nandroid
Click to expand...
Click to collapse
9. Now you need to find the specific name for the folder that holds your Nandroid Backup images, so type:
ls
Click to expand...
Click to collapse
and view the list that appears.
10. Now to enter the folder you want to back up to type
cd HT**********
Click to expand...
Click to collapse
obviously replacing the *s with your numbers and letters. FYI the number string is your Device Serial number.
11. Again type
ls
Click to expand...
Click to collapse
and view the list that appears.
12. Now to enter the folder you want to back up to type
cd BCD***-********-****
Click to expand...
Click to collapse
obviously replacing the *s with your numbers and letters. FYI the format of these digits is BCDXYZ-YYYYMMDD-HHMM from when the back up was created.
13. Now type:
nandroid-mobile.sh restore
Click to expand...
Click to collapse
14. Just press enter to select default.
15. Double check that the Default backup that is found is the one you want then press enter again.
Your selected backup will now be restored. When your CMD window looks like the one below you can reboot your phone and it will be as you remember it.
{
"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"
}
A big thanks goes to Pulser, without whom I would still be stuck, and this guide wouldn't have been written.
Nice. But are steps 6-12 really necessary? When in shell it should enough enter nandroid-mobile.sh -r, press enter to get you the list of available backups, pressing enter once again restores the last backup, or if you want an older just type the full name of that backup.
Install apk
Hello Fellow Androids!
If this is off topic, please accept my apologies. I am searching through all of XDA for a simple solution to adding apk. Now before you start bashing, please keep in mind that I am well aware of the "search" options + google + XDA etc.
Long story short, I have:
1) Rooted
2) Fashed many Roms (currently on Stock 2.1)
3) Lag Fixxed (see signature)
4) Removed Bloatware
5) I am familiar with ABD and commands
Problem:
All I'm trying to do is install certain "apk"s using ADB. I am well aware of the Program that installs/ pushes apps automatically that are found in G1 + Vibrant + HTC + Droid Forums without having to do any typin......BUT.....I would like to know my way around ABD <----Main reason why i dont want the easy way out.
I have been here:
http://forum.xda-developers.com/showthread.php?t=716806
as well as here:
http://forum.xda-developers.com/showthread.php?t=743457
even been here:
http://forum.xda-developers.com/showthread.php?t=740545
I know what you are thinking, why not use them? As i said before, i would like to be efficient with ADB. So...
I have tried methods found here:
http://forum.xda-developers.com/showthread.php?t=517874
As well as:
http://forum.xda-developers.com/showthread.php?t=532719
The problem I am having is:
Whether i navigate to my folder (desktop with all my apps) and use either
"adb push app /system/sd/app
adb push app-private /system/sd/app-private"
or simply
"adb install <path to file> - Example: adb install c:/apps/apps2sd.apk"
I always get the error: "cant find <whatever apk> to install"
No matter which directory i have it, i get that message.
Note:
1) I have debugging on
2) I mounted sd <----also tried Without mounting
3) I have used the same command when I removed bloatware but i understand Adding apks are slightly different.
4) I have all the drivers installed + Microsoft's .net framework + etc
What am i doing wrong?
All Critics, input, education bashing (just not hating) lol are welcome. Thanks!
put adb in your path... cd to the apk directory and run adb push *.apk /system....
TylerDurdenK said:
[HOW TO] Perform a Nandroid Restore via the Android Debug Bridge (ADB)
(This guide assums that you have already installed and set up adb tools on you PC)
and view the list that appears.
12. Now to enter the folder you want to back up to type
obviously replacing the *s with your numbers and letters. FYI the format of these digits is BCDXYZ-YYYYMMDD-HHMM from when the back up was created.
13. Now type:
MD window looks like the one below you can reboot your phone and it will be as you remember it.
http://farm3.static.flicn.[/QUOTE]
I get the error "nandroid-mobile.sh not found" after step 13. please help.
Click to expand...
Click to collapse
Dont use this, use jordfaz's clockworkmod, if you really need to use this adb script then you need to get nandroid-mobile.sh script somewhere

[GUIDE] *Rooting the Xoom for Dummies*

***Xoom Rooting Guide for N00bs***​
Hello Xoom Dev community! Sorry. I know you're thinking, "Man! Not another Xoom root guide?!". Lol. But I wanted to make this, so, here ya go...
***WARNING***
-This will erase everything on your xoom. Its like flashing flashing back to stock because of the unlocking process. So BACK everything up before continuing via USB, or your preferred backup app-
**Also, this Tutorial is for the 3G version ONLY. The Wifi model is different and uses an incompatible boot.img. Once again, ONLY FOR 3G MODEL**
Ok. So, rooting the Xoom isn’t really that “hard” of a task. I’m a n00b as well, so I did have a little difficulty doing it. Only because this method requires you to use adb, the command prompt, etc…
Well, I wanted to make a guide that should be ‘n00b-proof’. LOL. It’s really super simple.
**Bofore you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development --> USB Debugging**
Alright, you’re going to need some tools to get it done. First of all, download the Xoom USB drivers. Either get them from motodevs.com --> http://developer.motorola.com, which requires a free membership; or get them from the Motorola/Support site --> http://www.motorola.com/Support/US-EN/Consumer-Support/TABLETS/MOTOROLA_XOOM, and download the ‘motohelper’ program. I prefer the drivers from the dev site because they’re just stand-alone drivers. Motohelper is an actual app that “keeps your drivers up-to-date”. Both will have the same version of drivers, i.e. 4.9.0.
Now that we have the drivers installed plug in your Xoom to make sure all drivers/services were detected/installed properly. If you’re good, next we will need the Android SDK, if not already installed. To properly install it though, you must download the Java JDK from --> http://www.oracle.com/technetwork/java/javase/downloads/index.html, and click the “Download JDK” button. Choose your OS, and install.
**NOTE** If you’re running Vista/7 x64, Android SDK will not detect the REQUIRED Java kit installation. Yes, JDK has been properly installed, but the Registry doesn’t read the installation right. So, to get around this issue, either go here --> http://codearetoy.wordpress.com/2010/12/23/jdk-not-found-on-installing-android-sdk/, for a tutorial that gets it detected by modifying the Registry. Or, do what I did, and just download the .zip installer of Android SDK. I’m writing this guide based on the ‘zip type’ of installation, but I’m sure the directories are identical besides having SDK installed in your Program Files folder.
Whew! Now, either extract the SDK to a directory of choice, or point your mouse to the Program Files\Android SDK\ directory. There will be some folders like platforms, platform-tools, tools, etc…
Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
**NOTE** When I first installed SDK, I ran the emulator.exe from within the ‘tools’ directory. This updated everything, but I’m not sure if it matters for this tutorial?
Ok. The “hard” part is over. We should be all setup, and ready to type some commands! What you’ll need to do now is, open up a command prompt i.e. cmd. And do a cd --> to whatever path the ‘tools’ folder is in. For example, mine is in a Xoom folder from my documents. So the command would be “cd C:\Users\%name%\Documents\Xoom\android-sdk_r10-windows\android-sdk-windows\tools”. Without quotes of course.
You should now be pointed at the ‘tools’ folder from cmd, and next we can start the commands!
CHECKPOINT
- Xoom drivers installed, xoom is plugged in, & detected properly. To make sure, open Device Manager to see if the “ADB Interface” is there. **Sorry, I’m not sure ADB is in Device Manager before, or after rooting** Can’t remember! As long as you don’t have any ‘device is not properly installed’ pop-ups, you should be good!
{
"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"
}
- Android SDK is configured right, and cmd is pointed at the correct location.
-USB Debugging option is checked. Check above for instructions
***This is obviously, from Koush’s site, so give him some kudos please ***
***I will bold all commands, and try to put in ‘n00b’ terms***​
Type the following commands in CMD… after you have moved the “XOOM root” files.
1. Download the XOOM root zip.
2. Unzip the package, and
3. put the 3 files inside the same ‘tools’ folder we’re running cmd from!
4. adb reboot bootloader (skip the next 3 steps if you have already unlocked your Xoom via fastboot, which is another guide on XDA that just lets you unlock the Xoom. It’s not rooting.)
5. fastboot oem unlock
-You have to accept the terms by pressing the vol - down key, and then select 'accept' by pressing the vol + up key.
6. -wait for the Xoom to reboot completely.
**You may have to re-enable USB Debugging mode again for the next command**
7. adb reboot bootloader
8. fastboot flash boot rootboot.img
9. fastboot reboot
10. -wait for the Xoom to reboot completely.
11. adb remount
12. adb push su /system/bin/
13. adb shell --> You will now be mounted within adb shell…
14. ln –s /system/bin/su /system/xbin/su
15. chmod 4755 /system/bin/su
16. exit --> This gets you out of adb shell…
17. adb push Superuser.apk /system/app/
That is all! Now, unplug the Xoom and reboot it.
To verify your root is working properly, download an app such as, Cachemate, or any other that requires Superuser access. Open up Superuser to see if that apps’ rights were saved successfully.
Yay! Root access! But honestly, this tutorial will be outdated and inefficient, once the source code is out and then we’ll have a oneclickroot method. Which is way better! Until then, I hope anybody who is a little confused about the process benefits from this guide.
Happy moddin’!
good guide.
Thanks, I like this guide and made rooting my xoom super easy.
One other important initial step is to make sure USB debugging is enabled:
Settings>>Applications>>Development>>USB debugging
Hey, thank you guys for your kudos. I appreciate the feedback.
@jtseidner, Man you are a genius! That is a very important step that I left out! You couldn't root the Xoom without that option. I'll add it to the tutorial.
Thanks!
14. ln –s /system/bin/su /system/xbin/su
Its saying In: not found.. help
Hey. The command is all lower case so it would be "LN" not "IN". Just type it in all lower case. The rest of your command is ok. Simple syntax error, that's all. Let me know if it works and if you have any other concerns.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
ok i got to step fastboot oem unlock #5 and the screen shows choices. i accidentally chose device unlock operation aborted, the down arrow. now it wont go off this text screen. how can i reboot this xoom?
disregard, i pressed the volume UP and power, tablet is rebooting now.
Hey worked great for me only problem is that it wiped my xoom...probably said that somewhere in the instructions and i just missed it. Anyway Thanks.
Yeah sorry. I should put that on the tutorial. But im pretty sure any method of rooting the xoom will wipe it. Only because you have to unlock the device. Until we receive clockwork, this is the only way. Im glad you were successful with my guide though!
Thanks.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
Screen Stuck At Starting FastBoot Protocol Dont Know How Long This Screen Stays Up Or Have I Done Something Wrong I Downloded FastBoot Already And Put It In My Sdk Folder Can Someone Pleas Help Me
You shouldn't be stuck at fastboot. It probably means that your xoom wasn't fully rebooted into the bootloader. Fastboot is a program located in the tools folder and ran from your command prompt. So have your xoom loaded up and connect the usb. Make sure usb debugging is on. Open your cmd and point to that tools folder. Type the first command from step 4, adb reboot bootloader. This will restart your xoom and I believe you'll see the 'dual core technology' logo. Just wait a minute after step 4. Now try the remaining commands, but be sure to wait for reboots before typing the next commands. I have a note after each step that says wait for reboot. Please let me know if you have any further issues.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
This is utterly confusing.. can you explain in-depth please. Don't copy, but leave it as is; copy but replace the file, or replace it completely. Only three options.
for example... it will show adb.exe and adb.exe(2) - is that what you wanted?
misdirection said:
Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
This is utterly confusing.. can you explain in-depth please. Don't copy, but leave it as is; copy but replace the file, or replace it completely. Only three options.
for example... it will show adb.exe and adb.exe(2) - is that what you wanted?
Click to expand...
Click to collapse
Nevermind.. I was able to root my Xoom!!
Great! Sorry if it was misleading. Im not the best writer at times. All I meant was just to copy everything from the platform folder over to the tools folder without replacing, or writing duplicate files. Hope that makes sense?
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
Is this the stock .img or is it the tiamat one? I used other root guide but I'm interested in flashing this .img if it contains the stock kernel.
Sent from my Xoom using Tapatalk
This is the stock .img and this guide will work for the original stock firmware, along with the new 3.01. But this guide is ONLY for the 3g version of the Xoom. If you have any further questions please ask away.
EDIT: Sorry. I didn't fully understand your post. This guide doesn't include any kernels. It assumes you are coming from a stock system. If you are already rooted, and want to return to stock, you would probably have to do a complete restore, and re-lock your device. Then, if you just want the stock kernel; root with this guide, or similar. You can't flash the tiamat kernel unless you're already rooted. This tutorial just gives you root access. Im sure there is a way to go back to the original kernel, without having to restore, but I don't know where those instructions are? Poke around and you may find it. But you'll probably have to start over. Hope this helps!
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
Thanks. I have a WiFi only version and used another root method which included tiamats kernel. Currently having some reboot issues with the kernel so I was hoping to find a stock kernel that I can use.
Ok. Well, you can use this method to root, but the xoomroot files are different. This tutorial was based off the 3g only, and maybe ill add the wifi option as well.
Here's are great guide from xaositek for the wifi version...
http://forum.xda-developers.com/showthread.php?t=1010568
And I'm pretty sure it doesn't include the overclocked kernel.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
http://mirror1.kanged.net/motorola/stingray/xoomroot.zip
seems link are broken

[Q] Can't figure out how to flash CWM via Mac OS X

Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks
Orange_furball said:
Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks
Click to expand...
Click to collapse
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel
Re-Mi said:
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel
Click to expand...
Click to collapse
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
{
"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"
}
Ps: I'm not Paul.. The guy I bought this Mac off of left his info and I never took the time to take t off..
Orange_furball said:
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
Click to expand...
Click to collapse
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file
Re-Mi said:
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file
Click to expand...
Click to collapse
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/
Orange_furball said:
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/
Click to expand...
Click to collapse
I pm-ed you.
Re-Mi has helped me solved my issue! Thank you so much!
Here is more detail on what I did, First of all I followed Re-Mi's instructions. Here they are:
So first things first Root
http://forum.xda-developers.com/show....php?t=2387507
Sideload the app and run the apk
second install the xposed installer (latest apk file at the end of the first post) make sure it's installed (Launch the Xposed Installer and click on "Install/Update" ,Reboot ,Done!)
http://forum.xda-developers.com/show....php?t=1574401
Then install mod collection for Ouya and install CWM from there
http://forum.xda-developers.com/show....php?t=2359390
It's a long detour but i think it will work. After that just install stockplus rom and you got everything you wanted (otherwise you would not even bother to install cwm )
Click to expand...
Click to collapse
Now let me go into more detail. What you do is type the first link into your OUYA's web browser (It is under Make>Software>Web Browser I believe) Then download the file. Now go to Manage>Settings>Advanced>Storage>Downloads and hit the file you just downloaded. Install that APK, hit open, then hit root. Now accept the SU request. After this is done repeat the steps until you have the other file downloaded. Now install that APK for the Xposed Installer and hit "Install/Update" then reboot. Now download the mod collection from the third link.
Install it and install CWM from there. It will take you to a download link, wait a few seconds, then hit install CWM again. Now it'll be installed.
Plug your Ouya into your computer, If its a Mac you will need the program from www.android.com/filetransfer . If its Windows you wont need that. Go in XDA and download whatever ROM tickles your fancy. Drag and drop that into your Ouya's storage. Now on the Ouya reboot to recovery (Via the Mods app)
Now im CWM hit the install zip from SD card, select the .zip of the ROM you chose, and install. Now wait until its all done, reboot, and enjoy!
*IF YOUR OUYA GETS BRICKED, NEITHER I NOR RE-MI NOR ANYONE EXCEPT YOURSELF ARE RESPONSIBLE!*
Good luck! If this helps be sure to thank Re-Mi!!!

[GUIDE] Set up Android SDK (ADB) for Windows 8 / 8.1 / [ADB][Bootloader][Fastboot]

Android SDK - Powerful tool and easy to set up for use with your HTC One M8
{
"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"
}
The Reason that you would want to use Android SDK is because its very easy, it's well updated and it just WORKS! There is much more use with HTC devices with adb then with Samsung when it comes to the daily things like splash screens, radio updates, firmware. You will be dealing a lot with the bootloader and fastboot flashing. So to help out, I will post a helpful guide to help you get started for use with the HTC One M8.​
Click to expand...
Click to collapse
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
1. Download Android SDK For Windows
2. Click the
either the 32bit version or 64bit version
3. Create a folder in the C: and name it Android. See below
4. Place adt-bundle-windows in the Android Folder you just created. Use WinZip, WinRAR or 7-Zip to extract the contents inside the folder. See Below
5. Once extracted, Double click SDK Manager and instal all 4.4.2 and 4.3 items and under tools (SDK Tools and Platform Tools). See Picture Below
6. After all packages are installed and updated, download the latest HTC Sync Manager and install once download completes
7. Once Sync Manager completes installation process, go to control panel and uninstall HTC Sync Manager only, you will see HTC Driver in there as well (LEAVE IT THERE)
8. Important, make sure you enable developer options and turn on USB Debugging. Instructions Below if you are unsure how to do that
1. Go to Settings > About > Software information > More > Tap Build Number 5x
2. Once you get notification saying Developer options is unlocked go back to > settings
3. Click Developer options
4. Add check in the box USB Debugging
9. Plug phone into the computer and let it install all the drivers, you should see pop ups.
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\sdk\platform-tools
2. In Command prompt type
Code:
adb devices
3. If your output shows your device attached like below, then you are good to go!!!
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\sdk\platform-tools
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
Reserved if needed
Sent from my HTC6525LVW using Tapatalk
Thanks for the guide!
Can you add instructions for how to add adb to the environment variables so it can be accessed without having to cd to the platform-tools folder?
Sent from my HTC One M8
VolcanicSkunk said:
Thanks for the guide!
Can you add instructions for how to add adb to the environment variables so it can be accessed without having to cd to the platform-tools folder?
Sent from my HTC One M8
Click to expand...
Click to collapse
I will look into it if I have some time, you can post it in here if you like if you think others will appreciate it. Thanks
Sent from my HTC6525LVW using Tapatalk
OP Updated
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks
bdorr1105 said:
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks
Click to expand...
Click to collapse
Will this work for Windows 7 as well? I have Windows 7, and every time I try to plug my phone in to start the unlocking process, and I click on "Get Token ID"
It just sits at that screen and does nothing. Any help would be greatly appreciated!
theimmortalone said:
Will this work for Windows 7 as well? I have Windows 7, and every time I try to plug my phone in to start the unlocking process, and I click on "Get Token ID"
It just sits at that screen and does nothing. Any help would be greatly appreciated!
Click to expand...
Click to collapse
It should work the same for windows 7, but keep in mind the guide was created on Windows 8....I do not know the path of your adb folder, also, the phone will prompt you to allow the computer to access it, YOU HAVE TO ALLOW IT, or it will never work!!!
What command did you type? I dont see anything except HTC' ????
bdorr1105 said:
It should work the same for windows 7, but keep in mind the guide was created on Windows 8....I do not know the path of your adb folder, also, the phone will prompt you to allow the computer to access it, YOU HAVE TO ALLOW IT, or it will never work!!!
What command did you type? I dont see anything except HTC' ????
Click to expand...
Click to collapse
Okay, well that is my problem then, every time I plug my phone in, and it never asks me to allow it or not. How can I fix that issue? IT does it on my XP, but that is slower then hell so I prefer not to use it.
And as far has the "HTC" part, it doesn't go past that folder. I thought the all-in-one root kit was supposed to do it automatically?
theimmortalone said:
Okay, well that is my problem then, every time I plug my phone in, and it never asks me to allow it or not. How can I fix that issue? IT does it on my XP, but that is slower then hell so I prefer not to use it.
And as far has the "HTC" part, it doesn't go past that folder. I thought the all-in-one root kit was supposed to do it automatically?
Click to expand...
Click to collapse
You may have already accepted it, lets resolve the steps in order to make sure thats the problem, if you follow the guide, you create a Android folder and then extract the bundle inside of that
the path should be C:\Android\sdk\platform-tools
I want to you to open Command Prompt and do the following:
1. Win+R or Start>Run>cmd Hit enter
2. cd c:\Android\sdk\platform-tools
3. type adb devices > Look for prompt on phone and allow it
If it shows your device connected you are good to go
bdorr1105 said:
It should work the same for windows 7, but keep in mind the guide was created on Windows 8....I do not know the path of your adb folder, also, the phone will prompt you to allow the computer to access it, YOU HAVE TO ALLOW IT, or it will never work!!!
What command did you type? I dont see anything except HTC' ????
Click to expand...
Click to collapse
bdorr1105 said:
You may have already accepted it, lets resolve the steps in order to make sure thats the problem, if you follow the guide, you create a Android folder and then extract the bundle inside of that
the path should be C:\Android\sdk\platform-tools
I want to you to open Command Prompt and do the following:
1. Win+R or Start>Run>cmd Hit enter
2. cd c:\Android\sdk\platform-tools
3. type adb devices > Look for prompt on phone and allow it
If it shows your device connected you are good to go
Click to expand...
Click to collapse
I honestly do not remember that pop up coming up on my phone. So I'm not sure what's up with that. But I will do what you said above, and report back.
theimmortalone said:
I honestly do not remember that pop up coming up on my phone. So I'm not sure what's up with that. But I will do what you said above, and report back.
Click to expand...
Click to collapse
Also make sure have USB debugging enabled.... It's part of the process
Sent from my HTC6525LVW using Tapatalk
bdorr1105 said:
You may have already accepted it, lets resolve the steps in order to make sure thats the problem, if you follow the guide, you create a Android folder and then extract the bundle inside of that
the path should be C:\Android\sdk\platform-tools
I want to you to open Command Prompt and do the following:
1. Win+R or Start>Run>cmd Hit enter
2. cd c:\Android\sdk\platform-tools
3. type adb devices > Look for prompt on phone and allow it
If it shows your device connected you are good to go
Click to expand...
Click to collapse
SUCCESS!!
I believe I should be good to go now right?
---------- Post added at 06:07 PM ---------- Previous post was at 05:59 PM ----------
theimmortalone said:
SUCCESS!!
I believe I should be good to go now right?
Click to expand...
Click to collapse
Holy **** I finally got it to work. Thanks for your help man! Appreciate it!
theimmortalone said:
SUCCESS!!
I believe I should be good to go now right?
Click to expand...
Click to collapse
Yes you should, you need to go to C:\Android and double click SDK Manager.exe and update Android 4.4.2 API by clicking the check box. See Attached Picture
If you do not want to have to change directories, then you need to add that path just as the instructions say to do!
C:\Android\sdk\platform-tools
theimmortalone said:
SUCCESS!!
I believe I should be good to go now right?
---------- Post added at 06:07 PM ---------- Previous post was at 05:59 PM ----------
Holy **** I finally got it to work. Thanks for your help man! Appreciate it!
Click to expand...
Click to collapse
No problem

[Q] Soft bricked htc one m8 no OS

Looked all day for a similar situation and all the ones i found didnt help so this is my last resort.So today i decided to root my phone. I had great succsess and was eager to flash a new rom. My recovery is TWRP. I downloaded Android revolution hd to my external sd. I went into recovery mode swiped my rom, tried to flash Android revolution, the file was there but the image wasnt. Now i have no rom on my phone and cant figure out how to flash one using adb on terminal. The commands ive tried arent working and i get different results from others in similar situations. In fastboot it says 'fastboot usb' so i know its connected and the cables fine. Im definitely a noob at tech hence the reason i managed to make a stupid mistake like this but i could really use the help. Im a US Marine and need my phone by tomorrow. Sorry if this thread is in the wrong spot im new to forums. Thanks a lot guys.
What do you mean by "the file was there but the image wasnt" ?
Is it the zip file is on your external sd but can't see it in TWRP recovery ?
Make sure that you select Micro SDcard on storage option.
When you have an external sd, you don't really need those ADB commands ... just take it out and connect to a PC then put in a ROM.zip on your external sd
ckpv5 said:
What do you mean by "the file was there but the image wasnt" ?
Is it the zip file is on your external sd but can't see it in TWRP recovery ?
Make sure that you select Micro SDcard on storage option.
When you have an external sd, you don't really need those ADB commands ... just take it out and connect to a PC then put in a ROM.zip on your external sd
Click to expand...
Click to collapse
yes it was on my external but the image wasnt. But now i think my sd is broken theres a crack in it, and my computer doesnt pick it up anymore. convenient i know. Before i could see the whole file but the img. was missing. now none of its there. I can get a new sd and put a rom on like you said but i wouldnt be able to do that right now and was wondering if there was another way?
zacks94 said:
.... i wouldnt be able to do that right now and was wondering if there was another way?
Click to expand...
Click to collapse
Push the ROM.zip to internal sdcard
How-to :
Put a ROM.zip in your adb/fastboot folder
Put your device in TWRP recovery mode
Then adb push it to internal sdcard
command : adb push ROM.zip /data/media/0/
Once complete, select install - make sure the Storage selected is Internal Storage - you should see the ROM.zip
i will try this and get back to you. I appreciate the help.
zacks94 said:
yes it was on my external but the image wasnt. But now i think my sd is broken theres a crack in it, and my computer doesnt pick it up anymore. convenient i know. Before i could see the whole file but the img. was missing. now none of its there. I can get a new sd and put a rom on like you said but i wouldnt be able to do that right now and was wondering if there was another way?
Click to expand...
Click to collapse
If it's not picking up your phone in adb try redownloading the drivers, this website worked for me (http://www.andromods.com/download-files/get-htc-one-m8-usb-drivers-newest-all-models.html). Then try to adb push a stock rom to your device and redownload it in your recovery.
this is what i got and have gotten multiple times with different zips.
zacks94 said:
this is what i got and have gotten multiple times with different zips.
Click to expand...
Click to collapse
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/
1163
ckpv5 said:
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/
Click to expand...
Click to collapse
This is what i got while trying to push. Am i supposed to be on adb sideload, or bootloader? Sorry im dumb
ckpv5 said:
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/
Click to expand...
Click to collapse
woops. Ths...
zacks94 said:
This is what i got while trying to push. Am i supposed to be on adb sideload, or bootloader? Sorry im dumb
Click to expand...
Click to collapse
No need to select adb sideload or whatever ... just enter recovery, check mount - data is ticked then do what I mentioned before.
{
"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"
}
zacks94 said:
woops. Ths...
Click to expand...
Click to collapse
I don't know much about Mac, usually the different in command is only put the ./ infront of adb or fastboot
do you get your serial no and the word recovery when you run
./adb devices (put your device in recovery)
this is mine
View attachment 2913050
I tried to adb push HTC_One_(M8)_-_MaximusHD_7.0.0.zip /data/media/0/
(because I don't have the same ROM.zip as yours)
View attachment 2913055
And it is a successful effort
ckpv5 said:
No need to select adb sideload or whatever ... just enter recovery, check mount - data is ticked then do what I mentioned before.
View attachment 2913038
Click to expand...
Click to collapse
holy crap it worked. Thanks a lot.I really appreciate it.
zacks94 said:
holy crap it worked. Thanks a lot.I really appreciate it.
Click to expand...
Click to collapse
No problem ... glad that I could help
NO os. stuck in htc logo with CWM but device not recognized adb
ckpv5 said:
No problem ... glad that I could help
Click to expand...
Click to collapse
on mac. when i go to terminal and type fastboot devices it keeps coming with the message. "-bash: fastboot: command not found" i can boot into bootloader and into CWM but thats all. I have no OS. i have a few roms stored but when i flashed them it just stays stuck in the htc logo.
on my pc, i go to cmd and i downloaded android sdk. I placed a rom into platform-tools folder and when i do "adb sideload <filename>" it comes up with error: device not found.
I dont know what else to do. any help would be very appreciated regards
Raul
rauliroo said:
on mac. when i go to terminal and type fastboot devices it keeps coming with the message. "-bash: fastboot: command not found" i can boot into bootloader and into CWM but thats all. I have no OS. i have a few roms stored but when i flashed them it just stays stuck in the htc logo.
on my pc, i go to cmd and i downloaded android sdk. I placed a rom into platform-tools folder and when i do "adb sideload <filename>" it comes up with error: device not found.
I dont know what else to do. any help would be very appreciated regards
Raul
Click to expand...
Click to collapse
Your command is wrong.
On Mac .. you type
./fastboot devices
there is extra character needed ---> ./
when do adb command, it is ./adb
Note : I'm not familiar with CWM ... only TWRP ... all those I wrote here are based on TWRP recovery but should be the same
ckpv5 said:
Your command is wrong.
On Mac .. you type
./fastboot devices
there is extra character needed ---> ./
when do adb command, it is ./adb
Note : I'm not familiar with CWM ... only TWRP ... all those I wrote here are based on TWRP recovery but should be the same
Click to expand...
Click to collapse
It didn't work. I genuinely don't know whats missing. if device its not recognized. could be a driver issue on mac??
have a look at the screenshots
many thanks
Raul
Yep .. driver looks ok but you don't have fastboot & adb files ?
See this to get them : .http://forum.xda-developers.com/showthread.php?t=2390995
You mentioned you downloaded sdk, you need to run the command from platform-tools folder.
Check the screenshot how the directory looks : http://forum.xda-developers.com/showpost.php?p=55062969&postcount=10
You should have something like Rauls-MacBook-Air: platform-tools~Raul$ ./fastboot devices
BTW this is M8 forum ... why don't you post your problem in M7 forum ?
Maybe there are more people who familiar with Mac ... I never use one, I know only some basic.

Categories

Resources