Database Users

Need Mac Beta Testers: Interface for Pushing Files

Hello,
I need beta testers running Mac OS X to test a new application.
This application is for people who are either uncomfortable or unwilling to use Terminal and ./adb for pushing files to their device.
This first beta version is just to test how it works on different computers. It pushes the file to the sdcard of the phone using ./adb. The only input needed from the user is to select the file.
Later releases will let the user choose which folder on the device to copy to, but the next release will probably just involve pushing .apk to the /system/app folder.
Please let me know the results.
http://derekcwilkinson.com/PushFile.zip
Beta 2:
http://derekcwilkinson.com/Push_File_Beta_2.zip
Change Log:
Added option to choose the location that the file is to be pushed to.
Added Recovery application
Added Reboot application.
Planned Updates:
Pull File - Ready
Device Backup - PM me if you know a good way to backup with ./adb (mine is taking too long)
Device Backup w/SD - PM me if you know a good way to backup with ./adb (mine is taking too long)
Install .apk - testing
Uninstall .apk - testing
Restore Backup - going to take awhile (need to get device backup working first)
Restore Backup w/SD - going to take awhile (need to get device backup working first)
Flash ROM - testing

is this an actual program or a script?

Works fine for me

mrchu001 said:
is this an actual program or a script?
Click to expand...
Click to collapse
It's a program that runs a script
It's just a test to see how it works, I will turn it into a more "real" application later.

I've updated it to Beta 2

