[SOLVED!!!!] Cannot get bootsound to work on Harmonia

Re: Cannot get bootsound to work on Harmonia

if you have terminal (or a root explorer) on your ov, you can copy the file to your sdcard and use a text editor to open it and copy/paste the contents into the forum. that's what I have to do or things end up full of syntax errors.
 
Re: Cannot get bootsound to work on Harmonia

Im sorry for not replying sooner I sat lastnight staring at this and passed out. It was one of those says.

Now if I sound redundant bear with me.

You deleted the bootsound file created in /system/bin/ right?
You went into /system/etc/init/rc and deleted the code fro there right?
You then went to build.prop and deleted the code from there right?
Then you rebooted fresh let the phone settle for a couple minutes after boot.

Then you rerun the script made sure all permissions were set properly and all code was created in the various places? If your doing all this and its not working but it will work with the IHO roms, Im going to go out on a limb and say its got to be Harmonia giving conflicts. This seems to work on other phone running Froyo and custom versions of Froyo.

Maybe LeslieAnn can shed some loght on this Im at a short brick wall. I can see over it just not sure what to do to get over it.
 
Re: Cannot get bootsound to work on Harmonia

Okay I redid everything and rebooted. I got this error. This is the error I got before I made the bootsound directory:

$ export PATH=/data/local/bin:$PATH
$su
# cd /sdcard
# sh bootsnd.sh
Usage: mount [-r] [-w] [-o options] [-t type] device directory
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
bootsnd.sh: cannot create /system/etc/init.local.rc: read-only file system
touch: /system/bin/bootsound: Read-only file system
bootsnd.sh: cannot create /system/bin/bootsound: read-only file system
bootsnd.sh: cannot create /system/bin/bootsound: read-only file system
bootsnd.sh: cannot create /system/bin/bootsound: read-only file system
bootsnd.sh: cannot create /system/bin/bootsound: read-only file system
bootsnd.sh: cannot create /system/bin/bootsound: read-only file system
bootsnd.sh: cannot create /system/bin/bootsound: read-only file system
bootsnd.sh: cannot create /system/bin/bootsound: read-only file system
bootsnd.sh: cannot create /system/bin/bootsound: read-only file system
bootsnd.sh: cannot create /system/bin/bootsound: read-only file system
Unable to chmod /system/bin/bootsound: No such file or directory
No such user 'root:shell'
bootsnd.sh: cannot create /system/build.prop: read-only file system
bootsnd.sh: cannot create /system/build.prop: read-only file system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#
 
Re: Cannot get bootsound to work on Harmonia

Ok the problem with that is your not mounted.

Try this type this out.

Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

Or if you have adb on your pc type
Code:
adb remount

Im thinking because the system isnt mounted its not transfering the proper permissions either. Ill post mine after I get done with installing a update and get data2ext working again.

But for now I would say it is safe to say if your permissions look like a upside down L then you will be gtg.
 
Re: Cannot get bootsound to work on Harmonia

Ok talking with another member he figured out how to get it working.

Do this in your build.prop scroll to where it puts the command to play boot sounds.If there is a number of blank lines go up to the line above and delete those. Leave One line between the two and try that.

If this works I will be happier than a puppy with two peters.
 
Re: Cannot get bootsound to work on Harmonia

Ok I just got back to this thread. Ive had about a billin things blow up today and its only tuesday ( i think).

So Panda I was having a issue getting this to work on the mgr build. I stopped scrtached my head and thought hmm everything is where its suppose to be, check. Now lets see permissions, well that appears to be set properly and that one and WHAT HOLY HELL? The build.prop was not set to execute..so I changed that and that alone and bam playing sounds on reboot.


SOOOOO

Make sure your permissions on build.prop look like a upside down L.
 
Re: Cannot get bootsound to work on Harmonia

I'm not sure where to look for the upside down L.

I did everything you posted (thanks, by the way) and still no bootsound. I got the same error about "no such user: root:shell" when I tried mounting.
 
Re: Cannot get bootsound to work on Harmonia

Try this. Download super user from the market.
https://market.android.com/details?id=com.noshufou.android.su

Im seeing this as erro from not having superuser installed.
Not sure why but yeah see if this fixes the problem.

