I am trying to run the auto rooter in Fresh Kitchen 1.0.5 and I am encountering difficulty. Below is the full text from Powershell:
Windows PowerShell
Copyright (C) 2006 Microsoft Corporation. All rights reserved.
PS C:\Program Files\Fresh Kitchen>
PS C:\Program Files\Fresh Kitchen> > /system/bin/su
The term '>' is not recognized as a cmdlet, function, operable program, or scri
pt file. Verify the term and try again.
At line:1 char:2
+ > <<<< /system/bin/su
PS C:\Program Files\Fresh Kitchen> _image recovery /sdcard/recovery-RA-heroc-v1.
6.2.img
The term '_image' is not recognized as a cmdlet, function, operable program, or
script file. Verify the term and try again.
At line:1 char:7
+ _image <<<< recovery /sdcard/recovery-RA-heroc-v1.6.2.img
PS C:\Program Files\Fresh Kitchen
Any thoughts, ideas, guidance, etc... would be greatly appreciated. Thanks!!!
biggscott said:
I am trying to run the auto rooter in Fresh Kitchen 1.0.5 and I am encountering difficulty. Below is the full text from Powershell:
Windows PowerShell
Copyright (C) 2006 Microsoft Corporation. All rights reserved.
PS C:\Program Files\Fresh Kitchen>
PS C:\Program Files\Fresh Kitchen> > /system/bin/su
The term '>' is not recognized as a cmdlet, function, operable program, or scri
pt file. Verify the term and try again.
At line:1 char:2
+ > <<<< /system/bin/su
PS C:\Program Files\Fresh Kitchen> _image recovery /sdcard/recovery-RA-heroc-v1.
6.2.img
The term '_image' is not recognized as a cmdlet, function, operable program, or
script file. Verify the term and try again.
At line:1 char:7
+ _image <<<< recovery /sdcard/recovery-RA-heroc-v1.6.2.img
PS C:\Program Files\Fresh Kitchen
Any thoughts, ideas, guidance, etc... would be greatly appreciated. Thanks!!!
Click to expand...
Click to collapse
I tried on mine and it didn't work. Are you rooted already?
You may want to do it manually.. Let me get a link for it..
I had a bunch of problems rooting my phone with it today, but it ended up working okay. I'm not an expert on this so I don't have any specific advice for you but I'd just try different settings. Maybe try autorooting using CMD? And make sure HTC Sync isn't running any processes. Also make sure your phone isn't mounted.
Trying rooting with "Use cmd instead of Powershell" checked & see what you get.
Also instead of creating a new thread for an issue, post the issue in the official Fresh Kitchen thread.
So powershell was added specifically to fix this issue. In all of my tests using powershell fixed that problem. A very small % of windows 7 users see this problem. Now an even smaller % of people are seeing it even with powershell. I honestly don't know what's causing it at all. There is no explanation for it. It's in the part where the kitchen is acting as if it's typing on your keyboard, but your computer is completely ignoring the commands prior to any special characters.
The kitchen was written and developed on Windows 7 so I know it's not an overall problem. And as gu1dry said please don't make new threads for problems.
flipz-sent you a message on this as well. Ideas on how to get past this? Try CMD? Using XP OS. Edit: tried CMD- got "RA push failed. **daemon still not runningerror: cannot connect to daemon"
I had Sprint Stock RUU, Windows 7 Pro.
I rooted using older RA. Then when I tried rooting the new RA, I got a permission denied dialog box (not in the shell).
So I had to use the pre-kitchen to root the new RA. Which worked fine.
Using the pre kitchen auto root worked just fine. I was then able to cook the rom and flash to it.
PS. I tried a few different steps on my PC to try and get the kitchen root to work, including disabling all anti-virus, but could not get it to work.
Related
So i'm trying to install the cupcake build and i'm having difficulties in the terminal. chmod takes but when I try and execute the next command, like shown below, I get the following error. I have installed fastboot, hard spl and the modded jf1.42.
Macintosh:cupcake josephaaronmoody$ chmod a+x fastboot
Macintosh:cupcake josephaaronmoody$ ./fastboot flash system system.img
-bash: ./fastboot: cannot execute binary file.
plz help! [email protected]
I hate to think I could be liable for you bricking your phone, but as far as I know the ./ in front of fastboot shouldn't be there, and the command should just start with fastboot. I haven't installed cupcake but when I have used fastboot, commands have never start with "./"
What? ./ is how you launch binaries in linux (or osx). It looks like you might be using the linux binary and not the osx one.
try fastboot-osx-10_5.zip from http://forum.xda-developers.com/showthread.php?t=456071
thanks
That's the one I dl'ed but the instructions on the koush page are the one's i'm following. that's where I got the commands.
Connect my G1 with my laptop(Ubuntu 8.10 x64)
When I run the adb devices, it only said: List of devices attached
No devices line; It lists one line when I start the emulator program.
And not like the SDK for windows, there is not some folder related to drivers.
Does it support for linux x64? plz help.~
have you activated the debugger in your g1 ?
oh I remember when I was in ubuntu now
you gotta launch adb daemon as root
try this :
adb kill-server && sudo adb devices
and let me know if it worked
dixxa said:
have you activated the debugger in your g1 ?
Click to expand...
Click to collapse
Absolutely, it works fine in Vista x64 with SDK 1.1 r1
I had to do two things to get this to work (although this was on x86) -
1) Build the kernel with the Android drivers enabled. This might not be necessary; I have no idea if they are turned on in the kernels you get from the Ubuntu repository as mine has been custom built for a while, but I'm guessing that they aren't enabled by default because they are in the "staging" area as of 2.6.29.1. So these were in Device Drivers/Staging Drivers/Android.
2) Add a "50-android.rules" file to /etc/udev/rules.d that has this line:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
The idVendor is different if you have an ADP phone, I believe; this was the value worked for mine (non-dev). You can do an 'lsusb' after it's been plugged in and see what shows up. Also, try grepping /var/log/messages for "udev" after you plug it into a USB port and see if there are meaningful messages.
- Chris
Hi all,
I got similar issue here, the main difference is that i got ubuntu 9.04.
running adb daemons as root permit to see devices when it's started normally, but not when in fastboot mode.
I tried all suggestions above (and others!) without success :/
Thanks for any help
noz.geek said:
Hi all,
I got similar issue here, the main difference is that i got ubuntu 9.04.
running adb daemons as root permit to see devices when it's started normally, but not when in fastboot mode.
I tried all suggestions above (and others!) without success :/
Thanks for any help
Click to expand...
Click to collapse
copy the 50-android.rules file you created into a file called 51-android.rules. The problem is related to the order in which things are launched and copying this file to the new name will solve your problem.
I should also note that you will have to restart udev Or reboot or logout/in
to restart udev, In terminal type:
Code:
sudo /etc/init.d/udev restart
sudo is necessary~ thx
Hi all,
After creating 50-android.rules file in /etc/udev/rules.d, I can mount my sdcard on my gPhone to Ubuntu8.04 but I still see no thing when i type command : adb devices. I also did some commands which you gave here. Can anybody help me?
Thanks so much,
NPAK
npak243 said:
Hi all,
After creating 50-android.rules file in /etc/udev/rules.d, I can mount my sdcard on my gPhone to Ubuntu8.04 but I still see no thing when i type command : adb devices. I also did some commands which you gave here. Can anybody help me?
Thanks so much,
NPAK
Click to expand...
Click to collapse
Code:
$ sudo mv /etc/udev/rules.d/50-android.rules /etc/udev/rules.d/51-android.rules/code]
that should fix it ;)
Thanks,
It can work now!
I have the same problem here. adb used to be able to see my phone when I was using Ubuntu 8.10. After I upgraded to 9.04, it never worked. I tried change the udev rule file from 50-** to 51-** or as haykuro suggested to 51-**/code. I also changed the permission to 777. And I did kill and restart adb-server several times under root, but I still get nothing~~~
Can anyone help?
Ok, I have fedora 11 installed on most of my computers, since i love this distro to death. My big thing was trying to get adb to work. This is my guide to get it to work, for now.
First things first. Navigate to /etc/udev/rules.d as root. Create a rules file called 50-android.rules (touch 50-android.rules). NOTE: You are better off looking at the contents and picking a rules number set other than what is listed. Sometimes udev is picky. For the newbies, so if any rules start with '50', then change the number by one or two, like 51 or 52. Paste this into the file:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
Make sure you use ATTRS, not ATTR or SYSFS, since this is a newer updated udev system.
After that, run udevadm control --reload-rules to reload your rules files. Now just run ./adb devices as root to make sure it recognized your HTC dream. I am working on this fix right now so you don't need to be root, keep patient. Now you can adb shell into your device either as root OR normal user, just as long as you start the server as root. This is a permissions problem, and hopefully I can fix this and/or find a fix soon.
I wrote this because i searched high and low through google, and only found a few good parts as far as a fix. Hopefully this helps a few people out there.
Just wondering if this has helped anyone. If not, delete this thread or do whatever with it....
I have adb on my eeepc 900 with f11 I believe this method works too as well. although it says it has been tested with ubuntu, it works pretty well with f11.
http://www.talkandroid.com/android-sdk-install-guide/
Installing The Android SDK
First you will need to download the Android SDK pack .zip archive, once downloaded find a suitable installation location on your machine and extract the zipped files.
Please note: This installation location will be referred to as $SDK_ROOT from now on through this tutorial
Alternatively you can add /tools to your root path which will prevent the need to specify the full path to the tools directory along with enabling you to run Android Debug Bridge (adb) along with other command line tools.
To add /tools:
Linux
1. Edit the ~/.bash_profile or ~/.bashrc files looking for a line that sets the PATH variable.
2. Add the full path location to your $SDK_ROOT/tools location for the PATH variable.
3. If no PATH line exists you can add the line by typing the following:
4. export PATH=${PATH}:<path to your $SDK_ROOT/tools>
Click to expand...
Click to collapse
It helped me, since the creation of the file my OpenSuSE 11.0 recognizes the phone perfectly
Thanks a lot for your hint.
thanks it helped me. ill be looking forward to getting it to work without root
just use sudo instead
Just a heads up for user's using Ubuntu 9.10, this isn't needed. I connected my G1 to it and ran ADB with no adjustments to udev or anything else.
Pretty much it works out of the box.
Here is my version
download the .tgz file from googlecode
http://developer.android.com/sdk/index.html
sudo tar -xzvf android-sdk_r3-linux.tgz
Click to expand...
Click to collapse
Code:
sudo gedit ~/.bash_profile
heres my bash_profile
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH=$PATH:/android-sdk-linux/tools
Click to expand...
Click to collapse
logout
login
connect android g1 device via usb to pc
open a terminal
Code:
adb devices
if you cant get a device try it with superuser.
Don't you think that this is all just a little bit excessive?
To make it work in F11, just do this;
Download SDK, extract.
To use, type:
/path/to/sdk/tools/adb
Another option is to edit the /etc/profile and add
PATH=$PATH:/<Path to android-sdk>/tools
This option will allow any user to use the adb tools when logged in or if you
su -
into another user
I wrote a short guide as well for Windows and Ubuntu. Might help others.
Unfortunately, as anyone with a passing acquaintence with ADB knows, the scrolling issue can be a killer. I swear the other day I pressed "up" twice and it composed "rm /sdcard/rootfs.img /sdcard/system.ext2" and executed it. We run Android on our SD's btw.. Was not cool. Instead, I use ADB via telnet and it works beautifully. Here's how:
Code:
adb shell telnetd &
adb forward tcp:9999 tcp:23
Now type this: "telnet localhost 9999"
Enter "root" and hit enter
Finally update PATH: "export PATH=/usr/bin:/usr/sbin:/bin:/sbin:/system/sbin:/system/bin:/system/xbin:/system/xbin/bb:/data/local/bin"
Okay, so 4 lines to enter and you have a "regular, sane" shell connection to the phone and you can actually scroll through history and text without it jumbling the text and executing random code. Enjoy.
lbcoder said:
Don't you think that this is all just a little bit excessive?
To make it work in F11, just do this;
Download SDK, extract.
To use, type:
/path/to/sdk/tools/adb
Click to expand...
Click to collapse
that works too as well but i would rather open up a terminal and type
sudo adb devices
sensimila said:
that works too as well but i would rather open up a terminal and type
sudo adb devices
Click to expand...
Click to collapse
WHY would you want to make it *MORE COMPLICATED*??
There is NO NEED for root.
/path/to/adb ...
THATS ALL.
This is kind of funny... i wrote this because i had trouble with it, so i am just sharing my fix...
In case this is interesting to someone:
The fix mentioned in the first post has to be applied to open SuSE x86 and x64 edition to make the G1 work. The external device works without it, but not the adb device.
Thanks again!
Just wanted to come and post that this does work with OpenSUSE 11.2 x86. Did this hoping to get adb to work with my LG Ally and it does. Thanks!
(Still) works for me on 64bit SUSE 11.4.
Before adding this file, I could not access my device with adb, received permissions errors.
Added this file, and I can shell into my device.
Permissions on adb itself was not the problem, it was access to the device when udev found it.
[edit]Actually used the lines from http://developer.android.com/guide/developing/device.html[/edit]
[Linux/Mac] ADB & Fastboot Install Script
I have created a script to be used to install ADB and Fastboot on a Mac or a Linux computer. Simply run the script in Terminal or a similar application and it will copy ADB and Fastboot to /usr/local/bin/
Also, as of Version 3.1 this also installs the JDK for Linux-based systems.
While advanced users probably won't need this, it would be good for new users who need help using the ADB and Fastboot commands.
You can see the source at GitHub.
Download
If you have any problems or errors, let me know.
Changelog:
20171202
Moved entirely to GitHub
On Debian-based Linux, installs the adb and fastboot packages
Other systems, the binaries are pulled from Google's website
Executables are given +x permissions
Version 5.0
Hosted on GitHub and Google Code
Uses latest adb and fastboot (as of April 3, 2014)
Install to /usr/local/bin/
Version 4.1
Uses cp rather than mv
Hosted on GitHub again
Team BlueRidge project
Version 4.0
Now installs adb and fastboot to /usr/bin/ which is a more appropriate directory for the files.
Includes Readme now!
Version 3.1
Added JDK Install for Linux
Version 3
Created separate scripts for Linux & Mac
Updated uninstall script
Version 2.1.1
Fixed errors in installer
Version 2.1
More code efficient.
Better comments in script.
Version 2
Combined installer scripts into one Universal
Updated Uninstall.sh to remove udev rules
Version 1.1
Added udev rules for Linux
Version 1
Initial release
Linux
Didn't work on linux, I suggest making a seperate script for linux, I believe the problem is where it detects linux. It gets sudo but nothing more. I ran each command by itself under linux and it worked. Thanks.
shootind5nukes said:
Didn't work on linux, I suggest making a seperate script for linux, I believe the problem is where it detects linux. It gets sudo but nothing more. I ran each command by itself under linux and it worked. Thanks.
Click to expand...
Click to collapse
Thanks! I'll fix that and post an update soon!
JDK is now installed on Linux systems!
Now hosted on Google Code rather than GitHub.
Now installs to /usr/bin/, which is a more appropriate directory as these files are not required for normal system booting or are required for the general functions of your operating system.
i know this thread is old but i need some help.
my devices are not showing up after running the script.
i used adb devices and ./adb devices
boneskid1 said:
i know this thread is old but i need some help.
my devices are not showing up after running the script.
i used adb devices and ./adb devices
Click to expand...
Click to collapse
Does it say that ADB is not found or your devices?
Try enabling ADB (USB Debugging) on your device if it says no devices were found.
Gingerbread: Settings>Applications>Development>USB Debugging
Ice Cream Sandwich: Settings>Developer options>Android debugging
Thanks!!!! This worked perfectly. Using Ubuntu 11.10.
romuloxiii said:
Thanks!!!! This worked perfectly. Using Ubuntu 11.10.
Click to expand...
Click to collapse
I'm happy I could help! Don't forget to click "Thanks" if you liked it!
If you have any issues in the future with it, please feel free to let me know!
Good news!!! This is now a Team BlueRidge project and is on Team BlueRidge's GitHub
since tar.gz files are linux that means I download the zip file on my mac right? sorry if the question is obvious
prflash3 said:
since tar.gz files are linux that means I download the zip file on my mac right? sorry if the question is obvious
Click to expand...
Click to collapse
Download whichever for whichever platform. It's the script inside that you use that matters.
Trying to run the script on OSX, but when I am prompted to enter my password I can't type anything. Please help.
Ditto ul49, being prompted for a password, please advise
Simply type your account password. It won't look like anything is being typed but it is. This is how the "sudo" command works. It is for security.
really glad i found this.
i run "sh "sh script name" and i get this error
ADB-Install-Linux.sh: 5: ADB-Install-Linux.sh: Syntax error: newline unexpected
not sure if it's installed or what
thanks for making this set of scripts and if u could advise me on that error id be grateful.
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
crazy
apt-get install android-tools-fastboot
and
apt-get install android-tools-adb
worked
Just released the first update in two years. Sorry to leave this project unmaintained. The files are now hosted by Team BlueRidge as Google Code no longer supports downloads.
First, thank you very much for putting this together for fellow users. While I'm not the most savy of guys I thought I might just share my experience while installing this ADB + Fastboot package on my MacBook Pro (mid 2012) running OS X Mavericks 10.9.3 in the hopes that somebody might benefit from it as well.
So here it goes:
I tried running the installation script found in "Androidv5.zip" which up until now is the latest version (I think). The script failed to install:
"This will install ADB and Fastboot on your computer.
Root Permissions required. Please type your password.
Password:
Changed directory to /Users/User/Downloads/Androidv5
Moving ADB
cp: /usr/local/bin/adb: No such file or directory
ADB Moved to /usr/local/bin/adb
moving Fastboot
cp: /usr/local/bin/fastboot: No such file or directory
Fastboot moved to /usr/local/bin/fastboot
You may now run Android Debug Bridge and Fastboot commands
Have a nice day."
So I figured I'd open the script file and run each command manually but they would still not work. I then decided to open the target directory
from terminal and it couldn't find it either, so I openned the /usr/ directory to find where the /bin/ directory was... and I found it at | /usr/bin | instead of | /usr/local/bin |.
I ran the commands in the script again manually one by one with the target directory set to | /usr/bin | and then closed terminal and reopened. After that I tried running "adb devices" and the output was "permission denied".
I then applied a "chmod 775 /usr/bin/adb" "chmod 775 /usr/bin/fastboot", closed & reopened terminal and voilà it worked!
Again I'm not a savy guy... there might probably be a better way to do this or perhaps I didn't run the install script as it was supposed to but anyway I decided to let you guys know how it went just in case it proves useful to somebody else....
Then again thanks a lot for sharing this! I finally have ADB + Fastboot on my Mac without having to nag about downloading the Android SDK. :laugh: :good:
Originally Posted by mattlgroff
You are probably very mad at me for this, but here it goes.
chmod is not recognized as a command (tried the fix listed for this)
clean is not an installed program (tried the fix you just said for this too... I did Install from the beginning)
Also I was following the pictographic guide exactly...
Yes, I am steaming maaaaad! !! LOL
What do you see when you type in the Cygwin prompt: echo $PATH
Is /usr/bin found in there?
I am having the same issue re installed everything still getting the clear message.
I did locate the /usr/bin in the path command. Need a little help thanks
bump