Develop Bugs

[Q] Adb is not recognized as an intern or extern command

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

[fastboot] stock 6.2.1 fastboot mode without rooting or cables

All you need is working adb and fastboot on your PC.
Just like doing "idme bootmode 4002" in 6.2 but working in 6.2.1.
Download the attached fbmode.zip and run:
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
Then follow instructions to flash TWRP or whatever.
Experimental Version 0.9: includes nbmode for setting normal boot (4000) and rcmode for setting recovery boot (5000). Untested, PM me if there's a problem.

This should allow users who chmod'd/deleted /system and no longer have root to reboot to fastboot, correct?

I haven't tested it in that scenario, but it should. It shouldn't need anything more than adb. It's even static since I was too lazy to figure out why I was having trouble with shared libs.

pokey9000 said:
I haven't tested it in that scenario, but it should. It shouldn't need anything more than adb. It's even static since I was too lazy to figure out why I was having trouble with shared libs.
Click to expand...
Click to collapse
Confirmed, works fine for ppl that screwed off /system without a recovery.
*Stickyfied for awesomeness.

hello
thanks for your help
but it doensn't work for me
i booted the KF with the standard usb cable to use ADB
but refused this line : "adb shell /data/local/tmp/fbmode"
and impossible to go further
thanks if you have an idear
jluc

lucien12 said:
hello
thanks for your help
but it doensn't work for me
i booted the KF with the standard usb cable to use ADB
but refused this line : "adb shell /data/local/tmp/fbmode"
and impossible to go further
thanks if you have an idear
jluc
Click to expand...
Click to collapse
First make sure adb i even functioning
Code:
adb shell
if you get a $ or # prompt then it is,
then exit
Code:
exit
then
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot

Worked like a charm recovering a bricked KF 6.2.1.
applied this, installed TWRP, modified the driver, rebooted in recovery, and installed the stock update to 2.6.1 without wiping.
Now my KF is working again. this would have been a sad long day if you weren't here. thanks pokey9000

Thanks a ton! This works great! Any chance you're willing to release the source code to this?

jonas3d said:
Thanks a ton! This works great! Any chance you're willing to release the source code to this?
Click to expand...
Click to collapse
No, I'm hoping to make it a little harder for Amazon to close this up. That said, you could recreate this very quickly from an strace.
Sent from my SAMSUNG-SGH-I777 using xda premium

done that. device reboot and then pc show device as "unknown".
tried to install recovery no good. device not found.
only after "reboot normal" the pc find the device but then its like before: abdb cannot ......
please help

ilanlen said:
done that. device reboot and then pc show device as "unknown".
tried to install recovery no good. device not found.
only after "reboot normal" the pc find the device but then its like before: abdb cannot ......
please help
Click to expand...
Click to collapse
Sounds like you have a problem with fastboot on your PC. Search in General, there are a bunch of threads on this.
Sent from my SAMSUNG-SGH-I777 using xda premium

thepsman said:
Worked like a charm recovering a bricked KF 6.2.1.
applied this, installed TWRP, modified the driver, rebooted in recovery, and installed the stock update to 2.6.1 without wiping.
Now my KF is working again. this would have been a sad long day if you weren't here. thanks pokey9000
Click to expand...
Click to collapse
Did the same but did wipe. Now my Fire is stuck in the Kindle Fire logo. It doesn´t flash like before, but i wait more than 20 minutes and it doesn´t pass the logo.
I´ll try with the factory cable when the pieces arrive.

osozraz said:
Did the same but did wipe. Now my Fire is stuck in the Kindle Fire logo. It doesn´t flash like before, but i wait more than 20 minutes and it doesn´t pass the logo.
I´ll try with the factory cable when the pieces arrive.
Click to expand...
Click to collapse
Yes. This didn't really do anything for me.
Got excited when someone said that this should work for people who had screwed the system permissions.
---------- Post added at 10:41 AM ---------- Previous post was at 10:02 AM ----------
Okay okay. I won't question the usefulness of this again.
Got TWRP installed via the use of the OP. Had the yellow traingle crap happen but got around that with this advice:http://www.jayceooi.com/2011/12/27/how-to-solve-stuck-at-yellow-triangle-issue-on-kindle-fire/
Cheers pokey9000. Saved the day.
Cheers

Can someone help me out? I'm trying to get this working and after I type in adb shell I get this message:
exec '/system/bin/sh' failed: no such file or directory (2)
Any ideas? My KF is stuck on the notorious "your Kindle Fire has detected a problem" screen. I'm also looking at this thread but I'm thoroughly confused.
http://forum.xda-developers.com/showthread.php?t=1423099
I also tried the command in the first post and after adb push fbmode I get:
cannot start 'fbmode': no such file or directory

