Database Users

root Tattoo with Mac

Hey Boys and Girls,
where i can find an manual to root the tattoo with a mac?
sorry, i have search for this, but i cant find information for this

I don't thing that there is a difference.
As soon as you have SDK installed and adb works, the commands are the same.

hi,
i'm also doing all the rooting process from mac, just put the directory contain 'adb' shell into your home/user places and executing it with 'terminal'..

Same here, using a Mac ever since and also using it for Android development. Due to the underlying Unix core of OS X you just have to follow the steps as described for Linux. If it's just adb commands it's the same on every platform anyway.
You might want to add a
Code:
export PATH=${PATH}:/Users/yourusername/android.sdk/tools
to your .bash_profile file in your home folder so you don't have to cd to the SDK tools folder everytime. Happy rooting!

Mod. edit: not dev related, moved to general

Okay thanks for yours answers but i'm a newbie.
the background story is, I want to edit the boot.mp3. Because the startsound is really annoying
So i have download SDK, open the terminal and switch to usb-debbugging mode on my tattoo.
And now? sorry, I'm still missing a few knowledge
thanks for your help

well just use the various adb commands in Terminal Just type in "adb", press enter and you'll get a list of all possible commands. Assuming you've added the path to your sdk tools folder to your bash profile. Otherwise just drag & drop the adb binary from the tools folder onto your Terminal window, et voila.
The most used commands are probably push and pull where you can, well, push stuff to your phone or pull it to your computer.
So if you want to modify the boot.mp3 you would pull the original from the phone to your computer, modify it and push it back, overwriting the original file. In Terminal speak: ;-)
adb pull /system/media/bootscreen/boot.mp3
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Please note depending on the ROM you're using the paths may be different. To browse the device via Terminal type in "adb shell" and make a simple "ls" to list the directories, "cd" to change directories etc.
Or if you just want to use another mp3:
adb push /path/to/whatever.mp3 /system/media/bootscreen/boot.mp3
Again, on the Mac you can just drag & drop files onto the Terminal to get their full Unix paths like to your custom mp3

Thanks a lot. i love it its really simple
and now i have load and edit the the boot.mp3. But i can't push it to my tattoo, because i can only read but not write
I have tried to root my phone with "adb root" but it is the message "adbd cannot run as root in production builds"

Terminal: "adb remount", then push again

damn the next bad message "remount failed: Operation not permitted"

You need to root your phone first.
http://forum.xda-developers.com/showthread.php?t=637927

Okay i have executed the instructions. But I've stop at this part:
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
Yes i've root but i'cant download the "su binary" because its doesnt exist.
But its absolute essential to need the "su binary" to only copy the boot.mp3 to my phone? Or there is an other way? What are the commands to push the boot.mp3 back to may tattoo then i'm in the root mode like >> "#".
okay hope you understand me

You need "su" to do root stuff... no other way.
Download the package from 1 click root thread and find "su" there...
http://forum.xda-developers.com/showthread.php?t=644279

now, i have install the su binary. Then i does this command
user:~ user$ /Users/user/android-sdk-mac_86/tools/adb shell
$ /data/local/bin/su
#
Click to expand...
Click to collapse
And now? Is there a comand to push the boot.mp3 back to the phone in this mode >> "#" ?
I have try to open an new terminal window and type
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
but the answer is
failed to copy '/Users/android-sdk-mac_86/boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied
Click to expand...
Click to collapse
and adb remount doesnt work to

You also need tattoo-hack.ko file and do insmod tattoo-hack.ko to make /system writable.
Or even better... flash custom amon_ra recovery image and then a custom rom with all this already included.
Mine for example http://forum.xda-developers.com/showthread.php?t=702401
It doesnt have boot sound enabled

Okay thank you very much.
now it was successful

[Error] Unable to apply PUSH Command in ADB

Hello mates,
I am trying to Copy the BUSYBOX file to my /data/local/bin directory. But when i use the 'push' command it say adb: command not found. Hereby i have attached the image of my terminal.
Would you please help me in copying my files to the directory "/data/bin/local"
Also, where should i put the files which i need to copy. Eg. Since i need to copy 'busybox' to the /data/local/bin/, should i put the busybox in my Desktop, i.e. /home/android/platform-tools directory?

You should've not run the command from within the adb shell. Just go to the tools folder and type "adb push busybox data/local/bin" ofcourse without the ""
The busybox should be indeed be present in the folder from witch you run adb, in your case the "tool" folder.
Good luck!
Erwin
Sent from my HTC Wildfire using XDA App

@ErwinP.
Thanks for rectifying this mistake.
It worked.

You're welcome! I had to learn it the hard way myself, so I'm happy ik I can help someone! ;-)

Unable to "push su" in rooting my Xoom (push: not found) - any ideas?

