Database Info

[Q] Unroot / Return to Stock Recovery for Nexus S 4G (Sprint)

Gang, I've searched and couldn't find. I rooted the Sprint Nexus S 4G and installed CW recovery.
Would some one please be kind enough to point me on how to unroot and return to stock recovery for a return.
Thank you!

Why do you want to return it?

dmora01 said:
Why do you want to return it?
Click to expand...
Click to collapse
Exchanging for another, I appear to have a defective screen which flickers when phone is shaken.

Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.

r80ies said:
Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.
Click to expand...
Click to collapse
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.

What about the custom CWM recovery?
oldblue910 said:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse

a2k said:
What about the custom CWM recovery?
Click to expand...
Click to collapse
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse

oldblue910 said:
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
Many thanks!!!!

Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?

a2k said:
Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?
Click to expand...
Click to collapse
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.

oldblue910 said:
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.
Click to expand...
Click to collapse
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su

a2k said:
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su
Click to expand...
Click to collapse
OK check /system/bin then. Is BusyBox in there?

oldblue910 said:
OK check /system/bin then. Is BusyBox in there?
Click to expand...
Click to collapse
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?

a2k said:
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?
Click to expand...
Click to collapse
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.

oldblue910 said:
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.
Click to expand...
Click to collapse
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)

a2k said:
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)
Click to expand...
Click to collapse
Oh no wonder! You're all set then. BusyBox is located within Titanium Backup's data folder. You don't need to worry. BusyBox will go away when you uninstall Titanium. So just follow my updated instructions and you're good. Let me know if you have any problems. Make sure you have a nandroid backup of your ROM before you delete root, just in case! You can never be too careful!
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse

Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..

spdwiz18 said:
Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..
Click to expand...
Click to collapse
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.

oldblue910 said:
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.
Click to expand...
Click to collapse
Nope .... no such file. I even did a search for it with root explorer and it does not come up. If worse come to worse ill pull it from someone's Tom just so I have it on my phone. But I know I did not delete it.
Sent from my Nexus S 4G using XDA Premium App

That is very strange indeed. I wonder if Google didn't install it on the Nexus S 4G. Can any other NS4G owners verify if /etc/install-recovery.sh exists on your phone?