A little more info, when I go to the Amazon Kindle USB Device properties in Device Manager, under Volumes I click populate and I get this.
{
"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"
}
Basically my attempt at a partition using partition utility went horribly wrong.

Matt V said:
A little more info, when I go to the Amazon Kindle USB Device properties in Device Manager, under Volumes I click populate and I get this.
Basically my attempt at a partition using partition utility went horribly wrong.
Click to expand...
Click to collapse
Do you have FIREFIREFIRE or TWRP installed? The best route is to install FFF 1.1 if you can, rebuild the partition table, then install the stock image from TWRP.

I don't have anything installed, flashing the 6.2.1 update.zip removed everything. Is there a way to install FFF or TWRP without getting it to boot? I get the system/bin error anytime I try to execute anything in KFU.

Matt V said:
I don't have anything installed, flashing the 6.2.1 update.zip removed everything. Is there a way to install FFF or TWRP without getting it to boot? I get the system/bin error anytime I try to execute anything in KFU.
Click to expand...
Click to collapse
We are in the same situation. Without a working shell we are screwed. If only we could execute this without calling adb shell, but i think that´s impossible. Try to buy/build a factory cable to boot in fastboot. I´m still waiting for the pieces to build mine, will report when done.

osozraz said:
We are in the same situation. Without a working shell we are screwed. If only we could execute this without calling adb shell, but i think that´s impossible. Try to buy/build a factory cable to boot in fastboot. I´m still waiting for the pieces to build mine, will report when done.
Click to expand...
Click to collapse
Factory cable is probably your best route, though if you don't mind opening your Fire you could do this instead: http://forum.xda-developers.com/showthread.php?t=1405052&highlight=rekindle which will get you TWRP and FFF installed. Instead of using the FFF included (u-boot.bin) you should get the newer 1.1 release and run "fastboot oem format" before running "fastboot boot..." to put your partitions back to normal.

I did the same, but now I got splash screen "Kindle Fire" and now adb is not recognize my KF.
Please help!

Changing splash screen image via sdk

Hello.
For the past 3 hours i have struggled installing the sdk tools, so i could install custom splash images. I most of the time i was searching for a good tutorial but most of them failed me. Usualy i got a file(some kind of image), and i placed it into the rot of the sd card and just rebooted into hboot. the system detected the splash img file and prompted me to install it and that was that, but most of the threads contain a few codes that realy dont work for me. I installed sdk and it works fine but i realy dont understand from the codes forward how to put the .png image to .img and then flashing it trough the cmd prompt :s.

pitastrudl said:
Hello.
For the past 3 hours i have struggled installing the sdk tools, so i could install custom splash images. I most of the time i was searching for a good tutorial but most of them failed me. Usualy i got a file(some kind of image), and i placed it into the rot of the sd card and just rebooted into hboot. the system detected the splash img file and prompted me to install it and that was that, but most of the threads contain a few codes that realy dont work for me. I installed sdk and it works fine but i realy dont understand from the codes forward how to put the .png image to .img and then flashing it trough the cmd prompt :s.
Click to expand...
Click to collapse
Ok, a very rapid tutorial on splash screens:
You need an image that can fit you phone (480*800 pixels) and convert it to .img format
The best tutorial on how to flash a splash is this one: http://forum.xda-developers.com/showthread.php?t=1059520
If you want to flash the .img directly you will need ENG S-OFF (DO NOT FLASH ENG S-OFF if you phone was shipped with GB. Just flash the Hack Kit modified ENG S-OFF that supports all builds)
When you have the .img file ready, just put it in a folder in the PC where u can easily locate it.
Open a cmd as admin or terminal as root.
Enable usb debugging and charge only as default and plug the phone.
In cmd navigate to where the .img file is located (for instance: c:\users\your_user\Desktop)
Type: adb devices (it should show you serial number under devices attached)
If the above was allright type: adb reboot-bootloader (it will boot in fastboot usb)
Type: fastboot flash splash1 name_of_file.img
Once you get the OKAY. Finished near the bottom of the cmd session. Type: Fastboot reboot...
Enjoy your new splash...:laugh:

