Hey guys, need some help with this one from some of you with more android/linux experience than me.
In my continuing quest to make Blackhole as customizable as possible I've been working on a way for users to easily install paid apps (legally downloaded of course), and stuff that I don't have available in rom manager in one easy step at the same time the rom is installed. In pursuit of this goal I've found that it's possible for the update-script file inside a clockworkmod zip to call a script in the zip as well. I've gotten it to say it's run the script, but it doesn't do what it's supposed to. here's what i've got:
#! /bin/
busybox cp /sdcard/app/* /system/app/
When I type the command into a terminal on the phone it works. When I open an adb shell and type "bash install.sh" it works. But when I get the update.zip to run the script, or run it in root explorer it just says it's run it, but doesn't do anything.
Is there something I'm missing about how to call the script? Do I need to somehow add the bash program to the zip file so it can run the script right? Has anyone ever done something like this who can point me in the right direction?
do you have an output you can show us?
Sent from my SCH-I500 using XDA App
This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.
Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
wizang said:
This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.
Click to expand...
Click to collapse
Could very well be, it's not showing me any output when i run it the two ways it doesn't work, just says it's been run.
vegittoss15 said:
Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....
Click to expand...
Click to collapse
Haha, caught me. I was trying to remain incognito Yeah, i'll get 2.4 loaded back up on rom manager for you today. But if you flash 3.0 it will upgrade you to DL09 and the DJ05 kernels and modem are compatible, or at least no one i know of has had issues.
imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
sdcard is mounted when you go to recovery, because it's got to access the update.zip file on it to install anything. I'll try your code, do you know what to put after SYSTEM: to make it go to the /app directory? thanks for the idea, it's a different way to go, i didn't think about the fact the update-script could access the device if you don't use the "package" tag.
Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..
dcow90 said:
Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..
Click to expand...
Click to collapse
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.
I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.
This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500
imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
Well I gave that a shot, and i think it could work, but the recovery wouldnt do it. it says "non-package source path not yet supported" good idea tho.
yutsoku said:
I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.
Click to expand...
Click to collapse
If you can that would be great.
n0yd said:
This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500
Click to expand...
Click to collapse
I spent a good bit of time searching and most of the scripts I found were much more complex than what i need, or were written to run on a computer, which i've already done.
sonofskywalker3 said:
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.
Click to expand...
Click to collapse
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App
jt1134 said:
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.
sonofskywalker3 said:
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.
Click to expand...
Click to collapse
#!/bin/sh for scripts in recovery. #!/system/bin/sh for scripts in android.
Sent from my SCH-I500 using XDA App
Related
OK, I made a zip. Who wants to be my guinea pig? It's at the bottom of the post. (erase -signed and put it on the internal sd)
blackjackboy said:
I guess my idea would be to take the settings.apk from either the Vibrant dump or cyanogenmod 5.0 and push it to /system/app or wherever the settings.apk is located. Does anyone think that this would work or be willing to try it? I'm just worried that this will brick the touchwiz, and without an "original ROM" or RUU and custom recovery, I'm afraid to try it. Is there anyone braver than me?
Click to expand...
Click to collapse
Did you check this thread?
http://forum.xda-developers.com/showthread.php?t=728121
tbae2 said:
Did you check this thread?
http://forum.xda-developers.com/showthread.php?t=728121
Click to expand...
Click to collapse
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Well, the best thing to do, simply run a sql command along with the rooting update.zip.
I will work on this today and get back to you guys soon.
http://androidforums.com/samsung-ca...e-sideloading-apps-captivate.html#post1178618
Been done.
blackjackboy said:
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Click to expand...
Click to collapse
It isn't free but it isn't expensive either. You just dropped a large wad of cash for the phone, seems like another $3 to get it the way you want it wouldn't be such a big deal.
blackjackboy said:
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Click to expand...
Click to collapse
Droid Explorer is.
I'm an android noob but experienced linux user, so I came up with my own free solution: download a terminal emulator app (the one i got was free, and called, simply, Terminal Emulator, I think).
Then (in the terminal emulator):
Copy the settings.db file to the SD card:
To get superuser access so you can get to the settings.db file (need a rooted phone, obv):
Code:
$su
And confirm the popup allowing access.
Code:
#busybox cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
Then hook up your phone via USB (mass storage method) and use your window manager to copy that from the phone to the computer, edit with an SQL database browser, save it, verify it's still good, move it back to the SD card, then, back on the phone in the terminal emulator:
To get superuser access again:
Code:
$su
Shouldn't have to confirm the popup allowing access again, as the first time appears to do it.
Move the original file to a backup name (just to be safe):
Code:
#busybox mv /dbdata/databases/com.android.providers.settings/settings.db /dbdata/databases/com.android.providers.settings/settings.db.old
Copy the new (edited) file into place:
Code:
#busybox cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings/settings.db
Then reboot, and enjoy the ability to install non-market apps. My first install was Flash 10.1. Works fine on the Captivate.
blackjackboy said:
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Click to expand...
Click to collapse
Grab Android Mate from the market, it is free and has root level exploration
blackjackboy said:
OK, I made a zip. Who wants to be my guinea pig? It's at the bottom of the post. (erase -signed and put it on the internal sd)
Click to expand...
Click to collapse
This might also work, I have used it, pretty simple
http://m.androidcentral.com/sideload-android-apps-all-you-want-sideload-wonder-machine
Superoneclickroot has a one click enable non market apps next to the root button, fyi.
terrymc said:
This might also work, I have used it, pretty simple
http://m.androidcentral.com/sideload-android-apps-all-you-want-sideload-wonder-machine
Click to expand...
Click to collapse
Smasher816 said:
Superoneclickroot has a one click enable non market apps next to the root button, fyi.
Click to expand...
Click to collapse
:faceplam:
bump a year old thread? with these no less....
whats wrong with bumping a (insert # here) old thread? it hasnt been closed or deleted. as long as info pertaining to the OP is being posted shouldnt it be a non-issue? now if it was bumped with something like 'why bump this fossil thread?' then that would be a pointless bump. i gained info from the 1 year late post about superoneclick and thanked the guy for posting it.
EDIT: you spelled 'facepalm' wrong.
Well first it shouldn't even be here in development. And second thread closed.
Im new to forum but Ive been trolling for the past couple days. I currently rooted my Vibrant with One Click GalaxyRooter. Then purchased Root Explorer to view the hidden files and folders that I need to get to in order to remove some of the stock .apk and odex files.
Im currently in the /system/app directory and the first thing that I want to remove is that avatar icon and files. I long press the file in root explorer to delete it and it allows me to. Only problem is that when I go back or refresh the directory everything is still there even when I reboot my phone.
Any suggestion.
AnthonyJFranks said:
Im new to forum but Ive been trolling for the past couple days. I currently rooted my Vibrant with One Click GalaxyRooter. Then purchased Root Explorer to view the hidden files and folders that I need to get to in order to remove some of the stock .apk and odex files.
Im currently in the /system/app directory and the first thing that I want to remove is that avatar icon and files. I long press the file in root explorer to delete it and it allows me to. Only problem is that when I go back or refresh the directory everything is still there even when I reboot my phone.
Any suggestion.
Click to expand...
Click to collapse
When using Root Explorer, on the top part of the screen, press [Mount R/O] and try again. I think that might solve the issue. Post up the results!
Why didn't you just uninstall the files via titanium backup?
Master™ said:
Why didn't you just uninstall the files via titanium backup?
Click to expand...
Click to collapse
Forget what I said, use Mater's method. lol
I do see the Mount R/O in the top right hand section of the screen and I pressed it but it seems like it didnt do anything. It just shows my memory used / free and r/w [ Mount R/O]
I tried deleting a file still was there when I came back into the directory
How do I access the file directory in Titanium Backup
AnthonyJFranks said:
How do I access the file directory in Titanium Backup
Click to expand...
Click to collapse
You don't access the file directory. Titanium Backup will show you a list of ALL apps installed. You simply click and press uninstall. Simple, no fuss. You can even make a backup before you uninstall it in case you need it later. Done.
Use Titanium Backup like everyone said, I also had the same problem with other Root Explorers. Also be sure to delete the .zip file because it might cause problems later. Also do you know what trolling means? I think you meant lurking, because trolling implies you've been trying to get people angry.
I didn't even notice he said he had been trolling LOL. Get back troll! My brain automatically assumed lurking.
AnthonyJFranks said:
Im new to forum but Ive been trolling for the past couple days. I currently rooted my Vibrant with One Click GalaxyRooter. Then purchased Root Explorer to view the hidden files and folders that I need to get to in order to remove some of the stock .apk and odex files.
Im currently in the /system/app directory and the first thing that I want to remove is that avatar icon and files. I long press the file in root explorer to delete it and it allows me to. Only problem is that when I go back or refresh the directory everything is still there even when I reboot my phone.
Any suggestion.
Click to expand...
Click to collapse
Your system is set to read only.
Follow the instructions found in this post (forgive me i'm too new to post links, and i want to give credit to the solution):
hxxp://forum.xda-developers.com/showpost.php?p=8643744&postcount=6
Code:
$ mount -o rw,remount -t rfs /dev/block/stl9 /system
Run the command from terminal, and you should then be able to delete the files that you want.
Here do this I had this happen awhile back this worked
AustinKnight45 said:
Download busybox from market then run it and update it then after it updates and you have the latest busybox go back to root explorer and delete the bloat ware dont know why this works but it does.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
AustinKnight45 said:
Here do this I had this happen awhile back this worked
Click to expand...
Click to collapse
sentences without periods are hard to read.... ha
This didnt work
Sent from my SGH-T959 using XDA App
eatspaper said:
Your system is set to read only.
Follow the instructions found in this post (forgive me i'm too new to post links, and i want to give credit to the solution):
hxxp://forum.xda-developers.com/showpost.php?p=8643744&postcount=6
Code:
$ mount -o rw,remount -t rfs /dev/block/stl9 /system
Run the command from terminal, and you should then be able to delete the files that you want.
Click to expand...
Click to collapse
I tried this and it didn't work as well I got a error message that said operation not permitted
Sent from my SGH-T959 using XDA App
Any suggestion on whats going on, I know its rooted the super user always pops up when ever a couple apps or on
Sent from my SGH-T959 using XDA App
AnthonyJFranks said:
I tried this and it didn't work as well I got a error message that said operation not permitted
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Did you SU in the terminal first before you ran the command?
Hi,
Can anybody extract the APK for the LED Torch app preinstalled in Froyo?
I saw that the one include with Froyo on the Desire works with a Desire with Eclair. (But doesn't work with my Legend) So I would like to check if the one included in Froyo for the Legend will also work with the Legend on Eclair.
The package name is com.htc.flashlight
Thanks!
U don't have to wait....
Try this APP: Lamppu
But first u have to (Soft)root your Legend with (Universal Androot)
After that, install superuser APP. Now start Lamppu and allow superuser rights...
Now u can use your LED as torch.
Tried it self on my legend v.2.1
Sure about the name?
The only thing I found in the Modaco ROM was Flashlight.apk
Then again...I have no clue what I am doing
above file is not working
Yeah it doesn't install
Ok gentlemen, one more try.
Extracted, re-zipped and signed the apk using apk-manager.
Removed the system app from my phone using TitaniumBackup and installed the signed apk through Root Explorer.
Works for me. No guarantee that it does for any other ROM or Android version though.
Sorry for the video but I just found out how to do screencasts and love it
Its German but you should be able to understand it.
Notice that it is now uninstallable and listed as downloaded app.
denisman said:
Ok gentlemen, one more try.
Extracted, re-zipped and signed the apk using apk-manager.
Removed the system app from my phone using TitaniumBackup and installed the signed apk through Root Explorer.
Works for me. No guarantee that it does for any other ROM or Android version though.
Click to expand...
Click to collapse
Installed and ran for me in stock 2.1 but it didn't do anything with the flash when playing with it
Thanks for trying!
This one is installing correctly, and also loading correctly, but it doesn't light up the LED.
So it isn't working
Are you phones rooted?
First of all, you have to have deodexed apk and second, you need to set right permissions in sysfs.
Sent from my HTC Legend
BlaY0 said:
First of all, you have to have deodexed apk and second, you need to set right permissions in sysfs.
Sent from my HTC Legend
Click to expand...
Click to collapse
The apk is deodexed. As for the permissions. No clue how to set them right
Had to read up an hour last night just to learn enough to extract it. Big newbie here hehe. Guess I'll check some threads about sysfs permissions and try it again later.
Sysfs is everything under /sys directory. File /sys/class/leds/flashlight/brightnes should have read-write permission set for everyone.
Sent from my HTC Legend
BlaY0 said:
Sysfs is everything under /sys directory. File /sys/class/leds/flashlight/brightnes should have read-write permission set for everyone.
Sent from my HTC Legend
Click to expand...
Click to collapse
Ahhh thanks! I guess I understand now.
Ok I just flashed whitetigerdk's rev03 ROM which is a rooted 2.03 ROM.
Than I did the following in adb shell:
Code:
chmod 777 /sys/class/leds/flashlight/brightness
checked permissions with:
Code:
cd /sys/class/leds/flashlight
ls -l
and it has rw permission for everyone now.
Code:
-rwxrwxrwx root root 4096 2010-12-01 16:29 brightness
Problem is, that booting the phone resets the permissions.
EDIT:
I just repeated the procedure while the phone was booted in normal mode.
Permissions successfully changed AND flashlight is working correctly, including all three different light settings!
Still, a reboot resets the permissions.
Guess I have to find a way to make this change permanent now and all is done
Hah so cool. Never used chmod or any other linux command until today. Had to google everything while I was testing. Nice how much one can learn here.
Another EDIT:
Found something else that is interesting.
http://developer.android.com/reference/android/Manifest.permission.html#FLASHLIGHT
Would adding this to the AndroidManifest.xml help aswell? I'd do it myself but I have to work soon. Just tried it decoding the xml with AXMLPrinter and adding it. Unfortunatly I don't know how to save the xml in the right format again and just saving it corrupts the apk. If noone else wants to give it a try I'll check back after work.
denisman said:
Still, a reboot resets the permissions.
Click to expand...
Click to collapse
Yeah... this is done via init.rc which is inside initrd image. So you have two options... tweak init.rc (you would need to unpack boot.img image and extract initrd image, edit init.rc, make new initrd image and construct back boot.img... this can all be done in one swoop with dsixda's kitchen) or make a script that is run every boot (we are doing it via run-parts which also requires editing of init.rc... once again dsixda's kitchen can add this functionality in a single swoop)...
As for "android.permission.FLASHLIGHT" I'm not sure about it as I can see that HTC is doing it avoiding it (setting permissions to 666 by default in FroYo)...
If you want decoding/encoding xmls use ApkManager. It's a nice CLI tool that can decompile and compile apks back...
You are quite a fast learner, congrats.
Back home Got pretty late.
I don't actually need this since I am running a rooted Froyo ROM anyways but thought it would be an interesting task to get this working for others to easily use it and for me to learn more about Android. The first option sounds like it would require a bit too much end-user activity and would be limited to a certain set of ROMs if I understand it correctly.
Leaving the second and third option as the most user-friendly ones I guess.
I will read up more on init.rc and ways to script for it tomorrow. Sounds like a very powerful "tool" to know.
For now I will concentrate on the XML. Might be the most comfortable and ROM-independent way if I get it to work.
BlaY0 said:
As for "android.permission.FLASHLIGHT" I'm not sure about it as I can see that HTC is doing it avoiding it (setting permissions to 666 by default in FroYo)...
If you want decoding/encoding xmls use ApkManager. It's a nice CLI tool that can decompile and compile apks back...
Click to expand...
Click to collapse
Used Apk Manager to extract, zip and sign the apk in the first place. Really nice tool. Just didn't find an option to convert the xml from binary to readable, that's why I used AXMLPrinter2.jar which can do the conversion one-way but not back to binary.
I'll find a way
Thanks again for the input! Helped me a lot!
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.
I really need some help with moving a file to system/app
Not good at this kind of stuff.
Its in the root of my SD card
Sent from my SGH-T959 using XDA App
Code:
su
mv /Removeable/MicroSD/file.whatever /system/app/
Easy peezy
sassafras
Hahah thanks. Another easy question, any way to turn wifi off when you put in sleep mode? Big battery saver. Thanks
Sent from my SGH-T959 using XDA App
gobluewolverines4 said:
Hahah thanks. Another easy question, any way to turn wifi off when you put in sleep mode? Big battery saver. Thanks
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Go to settings -> wireless and networks -> wifi sleep policy
sassafras
Ok...noob here..what is the purpose of making at app a "system app"?
And then another question comes to mind; can you go back and make one of those system apps just a regular old app?
rpavich said:
Ok...noob here..what is the purpose of making at app a "system app"?
And then another question comes to mind; can you go back and make one of those system apps just a regular old app?
Click to expand...
Click to collapse
System apps are essentially going to be 'firmware' because unless you're rooted (which is not by design) they cannot be modified. If you make an app a system app, it theoretically can run better, though that is debatable, it will survive factory wipes and cannot be accidentally deleted. What you lose though is the ability to upgrade it in the market.
In all, it's not really necessary 90% of the time. The easiest way to make an app a system app, if you're interested, is to use Titanium Backup Pro. Not only will it copy the .apk over, but it will reassign the permissions of its /data folder as well.
sassafras
Thank you very much Sassafrass....that was informative.
sassafras_ said:
Code:
su
mv /Removeable/MicroSD/file.whatever /system/app/
Easy peezy
sassafras
Click to expand...
Click to collapse
Ive attempted this from the /sdcard/ and /Removable/MicroSD/
both attemps fail with a msg of "cross device link"
And suggestions???
Drukan said:
Ive attempted this from the /sdcard/ and /Removable/MicroSD/
both attemps fail with a msg of "cross device link"
And suggestions???
Click to expand...
Click to collapse
Cross device link occurs when you're attempting to move a file across storage devices due to the way mv works (it only rereferences the inode, not moving the actual data). Instead, use cp to copy it to the sd.
LightI3ulb said:
Cross device link occurs when you're attempting to move a file across storage devices due to the way mv works (it only rereferences the inode, not moving the actual data). Instead, use cp to copy it to the sd.
Click to expand...
Click to collapse
Exactly.
More specifically though, the mv binary included with android. The GNU mv tool included in any modern linux can tell if the data needs to be moved to different mounted devices and will do it if need be.
sassafras