(Update Fixed go to second page!!)
Well, this could be worse but here goes...
So multitouch keyboard sound were bugging me so i figured change them over to the click sound for wp7 instead, so i used root explorer backed up kb sounds
from system/media/ui and replaced them with wp7 kb sounds....
all went right except i noticed the the KeypresStandard sound wasnt working right (i would click and wouldnt hear anything, space and enter worked!) so i figured thats not good let me just replace all the sounds with my backup sound files, and same thing no sound just for Keypresstandard!!
Here is the odd thing if i hit the some keys real fast i get the keypresstandard to make a noise every now n then!!??
Is there a cache file i need to clear? i even did a factory restore (knowing that wouldnt do anything) but i figured why not
any ideas, I should of made a backup with cwm but i wasnt sure if i restored if i would brick this thing... so i never bothered with cwn at all sigh......
don't restore with cwm, cannot guarantee that it will work at this point.
double check the names of the default sounds and the new sounds, make sure they are named the same and in the same format (mp3, ogg, whatever)
There in .ogg, its just the KeypressStandard.ogg that seems messed up, other sound files for KB work fine, hmm anyone have keypressStandard.ogg? Maybe it got corrupted some how? im gonna try to make m own see if i can get it to work...
and for cwm, ya i figured not to even use it till i know it was safe... btw thanks for the reply!!
So... (update!)
For the life of me i cant fix the back up KeypressStandard.ogg, Ive never seen anything like this b4....
So what i did was take KBspace.ogg rename it to KeypressStandard.ogg and it works (not the ideal fix) but atleast its a sound..
I'll just to have to wait till a sbf is out to reflash the damn thing to stock, its not a big deal but ocd is such that i want it perfectly back to stock :: shrugs ::
Just pisses me off somtin so simple is giving me such a hard time, oh well, i can wait sorta, kinda, maybe
Just turn of the sound.
Sent from my MB865 using xda premium
kleeman7 said:
Just turn of the sound.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Ya that would be to simple, why ignore the problem when u could fix it
This may sound stupid, but did you check case on the filenames?
maybe filesize or permissions?
Would the cache/dalvik cache mess with the sounds maybe?
Here's my original maybe it will work for u
frycook15 said:
Here's my original maybe it will work for u
Click to expand...
Click to collapse
Thanks for sending the file,
Still Not working, I checked the permissions and they match to the other KB sound file, tried to wipe cache under the default recovery, still wont work.
The odd thing like i said b4 if i rename the KeypressSpace to KeypressStandard the sound file works without a problem.
Thanks again guys for the replies, I havent tried to clear davlik, I havent put cwm on yet so,any other free app on the market clear davlik ?
Thanks again All
FIXED!!!!!
Update! Fixed the problem
First i want to thank you guys for taking the time to try and help me out!!!!
This is how i fixed it, i was sitting around thinking about how in the past i had to play around with Motorola android phones for my g/f, she had the droid and many more on verizon, and i remember the fun i had modding here phones (aka i was the one stuck rooting/flashing anything for her)
Then it hit me , I used root explorer with her devices and i remembered how i had problems with.apk's i would modifiy and zipalign/resign then copy over to /system
So what i had to do was just use adb instead of root explorer. but enuff of my rambling this is how you do it!
1.Move file you want to push to sdcard of your phone
2 fire up adb
at prompt type
3.adb shell
4.su
5 mount -o rw,remount /dev/block/mtdblock3 /system
6 cat /sdcard/KeypressStandard.ogg > /system/media/audio/ui/KeypressStandard.ogg
7 chmod 755 /system/media/audio/ui/KeypressStandard.ogg
8 reboot
and thats it ....
This is a lesson for us all, Use an iPhone for any amount of time and slowly but surely all past knowledge of android/adb go out the window and u try the easier way first! either that or im just getting old (I do sometimes forget my own name) but hey i rather blame apple
thanks again all
command line rules. LOL
kirkgbr said:
command line rules. LOL
Click to expand...
Click to collapse
+1 on that
iB4STiD said:
Thanks for sending the file,
Still Not working, I checked the permissions and they match to the other KB sound file, tried to wipe cache under the default recovery, still wont work.
The odd thing like i said b4 if i rename the KeypressSpace to KeypressStandard the sound file works without a problem.
Thanks again guys for the replies, I havent tried to clear davlik, I havent put cwm on yet so,any other free app on the market clear davlik ?
Thanks again All
Click to expand...
Click to collapse
Welcome and well atleast u got it fixed lol
Sent from my MB865 using XDA Premium
Related
Hey all,
I know I just put up my tutorial on how to do this but hopefully this will make things easier for everyone. I'd still suggest doing a nandroid backup first just to make sure but I tested this on my phone so it should work. Just run the app and if this is the first time moving your apps to your sd card(and you want to keep the ones you have) leave the checkbox checked. Otherwise uncheck it. Then just press the buttons that correspond to what you want to do. Enjoy
In order to use this you MUST:
1: Have an apps-to-sd ROM
2: Have your sd card partitioned correctly with FAT32 first and ext2 second.
3: Have busybox already installed to /system/xbin
NOTE: I'll try to help as much as I can but I can't take responsibility for anything this does to your phone. I'm pretty sure nothing bad will happen and nothing irreparable can happen but gotta say these things just to be sure anytime I'm messing with root permissions.
ANOTHER NOTE: I'll put this up in the market for $1. It'll remain free here but people can donate to me that way.
YET ANOTHER NOTE: I've managed to get a new method working that's a lot more stable and flexible. I will keep this thread here but won't be maintaining it.
EDIT: Moving data is too unstable, I've removed the option. It doesn't force close anymore when you don't have the setup right, it just gives an error and wont let you do anything, so that's better.
Tried it this morning and worked great. You might add a pop up at the end of moving apps to restart the device. When less experienced people use it, they won't know to do that I'm afraid.
the app sends me into abootloop at the htc screen
ps
i tried from fresh wipe and sd
Nismo300zx said:
the app sends me into abootloop at the htc screen
ps
i tried from fresh wipe and sd
Click to expand...
Click to collapse
OH SHOOT!!! I fixed this problem on the market one but forgot to put it back up on here. Umm... for now no1 should use the one posted here, until I can get home and post the updated one. OR if you still want to fix this and don't much just a bit of fiddling in the recovery terminal, after moving apps to sd, restart in recovery mode and do this:
Code:
mount data
ln -s /system/sd/app /data/app
For anyone who cares about such things, the problem is that it deletes the /data/app folder and then makes a symlink, which sounds ok, except that every super user command has to be run through the whitelist app... which no longer exists. So it's not able to set up the link and all hell breaks loose.
i did use the 1 from here
it says ln: /data/app: file exists
if i already had apps2sd, tried to upgrade my phone from 5.0 to 5.01G, so I wiped...then data.img wouldn't flash over...if i do this, will my apps show up again?
Nismo300zx said:
i did use the 1 from here
Click to expand...
Click to collapse
ya it's the one from here that's broken, sorry. If you haven't already flashed back and everything(still have the boot loop) then you can use the code I posted and it should fix it. I'll post the updated version tonight when I get back home.
AbsoluteDesignz said:
if i already had apps2sd, tried to upgrade my phone from 5.0 to 5.01G, so I wiped...then data.img wouldn't flash over...if i do this, will my apps show up again?
Click to expand...
Click to collapse
Yes, just uncheck the checkbox. But you might want to read the note that I just posted, there's a known problem with it that has a fix but requires going into the recovery terminal. I'll post the updated version of this app that doesn't have that bug tonight.
jus tried and nothing ..now im stuck at tmobile g1 screen..im startin to think it just dnt like me
Nismo300zx said:
jus tried and nothing ..now im stuck at tmobile g1 screen..im startin to think it just dnt like me
Click to expand...
Click to collapse
Try reading a few of the posts above yours.
ThaBadBoy said:
Try reading a few of the posts above yours.
Click to expand...
Click to collapse
i been at this for 2days ive tried evrythin ..hmm time to give up soon
Nismo300zx said:
i been at this for 2days ive tried evrythin ..hmm time to give up soon
Click to expand...
Click to collapse
Not really,,
According to the like 6th post or something its states this app wont work if you download it from here, but if you were to get it through the market....
Bob should now be your uncle
if you give him some time as clearly posted again, he will fix the app from the first post and replace it later on
Dantehman said:
Not really,,
According to the like 6th post or something its states this app wont work if you download it from here, but if you were to get it through the market....
Bob should now be your uncle
if you give him some time as clearly posted again, he will fix the app from the first post and replace it later on
Click to expand...
Click to collapse
ok if i typed the commands in manually and it wnt work ..and the app wnt work ..im tired of wipin the fone and formattin the sd card...=[ i give up
Nismo300zx said:
ok if i typed the commands in manually and it wnt work ..and the app wnt work ..im tired of wipin the fone and formattin the sd card...=[ i give up
Click to expand...
Click to collapse
you had the "stale NFS handle" right? I'm not really sure what's going on but something in your phone's file system sounds like it went screwy. Maybe someone like JF or LucidREM could help? Your problem goes way over my head and I'm guessing the same is true of a lot of people on here unfortunately.
its cool imma jus stay with apps n caches to sd...n kep dalvik on the fone..i got passed the nfs error and get stuck at tmo g1 screen maybe ill try again l8ter
jf rom
Ok question I know it says apps to sd rom is needed does this mean only haykuro roms? I have a jfrc33 1.42 and I could do apps to sd using this rom (planning on doing it tonight my 8gig class 6 card arrived) so my question is can I just use this app or do I need to do all the steps manually
jjjackson56 said:
Ok question I know it says apps to sd rom is needed does this mean only haykuro roms? I have a jfrc33 1.42 and I could do apps to sd using this rom (planning on doing it tonight my 8gig class 6 card arrived) so my question is can I just use this app or do I need to do all the steps manually
Click to expand...
Click to collapse
It should work on any apps to sd ROM. This includes LucidREM's modified JF ROMs. If you're gonna be manually changing it into an apps to sd, then I would think it would work but can't promise it. I wasn't able to figure that out when I tried so I'm not 100% sure that they work the same but I would imagine they would. Again, though, the one posted here has that known bug which will be fixed after I get home from work.
Short answer(s):
Haykuro's ROM: definitely works
LucidREM ROM: Don't have it to test it but almost assuredly works
Self-modified: probably works?
Sounds good I wasn't doing it till later tonight anyways (stuck at work also) also is it still a good idea to keep ext2 parititon less then 2gb like lucid reported on his tutorial
jjjackson56 said:
Sounds good I wasn't doing it till later tonight anyways (stuck at work also) also is it still a good idea to keep ext2 parititon less then 2gb like lucid reported on his tutorial
Click to expand...
Click to collapse
Probably, I haven't tried anything bigger... and seriously, you'd need a crazy amount of apps to fill up even 1GB...
[email protected] said:
Probably, I haven't tried anything bigger... and seriously, you'd need a crazy amount of apps to fill up even 1GB...
Click to expand...
Click to collapse
True. that sure would be a lot I dont even think all the apps in the market would fill 2gigs lol. Thanks for your work look forward to trying it later
well when i was going delete happy I accidentally killed this off.. would one of you be kind enough to upload it for me
Copied this from /system/app hopefully this is what you need.
tcberg2010 said:
Copied this from /system/app hopefully this is what you need.
Click to expand...
Click to collapse
i grabbed it out of the system.img but yes that is what I need.. just cant get back in adb while in recovery lol
lol, i didn't delete anything when i first got su, and i've been afraid to turn my phone off even though i have superuser permissions, titanium, just didn't want to take th chance. Good luck getting back into recovery.
Maybe try using Bloo for Android or Babbler instead
tcberg2010 said:
lol, i didn't delete anything when i first got su, and i've been afraid to turn my phone off even though i have superuser permissions, titanium, just didn't want to take th chance. Good luck getting back into recovery.
Maybe try using Bloo for Android or Babbler instead
Click to expand...
Click to collapse
ya i forgot to install busybox the first time so i tried for another day straight got back in and then deleted this like a idiot.. the offical FB app still works from market but I cant sync anyones facebook to my contacts atm.
Dont know if you tried
Get the loop.bat and it makes it pretty easy to get in
sometimes I have to do it 2 or 3 times but thats about the most it takes me to get into adb.
try it, it made rooting this phone the easiest root method on any phone I rooted so far.
did a 3g fender
a bunch of moto droids and one N1
I tried to post the bat file but its not working so here's my second method for you
Open a text program and paste all this in it then save it as loop.bat
:TOP
adb shell
GOTO TOP
This will make it easy to get into recovery for you
watch for the error to show up then you know you got it then you hit
ctrl+c to stop it
I had to use the loop.bat file to get adb in recovery, content for now until someone figures out how to unlock NAND protection.
Sent from my ADR6300 using Tapatalk
Did the same thing. Downloaded that file and it won't let me install it tho.???? Any suggestions?
same problem he is Havin
just wait for the nand unlock and all will be well then
Same problem
I downloaded the file, can someone please explain how to install it using ADB?
I have been trolling the forums for awhile and I never post but this is something that I have not been able to come across. Why after I used the bootstrap app and load into the recovery menu that now every time I go to reboot my phone I automatically go into the recovery menu even after a successful boot? Hope I worded that right. Please help and thank you!!
just realized I am in the theme section. Can this be moved to the appropriate board. THANKS!!
That's the way it works, it hijacks the bootloader, trust me its a good thing. Bootloop, battery pull, recovery, restore backup. Several times I've been glad it works that way.
Sent from my DROIDX using XDA App
Wait. I have a normal reboot. Maybe mine is messed up?
Yeah I got that but I thought it was only if I pulled the battery after it bootlooped. It does it every reboot except after I flashed a "rom", but I didn't like the rom so I reverted back to stock. I mean its awesome to have the security blanket but it can also be a bad thing if my 14 yo cousin gets ahold of my phone then formats my system an then reboots. Thanks for the help by the way.
Sent from my DROIDX using XDA App
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
If you want to remove bootstrap, you can do SBF flash, which I did several times and it perfectly works.
Zaphod-Beeblebrox said:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
Click to expand...
Click to collapse
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Oh and thanks for the help by the way.
UPDATE:
So I think I found it.
Unroot and Remove Recovery Via RootExplorer
jkpair said:
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Click to expand...
Click to collapse
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Zaphod-Beeblebrox said:
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Click to expand...
Click to collapse
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
jkpair said:
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
Click to expand...
Click to collapse
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Zaphod-Beeblebrox said:
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Click to expand...
Click to collapse
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
jkpair said:
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
Click to expand...
Click to collapse
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Zaphod-Beeblebrox said:
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Click to expand...
Click to collapse
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
jkpair said:
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
Click to expand...
Click to collapse
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
DrewDanger said:
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
From my earlier post:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
Click to expand...
Click to collapse
I went through Astro and searched "/data/.recovery_mode" but it didnt bring up that file. I guess Im just confused at what exactly Im supposed to be looking for...
Yeah I ended up using a root file manager to do this was really easy. Just go the root menu and browse to data find recovery_mode and delete then reboot.
Oh and astro will not show what is in the data folder you have to get a root explorer app I think the one I used was android mate.
Sent from my DROIDX using XDA App
Ok cool I'll check that out. When I use Astro and go under "system" and scroll down it has a "recovery from boot" folder. Any idea what that is? When I open it there is a bunch of code script in it
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
DrewDanger said:
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
Click to expand...
Click to collapse
Yeah it has an option to unroot, but I can't state whether or not this is the best method to remove the root. I acctually am keeping my root and bootloader. Yeah I will be glad when there is a true rom as well but progress is progress.
These are the Galaxy S II Boot and Shutdown animations with corresponding sounds (GINGERBREAD ONLY).
Instructions for CWM:
Put GB_S2_Boot-and-Shutdown.zip on the root of your SD card
Power off your phone
Hold Volume Up & Volume Down while pressing the power button to enter CWM
Choose "Install zip from sd card"
Choose "Choose zip to install"
Select GB_S2_Boot-and-Shutdown.zip
Confirm selection
Choose "***go back***"
Choose "reboot phone"
Enjoy new animations!
If, for some really strange reason you're *not* running drhonk's amazing KG4 kernel w/red cwm & ext4 support, then you will need to remount /system as read/write, push the contents of /system from the zip file to /system on your phone, and then make sure all the files have the right permissions (644 or 0644).
Credits:
joedeveloper - boot animations
virajss - shutdown animation
chadster214 - randomly picked a cwm file he had made to figure out how to make my own
Myself - audio files & packaging
If this made your life easier, please hit the thanks button!
It worked.. Cooooolll
it's work but i can't hear the sound
nOl3ell said:
it's work but i can't hear the sound
Click to expand...
Click to collapse
Try flashing it, again. Maybe the sound files didn't take or the permissions didn't set. I can hear both sounds. If that doesn't work, get back to me and we'll try some troubleshooting
Jay Aristide said:
Try flashing it, again. Maybe the sound files didn't take or the permissions didn't set. I can hear both sounds. If that doesn't work, get back to me and we'll try some troubleshooting
Click to expand...
Click to collapse
Thx bro....and how can i set permissions (644 or 0644)
nOl3ell said:
Thx bro....and how can i set permissions (644 or 0644)
Click to expand...
Click to collapse
In a terminal or adb shell, the command is chmod
Code:
# chmod 644 /system/media/bootsamsung.qmg
You'll have to remount /system as read/write first, though (I use root explorer for such things). Did you try just re-flashing the zip, first?
thanks it worked great! Didn't like that it actually says SGS II, but other than that it's a good boot animation... better than stock pink gay one.
**presses thanks button**
works great! Glad that the tmobile epileptic pink text screen is now gone for me.
I flashed twice and still no sound? Well I shouldn't say no sound cuz I heard the sound 5 times outta 20 only works sumtimes any suggestions its not that big of a deal as long I it ain't that gay pink Tmobile one lol
Sent from my SGH-T959V using xda premium
bbobarino said:
I flashed twice and still no sound? Well I shouldn't say no sound cuz I heard the sound 5 times outta 20 only works sumtimes any suggestions its not that big of a deal as long I it ain't that gay pink Tmobile one lol
Click to expand...
Click to collapse
The sound is pretty quiet for me, but I'd say I hear it 6 out of 10 times on average. No suggestions, though.. Sorry.. If anybody can shed any light it would be appreciated
Love it!!!
this is really nice! I love it! thanks Jay
Quick question, When I boot into recovery it does not have an option to install zip from SD? it just says reinstall packages,delete user data, delete cash ?
You need to intall one od Dr.honk's kernel and what ROM are you.on?
Sent from my SGH-T959V using XDA App
killnkajun said:
Quick question, When I boot into recovery it does not have an option to install zip from SD? it just says reinstall packages,delete user data, delete cash ?
Click to expand...
Click to collapse
That's standard Samsung Recovery. You need to do this from ClockworkMod recovery (CwM).
Yeah I'm stock, but rooted. I'm not comfortable flashing custom roms yet
I don't really see that much difference or enough difference to flash a custom rom
But I really dont like the pink "gay" boot screens
killnkajun said:
Yeah I'm stock, but rooted. I'm not comfortable flashing custom roms yet
I don't really see that much difference or enough difference to flash a custom rom
But I really dont like the pink "gay" boot screens
Click to expand...
Click to collapse
If you are rooted, follow this thread to change the pink boot animations to SII ones.
http://forum.xda-developers.com/showthread.php?t=1209211
Yeah, what he said If you pull apart the .zip file I have here, you can easily push all of these files to their appropriate places, yourself.
It's worth mentioning, though, that the shutdown file in my zip won't work with your phone, as you're not running gingerbread. The shutdown animation for Froyo is actually a series of .png images, a configuration file, and a .ogg sound file.... There are at least two threads on these forums that explain how to replace the froyo shutdown animation with the one from the stock Galaxy S
Gorgeous animation. Thanks!
Sent from my SGH-T959V using XDA App
Well I jumped in neck deep, got the new GB and doc's kernel.
Sweet bootup now thanks!
Thank you! Love it.
Sent from my Samsung Galaxy S 4G
hey guys i have made and tested some boot audios for the p6200 and the p6210 they all work and are reformatted to work with the booting up of the tab
NOTE: I am not responsibly for the bricking of your tab or nuclear war so don't have a go at me if you mess it up haha
REQUIREMENT: you must have root to make this work or you could end up in a messy situation haha i say could i mean i don't know what will happen if you are not rooted.
oh i will add more so just hold on a bit
Hey so basically i use cwm to flash the zip files? Am on DXKL3 Malaysia firmware rooted with cwm.
Thanks & Cheers!
Sent from my GT-P6200 using xda premium
sahildeswal said:
Hey so basically i use cwm to flash the zip files? Am on DXKL3 Malaysia firmware rooted with cwm.
Thanks & Cheers!
Sent from my GT-P6200 using xda premium
Click to expand...
Click to collapse
sure thats it haha. it really does not matter what firmware version you are using it will work an any its universal as far as g tabs go.
Great work jmar... another customised item we got on this great device.
if only we can found a way to change the boot logo also...
edan1979 said:
Great work jmar... another customised item we got on this great device.
if only we can found a way to change the boot logo also...
Click to expand...
Click to collapse
i will be looking in to tham i may try pulling the default doot animation and moding it
got less to do today at work so i play with the files...
Star Trek Computer Standby sound...
edan1979 said:
got less to do today at work so i play with the files...
Star Trek Computer Standby sound...
Click to expand...
Click to collapse
so does this work or do you want me to turn it in to one? haha
its working fine... pretty easy to do it...
edan1979 said:
its working fine... pretty easy to do it...
Click to expand...
Click to collapse
thanks man ur awesome
How about a silent boot sound? Or is there a way to turn off the boot sound without turning the system volume to zero?
rename poweron.wav or delete it. recommend renaming in /system/etc/
boot logos,: Im guessing from my experience so far they are going to be in param.lfs and/or C-header code format in kernel. both are nearly impossible to change and will take a lot of work but can be done.
I will probably look more into this in the coming week. There very well may be one in each location I mentioned. Images will likely not be able to be much bigger than stock, which probably isnt much.
the one in the kernel will not be easily changeable for each person , where as hopefully a hex edit hack would allow us to change the one in param.lfs with root explorer on the fly.
I already searched param.lfs for logo.jpg(common for samsung) and came up empty.
Next I will try a script for extracting images from param.lfs
Happy Hacking!!
Gazorninplat said:
How about a silent boot sound? Or is there a way to turn off the boot sound without turning the system volume to zero?
Click to expand...
Click to collapse
lol... record a silent sound in media recorder...
here.. silent for you... in surround...
oh btw... the file name is 1_Power_on.ogg or wav
thanks, yeah I knew the name wasn't exact, just typing from memory. Should have been able to find it.
Dazed and confused...
OK there is a very high likely hood that I am doing something highly stupid but I gotta ask why this isn't working for me.
I have a P6210 that is rooted. In CWM I go to the "Install zip from sd card" then choose either "choose zip from sdcard" or "choose zip from internal scard" depending whether I want to chose a zip from the internal or external sd card. I then choose the appropriate zip and away I go correct?
If that is the case for some strange reason this isn't working. I would really like to use the silent boot because I hate the stock boot up tones.
This is the output when I select any zip to install from this thread:
-- Installing: /sdcard/silent_boot.zip
Finding update package...
Opening update package...
Installing update...
Reverting back to stock.
Wiping dalvik cache.
Formatting cache.
Copying Files
Setting permissions.
Install Complete.
hmmm... yup that not working... use root explorer and try go to root system/etc and rename the 1_Power_on files to something else... and see if its working
btw i re-create the files... try this