Thanks for all the help!
But there is another problem, you see when i try to make the .img file with the command in command prompt "adb nbimg -F splash1.bmp -w 480 -h 800", it rolls down some text,
{
"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 also when i went looking for the adb i doscovered this, and the instructions say
Step 3. Copy this Bitmap to your TOOLS folder of your SDK package
Step 4. From ADB, within the TOOLS directory, type the following
adb nbimg -F splash1.bmp -w 480 -h 800
Click to expand...
Click to collapse
The problem is that there is no adb in the tools folder but it went to platform-tools. Im realy out of luck

pitastrudl said:
Thanks for all the help!
But there is another problem, you see when i try to make the .img file with the command in command prompt "adb nbimg -F splash1.bmp -w 480 -h 800", it rolls down some text,
and also when i went looking for the adb i doscovered this, and the instructions say
The problem is that there is no adb in the tools folder but it went to platform-tools. Im realy out of luck
Click to expand...
Click to collapse
You are not out of luck...from adb means that you have to be located in the sdk-tools folder (c:\users\android\sdk\sdk-tools) in the cmd session and from there run the commands...adb stands for Android Debug Bridge which is the connection between PC and phone and was installed when u installed the sdk package.

Cool!

glevitan said:
Ok, a very rapid tutorial on splash screens:
You need an image that can fit you phone (480*800 pixels) and convert it to .img format
The best tutorial on how to flash a splash is this one: http://forum.xda-developers.com/showthread.php?t=1059520
If you want to flash the .img directly you will need ENG S-OFF (DO NOT FLASH ENG S-OFF if you phone was shipped with GB. Just flash the Hack Kit modified ENG S-OFF that supports all builds)
When you have the .img file ready, just put it in a folder in the PC where u can easily locate it.
Open a cmd as admin or terminal as root.
Enable usb debugging and charge only as default and plug the phone.
In cmd navigate to where the .img file is located (for instance: c:\users\your_user\Desktop)
Type: adb devices (it should show you serial number under devices attached)
If the above was allright type: adb reboot-bootloader (it will boot in fastboot usb)
Type: fastboot flash splash1 name_of_file.img
Once you get the OKAY. Finished near the bottom of the cmd session. Type: Fastboot reboot...
Enjoy your new splash...:laugh:
Click to expand...
Click to collapse
Thanks, I will be trying this tonight when I get home.

now it says could not open splash1.bmp. its in the right format, i tryed resaving it and everything.

pitastrudl said:
now it says could not open splash1.bmp. its in the right format, i tryed resaving it and everything.
Click to expand...
Click to collapse
If it is the nb file you won't be able to open it...

I cant get the nb file, the command cant open it,
here is the image, if you could try. I tryed with other images but it still cant open it

pitastrudl said:
I cant get the nb file, the command cant open it,
here is the image, if you could try. I tryed with other images but it still cant open it
Click to expand...
Click to collapse
That is not the image you have to flash to your phone (and rename to .img)...that is the one with the .nb extension...

Hey, every time i try to open it i cant and it clearly says,
Step 4. From ADB, within the TOOLS directory, type the following
Code:
nbimg -F splash1.bmp -w 480 -h 800
Step 5. Take your newly made nb image, and rename the extension to ".img"
Click to expand...
Click to collapse
I have done that, but the problem is that i wont open the damn splash1.bmp , so it would convert to the nb image.
And your last anwser is realy confusing me
That is not the image you have to flash to your phone (and rename to .img)...that is the one with the .nb extension...
Click to expand...
Click to collapse
If it is the image with the .nb extension then i have to rename it to .img?! it states in the instructions.
Step 5. Take your newly made nb image, and rename the extension to ".img"
Click to expand...
Click to collapse

Simple guide to ADB/Fastboot

I've noticed an increase of users "bricking" their handsets. I use the term "bricking" in the slightest sense, as to them, it is bricked.
The main cause is simply a lack of background knowledge & experience with ADB & Fastboot, I've also noticed that the very helpful guides to recover handsets from this "bricked" state, have an assumption that the users know basic things such as using ADB/Fastboot & cmd. The very things that caused the "brick" in the first place.
Here I'm going to throw together a crash course in the very basics of ADB/Fastboot and how to implement them into your system so that they work all the time and from anywhere on your system. Then an example on how to flash a ROM.
Ensure that USB debugging is enabled on your handset. On HTC Sense it can be found under Settings > Developer Options > Check USB Debugging.
Step One - Download ADB & Fastboot - HERE
Step Two - Extract this to a folder on your C:\ - e.g. "C:\ADB"
Step Three - Add this location to your System PATH - This is important as it makes things a lot easier later
Control Panel > System > Advanced System Settings > Environment Variables...
At the bottom "System Variables" scroll down and find "Path", Click it then "Edit..."
Add to the end of the line named "Variable Value:" ";C:\ADB\" - Try not to delete anything previously in there, the ; is needed, just omit the quotes "".
Hit Ok on the menus and go back to your desktop.
Step Four - Reboot your system or just log out and back in.
Here is a image guide to follow.
{
"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"
}
-
-
Adding ADB & Fastboot to your System PATH allows you to run the commands adb & fastboot from anywhere in your system. Normally the guide you'd follow would say,
cd into fastboot folder
Click to expand...
Click to collapse
Now you don't need to.
Example usage.
You download a new ROM (CM10) plus GApps & the boot.img from the relevant thread. You copy the ROM & GApps from your computers download folder to your handset. Unmount USB storage and you do the following, making sure that your handset is still plugged in.
Open your computers default download folder.
Shift + Right Click > Open command window here
Type the following
adb devices > Serial Number should be printed
adb reboot bootloader > Device reboots into HBOOT, Fastboot is automatically selected.
fastboot devices > Serial Number should be printed again
fastboot flash boot boot.img > boot.img is sent and flashed, easy. Sometimes the boot.img maybe named different, just start typing and hit TAB, should autocomplete.
fastboot erase cache > not always needed, better being safe
Press the power button on your handset to enter HBOOT, then navigate to RECOVERY and press power.
In Recovery, make your backups as per, and wipe & flash the ROM + GApps, then reboot normally.
Profit
If you still do not understand what you are doing, don't do it. You would not attempt to change a head gasket in your cars engine, unless you knew and understood what you were doing. If you are unsure, search, read & ask until you know what your doing. Sometimes what I write looks too clinical so here's a :cyclops: smiley to lighten the post.

Andy said:
I've noticed an increase of users "bricking" their handsets. I use the term "bricking" in the slightest sense, as to them, it is bricked.
The main cause is simply a lack of background knowledge & experience with ADB & Fastboot, I've also noticed that the very helpful guides to recover handsets from this "bricked" state, have an assumption that the users know basic things such as using ADB/Fastboot & cmd. The very things that caused the "brick" in the first place.
Here I'm going to throw together a crash course in the very basics of ADB/Fastboot and how to implement them into your system so that they work all the time and from anywhere on your system. Then an example on how to flash a ROM.
Ensure that USB debugging is enabled on your handset. On HTC Sense it can be found under Settings > Developer Options > Check USB Debugging.
Step One - Download ADB & Fastboot - HERE
Step Two - Extract this to a folder on your C:\ - e.g. "C:\ADB"
Step Three - Add this location to your System PATH - This is important as it makes things a lot easier later
Control Panel > System > Advanced System Settings > Environment Variables...
At the bottom "System Variables" scroll down and find "Path", Click it then "Edit..."
Add to the end of the line named "Variable Value:" ";C:\ADB\" - Try not to delete anything previously in there, the ; is needed, just omit the quotes "".
Hit Ok on the menus and go back to your desktop.
Step Four - Reboot your system or just log out and back in.
Here is a image guide to follow.
-
-
Adding ADB & Fastboot to your System PATH allows you to run the commands adb & fastboot from anywhere in your system. Normally the guide you'd follow would say,
Now you don't need to.
Example usage.
You download a new ROM (CM10) plus GApps & the boot.img from the relevant thread. You copy the ROM & GApps from your computers download folder to your handset. Unmount USB storage and you do the following, making sure that your handset is still plugged in.
Open your computers default download folder.
Shift + Right Click > Open command window here
Type the following
adb devices > Serial Number should be printed
adb reboot bootloader > Device reboots into HBOOT, Fastboot is automatically selected.
fastboot devices > Serial Number should be printed again
fastboot flash boot boot.img > boot.img is sent and flashed, easy. Sometimes the boot.img maybe named different, just start typing and hit TAB, should autocomplete.
fastboot erase cache > not always needed, better being safe
Press the power button on your handset to enter HBOOT, then navigate to RECOVERY and press power.
In Recovery, make your backups as per, and wipe & flash the ROM + GApps, then reboot normally.
Profit
Click to expand...
Click to collapse
This is what i was looking for. I am just about to flash a ROM in a HTC vivid S-ON and i need it to flash the kernel manually.
Thank you. :cyclops:

Can you boot into recovery with a fast boot command?
Sent from my HTC One X using xda app-developers app

Tw1tchy said:
Can you boot into recovery with a fast boot command?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Fastboot works in the bootloader
ADB works in the running OS and the recovery
So fastboot reboot recovery will work in the bootloader, adb reboot recovery works in the running OS and inside the recovery (if you want to reboot it for some reason when you are already in)

Unfortunately there is no fastboot command (AFAIK) to reboot into recovery from fastboot directly. Your only fastboot reboot options are
fastboot <command>
Code:
reboot
reboot-bootloader

Andy said:
Unfortunately there is no fastboot command (AFAIK) to reboot into recovery from fastboot directly. Your only fastboot reboot options are
fastboot <command>
Code:
reboot
reboot-bootloader
Click to expand...
Click to collapse
Ah my mistake , sorry mate. So it only apply to adb .
Thanks

Mr Hofs said:
Ah my mistake , sorry mate. So it only apply to adb .
Thanks
Click to expand...
Click to collapse
if you are in ADB
"
adb reboot bootleader
adb reboot recovery.
"
but if you are in fastboot you need to navigate to recovery option using the vol up and vol down keys and power on recovery.

:facepalm:
and i was wondering why fastboot write: waiting for device, of course if i use fastboot instead adb to try to reboot my phone in OS
i had forgotten...

Hi Im desperatte trying to root my ATT HTC ONE X with 1.5 using this method http://forum.xda-developers.com/showthread.php?t=1709296
I found this tutorial and I dont know if could work.
I have one big question: After i extracted the file in step one I get a folder named fastboot, instead en adb folder U mentioned in step 2
Im feeling stupid asking so basic things but I prefer to ask and not cry later
Thanks

ErnestoD said:
Hi Im desperatte trying to root my ATT HTC ONE X with 1.5 using this method http://forum.xda-developers.com/showthread.php?t=1709296
I found this tutorial and I dont know if could work.
I have one big question: After i extracted the file in step one I get a folder named fastboot, instead en adb folder U mentioned in step 2
Im feeling stupid asking so basic things but I prefer to ask and not cry later
Thanks
Click to expand...
Click to collapse
No worries, mate. Fastboot folder contains both fastboot and adb commands, so all you have to do is open command prompt in it (something like C:/fastboot/) and then type commands.
Beforehand, you must have htc drivers installed, and the phone connected, of course.
Also, beware that this forum is for International One X with Tegra 3, so be careful with instructions found here.

Thanks man.
I undestood what u said.
My problem is with the fisrt command I should write in the root proccess: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
I copied SU as stated, then typed adb shell and then rm /data/data/com.redbend.vdmc/lib/libvd* . here I get notification about missin file or folder.
The thread Im in is: http://forum.xda-developers.com/showthread.php?t=1709296
Do U understant what should I do or. If Im missing something
Thanks
[email protected]|-|oR said:
No worries, mate. Fastboot folder contains both fastboot and adb commands, so all you have to do is open command prompt in it (something like C:/fastboot/) and then type commands.
Beforehand, you must have htc drivers installed, and the phone connected, of course.
Also, beware that this forum is for International One X with Tegra 3, so be careful with instructions found here.
Click to expand...
Click to collapse

Where did you extract your fasboot/adb commands? Is SU in the same folder? Where do you open your command prompt?
Again, I'm no expert in AT&T One X, but fastboot/adb should be the same.
I suggest you open Windows Explorer, go to your fastboot/adb folder, press SHIFT, and right click your mouse.
Select "Open command window here".
Then type "adb devices" (make sure your phone is connected with USB cable, and USB debugging is turned on).
If adb sees your phone that's good.
Type dir and see if SU inside the folder.
Then follow the steps you should.
I hope this helps.

yes It has worked . Thanks man.
So now I know Im at least oriented. Lets see If I receive more help in the root thread Im talking about.
Thanks one more time
[email protected]|-|oR;40510609]Where did you extract your fasboot/adb commands? Is SU in the same folder? Where do you open your command prompt?
Again, I'm no expert in AT&T One X, but fastboot/adb should be the same.
I suggest you open Windows Explorer, go to your fastboot/adb folder, press SHIFT, and right click your mouse.
Select "Open command window here".
Then type "adb devices" (make sure your phone is connected with USB cable, and USB debugging is turned on).
If adb sees your phone that's good.
Type dir and see if SU inside the folder.
Then follow the steps you should.
I hope this helps.[/QUOTE]

It's alright, mate. That's the whole spirit of XDA.
Take care of you and of your One X, mate! :good:

Thanks
Woot Saved me
Thanks

[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!!!