Root you Droid charge the Clean way (adb)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://www.samsung.com/us/support/downloads/SCH-I510RAAVZW
DRIVERS- Once you go to the download link you should see
"MANUALS l SOFTWARE" click on software and download those drivers! If your phone is plugged in while you are doing the download this is ideal because they will automatically sync.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://developer.android.com/sdk/index.html
DOWNLOAD SDK- (Get the zip and paste it in your C:\ Drive for less headache)
After you have downloaded and pasted in your C:\ run "SDK Manager.exe" If your on Vista I run everything as Admin so just run it as Admin so there's no mix ups.. Whenever you run a program while following this tut USE ADMIN!!
When you run the program a little black box similar to cmd pops up.. just move it out of the way because its not important.
That being said you should now see a loading box and if your computer runs pretty quick it should be about done by the time you get done reading this.
Check the very first box and uncheck the rest.. all you need is the "platform-tools option. The other stuff is irrelavent to what were trying to accomplish.
Once you have the folder "platform-tools which is going to be inside your Android folder.. (the one we pasted to our C:\ not too long ago) look inside the folder to confirm that "adb.exe" is inside.. if it is then close out of sdk if not.. figure out what you did wrong and fix it! by default the adb.exe is in your tools folder so if all else fails follow my instructions using your tools folder meaning everything I use the word "platform-tools" you would just use "tools" or wherever adb.exe is located.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This tutorial is WORD FOR WORD meaning this is exactly what you type into your command prompt
The "$"s and the "#"s are what you SHOULD see after you have typed in adb shell once you've navigated to your sdk folder.(If you have no clue what im talking about, you will just continue reading)
BEFORE WE BEGIN download GingerBreak, busybox, Superuser.apk, su
EVERYTHING IS CASE SENSETIVE so make sure your watching that.. if something doesn't work.. you prolly misspelled or
didn't put a space or didn't have the right case..
DroidChargeADB_rootKIT.rar
http://www.multiupload.com/1Z5DDP79QI
After you have downloaded the DroidChargeADB_rootKIT extract them into your /Android/platform-tools/ folder wherever it is..
Default location for platform-tools is usually this
win32- C:\Program Files\Android\android-sdk\platform-tools (wherever your adb.exe is, is where you should set your path)
win64- C:\Program Files (x86)\Android\android-sdk\platform-tools
Click start go to command line (go to "run" and type in "cmd")
after the "~~~~~~~~" is when it begins and thats when you type word for word what ive typed out
unless i have said something then I will make it obvious that you dont type that also I will put (Dont type this)
at the beginning of my text and at the end.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cd C:\Android\platform-tools
adb devices
adb push GingerBreak /data/local/
adb push Superuser.apk /data/local/
adb push su /data/local
adb push busybox /data/local/
adb shell
$cd /data/local/
$chmod 700 /data/local/GingerBreak
$chmod 755 /data/local/busybox
$./GingerBreak (<~~~~Dont forget the period (Dont type this))
(DONT TYPE THIS)
THIS
BIG
LONG
LIST
OF
USLESS
INFORMATION
(DONT TYPE THIS/)
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#chmod 777 /system/bin
#./busybox cp busybox /system/bin (<~~~~Dont forget the period(NO TYPE))
#chown root /system/bin/busybox
#chmod 777 /system/app
#chmod 755 /system/app
#chmod 4755 /system/app
#busybox cp Superuser.apk /system/app
#busybox cp su /system/bin
#chown root /system/bin/su
#chmod 755 /system/bin
#chmod 4755 /system/bin/su
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
#restart
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
YOUR ROOTED THE PROPER WAY!! And its a very clean root.. Hope I helped.. Dont tell me I helped! CLICK THE BUTTON! =] ty for reading all that hahahahaha..
ONE other thing. DONT BE "THAT" GUY.. haha shutup. you know exactly what I mean.
ALSO if you want stock EE1 versions of this software with cool fonts,backgrounds,de-bloated,cool ringtons, already rooted(or non-rooted) and odin ready, just let me know and Ill upload them!

That Guy u Kno said:
=] ty for reading all that hahahahaha..
ONE other thing. DONT BE "THAT" GUY.. haha shutup. you know exactly what I mean.
ALSO if you want stock EE1 versions of this software with cool fonts,backgrounds,de-bloated,cool ringtons, already rooted(or non-rooted) and odin ready, just let me know and Ill upload them!
Click to expand...
Click to collapse
I....don't......know.....how......to......respond!?
There is some useful info here but everyone just flashes stuff here. We use kernels that root the phone for us, thereby not needing to manually root it.