So I just got to one of the final steps in rooting my xoom, but for some reason, when I enter the "push su /system/bin/" command, I get a "push: not found" response. I'm completely stuck at this step...anyone have any ideas on this one??

Was adb remount succesful before you tried?

joeski27 said:
So I just got to one of the final steps in rooting my xoom, but for some reason, when I enter the "push su /system/bin/" command, I get a "push: not found" response. I'm completely stuck at this step...anyone have any ideas on this one??
Click to expand...
Click to collapse
I ran in to this. Make sure your Xoom is not on the lock screen. Should be good to go.

PaulG1488 said:
Was adb remount succesful before you tried?
Click to expand...
Click to collapse
Yes, adb remount was in fact successful.
Edit - now I'm getting "cannot stat 'su': No such file or directory"

just to be clear, is it supposed to be:
adb push su /system/bin/
or
adb shell push su /system/bin/
???

syntax is "adb push ..."

bcgaynor82 said:
syntax is "adb push ..."
Click to expand...
Click to collapse
thats what I thought, and when I do this I get the "cannot stat 'su': No such file or directory" error message.
I have no idea what's going on here. Its almost as if I dont have the xoomroot files (including su) in the correct place, but they are there in the SDK tools folder as they are supposed to be. UGH!?!!?

joeski27 said:
thats what I thought, and when I do this I get the "cannot stat 'su': No such file or directory" error message. ?????
Click to expand...
Click to collapse
Make sure that one of the following is true:
the files you want to push are in the same folder as adb
adb is in your path and you are in the directory that the files are
Also make sure you are running this from your computer and not the Xoom, although it sounds like you are bumping into one of the two scenarios above.

nindoja said:
Make sure that one of the following is true:
the files you want to push are in the same folder as adb
adb is in your path and you are in the directory that the files are
Also make sure you are running this from your computer and not the Xoom, although it sounds like you are bumping into one of the two scenarios above.
Click to expand...
Click to collapse
yes they are in the same folder as adb, and I'm in the adb directory while in terminal. still getting the same error message. I'm so lost on this one.

Is there any chance that the unlock didn't take? Though I can't see how it didn't - I went through the entire procedure, answered all the prompts during fastboot, and it did erase/reset the tablet afterwards, so I'm guessing that isn't it.

joeski27 said:
yes they are in the same folder as adb, and I'm in the adb directory while in terminal. still getting the same error message. I'm so lost on this one.
Click to expand...
Click to collapse
Any chance you can screenshot your sdk tools folder

They're supposed to be in the 'platform-tools' folder, not tools. The files go in the same folder as adb so it knows where they are.

PaulG1488 said:
Any chance you can screenshot your sdk tools folder
Click to expand...
Click to collapse
Screenshot of my sdk tools folder:
EDIT: heres the link:
http://i869.photobucket.com/albums/ab259/olesweski/Screenshot2011-03-03at122552AM.png?t=1299130486

Elysian893 said:
They're supposed to be in the 'platform-tools' folder, not tools. The files go in the same folder as adb so it knows where they are.
Click to expand...
Click to collapse
I know, but I had already moved adb into the tools folder earlier on. So they are in the same folder.

send a screenshot of everything in your command prompt if u can please

PaulG1488 said:
send a screenshot of everything in your command prompt if u can please
Click to expand...
Click to collapse
here's the screenshot of my terminal:
http://i869.photobucket.com/albums/ab259/olesweski/Screenshot2011-03-03at124929AM.png?t=1299131460

Do you have the 3.0 sdk installed
Wait I see the problem after you remounted you have to direct it back into your tools foledr before doing the adb push command

PaulG1488 said:
Do you have the 3.0 sdk installed
Click to expand...
Click to collapse
all I know is that i have the latest sdk installed, but are you referring to something additional to that? such as "SDK Platform Android 3.0, API 11, revision 1" ?

joeski27 said:
all I know is that i have the latest sdk installed, but are you referring to something additional to that?
Click to expand...
Click to collapse
After u did adb remount it took you back to your main folder make sure you direct it back to your tools folder then run the adb push command and problem will be solved

PaulG1488 said:
After u did adb remount it took you back to your main folder make sure you direct it back to your tools folder then run the adb push command and problem will be solved
Click to expand...
Click to collapse
So I just did the remount again (successfully), and now instead of just entering "adb push ...", I would need to do what?
EDIT - just tried this, and got this result:
Joseph-Olesweskis-iMac:~ olesweski$ /Users/olesweski/Desktop/android-sdk-mac_x86/tools adb push su /system/bin/
-bash: /Users/olesweski/Desktop/android-sdk-mac_x86/tools: is a directory

[Q] Is it possible to push apps via adb to an encrypted xoom?