Also for the upside down L.

Lock press the file then select permissions. It will give check boxes. The x's should make a upside down L.
 
Last edited:
Re: Cannot get bootsound to work on Harmonia

I have Superuser installed. Just updated it, in fact.

I do have the upside down l, btw.
 
Re: Cannot get bootsound to work on Harmonia

Im at the point Im just googling this now. Its beyond what I can logically think is wrong. But Im seeing this error as being not having something installed and permissions set properly.

I wonder if somebody els running Harmonia can try and see if they can get the bootsound to work and if not post what they see as errors.
 
Re: Cannot get bootsound to work on Harmonia

Try going to setting/applications and wipe the data for Superuser. I had a weird problem when I updated it and some of my apps lost root access as if I selected decline on allowing it when I know I allowed it long ago and have used it as root before. I wiped data for it and re-updated superuser and it worked fine.
 
Re: Cannot get bootsound to work on Harmonia

I'd like to know, too, if anyone running Harmonia is having these issues.

BTW in init.local.rc, is there supposed to be anything other than the ###Bootsound safe to delete### stuff?
Init.local.rc is the only thing I have that comes close to /system/etc/init/rc that I have. I don't have /system/etc/init/rc and init.local.rc had the code to delete in it.
 
Re: Cannot get bootsound to work on Harmonia

Try going to setting/applications and wipe the data for Superuser. I had a weird problem when I updated it and some of my apps lost root access as if I selected decline on allowing it when I know I allowed it long ago and have used it as root before. I wiped data for it and re-updated superuser and it worked fine.

Just updated Superuser and no change.
 
Re: Cannot get bootsound to work on Harmonia

Here is a flashable zip file that will enable bootsounds on IHO builds, might work on Harmonia as well. I made it very verbose during the installation process, if it errors out at any point, please let me know what it says.

Note- You will have to remove any lines in the init.local.rc pertaining to bootsounds, as well as remove the single line in build.prop before flashing this. You need a clean slate to work from. ;)
 
Re: Cannot get bootsound to work on Harmonia

I'd like to know, too, if anyone running Harmonia is having these issues.

BTW in init.local.rc, is there supposed to be anything other than the ###Bootsound safe to delete### stuff?
Init.local.rc is the only thing I have that comes close to /system/etc/init/rc that I have. I don't have /system/etc/init/rc and init.local.rc had the code to delete in it.

Yes this is the file system. This will teach me to not pay attention when blindly reposting peoples fixes. I do recall seeing the /system/etc/init.rc before tho so /shrug. But if you check local and the code is there then that is the right file.

Um on Harmonia Im not sure if there will be or not. ON CM7 roms there is other stuff but its only one thing.
 
Re: Cannot get bootsound to work on Harmonia

Well now it vibrates when the Harmonia screen displays at bootup. This just gets more and more interesting. It doesnt happen all the time. But it started when I started this quest for a bootsound.
 
Re: Cannot get bootsound to work on Harmonia

Okay. So I tried a little something different. I did a little research on the error "No such user root: shell". Someone a while back had that issue and was told to use a command line for Terminal to change "root: shell" to "root.shell". I tried the command in the link I found and it didn't work. So I had an idea. I went into the bootsnd.sh file and changed where it says "root: shell" to "root.shell". I tried to run the script again in Terminal after doing this and it got rid of the "No such user root:shell" error. Now it just says this when I run the script in Terminal:

Usage: mount [-r] [-w] [-o options] [-t type] device directory
Usage: mount [-r] [-w] [-o options] [-t type] device directory

And the boot sound still doesn't play on start up.

I'd like to know what the "Usage: mount..." stuff means. I hope there is a way to crack this egg! Maybe this rom won't allow a bootsound at all, but I'd like to try to make it work.
 
Last edited:
Re: Cannot get bootsound to work on Harmonia

That is how the system knows to mount the various parts of the file system so they can be modified.

When your getting that error it normally means your superuser is not authorized for the application trying to use it.
 
The "usage mount:" message means that the command syntax is not correct.

Sent from my VM670 using Tapatalk
 

Trending Posts

Members online

Forum statistics

Threads
957,053
Messages
6,971,220
Members
3,163,694
Latest member
andrewmil85