Problem trying to root my Epic 4g - General Questions and Answers

I'm using a mac, an epic4g (eb13) I've got the usb debugging enabled and I can't get this to work:
here's what I get:
Original one click made by joeykrim and one click installer made by noobnl and firon
busybox by skeeterslint
Press any key to continue...
Starting adb server
./run.sh: line 23: adb: command not found
./run.sh: line 26: adb: command not found
./run.sh: line 33: adb: command not found
./run.sh: line 35: adb: command not found
Phone is not connected. Press any key to continue.\n./run.sh: line 35: adb: command not found
Phone is not connected. Press any key to continue.\n./run.sh: line 35: adb: command not found
-----
any idea what I'm doing wrong?

Related

[Resolved] [Q] Setting Up ADB/USB Drivers for Android Devices in Ubuntu maverick 10.10?

OK so I tried these instruciton for Lucid on Maverick. I would post the link but I can't cuz I'm a newbie.
Download the latest Android SDK from Google: Android SDK
Extract the TGZ file to your home/user directory
NOTE: User would be your username
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Login as root and create this file: /etc/udev/rules.d/##-android.rules
NOTE: In the above file replace ## with the number 50 if you are running Gusty/Hardy/Dapper (50-android.rules) or with the number 70 if you are running Karmic Koala/Lucid Lynx(70-android.rules)
Or simply type in terminal sudo gedit /etc/udev/rules.d/##-android.rules then enter your password
The file should read:
For Gusty/Hardy: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
For Dapper: SUBSYSTEM==”usb_device”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
For Karmic Koala: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
For Lucid: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
NOTE: In the above lines the code ”0bb4″ refers to a HTC device. If your phone is from a different manufacturer, replace the code with the appropriate from the table below.
Execute: sudo chmod a+rx /etc/udev/rules.d/70-android.rules
Reboot
To run ADB you need to add an environment variable to your bashrc file:
Open a terminal window and type: sudo gedit .bashrc
Add the following line at the end: export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools
Save and close
You should be ready to go, type adb devices in a terminal window with your phone plugged in.
If you see a serial number pop up that means you are done. Should look something like this:
List of devices attached
HT99PHF02521 device
If for some reasons when running adb devices gives you a “no permissions” error, try typing the following in terminal
adb kill-server
adb start-server
USB Vendor IDs
MANUFACTURER USB VENDOR ID
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2
Common ADB Commands
- Lists which devices are currently attached to your computer
adb devices
- Drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
adb shell
- Lets you install an Android application on your phone
adb install
- Remounts your system in write mode – this lets you alter system files on your phone using ADB
adb remount
- Rets you upload files to your phones filesystem
adb push
- Lets you download files off your phones filesystem
adb pull
- Starts dumping debugging information from your handset to the console – useful for debugging your apps
adb logcat
Now, as for the credits, I took TheUnlockr “How To” for Windows as a base for this guide.
Click to expand...
Click to collapse
But it doesn't work in maverick. Please help. Because I really want to overlock my phone.
Also keep in mind I'm fairly new to Linux so be easy on the newbie.
Thanks guys.
49 views and no responds? Please help I'm desperate here.
So did post this in the wrong section? This silent treatment is killing me. lol
in terminal type:
$ sudo -i
$ gedit .bashrc
insert the same line at the end: export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools
$ exit
$ sudo -i
$ adb kill-server
$ adb start-server
$ adb devices
benholiio said:
in terminal type:
$ sudo -i
$ gedit .bashrc
insert the same line at the end: export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools
$ exit
$ sudo -i
$ adb kill-server
$ adb start-server
$ adb devices
Click to expand...
Click to collapse
Dude this is for adb, not for recognizing the USB...
My phone is HTC Desire and I am still figuring out why it doesnt work on 10.10 with all the rules...
hungrysquid said:
Dude this is for adb, not for recognizing the USB...
My phone is HTC Desire and I am still figuring out why it doesnt work on 10.10 with all the rules...
Click to expand...
Click to collapse
I'm assuming thisisspeedy got to the same stage i did: USB connects, i can access files through maverick, however adb won't detect the device to allow push/pull/shell.
simply elevating to root & editing the bash script on maverick solves the problem.
I have my Galaxy S connected to Maverick via USB, and i can run all ADB functions.
It should work for HTC using the correct code. If you have a problem with Ubuntu detecting your device on USB when you've set USB to mount on Android, PM me and I'll see if i can help.
Could someone post a link for the Lucid dirs? Thanks.
Sent from my T-Mobile G2 using XDA App
Thanks for everyone responses.
I figured it out thanks to this.
[QUOTEThe Android Debug Bridge (adb) is a tool lets you manage the state of an emulator instance or Android-powered device.
I was trying to run it for the first time on my ubuntu 9.10 box and I kept getting this error:
desktop:~/dev/Android/android-sdk-linux/tools$ adb
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'aub' from package 'aub' (universe)
Command 'dab' from package 'bsdgames' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'arb' from package 'arb' (multiverse)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'sun-java6-jdk' (multiverse)
Command 'ab' from package 'apache2-utils' (main)
adb: command not found
What was I doing wrong?
A quick google search shows me the error of my ways.. I haven't added my Android SDK tools directory to my system path!
It should go something like this...
open a terminal window and type:
$ echo $PATH
---(should return the directories associated with $PATH)
$ export PATH=$PATH:/home/YOUR-USERNAME/sdk/tools
---(replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH
---(you should now see your tools directory added to the end of the $PATH variable)
$ adb devices
---(now adb should do something, if nothing else at least error, no devices)
And now I get:
List of devices attached
emulator-5554 device
Sweet Success!
p.s. Adding to the system path in Windows is along the lines of :
right-click '(My) Computer'
Select 'Properties'
Go to 'Advanced' or whatever tab you find 'Environment Variables'
Select 'Path' then 'Edit' and add your new path in.][/QUOTE]
adb trouble
Hi i am runing on Ubuntu Maverick with device Huawei U8110 on Celestial Teapot 4 ROM
java jdk ver6
installed Android SDK and tools in the home folder
i edit the rules file 99-android.rules to SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
saved and added the file permisions
restart the udev
Connected the Phone put the debug mode on
kill the adb then started
And Then Run The comand
[email protected]:/home/android-sdk-linux_x86/platform-tools# ./adb devices
List of devices attached
There is nothing in the list....?
HELP!? Please......
I use it for Marveric.
vim /etc/udev/rules.d/70-android.rules
# IS01
SUBSYSTEM=="usb",ATTRS{idVendor}=="04dd",ATTRS{idProduct}=="04dd",MODE="0666",OWNER="root"
# GalaxyS
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="681c",MODE="0666",OWNER="root"
# bravo
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
add like a above. then
/etc/init.d/udev restart
Good luck!
thisisspeedy said:
I figured it out thanks to this.
[QUOTEThe Android Debug Bridge (adb) is a tool lets you manage the state of an emulator instance or Android-powered device.
I was trying to run it for the first time on my ubuntu 9.10 box and I kept getting this error:
desktop:~/dev/Android/android-sdk-linux/tools$ adb
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'aub' from package 'aub' (universe)
Command 'dab' from package 'bsdgames' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'arb' from package 'arb' (multiverse)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'sun-java6-jdk' (multiverse)
Command 'ab' from package 'apache2-utils' (main)
adb: command not found
What was I doing wrong?
A quick google search shows me the error of my ways.. I haven't added my Android SDK tools directory to my system path!
It should go something like this...
open a terminal window and type:
$ echo $PATH
---(should return the directories associated with $PATH)
$ export PATH=$PATH:/home/YOUR-USERNAME/sdk/tools
---(replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH
---(you should now see your tools directory added to the end of the $PATH variable)
$ adb devices
---(now adb should do something, if nothing else at least error, no devices)
And now I get:
List of devices attached
emulator-5554 device
Sweet Success!
p.s. Adding to the system path in Windows is along the lines of :
right-click '(My) Computer'
Select 'Properties'
Go to 'Advanced' or whatever tab you find 'Environment Variables'
Select 'Path' then 'Edit' and add your new path in.]
Click to expand...
Click to collapse
============================================================
THANK YOU!! (I did hit 'THANKS' as well)...
You pointed me in the right direction with Ubuntu 10.04.
The only change was with SDK..the 'adb' has moved to $ ~/platform-tools/
By the way folks, when you install SDK, it would be wise to do all the updates, otherwise the platform-tools folder won't be an option....:cyclops:
"The order has been restored.."

ADB not working in Ubuntu10.10

whenever i use adb in ubuntu it just says this:
Code:
[email protected]:~# cd /sdk/platform-tools
[email protected]:/sdk/platform-tools# adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
doesnt make sense.. works in windows but im tired of rebooting to use adb
any ideas?
Make sure adb in is your PATH: echo $PATH
If not, add it: export PATH=$PATH:/path/to/sdk/platform-tools
ikon8 said:
Make sure adb in is your PATH: echo $PATH
If not, add it: export PATH=$PATH:/path/to/sdk/platform-tools
Click to expand...
Click to collapse
I think you mean in your bash file. Go into your home folder and hit control-h. It should show hidden files. Open your bash and put the above-mentioned.
If you don't want to go that far you can always navigate to that directory and punch in the commands.
Sent from my ADR6400L using Tapatalk
thanks for the replies guys but ive already done that as well..ugh this is frustrating
You run an executable binary with a ./ before it in linux.
./adb devices
Like that.
But it's really best to add the directory to your path, so you can run adb from any directory easily.
Add this line to your .bashrc file (which is in your home directory) at the end:
export PATH=/sdk/platform-tools:$PATH
Then close and open a new terminal. Then you should be able to run adb without the ./ from any directory.
If that still doesn't work, type "echo $PATH" and make sure it shows the directory there. If not, you did something wrong saving that line in your .bashrc file, or it's not being loaded properly.
Nikolai2.1 said:
whenever i use adb in ubuntu it just says this:
Code:
[email protected]:~# cd /sdk/platform-tools
[email protected]:/sdk/platform-tools# adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
doesnt make sense.. works in windows but im tired of rebooting to use adb
any ideas?
Click to expand...
Click to collapse
I know exactly what this is. Get out of hard root and stay in your regular home folder. There are two things that will make this simple for you. 1. take the adb executable and place it in your users bin. so that would be something like /usr/bin...once again make sure you are in nautilus as the regular user and not root! 2. Now go back into your terminal and invoke it by typing sudo adb start-server...then sudo adb devices...the key thing here is that ubuntu's permissions are a bit screwy so you have to use adb in this manner. once again sudo everthing ("sudo adb" etc.)...do not become hard root in ubuntu (sudo su)
EDIT: btw if you use this method you will not have to worry about paths as long as it's in your user bin...you dont have to ./adb devices either if you do it this way
Javis
GrdLock said:
You run an executable binary with a ./ before it in linux.
./adb devices
Like that.
But it's really best to add the directory to your path, so you can run adb from any directory easily.
Add this line to your .bashrc file (which is in your home directory) at the end:
export PATH=/sdk/platform-tools:$PATH
Then close and open a new terminal. Then you should be able to run adb without the ./ from any directory.
If that still doesn't work, type "echo $PATH" and make sure it shows the directory there. If not, you did something wrong saving that line in your .bashrc file, or it's not being loaded properly.
Click to expand...
Click to collapse
trendsetter37 said:
I know exactly what this is. Get out of hard root and stay in your regular home folder. There are two things that will make this simple for you. 1. take the adb executable and place it in your users bin. so that would be something like /usr/bin...once again make sure you are in nautilus as the regular user and not root! 2. Now go back into your terminal and invoke it by typing sudo adb start-server...then sudo adb devices...the key thing here is that ubuntu's permissions are a bit screwy so you have to use adb in this manner. once again sudo everthing ("sudo adb" etc.)...do not become hard root in ubuntu (sudo su)
EDIT: btw if you use this method you will not have to worry about paths as long as it's in your user bin...you dont have to ./adb devices either if you do it this way
Javis
Click to expand...
Click to collapse
Thank you both for the advice! Both things worked very well and i appreciate the advise!

[Q] Cant get kindle fire into fastboot

Ive been trying out pokey'9000 [fastboot] stock 6.2.1 fastboot mode without rooting or cables to get my kindle fire into fastboot, I typed in the"adb shell " command and get:
"[email protected]: $" so i guess adb is working I then follow the next step,
"adb push fbmode /data/local/tmp"
and get:
"942 KB/s (510876 bytes in 0.529s)" then:
"adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode"
but just after this final line I get:
"fail opening shift: No such file or directory"
My kindle is rooted and has superuser access already but I cant get it into fastboot mode, also tried:
" adb shell su -c 'idme bootmode 4002' "
and get :
" Reading idme data...
Setting bootmode to 4002
writing new vars to temp area
you must reboot before new values will take efect "
I reboot my kindle bust still cant get into fastboot. What could I possibly be doing wrong?

Please Help Me Root my S4

Hi everyone,
I've recently just bought my first Android phone. What's the first thing I want to do with it? Root it and install hyperdrive. However, I am running into some problems with the rooting process itself, so if anyone could help that would be great....
I am on a Mac, so this rooting process is a tad more difficult than the Windows process, but not something that should be giving these errors. It should be noted that I was originally naive and installed Motochopper on my MK2 build before realizing that I needed to install saferoot. Since then, I have uninstalled superuser via the native uninstall function. I know there's about a 99% chance that the way I uninstalled that was incorrect, but I never actually reached a root from motochopper, so I thought I would have been fine. Please correct me If I am wrong. Anyway, upon using terminal to try and root, I get this result.
Code:
Last login: Tue Jan 28 16:52:33 on ttys001
Kevins-Mac-mini:~ kmcianfarini$ cd desktop
Kevins-Mac-mini:desktop kmcianfarini$ cd saferoot
Kevins-Mac-mini:saferoot kmcianfarini$ sh ./install.sh
--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
Waiting for device...
Watch your phone. Unlock it and give permission for the install to run.
./install.sh: line 10: adb: command not found
Sending files to your device...
./install.sh: line 12: adb: command not found
./install.sh: line 13: adb: command not found
./install.sh: line 14: adb: command not found
./install.sh: line 15: adb: command not found
./install.sh: line 16: adb: command not found
./install.sh: line 17: adb: command not found
./install.sh: line 18: adb: command not found
Starting rooting program.
./install.sh: line 21: adb: command not found
Removing temporary files...
./install.sh: line 24: adb: command not found
./install.sh: line 25: adb: command not found
./install.sh: line 26: adb: command not found
./install.sh: line 27: adb: command not found
./install.sh: line 28: adb: command not found
Rebooting...Please wait.
./install.sh: line 31: adb: command not found
Waiting for device to re-appear...
./install.sh: line 33: adb: command not found
Unlock your phone, and when prompted, give SuperSU permission for
'ADB shell' to run.
./install.sh: line 37: adb: command not found
./install.sh: line 38: adb: command not found
./install.sh: line 39: adb: command not found
./install.sh: line 40: adb: command not found
./install.sh: line 41: adb: command not found
./install.sh: line 42: adb: command not found
./install.sh: line 43: adb: command not found
./install.sh: line 44: adb: command not found
./install.sh: line 45: adb: command not found
./install.sh: line 46: adb: command not found
./install.sh: line 47: adb: command not found
./install.sh: line 48: adb: command not found
./install.sh: line 49: adb: command not found
./install.sh: line 50: adb: command not found
Installing busybox
./install.sh: line 52: adb: command not found
./install.sh: line 53: adb: command not found
./install.sh: line 54: adb: command not found
./install.sh: line 55: adb: command not found
./install.sh: line 56: adb: command not found
./install.sh: line 57: adb: command not found
--- All Finished ---
If someone could please help me that would be great. Thank you, and sorry for any form of ignorance I may be displaying. I have been used to iOS and the jailbreak community for a very long time.
Cheers
well i dont know much about iOS but i do have a S4 and im running on windows and for windows theres a software called kingoapp root you can try it maybe it supports for the iOS too... i must say you have to find a serial key before you root if not it wont root or else try rooting by installing custom recvovery like CWM or TWRP via odin and using the superuser apk...
Good Luck!

ADB SHELL: command fails "Applet not found" - hint: works via Terminal Emulator.

ADB SHELL: command fails "Applet not found" - hint: works via Terminal Emulator.
Hi,
Distro: Cyanogenmod 10.1.3-n7000 (Android 4.2.2).
Subject: Shell commands.
Error message: applet not found.
hints: issue only via ADB interface, commands do work inside Terminal Emulator on Android.
Voilà, i tried to be biref and straight.
I have check the first 5 pages thread but most are without response or suggestion are weaks.
The symlink thingy and other suggestion does not works.
It does NOT fails with all the commands in ADB shell, for instance sed, modinfo, less and so for work, but most the command related to network : ip, iproute get this error message "applet not found".
Although, they are all symlinked to busybox.

Categories

Resources