I'm copied/pasted the android folder into /User/document but when i run "Push File With Location" show this error message -->
( iMac Snow Leopard v.10.6.3 build 10D573

@rainbow
same thing happening to me!

rainbow2112 said:
I'm copied/pasted the android folder into /User/document but when i run "Push File With Location" show this error message -->
( iMac Snow Leopard v.10.6.3 build 10D573
Click to expand...
Click to collapse
Hmm, strange, I haven't had any beta testers have this issue.
Is the phone connected with USB debugging?

derekwilkinson said:
Is the phone connected with USB debugging?
Click to expand...
Click to collapse
Yes, I have always flag on debugging USB mode.

rainbow2112 said:
Yes, I have always flag on debugging USB mode.
Click to expand...
Click to collapse
Try this, and tell me where the error comes up.
http://derekcwilkinson.com/PushFileSource.zip

derekwilkinson said:
Try this, and tell me where the error comes up.
http://derekcwilkinson.com/PushFileSource.zip
Click to expand...
Click to collapse
When run this, automator show this windows ...

rainbow2112 said:
When run this, automator show this windows ...
Click to expand...
Click to collapse
Ah, you're using a different language. That could be the problem. Is the folder path still /Documents/Android/SDK/tools on your computer?
Also, when you run it in Automator, where does the error occur?

derekwilkinson said:
Ah, you're using a different language. That could be the problem. Is the folder path still /Documents/Android/SDK/tools on your computer?
Also, when you run it in Automator, where does the error occur?
Click to expand...
Click to collapse
The folder path in my iMac is /Users/Rainbow/Documents/Android/SDK/tools
the error occur after a few seconds after click OK after choosing the file to be sent to MemoryCard

Okay, if it doesn't occur until then, that means it sees the device and android SDK. Is the SD card mounted on the computer? are you copying to /sdcard/ as the file path?

derekwilkinson said:
Okay, if it doesn't occur until then, that means it sees the device and android SDK. Is the SD card mounted on the computer? are you copying to /sdcard/ as the file path?
Click to expand...
Click to collapse
No, sdcard no is mounted.
i don't understand this_ " are you copying to /sdcard/ as the file path?" sorry

When that window pops up (the one in your screenshot) are you putting /sdcard/ in the text box?

im going to try your app out =]
excited.

Sick of windows..
I am so sick of using a windows computer to do anything on my Hero so as soon as I get home tomorrow I will be trying this out on my system. SL 10.6.4 and I will be so happy to do it..

404 File not found. I'd love to help test this - can someone please re-upload the zip?
Edited 1/16/11
I'm using root explorer so this isn't really necessary for me anymore.

cloudstrife7 said:
404 File not found. I'd love to help test this - can someone please re-upload the zip?
Edited 1/16/11
I'm using root explorer so this isn't really necessary for me anymore.
Click to expand...
Click to collapse
I'm a bit confused--PushFile is for pushing files from your Mac to phone (in other words, a computer-side application), while Root Explorer is a file manager for the phone (a phone side app), that, unless I've missed something, does not replicate the functionality that PushFile attempted to provide. Am I missing some cool new feature of Root Explorer that lets you easily transfer files from your Mac to your phone?

The Viewsonic G Tablet Super Thread (w/Market, Gmail, and Maps!)

I've tried this twice already with a factory reset in between each try, and it's worked both times!
Attached is a bunch of files you will need to make this work.
Download the attached Zip file and extrat the contents to your desktop
Mount your G and upload the "G Tablet" folder to your G's internal SD card
Using AndRootFile or any other file manager that supports root access, mount as R/W, and copy the contents of G Tablet\permissions to System\etc\permissions.
Copy the contents of G Tablet\framework to System\Framework
Copy the contents of G Tablet\lib to System\lib
Copy all the APK's found inside G Tablet\APK into your system\app folder.
Install them in this order:
GoogleServicesFramework.apk
OneTimeInitializer.apk
SetupWizard.apk
Talk.apk
Vending.apk
Gmail.apk
Maps.apk
Make sure you remount it as R/O when you're done!
Restart your G, Connect to Wifi, then launch Market.
Follow the standard Google Account setup procedure and enjoy your newly installed Market.
PROOF THAT IT WORKS (the guide might be broken at some point though, see explanation below): http://www.youtube.com/watch?v=3dm2Kax8RQM
Someone please test this and let me know if you have any problems. Factory resetting doesn't delete any files I might have moved into the system folder so I might be missing something in this guide.
Feel free to donate to my beer fund if this helped you
Copying the following over from my thread over at Overclock.net (best computer enthusiast community, ever!)
Guides:
Setting Up ADB:
The ADB drivers do not recognize the Tegra hardware by default. You need to modify the USB inf file in order for it to recognize it and install the proper hardware.
Go to the usb_driver folder inside your Android SDK folder
Open up android_winusb.inf
Add the following under [Google.NTx86] and save (or if you prefer, download my pre-modified android_winusb.inf attached to the bottom of this post, and replace your existing android_winusb.inf with mine).
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
If you are running a 64 bit version of Windows, you need to add that code to the [Google.NTamd64] section as well.
Next, open a command prompt and type
Code:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
On your G, go to Settings -> Applications -> Development, and check "USB Debugging"
Plug in your USB cable, it will tell you that some drivers were not installed. That's okay! Point it to your usb_driver folder and it'll install the proper drivers.
Make sure ADB is working by opening a command prompt, navigating to your android sdk "tools" folder, and typing
Code:
adb devices
You should see a bunch of numbers if everything is set up correctly.
Click to expand...
Click to collapse
Rooting:
You need to have ADB fully working before proceeding. The easiest way to root is by using CLShortFuse's SuperOneClick. If you can spare the money, consider donating a buck or two to his beer fund
Connect your G and make sure USB debugging is enabled/ADB is working.
Extract the contents of SuperOneClickv1.5.2-ShortFuse.zip to a folder of your choice.
Run SuperOneClick.exe and click on Root. Wait for the process to finish, and you're rooted! Easy as pie.
Click to expand...
Click to collapse
Installing Launcher Pro/ADW:
It's actually really easy.
Download the Launcher Pro APK from here: http://www.launcherpro.com/apk/LauncherPro-0.8.1.1.apk
Connect your G and move the Launcher APK over to your Tablet's internal/external SD card.
Using whatever file manager you prefer (on your G), execute the Launcher Pro APK and install it.
Upon completion, hit the Home button and choose LauncherPro as your default launcher.
Reboot and feel the speed!
Click to expand...
Click to collapse
Fixes:
Wifi Fix:
If your Wifi "errors" upon enabling, try one of the following methods
Method 1:
Reboot. Seriously, it fixes the problem a large portion of the time.
Click to expand...
Click to collapse
Method 2:
Download Wefi from here: http://www.wefi.com/download/android/
Install the APK on your G.
Run WeFi, hit the menu button (button between back and home), and hit Settings
Make sure Automatic Startup is checked. Click on "Wi-Fi on WeFi start" and choose "Always Turn On"
Restart your G and pray.
Click to expand...
Click to collapse
Method 3: Master Reset (you will lose all your apps)
Go to settings -> Security and do a Factory Wipe.
This works only SOMETIMES, but is not a guaranteed fix, so only use this as a last ditch resort
Click to expand...
Click to collapse

nicely done, sir

Awesome job. OCN FTW

Fantastic.. worked like a champ!
Thanks!

Where did you find the USB drivers to mount the device?

Can i also include the contacts, mail, and calendar gapps?

mattmanion said:
Where did you find the USB drivers to mount the device?
Click to expand...
Click to collapse
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"

insight3fl said:
Can i also include the contacts, mail, and calendar gapps?
Click to expand...
Click to collapse
Go for it, let us know what you find

r34p3rex said:
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"
Click to expand...
Click to collapse
Do you know if there is a tutorial out there for installing the Root Explorer or Astro file manager on this thing? Sorry, I'm a newbie.

VERY NICE WORK!
FYI I reposted this on the slatedroid.com forum gave you credit and linked back to this thread. If you don't want it on there let me know and I will take it down.

by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?

Does anyone know why live wallpapers aren't available?

tri0xinn said:
by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?
Click to expand...
Click to collapse
I will look into that. The most likely reason is the lack of a unique Android ID.

does the regular nullsoft winamp show up for you?

great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.

xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
Gunth you want me to help over Teamviewer?

My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?

insight3fl said:
My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?
Click to expand...
Click to collapse
You need to run each APK manually through Root Explorer (or any package installer of your choice). Placing them there does not do anything

xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
I'm having the same issue Gunth so when you get it working let me know

Just finished up installing the apks. Got a problem though. Now my home and search buttons don't work. Also lost Airplane mode when powering off.
*EDIT* Just watched your video. I don't think that's a finicky button. I think this hack causes the problem.
*EDIT 2* Just did a reset. Home button and search work again. So, it's got to be the hack.
Doc

Xoom WiFi System Dump 3.0.1

Click HERE
Working on trying to get some deodex love going...
Just got Xoom WiFi tonight, let me know what I can do to help out the xoom wifi community.

I am curious. How were you able to extract the stock system dump image for the wifi version? Could you put down instructions since I am trying to learn these things.

Just a quick heads up. Moto was handing out DMCA notices on sysdumps. You may wanna save it for those who make it to #xoom on freenode.

bigrushdog said:
Just a quick heads up. Moto was handing out DMCA notices on sysdumps. You may wanna save it for those who make it to #xoom on freenode.
Click to expand...
Click to collapse
Moto can suck an egg...will post link on my site :-D
Feel free to post the link on irc...
teamdefuse.com

Angdroid said:
Click HERE
Working on trying to get some deodex love going...
Just got Xoom WiFi tonight, let me know what I can do to help out the xoom wifi community.
Click to expand...
Click to collapse
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks

ericdabbs said:
I am curious. How were you able to extract the stock system dump image for the wifi version? Could you put down instructions since I am trying to learn these things.
Click to expand...
Click to collapse
Install latest moto drivers
Install Android SDK
Enable USB Debug in Xoom settings
Open command prompt
Create new directory
CD to new directory
At command prompt type: adb pull /
files will be dumped to current path of command prompt

I Got the one (well, couple a clicks) root and unroot covered. You can check that one off the list. Thread open over yonder if you want to give it a spin... I am just uploading the newest version that one click updates to HRI66.

jwtyler said:
I Got the one (well, couple a clicks) root and unroot covered. You can check that one off the list. Thread open over yonder if you want to give it a spin... I am just uploading the newest version that one click updates to HRI66.
Click to expand...
Click to collapse
good, will be looking for it. NOW, an easy way to overclock to 1.5 would be wonderfull...

ericizzy1 said:
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks
Click to expand...
Click to collapse
1 is being worked on...NVM...Check out jwtyler one click root thread.
2 & 4 Going to try the same method that was used for Droid2 and DroidX. Create module for OC. I have not had time yet to look at kernel but I see someone is already creating kernels so should be able to do it from kernel with multiple settings; not sure if kernel behaves same way as it does in Droid.
3 Not sure if bootstrap (clockwork recovery) is available yet for Xoom WiFi but if it is just make a backup before you mod anything.
Not sure what you are talking about with 5 and 6 ... I am a Xoom noob, only been out of box for a couple of hours

ericizzy1 said:
good, will be looking for it. NOW, an easy way to overclock to 1.5 would be wonderfull...
Click to expand...
Click to collapse
Sweet
Drop me a line if you want to try to bang out some stuff together...

Thanks Angdroid for the system dump. I downloaded a copy of the system dump for kicks. I will keep it on my hard drive in case anyone loses it and needs a backup copy.
Hopefully we can create a stock boot.img soon for us wifi owners in case something goes wrong or need to return it to factory state. It looks like from the system dump we have access to the stock bcm4329.ko wifi driver.

ericdabbs said:
Thanks Angdroid for the system dump. I downloaded a copy of the system dump for kicks. I will keep it on my hard drive in case anyone loses it and needs a backup copy.
Hopefully we can create a stock boot.img soon for us wifi owners in case something goes wrong or need to return it to factory state. It looks like from the system dump we have access to the stock bcm4329.ko wifi driver.
Click to expand...
Click to collapse
Any word on the stock boot.img?

fabian29906 said:
Any word on the stock boot.img?
Click to expand...
Click to collapse
I am not a developer. I just meant a community as a whole come up with the files for the stock boot.img.
Still no word from Motorola of providing the stock boot.img for the wifi Xoom.

Do you think it's possible to extract languages in Wifi firmware to flash 3g xoom?
Or flash with entire wifi firmware?

I don't think the adb pull way is the best way at it.
Creating an actual image using dd will retain symlinks and mod perms (not owners).. but it also won't dump a bunch of tiny >1kb files on your computer (whose cluster size may be over 4kb).. plus you can mount it as a loop device..
adb shell
# busybox dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/mnt/sdcard/system.img
and then if you want
adb pull /mnt/sdcard/system.img
but I wouldn't.. just using the mtp interface is faster..

sausalito said:
Do you think it's possible to extract languages in Wifi firmware to flash 3g xoom?
Or flash with entire wifi firmware?
Click to expand...
Click to collapse
What do you mean? are you talking about the ./system/vendor/firmware/fw_bcm4329.bin
I just compared the two system images for both devices
fw_bcm4329_mfg.bin is the only file with a matching checksum..
I gotta run.. otherwise i'd check the version with a hex editor..
I doubt you're talking about the wifi firmware anyways..

ericizzy1 said:
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks
Click to expand...
Click to collapse
Ya! A color calibration app would be awesome!
Azrael X 4.0

100mbit:
http://gititbit.ch/xRx3 - Xoom_Wifi_3.0.1.zip

That's what I did for this image. http://www.mediafire.com/file/2fknnmy6nw6i19n/StockWiFiSystem.zip
Note, you need to be able to mount a YAFS2 filesystem to read the contents.
Blades said:
I don't think the adb pull way is the best way at it.
Creating an actual image using dd will retain symlinks and mod perms (not owners).. but it also won't dump a bunch of tiny >1kb files on your computer (whose cluster size may be over 4kb).. plus you can mount it as a loop device..
adb shell
# busybox dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/mnt/sdcard/system.img
and then if you want
adb pull /mnt/sdcard/system.img
but I wouldn't.. just using the mtp interface is faster..
Click to expand...
Click to collapse
Sent from my Xoom using Tapatalk

can someone post the 3.1 wifi-model USA system
(i need build.prop)

CM7 / AOSP Boot sound [working]

Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
Credit to barnacles10 and lithid-cm
*NOTE: Anything in brackets is either description of what is happening or an action you need to perform; don't type in anything in brackets*
What you need to do to get a boot sound on CM7/AOSP is the following.
1. http://dl.dropbox.com/u/19699565/bootsnd.sh Apparently some people had issues with the first link, so I uploaded it again. Download that file, place on your sdcard.
2. Take whatever sound you want and rename it to: android_audio.mp3 [needs to be mp3 format] and then place in your adb tools folder.
3. On your phone, open terminal emulator, and type in the following:
su [enter]
cd /sdcard [enter]
ls [to list all files, you should see bootsnd.sh]
sh bootsnd.sh [enter]
You won't see a confirmation, or message, it just runs, and returns you to a # sign.
From your computer, adb push the android_audio.mp3 to the /system/media folder, reboot, and you'll have a sound.
If you don't like / know how to use adb, using root explorer and placing the android_audio.mp3 in the system/media folder works just as well. Reboot, and enjoy your boot sound.
*NOTE*
If you flash / change roms, you'll have to re-run the process to enable the boot sound again. If you get tired of it / don't want it, you can use root explorer and delete the file.
Alternate method:
For those that don't like using the terminal emulator, you can do it via adb:
navigate to your adb folder via commanda prompt, then issue the following commands:
adb remount
adb shell
cd /sdcard
ls [will list files, you should see bootsnd.sh]
sh bootsnd.sh
Like in the emulator, you will be returned with a # sign. Then place the audio file in the folder I specified. Just decided like posting an alt method. Enjoy.

Nice post I'm going to do this now!
Sent from my PC36100 using XDA Premium App

Well I do hope you enjoy it.

Excellent, trying this now!
Edit: Works great on CM7 7.0.2.1!!! Nice find!
.........at 8 am today someone poisons the coffee....do not drink the coffee. More instructions will follow.
Cordially,
Future Dwight

teh roxxorz said:
Well I do hope you enjoy it.
Click to expand...
Click to collapse
And I must say it has worked flawlessly.. I maintain a small network off friends rooted phones and this is one off the "hit" fixed so far everybody loves it. Thanks again for the help with this the other day..
Sent from my PC36100 using XDA Premium App

I really want this.. I just found this thread after searching and searching for an answer.. I just about gave up but I think I still my have a problem. My hboot version is 2.10 and dont think this will allow me to use pushboot.... any ideas

opps.. guess I should have read the whole post..... I am bout to give it a try

frikin awesome thanks a bunch.. I dont know what that little file did but it worked .. wooohoooooooooooo

teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. Download that file, place on your sdcard.
that download just shows up as a text file... am i doin it wrong?
Click to expand...
Click to collapse

@teh roxxorz: Thanks a lot man. I had to search a longtime to find this. You're the man. Seems like CM7.02.1 doesn't have that bootsnd.sh file embedded. Maybe the latest stable has it. If I wasn't new to the forum I'd know how to hit you with a "Thank You"...

youdoofus said:
teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. Download that file, place on your sdcard.
that download just shows up as a text file... am i doin it wrong?
Click to expand...
Click to collapse
The file should save as a .sh. If it doesn't show up as .sh when you are saving it, save it as all file types, and that should work as well.
If you double click it, it should prompt you with the "no program found...do you want to...blah blah" And it should show bootsound.sh
Click to expand...
Click to collapse

gReeNzZz said:
@teh roxxorz: Thanks a lot man. I had to search a longtime to find this. You're the man. Seems like CM7.02.1 doesn't have that bootsnd.sh file embedded. Maybe the latest stable has it. If I wasn't new to the forum I'd know how to hit you with a "Thank You"...
Click to expand...
Click to collapse
Well AOSP roms [i.e CM7] wasn't designed to have boot souns, so it probably won't be integrated [my speculation].
And if you ever want to "thank" anyone, at the bottom of every post, you'll see a "thanks" button, and then you have "thanked" them, and the user can see it.

Can't get this flashed. I tried to rename what I had downloaded from cyan's web site, Droid eye audio.zip, even tried to just flash it. A little help please
Sent from my ERIS ADR6200 using XDA App

chefrjd33 said:
Can't get this flashed. I tried to rename what I had downloaded from cyan's web site, Droid eye audio.zip, even tried to just flash it. A little help please
Sent from my ERIS ADR6200 using XDA App
Click to expand...
Click to collapse
Well if its a zip file. Extract the file, it should be an mp3 inside. Rename that file to android_auido [should have .mp3 extension already].

It launches rom manager and tells me its a operating system. Did I get the wrong file.
Sent from my ERIS ADR6200 using XDA App

chefrjd33 said:
It launches rom manager and tells me its a operating system. Did I get the wrong file.
Sent from my ERIS ADR6200 using XDA App
Click to expand...
Click to collapse
Where are you opening the file that its making it open from rom manager?

teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. http://dl.dropbox.com/u/19699565/bootsnd.sh Download that file, place on your sdcard.
2. Take whatever sound you want and rename it to: android_audio.mp3 [needs to be mp3 format] and then place in your adb tools folder.
3. On your phone, open terminal emulator, and type in the following:
su [enter]
cd /sdcard [enter]
ls [to list all files, you should see bootsnd.sh]
sh bootsnd.sh [enter]
You won't see a confirmation, or message, it just runs, and returns you to a # sign.
From your computer, adb push the android_audio.mp3 to the /system/media folder, reboot, and you'll have a sound.
If you don't like / know how to use adb, using root explorer and placing the android_audio.mp3 in the system/media folder works just as well. Reboot, and enjoy your boot sound.
*NOTE*
If you flash / change roms, you'll have to re-run the process to enable the boot sound again. If you get tired of it / don't want it, you can use root explorer and delete the file.
Click to expand...
Click to collapse
Ok just tried this without using adb as I think its million times better to just use a ftp app and get this done in seconds. But I dont know why its not working. I check the name to make sure I wasnt putting in the .mp3 twice and for some reason it wont play the file. And its in MP3 format.

I had some that wouldn't play for some reason too. Try a different mp3 file and see id it work. If not did u get the bootsnd file placed on the root of sd card and pushed the file with adb. Or my preferred method terminal emulator.
Kings GB Destroyed EVO

Or tell me what steps udid do.
Kings GB Destroyed EVO

cmurray77 said:
I had some that wouldn't play for some reason too. Try a different mp3 file and see id it work. If not did u get the bootsnd file placed on the root of sd card and pushed the file with adb. Or my preferred method terminal emulator.
Kings GB Destroyed EVO
Click to expand...
Click to collapse
Really well I actually tried the audio from the driod just to see but I try a couple more. Yeah the problem with using those they are more timely and both USB ports are beyond ****ed right lol. But I should just be able to do this over FTP. Was there anything similar to the ones that worked to the ones that did.

For those wanting to just root, here's some help

This is for those on ICS only. If you have upgraded to jellybean, this will not work.
There have been other posts, and this one is nothing new, in fact it's a remake of DebugfsRoot so that author gets all credit. I just made a couple of tweaks to help those that might be having a fuss with it. First, this is assuming you are using a windows PC. I don't work on MACs. Next, make sure you have ADB working properly on your PC. To do this:
Go to your start menu and open a command prompt, usually by typing "cmd" in the run blank.
Type adb
If you don't get a whole heap of feedback of how to use adb returned to you, and instead get an error, you don't have it set right. If you're sure you installed the development kit and you have ADB on your PC, do the following:
FIND IT... and add it to your system path variable. adb.exe comes with the root extract, so if you don't have the kit installed, you can use that instead, but seriously, if you want to root and enjoy this hobby to its fullest, install the android kit. The most common location is "C:\Program Files (x86)\Android\android-sdk-windows\platform-tools" - but hey, get this, did you know the asus sync software available from their site also includes it? I just now found that out haha...
To add whichever absolute path to your system path variable, start menu > control panel > system > advanced system settings > environment variables button > In the system variables window, scroll down to path, click it, click EDIT > move your cursor to the very end and add ; again that's (semi-colon) - you'll see other entries there which show you, just follow the pattern. Remember, you only need to do this if your original attempt at typing adb didn't work. Save your settings, return to that command window, and try adb again, you should have better results this time.
Now then, download the root package here:
https://dl.dropbox.com/u/33560221/DebugfsRoot_v1.8.exe
This is the original software with slight enhancements by me...those enhancements are all to the BAT file, and are as follows:
The EXE file is a self-extracting archive which will extract the contents to C:\tabletroot Please don't change this install location. You'll see why in a moment. the RootDebugfs.bat was edited as follows:
Within each push command, I preceeded the file name with C:\tabletroot so it knows exactly where to find what it needs. I found if you just pushed without it, it didn't like it too much.
Last, after each "wait-for-device" command, I added TIMEOUT 120 This forces the batch file to sleep for 2 minutes allowing plenty of time for your tablet to reboot. I found if you didn't do this, it would try to do the next commands way too soon causing failure. This should give enough time for you to get to your desktop before the next command is issued. If you find it's too long and you're ready to go, just press a key and that will kill the clock. If not long enough, edit the batch file with any text editor, and increase the timeout time.
All other files are what was originally found. I didn't update any of the apks or edit any other file than the main batch file. That's it. I used these exact files to root my tf300t on firmware version .30 with no issue of any kind. I hope this helps someone. If you run into trouble, not sure how much help I can be. I'm simply posting exactly what I did. I didn't author anything other than the edits mentioned above. Good luck.

Did the your_path thing and it didn't work.

Could you describe just a bit more which part you're having trouble with and what happened?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

I added ;<your_path> at the end of the path and it did not change anything in the CMD window after imputing adb, when nothing happened before.
I'm sure it's something that I did not do that went wrong.

The your path thing was just a descriptor. You need to replace that with the location of your adb.exe file so it would look like ;c:\program files\ ... and so on. I gave a sample path of where mine is but it could vary between systems.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Well if my previous answer doesn't prove I've never rooted anything...
Where do you DL the adb file from?

Couple Choices
10010110 said:
Well if my previous answer doesn't prove I've never rooted anything...
Where do you DL the adb file from?
Click to expand...
Click to collapse
OK, I will assume you do not have the android development kit installed, so you still have a couple of choices here:
ADB comes with the archive I directed you to download, so if you download it and run the EXE, you'll find ADB inside the newly created folder I mentioned, so using this method, you would add... ;C:\tabletroot
ADB also comes with the ASUS sync software found on the ASUS website. If you have / will download and install this software, the ADB file will be located here: C:\Program Files (x86)\ASUS\ASUS Sync or it might be in C:\Program Files\ASUS\ASUS Sync just depends on the type of system you have. I have a 64-bit OS, so I have a Program Files and a Program Files (x86) folder (the x86 is for 32-bit programs) - in this situation, you would want to add ;C:\Program Files (x86)\ASUS\ASUS Sync or ;C:\Program Files\ASUS\ASUS Sync
Remember if you go with option one, download the archive I provided and run it before you add / test to your path variable, because that's what puts ADB in place. Once you have that all done, just go run the BAT file - after you connect your tablet and can see it on your PC as a media device that is

Clarification
So using this method do we need the blob files or was that just for downgrading, and since we don't need to downgrade using this method, everything that we need is in that self extracting exe file? I'm not interested to unlock bootloader -for now-...just want a few tweaks and to install a few root apps
Sorry, I only have experience rooting a couple HTC devices and they were both 1 touch and rooted.

I hear you, and they are legit questions. This is for rooting only. This procedure doesn't unlock your bootloader, which is why i used it. All you need is in the archive.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Another question, do you have to put the tablet into any special mode in order for the batch file to work? If I remember correctly, the phones just had to be on, plugged in via usb (duh) and the batch files did the rest. The batch file has the 120 second pause, but it seems like it does the first part with -
1. waiting for device to be detected
2. daemon not started
3. daemon started successfully
then it just sits there, and its been longer than 2 minutes...what am I missing?

Only mode i know of is to put it in media mode mentioned above. Also I've read to turn off asus sync found in the sync section of settings.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

HandicapFailure said:
Another question, do you have to put the tablet into any special mode in order for the batch file to work? If I remember correctly, the phones just had to be on, plugged in via usb (duh) and the batch files did the rest. The batch file has the 120 second pause, but it seems like it does the first part with -
1. waiting for device to be detected
2. daemon not started
3. daemon started successfully
then it just sits there, and its been longer than 2 minutes...what am I missing?
Click to expand...
Click to collapse
Either unknown sources, or USB debugging might need to be on.

Ah yes forgot those. I'd do both thankya.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

FYI the batch file does not work with windows xp, I searched and seems timeout is not supported. Sucks having an old OS..
I ran the commands manually and the root worked, so thanks anyway!

rickc3k said:
FYI the batch file does not work with windows xp, I searched and seems timeout is not supported. Sucks having an old OS..
I ran the commands manually and the root worked, so thanks anyway!
Click to expand...
Click to collapse
Wow, I didn't know that. Thanks for the tip.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app