kernels never work for me.. i gotta do it the hard way =(

That Guy u Kno said:
kernels never work for me.. i gotta do it the hard way =(
Click to expand...
Click to collapse
You're going the very hard way if you're on anything but ED1 as none of the root exploits work on ED2/EE4 or the GB leaks.

I really don't understand why you need this...
Sent from my Droid Charge running GummyFroyo 1.9.1

Thanks for putting this out there. Its nice to know there's another way to do this.
Sent from my SCH-I510 using Tapatalk

putney1477 said:
Thanks for putting this out there. Its nice to know there's another way to do this.
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
Agreed, I personally won't use this but hey, options are always nice.

kvswim said:
I really don't understand why you need this...
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
I find it useful as i have had trouble with the "easy" methods as well. This could come in quite handy.
Sent from my SCH-I510 using Tapatalk

mr.terry said:
I find it useful as i have had trouble with the "easy" methods as well. This could come in quite handy.
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
This won't come in handy at all. As of ED2, which was released the day that the Charge launched, no known exploit methods work to gain temp-root access. So, unless you're keeping your phone on ED1 for the entire life of the phone, this method is useless.

imnuts said:
This won't come in handy at all. As of ED2, which was released the day that the Charge launched, no known exploit methods work to gain temp-root access. So, unless you're keeping your phone on ED1 for the entire life of the phone, this method is useless.
Click to expand...
Click to collapse
Exactly, if you root this and then boot the phone, it will unroot itself unless you are running ED1, and that's just..... pointless.

imnuts said:
This won't come in handy at all. As of ED2, which was released the day that the Charge launched, no known exploit methods work to gain temp-root access. So, unless you're keeping your phone on ED1 for the entire life of the phone, this method is useless.
Click to expand...
Click to collapse
Ahhh i see. Good to know. I come from a couple of years of playing with a rooted og droid and the charge is new territory for me. Thanks for the heads up.
Sent from my SCH-I510 using Tapatalk

One click root is the same exact concept... Its clean regardless. But thanks for the effort of typing all that up, lol.

Although the "purpose" of this tut may be worthless quite a few of the commands you learn from this are essential in all builds.. such as chmod, chown, mount... I still use these commands frequently although this is beginner level (still good )

No boot animation

Hi
I'm using the Infused rom with infusion Kernel
Since I flashed the Rom i don't have any boot anim...
After a long samsung logo the launcher appear.
I already tried to reflash, do factory, but nothing help.
I also tried a boot anim changer app and even when it said its applied, there is still no boot anim....
Any ideas guys?
Sent from my SAMSUNG-SGH-I997 using XDA App

Go in root explorer and go to system/media/scroll down and check to see if there is a boot animation.zip in there
Sent from my B.A. Infuse 4G

Root exploret crash everytime i open it
Sent from my SAMSUNG-SGH-I997 using XDA App

Teranox said:
Root exploret crash everytime i open it
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
The only time Root Explorer crashes on me, it's because I don't have root permission. Assuming you are rooted, can try three things:
1) Go into the Superuser App and find root explorer if its there and choose to forget it.
2) If that doesn't work reboot.
3) If THAT doesn't work try a different file explorer.

I have root and root explorer display that it got root permission a second before.it.crashed.
I've used an.other program and i can.confirm there is.the bootanimation.zip in the folder....even tried to change it for an.other on (ice cream sandwish boot).
I rebooted about 5 time and still no boot animation....
Could the os have problem reading a zip file???
Sent from my SAMSUNG-SGH-I997 using XDA App

I was thinking about something.
Could I get no bootanimation because my phone is fast to boot?
one it's powered on, it take about 15-20 seconds before i get to the OS....
Sent from my SAMSUNG-SGH-I997 using XDA App

Jeez that's a head scratcher...what about permissions? Mine are all checked but Others/Write. That's really weird a factory reflash didn't work..

In Android Terminal Emulator, assuming you've already remounted /system read/write, try:
Code:
chmod 644 /system/media/bootanimation.zip
Other possibilities:
Some versions of the bootanimation binary only support PNG bootanimations, not JPEGs like the ICS bootanimation.
Some insist on it being /system/media/sanim.zip

Entropy512 said:
In Android Terminal Emulator, assuming you've already remounted /system read/write, try:
Code:
chmod 644 /system/media/bootanimation.zip
Other possibilities:
Some versions of the bootanimation binary only support PNG bootanimations, not JPEGs like the ICS bootanimation.
Some insist on it being /system/media/sanim.zip
Click to expand...
Click to collapse
Entropy512's answer is good. Listen to him.
Don't be afraid
eXpeR¡MeNt

Entropy512 said:
In Android Terminal Emulator, assuming you've already remounted /system read/write, try:
Code:
chmod 644 /system/media/bootanimation.zip
Other possibilities:
Some versions of the bootanimation binary only support PNG bootanimations, not JPEGs like the ICS bootanimation.
Some insist on it being /system/media/sanim.zip
Click to expand...
Click to collapse
What do you mean by remounted /system read/write ?

Entropy512 said:
In Android Terminal Emulator, assuming you've already remounted /system read/write, try:
Code:
chmod 644 /system/media/bootanimation.zip
Other possibilities:
Some versions of the bootanimation binary only support PNG bootanimations, not JPEGs like the ICS bootanimation.
Some insist on it being /system/media/sanim.zip
Click to expand...
Click to collapse
When I Just enter the code it say: Unable to chmod '...' Read-only file system