the subject says it all. I've been trying to push apps to my encrypted xoom all afternoon without any luck...
I'll go ahead and admit upfront that I am a noob when it comes to using the sdk... so that could also be a major factor.

adb install (insert exact location+ filename.apk for the app you want to install)
I just tested it out
for example
adb install C:/abc.apk

What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.

scsa20 said:
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
Click to expand...
Click to collapse
I just tried to execute adb remount (I had not until you mentioned it), but I get a "remount failed: operation not permitted".
Code:
Hannibal:platform-tools dmoore$ ./adb install /Users/dmoore/Documents/android-sdk/platform-tools/AsusReader.apk
1259 KB/s (7747001 bytes in 6.007s)
pkg: /data/local/tmp/AsusReader.apk
Failure [INSTALL_FAILED_DEXOPT]
Additional information: I am on a MacBook Pro using the latest version of the SDK (downloaded it yesterday).

try typing "adb devices" if it does not list your xoom try installing or re-installing the motorola usb drivers
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/

Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?

Sic123 said:
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Click to expand...
Click to collapse
I've already installed the Android File Transfer app... it only allows me to browse the SD card - not the root fs... unless there's something I'm missing...

dmoore44 said:
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Click to expand...
Click to collapse
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file

Sic123 said:
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Click to expand...
Click to collapse
I have the odex file, so i'm not terribly worried about that.
My major question would be this though... Do I need to go full blown root, or can I just unlock the device?

- exec '/system/bin/sh' failed: No such file or directory (2) -

I am running the cm7 rom but last night I installed busybox and ran the v6 supercharger script. Now my wifi no longer works. I tried to install the new version of cm7 but I get this error when i try to access dab shell.
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is it possible to fix this? if not what is the easiest way to return to stock and start over. Thank you.

rydinsmoothx said:
I am running the cm7 rom but last night I installed busybox and ran the v6 supercharger script. Now my wifi no longer works. I tried to install the new version of cm7 but I get this error when i try to access dab shell.
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is it possible to fix this? if not what is the easiest way to return to stock and start over. Thank you.
Click to expand...
Click to collapse
Not gonna happen unless you can get into recovery or have the special usb cable to throw your device into fastboot (search the unbricking thread for more information on that). If you get lucky and can fix it + revert to stock, I would not install cm7 again until doing so is more noob friendly and forgiving.
The issues people are having with installing cm7 and severely screwing up their kindle are pretty epidemic due to the issues with recovery for those that don't prepare ahead of time for the possibility of disaster. The maintainer should really either close it out for now to the public or make the disclaimer much larger.

I have the same error. This is end. Only Factory Cable can help you but even with this cable I'm not sure what you can restore it.

i can still operate the kindle fire. I'm looking in /system/bin folder and it appears i am missing the sh file. if i replace it can i gain dab shell access again? if this is possible where can i get the sh file?

rydinsmoothx said:
i can still operate the kindle fire. I'm looking in /system/bin folder and it appears i am missing the sh file. if i replace it can i gain dab shell access again? if this is possible where can i get the sh file?
Click to expand...
Click to collapse
Operate how? Also, please don't double post in 2 threads.

My bad . It boots into cm7. I'm missing the sh file for some reason. Wifi also stopped working and Some apps don't work. This Happened after i used v6 supercharger. My goal is to go back to stock but I can't access adb shell.

rydinsmoothx said:
My bad . It boots into cm7. I'm missing the sh file for some reason. Wifi also stopped working and Some apps don't work. This Happened after i used v6 supercharger. My goal is to go back to stock but I can't access adb shell.
Click to expand...
Click to collapse
Could be a bit more explicit. Boots as in "yay, i see a logo and can't use my device beyond a paperweight that displays the cm7 logo" or boots as in "yay, i can use my device like normal and it's not bricked or malfunctioning"
Anyways, if you actually have root privileges and can mount system in read/write, get the sh binary out of the CM7 download by unzipping it or whatever and copy it over, making sure to match the owner/group and permissions that the other things in the /system/bin directory have. Since I'm guessing you're not command line savvy, I recommend doing this in root explorer or buying it if you do not have it.
Also, many of us do not own kindles and a larger % are also not running cm7 on their kindle so saying "i ran some random script that I won't say what it does and where I found it" does not help your situation either as far as getting a helpful answer.

Can you type ADB DEVICES at your command line and get a device? What about fastboot? Can you get devices to show there while at the command line?If yes, I am sure you can flash the CWM recovery to get ADB, then follow the steps to get back to stock...Dont blame me though if it doesnt work

I got the script script from someone in the cm7 thread, its supposed to opitimize the ram usage thus making the rom more smooth. He said it worked for him so I gave it a shot. I think it unrooted my kindle because I can't gain root access with root explorer. My devices shows up in adb devices but since I can't use adb shell I can't enable the fast boot.