I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU CAUSE!
So you are stumbling around XDA and you really want some kind of app or something, but you think you cant because you have a Mac, well I am here to tell you wrong.
The biggest and most used mistake for mac users when trying to use ADB is this:
HTML:
Inas-iMac:~ Hans$ /AndroidSDk/tools
-bash: /AndroidSDk/tools: is a directory
Inas-iMac:~ Hans$
Well this is how you do it!
Watch this!
http://www.youtube.com/watch?v=GLAMG4xU_lE
To make your phone go into debug mode go to settings/applications/development and check debug
DO NOT MOUNT PHONE! Just let it be
I did not go to deep into the process because this is made for complete beginners!
Why not follow the official SDK install instructions and add the path to bash_profile..
developer.android.com/sdk/installing.html#Installing
In my opinion that's not too hard for a newbie.. (i managed to do that) And after doing that you don't need to change directories with cd command, you can just type adb whatevercommand from your home dir which is the default location when you open the terminal.
Drag and drop is a little a fail.... one can add "alias" (linux can do it, probably mac too)
Little How-to:
Code:
$ nano ./bashrc
add and adapt the following line to bashrc:
Code:
alias adb="/home/carbonyle/android-sdk-linux_86/tools/adb"
now you just have to type "adb" from a terminal emulator to run it, eg:
Code:
$ adb shell
# reboot recovery
or
Code:
adb install ./Download/myFavortiteApp.apk
and so on...
ps: we don't need to "adb remount" at worst we can just "adb kill-server" then "adb start-server" if the device is not accessible
So i rooted my desire using the modaco r6 root.
I'm using defrost 1.0 atm and when I'm entering recovery i cant use any adb command, except for devices which show my desire in recovery mode.
all other commands return an error like:
su:
/sbin/sh: su: not found
logcat:
/sbin/sh: exec: line 1: logcat: not found
install
/sbin/sh: pm: not found
just to name a few.
i just got it so i don't know if they worked before.
however i did get one boot loop due to flashing the circle battery mode.
after which i recovered the nandroid backup.
If you need more info tell me what to do im clueless, im prolly just doing something very stupid.
Thanks in advance.
Go into partitions menu and mount /system then try.
No go doesn't even change the error.
so no ideas? i got no wifi or 3g connectivity atm so you guys are my last resort.
just some updates i flashed mcr 3.1 and it change in addition htc sync doesn't recognize my desire now.
you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?
Can you not boot into fastboot. Volume down and power. Then go to recovery. Then hold volume up and power. Select wipe data and wipe cache. Wouldn't that solve your wifi issues etc?
Wait...if you're using root r6 then your using fake flash aren't you? Try looking for r5 and use pauls recovery or look for amskghs recovery and use that. Pretty sure adb stuff doesn't work easily with fake-flash.
cgrec92 said:
you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?
Click to expand...
Click to collapse
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.
Hash = #
What exact commands are you doing and what are you trying to achieve?
I really want to help
LByte said:
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.
Click to expand...
Click to collapse
I had your same problems and felt retarded too, but it might be something funky with the dos command prompt in windows. Follow these instructions to make adb commands universal so it doesn't matter what directory the dos command prompt thinks you're in (because obviously it didn't actually move you to the tools folder somehow even though you instructed it too):
- Also, Mikey1022 has reminded me to add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android-sdk-windows-1.1_r1\tools
This was found here: sorry can't post link to give proper credit, but do a google search for adb for dummies or adb commands, it's an xda forum post...
The thread looks dead, but im going to post the possible solution anyway.
PM commands like install and uninstall doesnt work in recovery mode, so if you want to use them, run the commands when the phone had booted normally.
i have same problem? anyone help me
adb error /sbin/sh: exec: line 1: logcat: not found
SOLVED! Followed the Guide in Post #5, than kept getting an error saying libncurse.so.5 cannot be found. I than opened the Package Manager and downloaded everything in the sun-java6-sdk and anything related to it. Than searched for anything of libncurse and installed those. than got a libc++ (or similar) missing than went back to Package Manager and download anything with libc++ in it. Afterwards, ran fine.
One quirk, as I'm sure this will be general knowledge to any Linux user but I am still a newbie at it. In root # i had to do ./adb to run the command, running just # abd gave me errors, exiting root back to $ alowed me to just use $ adb and not have to do ./adb
I know it's pretty shoddy, I think i downloaded 250MB of stuff I'm not sure I need. lol. I searched for the libncurse.so.5 file and had a lot of em, i think the package that actually did the trick was a ncurse32bit package, as I am on a 64 bit system. So take that into consideration
downloaded the android sdk, extracted it, however, when i use terminal and goto the tools folder and use adb
i get...
[email protected] /usr/bin/android-sdk/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 '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)
adb: command not found
Click to expand...
Click to collapse
I read something about adding it to path, and i went into my .profile and added in the :/usr/bin/android-sdk/tools after the $PATH yaddayadda but it still didn't work.
Any help is appreciated. This is really the only thing keeping me from wiping the 120gb partition for Win7 and using Linux only(which only has a 21gb partition)
Nrre said:
downloaded the android sdk, extracted it, however, when i use terminal and goto the tools folder and use adb
i get...
I read something about adding it to path, and i went into my .profile and added in the :/usr/bin/android-sdk/tools after the $PATH yaddayadda but it still didn't work.
Any help is appreciated. This is really the only thing keeping me from wiping the 120gb partition for Win7 and using Linux only(which only has a 21gb partition)
Click to expand...
Click to collapse
Since the android sdk doesn't actually install on your computer but placed there by you, you must make sure everything is in place for it to work properly. I am relatively new to linux myself, but this is what i've done to get it working properly:
create /etc/init.d/adbd
you will need to do this as root.
Code:
gksu gedit /etc/init.d/adbd
paste this into the file
Code:
#!/bin/sh
#
# For ADB deamon (Android Device Bridge)
#
case "$1" in
start)
/usr/bin/android-sdk/tools/adb start-server
;;
stop)
/usr/bin/android-sdk/tools/adb kill-server
;;
*)
echo "Usage: $0 start|stop" >&2
exit 3
;;
esac
now run this:
Code:
sudo ln -s /etc/init.d/adbd /etc/rc2.d/S10adbd
What you just did there was make sure adb daemon started as root whenever you booted (if you don't start it as root you will get errors later on down the road)
I'm not sure about mint, but on ubuntu its easier to just add the tools folder to your /etc/environment file.
Code:
gksu gedit /etc/environment
the file should look something like this:
Code:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/bin/android-sdk/tools"
go ahead and reboot just to make sure everything sticks. You should be good from then on.
You could add the path to your profile, but then if you have to run something as sudo, or if you have another user trying to do something similar, it could be a headache. If you don't have a /etc/environment, or if the above still doesn't work, go ahead and see if you have a ~/.bashrc.
edit that:
Code:
gksu gedit ~/.bashrc
add this to the bottom:
Code:
export PATH=${PATH}:/usr/bin/android-sdk/tools
let me know if this works, and if there are any more experienced linux users out there who notice any mistakes of mine, or have better advice please chip in. I just know I went through a huge amount of frustration to get adb to work properly, through much trial and error. this is the culmination of what i went through that was easiest for me. BTW i stole that code for the daemon to startup as root from somewhere else.
EDIT: I just realized my daemon is still not starting on boot? although, with the above script i can start it via:
Code:
sudo service adbd start
someone smarter than me, chip in and tell me what i'm doing wrong?
OP, you can always start the daemon yourself as root by typing
Code:
sudo /usr/bin/android-sdk/tools/adb start-server
EDIT: woops. I fixed the code above, as well as fixed my problem. on creating a link to rc2.d i typed "s10adbd" originally and it should be "S10adbd".
OP, this is a great example why paying attention to capital/lower case letters are super important when learning linux.
i changed my link and everything works on my system.
think i'm still doing it wrong. i didn't have a .bashrc file but i did have a bash.bashrc file.
i know linux mint is based off ubuntu.
here is my command line after doing everything above
richard-laptop richard # /usr/bin/android-sdk/tools/adb start-server
/usr/bin/android-sdk/tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
richard-laptop richard # sudo service adbd start
adbd: unrecognized service
richard-laptop richard # adb shell
adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse
think i'll take the laptop into work and mess with it tonight.
If you don't setup a your bash file, you can issue adb commands by using standard terminal commands from the /tools directory:
user:~$ ./adb start-server
Click to expand...
Click to collapse
To setup your .bash file, right from Google:
# On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ directory to it. If you don't see a line setting the path, you can add one:
export PATH=${PATH}:<your_sdk_dir>/tools
Click to expand...
Click to collapse
From terminal, you can run
user:~$ gedit ~/.bashrc
Click to expand...
Click to collapse
Nrre said:
think i'll take the laptop into work and mess with it tonight.
Click to expand...
Click to collapse
Please follow these instructions (source = wiki.cyanogenmod.com):
Ubuntu: Android SDK, ADB, Fastboot.
There are various great tutorials online to help you set these options up for Windows, but the process of setting this up in Ubuntu Linux is rather fragmented across various different forums, and can be rather confusing! This is a tutorial I have put together after having real trouble setting it up myself, after trawling through numerous forums, and getting help from many very helpful folks on various forums including this one!
Tutorial: This will show you how to complete the basic set up of the Android sdk, and then how to enable the 'adb' and 'fastboot' connections so as to allow you to issue commands from the terminal directly to your phone.
Disclaimer: As always, you follow this tutorial at your own risk, nobody is forcing you to! I take absolutely no responsibility for damage to your computer / mobile phone etc. This is the process I have followed, and it is working fine!
Basic Android sdk installation and set-up:
You will need to download the following files before you start:
android_sdk_r05-linux_86.tgz [1]
Fastboot [2]
1. Extract the 'android_sdk_r05-linux_86.tgz' file to your 'Home' folder and rename it to 'sdk' to make things easier later on.
2. Move the fastboot file in to the 'Tools' folder inside the 'sdk' folder.
3. Now right click on both the 'fastboot' and 'adb' files (inside the tools folder) and choose 'Properties' and then the 'Permissions' tab, and ensure they both have the 'allow executing file as program' box is ticked...Now reboot the computer, sorted!
Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal
1.Open your 'Home' folder. Press 'Ctrl' & 'H' at the same time to view hidden files, and then open the '.bashrc' file and add the following text to the top of the file:
#AndroidDev PATH
export PATH=$PATH:/home/username/sdk/tools
2.Obviously you will need to replace 'username' with your own...Save the file and exit.
3.Now log-in as root.
3. Navigate to the following directory in the root filesystem: /etc/udev/rules.d/
4. Create the following empty file:
(ubuntu 10.04)
99-android.rules
(ubuntu 9.10)
70-android.rules
(ubuntu 7.10/8.04)
51-android.rules
5. You then need to edit the file with the following text (depending on your version of ubuntu):
ubuntu 7.10/8.04/9.10:
SUBSYSTEM==”usb”, ATTRS{idVendor}==”0bb4”, MODE=”0666”
SUBSYSTEM==”usb”, ATTRS{idVendor}==”18d1”, MODE=”0666”
SUBSYSTEM==”usb”, ATTRS{idVendor}==”22b8”, MODE=”0666”
ubuntu 6.06:
SUBSYSTEM==”usb_device”, SYSFS{idvendor}==”0bb4”, MODE=”0666”
SUBSYSTEM==”usb_device”, SYSFS{idvendor}==”18d1”, MODE=”0666”
SUBSYSTEM==”usb_device”, SYSFS{idvendor}==”22b8”, MODE=”0666”
6. Save this file, and then open the terminal and enter the following command:
chmod a+rx /etc/udev/rules.d/70-android.rules
Change the '70' to '51' depending on your version of ubuntu.
For a list of the vendor ID's go here: VendorID's [3]
7. Now reboot the computer.
8. Open Terminal, and issue the following commands:
su
cd /home/username/sdk/tools/
./adb kill-server
./adb start-server
You will now be able to open a terminal and carry out 'adb' and 'fastboot' commands directly.
Credit and thanks to:
koalaboy, Apostasy, Cloverdale, wddglr, JgeZau.
EDIT: I have followed this tutorial to the letter myself today on my laptop to prove it works, for both yours the reader, and my own peace of mind as the writer! Enjoy, it works flawlessly!
Click to expand...
Click to collapse
I have followed these directions more than once and each time they work flawlessly. This should work with Linux Mint, since Mint's based off Ubuntu.
For Part 4, use Ubuntu 10.04 when creating the empty file and for Part 5, use this SUBSYSTEM: SUBSYSTEM==”usb”, ATTRS{idVendor}==”0bb4”, MODE=”0666” and paste that into your 99-android.rules file.
followed to a T.
not sure how to log in as root, so i just 'run as administrator' i can't find anything on root for this.
i still get the following after i do that entire guide
richard-laptop richard # cd /home/richard/sdk/tools
richard-laptop tools # ./adb kill-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
richard-laptop tools # ./adb start-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse
Nrre said:
followed to a T.
not sure how to log in as root, so i just 'run as administrator' i can't find anything on root for this.
i still get the following after i do that entire guide
Click to expand...
Click to collapse
To login in as root, you enter:
Code:
sudo su
As for the "error while loading shared libraries: libncurses.so.5" -- I've never seen that error before. Might be Linux Mint problem? I currently run Ubuntu 10.04 32 Bit.
when i do SU it asks my password and the $ becomes a #
i assume that is root? i dont have to do SUDO i just did SU
yeah if i do SUDU SU i get a 'SUDO command not found'
gonna post this over on the linux mint forums see if they can help me to.
Nrre said:
when i do SU it asks my password and the $ becomes a #
i assume that is root? i dont have to do SUDO i just did SU
yeah if i do SUDU SU i get a 'SUDO command not found'
gonna post this over on the linux mint forums see if they can help me to.
Click to expand...
Click to collapse
Wait... wait.. are you trying to do following instructions on your phone or on your computer?
If you run su on your phone, sure you'll get root (# sign). But the command, sudo su was meant for your computer. The instructions I listed are for your computer with Linux Mint installed.
yeah i'm doing it on my computer =P
if i do SUDU SU it gives me that error, but SU gives me #
so...i was hoping it'd all be teh same since Mint is based off ubuntu and half my updates are ubuntu files.
[email protected] ~ $ sudu
No command 'sudu' found, did you mean:
Command 'sudo' from package 'sudo' (main)
Command 'sudo' from package 'sudo-ldap' (universe)
Command 'tudu' from package 'tudu' (universe)
sudu: command not found
[email protected] ~ $ SUDU su
SUDU: command not found
[email protected] ~ $ SUDU SU
SUDU: command not found
Click to expand...
Click to collapse
so, not sure what else to do.
sudo
not sudu
elegantai said:
sudo
not sudu
Click to expand...
Click to collapse
balls, well i still get the same result after i go through and make all the changes and use SUDO SU instead of just SU, i get the same prompt with #
this is still my end result.
richard-laptop richard # cd /home/richard/sdk/tools/
richard-laptop tools # ./adb kill-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
richard-laptop tools # ./adb start-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse
makes me feel like i'm missing a file somewhere. i did download the newest android sdk and not the older version that is in the guide. but i still installed the packages for android 2.1 and 2.2
suppose i'll delete it all and start over.
EDIT: Went through, put in proper vendor IDs and noticed i put Richard in the Path and not richard, still, says it's missing the same "libncurses.so.5" so...not sure what to do. =/
I don't know that error either, but looking at this thread:
http://bbs.archlinux.org/viewtopic.php?id=66878
sounds like it could be a java issue? Didn't think to ask, have you installed the java sdk? which version of java are you running?
now that i think about it...i don't believe i downloaded a new java...
the worse news is my win7 got corrupted somehow =P so now i only have Linux so time to dig in and try this out.
I'd download the stuff now but I'm tethering through my phone so i'm lucky to get 600kbps download speeds in this reception area.
I could step 10 feet outside and hit 1200kbps though. So i formatted the HD and reinstalled Linux Mint. Once i get home I'll look into the JDK as that makes sense now that I think about it to.
EDIT: Should I install Eclipse also? Installing Android SDK and Java6 JDK right now. I really just want to use ADB for now to send commands to phone etc.
No need for eclipse.. That's just for actual development
ADB Error: /home/richard/sdk/tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
'adb start-server' failed.
Click to expand...
Click to collapse
this shows up int he Android SDK/AVD manager as i install all the packages...
EDIT: opened up software manager, and downloaded every sun-java package, than installed everything that showed up when i typed libncurses ... once it's done will reboot and try again =P
2nd EDIT: i decided to search for libncurses.so.5 and i have 3 of em, one in usr/lib, /lib64 and something else.
so..not sure where else to put it, went into synaptics thing or something and downloaded ncurses32bit as i noticed none of my lib32 folders had it...giving it a go.
btw... my .bashrc is .profile, i copied .profile and renamed it to .bashrc and my prompt stopped showing up in terminal...linux is so weird.
3rd EDIT: Just isn't meant to be. got to ./adb kill-server and instead of missing the libncurse.so.5 i am now missing..
richard-laptop tools # ./adb kill-server
./adb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse
off i go to hunt this package down
it's working...finally
however...
richard-laptop tools # adb devices
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 '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)
adb: command not found
richard-laptop tools # ./adb devices
List of devices attached
HT*********** device
Click to expand...
Click to collapse
i have ot do ./adb and not just adb
EDIT: exit su, and in $, lets me just do adb.
THANK YOU EVERYONE <3 Wish I could +rep or Thanks your post here.!!
changed title to reflect it. was a good 'thrown under the bus' into linux. now to read up more on it. w/out losing half my CCNA knowledge i've gathered...ha
Enjoy Linux. You'll enjoy it once you get used to it.
Sent from my PC36100 using XDA App
Nrre said:
it's working...finally
however...
i have ot do ./adb and not just adb
EDIT: exit su, and in $, lets me just do adb.
THANK YOU EVERYONE <3 Wish I could +rep or Thanks your post here.!!
changed title to reflect it. was a good 'thrown under the bus' into linux. now to read up more on it. w/out losing half my CCNA knowledge i've gathered...ha
Click to expand...
Click to collapse
Since this has been solved, I would advise posting the resolution on the first page -- so new users are aware of what exactly you had to do to fix it.
ok i want to know if anyone else has this, if so is there a way for my to turn it off or something, when i do adb shell it gives extra stuff like numbers and other stuff if doesnt just give me listing of files
to understand better look at picture
Those are the linux shell colour codes... for colouful text
unfortunately the windows cmd shell can't handle these.
This thread should hopefully sort you out.
HTH
thanks ! but this jus happen soon as i updated the stupid SDK,as well is there a Permanent fix for this for Windows cmd, instead my getting another terminal shell
so i gave that a try and all im getting is
not found
So does the link help or not?
Does this work for you ls --color=never
i knew that command for a temp color off but to have it fully off while in adb shell you have to do alias ls-'ls --color=never'
this is still a temp fix not a permanent one, i was hoping to find one but so far there is non other than using a different type of cmd prompt/terminal that supports it
Try what is mentioned in post 2 of that thread.
once you've done that, instead of typing ls
you would type ll (which just executes ls with the no color flag)
I just found this thread which may be of interest too.
Its an app called ansicon which will enable coloured output on a windows shell.
Just downloaded & tried it out... it works!
waydownsouth said:
Try what is mentioned in post 2 of that thread.
once you've done that, instead of typing ls
you would type ll (which just executes ls with the no color flag)
Click to expand...
Click to collapse
i did and i got
"not Found"
edit
Ok so i did the ansicon way, what i did was downloaded the right setup for my laptop X64
i placed it in my program files
then i ran ansicon.exe and terminal pop up
after that i did this in it
ansicon.exe -i
after i closed it and open regular cmd pmpt and did adb shell and BAM no more wacky characters shows colors in regualr cmd thnks and sweet
i read through all the posts and am having trouble. i have a macbook now and my htc one v is stuck in a boot loop. i need some simple instructions or a link to how to flash a kernel on mac. i have googled it ect and i may be dumb or i cant seem to find the answer and everyone is always so helpful here and im getting frustrated. thank you so much. my phone is already rooted with a custom recovery. its a virgin mobile us
Go developer.android.com and download the SDK & move it to your home directory ("~" or /Users/<username>)
Go to <sdk-location>/tools and launch "Android"
Download the platform tools
Open terminal
Open Finder to <sdk-location>/platform-tools
In terminal, type "sudo cp"; drag adb from the Finder window into the Terminal window; type "/usr/bin/"; hit enter
Enter your password
Repeat the above three steps, but drag "fastboot" instead of "adb"
Close terminal
Open terminal (it sounds weird, but just do it)
Now, and forever, do this to install a kernel:
Download kernel
Connect phone to computer
Make sure USB Debugging is enabled (Settings>Development>USB Debugging)
In terminal, type "adb reboot bootloader"
In terminal, type "fastboot flash boot"; drag in the kernel from finder; hit enter
Examples:
Code:
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
adb reboot recovery
fastboot flash boot /Users/Username/Downloads/boot.img
kalaker said:
Go developer.android.com and download the SDK & move it to your home directory ("~" or /Users/<username>)
Go to <sdk-location>/tools and launch "Android"
Download the platform tools
Open terminal
Open Finder to <sdk-location>/platform-tools
In terminal, type "sudo cp"; drag adb from the Finder window into the Terminal window; type "/usr/bin/"; hit enter
Enter your password
Repeat the above three steps, but drag "fastboot" instead of "adb"
Close terminal
Open terminal (it sounds weird, but just do it)
Now, and forever, do this to install a kernel:
Download kernel
Connect phone to computer
Make sure USB Debugging is enabled (Settings>Development>USB Debugging)
In terminal, type "adb reboot bootloader"
In terminal, type "fastboot flash boot"; drag in the kernel from finder; hit enter
Examples:
Code:
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
adb reboot recovery
fastboot flash boot /Users/Username/Downloads/boot.img
Click to expand...
Click to collapse
kalekar, mid if i take this instructions and put them in my thread?
cybervibin said:
kalekar, mid if i take this instructions and put them in my thread?
Click to expand...
Click to collapse
No problem! You may want to clean them up a bit; I was in a hurry when I typed those.
sure thanks ill credit u for it
Moved to Q&A
Moderating from my One Xl
It's very simple. Follow whatever instructions are for the kernel, rom, whatever, but add "./" in front of the commands. So "fastboot flash boot" becomes "./fastboot flash boot"
Sent from Hoth.
MonsterNo7 said:
It's very simple. Follow whatever instructions are for the kernel, rom, whatever, but add "./" in front of the commands. So "fastboot flash boot" becomes "./fastboot flash boot"
Sent from Hoth.
Click to expand...
Click to collapse
No! That only works if he has done
Code:
cd <sdkdir>/platform-tools
other wise, it will fail and confuse him even more. Doing cp to /usr/bin/ will allow him to never have to do "./" before the command.
kalaker said:
No! That only works if he has done
Code:
cd /platform-tools
other wise, it will fail and confuse him even more. Doing cp to /usr/bin/ will allow him to never have to do "./" before the command.
Click to expand...
Click to collapse
Ok ok calm down. I do it my way multiple times a week, I've never had an issue. Sure I have to cd into the directory, but that's only one more line of code. If your way will be easier then cool.
Sent from Hoth.