Teranox said:
I was thinking about something.
Could I get no bootanimation because my phone is fast to boot?
one it's powered on, it take about 15-20 seconds before i get to the OS....
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
So you are fast booting your phone?
Teranox said:
What do you mean by remounted /system read/write ?
Click to expand...
Click to collapse
And he's talking about the r/w, r/o option in root explorer so you can edit permissions,move files etc. Also, you can download an Android Terminal Emulator in the market.

xIC-MACIx said:
So you are fast booting your phone?
And he's talking about the r/w, r/o option in root explorer so you can edit permissions,move files etc. Also, you can download an Android Terminal Emulator in the market.
Click to expand...
Click to collapse
Maybe my phone is fast booting by itself because I did nothing to help it boot as fast as this. since I Flashed the ROM the boot is blazing fast.
I did Mounted as RW with an app called Remount. It do the Root remount and it seems to work (for mounting) BUT! Still no boot anim.
I began to think that it's not that bad as I don't really reboot 5 time a day to enjoy a psychedelic screen lolll.
but still....it's more the Why than the How in this case

Teranox said:
What do you mean by remounted /system read/write ?
Click to expand...
Click to collapse
^^ this means that Entropy's instructions are assuming that you remounted system as read/write so that you can edit replace the bootanimation.zip. In Root Explorer once you navigate to system/media then in the top left it will say "mounted as r/o" next to that is a button that says "mount r/w" click that and it should "remount" your system as read/write.
At this point you should be able to replace the old with the new bootanimation.zip.
Reboot, and you're done.
If it still hangs and shows NO animation then my guess is you are using an incompatible bootanimation (that does happen, and will just stay black then your phone will just start, with no animation) try a different one, like the one below I know for sure works on the Infuse
http://dl.dropbox.com/u/19412696/480x800_AndroidParticles1_Blue.zip
X
Don't be afraid,
eXpeR¡MeNt
Edit: Sorry it took me a long time to write all that on my Infuse, while i'm watching a movie also. Now that I posted I see others have informed you of the r/w stuff, but 2nd half is most likely your case.

[Q] Blur Camera won't install

Alright so here's my problem: After rooting my phone, I started to play around with a couple of camera apps from different ROMs such as MIUI. Me being an idiot though, deleted the stock Blur camera Apk. Using a system dump of the Atrix, 2 I tried to reinstall it, by placing it in system/app. For some reason. It wouldn't install (show up on my app directory). Anybody have any idea as to why this is happening? Any help would be greatly appreciated, because I really need a camera app.that's supports 1080p video. Thanks in advance!!!

farshad525hou said:
Alright so here's my problem: After rooting my phone, I started to play around with a couple of camera apps from different ROMs such as MIUI. Me being an idiot though, deleted the stock Blur camera Apk. Using a system dump of the Atrix, 2 I tried to reinstall it, by placing it in system/app. For some reason. It wouldn't install (show up on my app directory). Anybody have any idea as to why this is happening? Any help would be greatly appreciated, because I really need a camera app.that's supports 1080p video. Thanks in advance!!!
Click to expand...
Click to collapse
Push the sick app via adb. I read somewhere that with apps such as root explorer it doesn't work for some reason. Hope this helps.
Sent from my MB865 using Tapatalk

Yes, always use adb to push system apps. Root Explorer will not work.
Sent from my mAtrix2!!

For some reason i get permission denied whenever i try to push through adb. How do i get around this?

farshad525hou said:
For some reason i get permission denied whenever i try to push through adb. How do i get around this?
Click to expand...
Click to collapse
To copy anything to /system/app, you need root access.
This will be a 2 step process.
1) push the file from your computer to your phone in a directory that the shell has access to, i.e. /data/local for instance.
2) adb shell into the phone and su, remount /system as rw, then cp the file from /data/local/ to /system/bin
That should elimiate the issue with permission denied, with adb push.

jimbridgman said:
To copy anything to /system/app, you need root access, have you rooted the phone?
If you have rooted the phone, this will be a 2 step process.
1) push the file from your computer to your phone in a directory that the shell has access to, i.e. /data/local for instance.
2) adb shell into the phone and su, remount /system as rw, then cp the file from /data/local/ to /system/bin
That should elimiate the issue with permission denied, with adb push.
Click to expand...
Click to collapse
Yes my phone is rooted. How do I remount /system as rw? Then how do i cp the file? Thanks for your help!

I figured out how to push the file with adb, but the app still does not show up. Any other ideas?

farshad525hou said:
Yes my phone is rooted. How do I remount /system as rw? Then how do i cp the file? Thanks for your help!
Click to expand...
Click to collapse
Ok, run EVERYTHING between Code:, and End code from the command line. Just make sure you are in the directory you saved your backup camera.apk to, from your windows command prompt, before you run the commands below.
Code:
adb push BlurCamera.apk /data/local
adb shell
su
mount -o remount, rw /system
cd /data/local
cp BlurCamera.apk /system/app
chown root /system/app/BlurCamera.apk
chgrp root /system/app/BlurCamera.apk
chmod 644 /system/app/BlurCamera.apk
mount -o remount, ro /system
exit
exit
End code
That should hopefully fix it.

jimbridgman said:
Ok, run EVERYTHING between Code:, and End code from the command line. Just make sure you are in the directory you saved your backup camera.apk to, from your windows command prompt, before you run the commands below.
Code:
adb push BlurCamera.apk /data/local
adb shell
su
mount -o remount, rw /system
cd /data/local
cp BlurCamera.apk /system/app
chown root /system/app/BlurCamera.apk
chgrp root /system/app/BlurCamera.apk
chmod 644 /system/app/BlurCamera.apk
mount -o remount, ro /system
exit
exit
End code
That should hopefully fix it.
Click to expand...
Click to collapse
Sadly this didn't work either. I don't know what I'm doing wrong. Btw, thanks for your help so far!

Quick question....is the blurcamera.odex file still in the system/app. If you have deleted it also you will have to replace it as well.

JRW 28 said:
Quick question....is the blurcamera.odex file still in the system/app. If you have deleted it also you will have to replace it as well.
Click to expand...
Click to collapse
I could only find a deodexed system dump

Here ya go, zip has both camera.apk and odex. Try using file explorer again and make sure it is r/w . Hope it helps
http://db.tt/v0FQKpKr

JRW 28 said:
Here ya go, zip has both camera.apk and odex. Try using file explorer again and make sure it is r/w . Hope it helps
http://db.tt/v0FQKpKr
Click to expand...
Click to collapse
Thanks for the files! But once again sadly the file doesn't appear under my app drawer. I tried using adb and root explorer, with no luck. Is there anything I'm missing? Btw, JRW are those files from the atrix 2?

There both straight off of my phone...that's weird cause I have removed both of them trying out various cameras and never had a problem reinstalling them?
Are you rebooting afterwards?

JRW 28 said:
There both straight off of my phone...that's weird cause I have removed both of them trying out various cameras and never had a problem reinstalling them?
Are you rebooting afterwards?
Click to expand...
Click to collapse
Yeah I am. Can you walk me through what you do when you re install the apps? I am really confused. Is there anything that might be interfering?

Go into file explorer and make sure your system folder is r/w along with both the blurcamera.apk and blurcamera.odex.... then drop both of them into system/app and reboot. Wouldn't think anything else would be interfering?

JRW 28 said:
Go into file explorer and make sure your system folder is r/w along with both the blurcamera.apk and blurcamera.odex.... then drop both of them into system/app and reboot. Wouldn't think anything else would be interfering?
Click to expand...
Click to collapse
How do I make sure that BlurCamera.apk and BlurCamera.odex are both r/w?

Im not sure if it really matters on them but long pressing on either of them in file explorer should bring up the permissions and you can change from there. Do the same on your system folder just to double check that the permissions are correct

JRW 28 said:
Im not sure if it really matters on them but long pressing on either of them in file explorer should bring up the permissions and you can change from there. Do the same on your system folder just to double check that the permissions are correct
Click to expand...
Click to collapse
Yeah still no luck... no idea whats wrong

Try pushing them with ADB .....usually that will take care of it

Bionic ROM boot animation sounds?

I have Bionix ROM and I'm trying to add sounds to my bionic boot animation. But there isn't a poweron folder and I tried putting it in the history folder but it still doesn't work. Is there any way to add sounds to the animation?
EDIT: Changed to Bionix ROM and it still hasn't worked. Also tried putting sound file in Notification file and no luck D:
Sent from my Chuck Norris fishbowl

I think it has to do with the kernel, faux kernels don't have boot sound. Dunno about morfic or stock kernels either since I only rock faux ds kernels when released.
Sent from my LG-P999 using xda premium

d12unk13astard said:
I think it has to do with the kernel, faux kernels don't have boot sound. Dunno about morfic or stock kernels either since I only rock faux ds kernels when released.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
What kernels do have boot sound?

testing a method...will post back results ...good or bad

I was able to get sound...tried lots n lots. There is a TON posted here on the subject...found my solution in the HTC forums. Don't have the link handy but search CM7 boot sound. There is a file called bootsnd.sh that will append the necessary files and create the bootsound app needed. To finally get this to work I reflashed a new nightly of CM7. This also removed Trinity kernel...so maybe that was mucking things up. Ill reflash Trinity and see.
But to recap ...yes boot sound on LG g2x with cm7 is a go.
Sent from my LG-P999 using XDA App

OK, I'm going to try cm7. Will posts results to verify.
Sent from my Bionix 2 - A TeamWhiskey Production using xda premium

Taken from somewhere here in xda. (http://forum.xda-developers.com/showthread.php?t=1048231)
I cleared cache and dalvic using CWM.
I flashed a fresh CM7 nightly using CWM.
I Followed terminal emulator instructions...I'm sure adb from command line will work also. I used root explorer to copy android_audio.mp3 (don't forget to set system folder as R/W with root explorer.
1) search for and Download the bootsnd.sh file. Save it to the root directory of your SD Card on your Device.
2. Take whatever sound you want and rename it to: android_audio.mp3 (needs to be mp3 format) and then place in your adb directory.
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 or know how to use adb, using root explorer and placing the android_audio.mp3 in the system/media folder works just as well (Mount the /system as R/W First). 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
Sent from my LG-P999 using XDA App

jhayton said:
(don't forget to set system folder as R/W with root explorer.
(Mount the /system as R/W First). Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
What do you mean by setting the system folder as R/W? It means read/write right? (lol write right)
EDIT: Plus how do I set it to R/W ( Sry im a little of a noob when it comes to things like this, im better at game developing )

thor6577 said:
What do you mean by setting the system folder as R/W? It means read/write right? (lol write right)
EDIT: Plus how do I set it to R/W ( Sry im a little of a noob when it comes to things like this, im better at game developing )
Click to expand...
Click to collapse
Using a utility like Root Explorer (A paid app but worth the 4$, there may be a free alternative), makes this a trivial task...simply click the "Make R/W" will make the system directory ...you guessed it "Read/Writable". Normally its "Read Only" (R/O).
Im not 100% sure about this (im sure ill be corrected) as Root Explorer has made me lazy, but using ADB and issuing the command ADB Remount, will make the file system R/W (per the ADB Wiki adb remount - remounts the /system partition on the device read-write)
So using ADB to push your files, make all your edits on your local machine, then put them in your ADB directory, and issue commands as follows:
ADB remount
ADB push build.prop /system
ADB push init.local.rc /system/etc
ADB push bootsound /system/bin
ADB push android_audio.mp3 /data/local

Grr after I tried it it still doesn't work!!!
EDIT:Im reflashing ROM in case.
EDIT 2 : Yup didn't work.
Sent from my LG-P999 using xda premium

Open terminal emulator and type
Su
Then at the # type bootsound
Do u hear sound? If not something is incorrect
If you do...then its your kernel.
Trinity breaks my bootsound.
Still looking for a fix
Sent from my LG-P999 using XDA App

jhayton said:
Open terminal emulator and type
Su
Then at the # type bootsound
Do u hear sound? If not something is incorrect
If you do...then its your kernel.
Trinity breaks my bootsound.
Still looking for a fix
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Nope didn't hear nothing.
Sent from my LG-P999 using xda premium