Database Users

[Tutorial] Remove Default Bootanimations

If you want to remove the carrier branded boot and shutdown animations or the default Samsung animations that you see upon startup and shutdown, you can enter these commands via adb shell or in a terminal emulator on your Galaxy Tab. This code renames the files so that they are no longer accessed when the device is started while keeping them from auto-replicating. Deleting or moving the files with root explorer will not work because the files will be replaced almost immediately. You have to be rooted in order to gain the superuser privileges needed to edit the files in /system.
If you aren't already rooted, you can use z4root or superoneclick.
After that, if you choose, you can enter the commands through adb shell or through a terminal emulator available through the market. If you are not familiar with adb, you can get information on it here: basic adb/shell info
If you don't want to be tethered to the computer, you can take the terminal emulator route. I used "Android Terminal Emulator" by Jack Palevich. It is free on the market, but I'm sure that any of the other ones will work just as well.
If you have a Sprint Galaxy Tab and want to remove the Sprint animations/sounds at startup and shutdown, enter the following commands. Be careful, because you are editing /system files.
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
mv /system/media/bootani.qmg /system/media/_bootani.qmg
mv /system/media/video/shutdown/shutdown.qmg /system/media/video/shutdown/_shutdown.qmg
mv /system/media/audio/ui/PowerOff.wav /system/media/audio/ui/_PowerOff.wav
mv /system/etc/PowerOn.snd /system/etc/_PowerOn.snd
mount -o remount,ro /dev/mtdblock3 /system
exit
For those of you with tabs other than the Sprint Tab, you may have to add the line:
Code:
mv /system/etc/PowerOn.wav /system/etc/_PowerOn.wav
This line goes after the command to move "PowerOn.snd"
These commands will leave the standard Samsung bootanimation. If you want to get rid of all bootanimations completely you can enter the following code:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
mv /system/media/bootani.qmg /system/media/_bootani.qmg
mv /system/media/samsungani.qmg /system/media/_samsungani.qmg
mv /system/media/video/shutdown/shutdown.qmg /system/media/video/shutdown/_shutdown.qmg
mv /system/media/audio/ui/PowerOff.wav /system/media/audio/ui/_PowerOff.wav
mv /system/etc/PowerOn.snd /system/etc/_PowerOn.snd
mount -o remount,ro /dev/mtdblock3 /system
exit
Now open your terminal or adb shell again.
Now enter:
Code:
su
cd /data/local
chmod 777 nobootani.sh
./nobootani.sh
exit
Now restart your tab. You will see that the shutdown animation is gone. When the tab restarts, the carrier/default animations are gone.

thanks
thanks a lot rkmj - I can confirm that this is working on my Sprint CDMA Galaxy Tab. The animations has been removed.
I just got it a couple of days back and I am in the process of removing all the junk from samsung and sprint without flashing a custom ROM cuz seriously there isnt any worth taking the risk.
I have cleaned almost all of them and with this fix my TAB just feels like totally unbranded now.
Next step is to make it faster without a custom ROM, ideas are welcome or maybe a safe list of services I can disable without breaking my tab.

Nice, thanks man
Sent from my GT-P1000 using XDA App

The at&t startup logo and sound is gone with overcome rom, but the t-mobile startup logo is still there.
So what will remove the t-mobile start screen?

I'm pretty sure this will remove the T-Mobile startup. Most of the carrier-branded startup routines are in the same locations. If this doesn't work though, you might check /system/media for a file called "bootanimation.zip" If that fails to produce, check /data/local for the same file. If you have that "bootanimstion.zip" file, you can either swap that bootabimation file for a custom one or get rid of it altogether.
Sent from my Samsung Galaxy Tab

rkmj said:
I'm pretty sure this will remove the T-Mobile startup. Most of the carrier-branded startup routines are in the same locations. If this doesn't work though, you might check /system/media for a file called "bootanimation.zip" If that fails to produce, check /data/local for the same file. If you have that "bootanimstion.zip" file, you can either swap that bootabimation file for a custom one or get rid of it altogether.
Sent from my Samsung Galaxy Tab
Click to expand...
Click to collapse
I have a tmobile galaxy tab, and the bootanimation.zip is just the startup movie that plays. Mine has been replaced with anouther. The white tmobile screen bugs the heck out of me, is not part of my custom boot animation but still shows. So does the samsung galaxy tab black screen.
Can I get rid of these two screens?
Sent from my GT-P1000 using XDA Premium App

There's an app called BAC or Boot Animation Changer that works with my rooted Moto Droid but not with my rooted Sprint Galaxy Tab. Would you have any idea whether after removing the boot animation if it will work? TIA
I'll test and see what results I get; just thought it might be good to have an informed opinion first. And many thanks for the post.

Thanks for this; just wanted to get rid of my carrier branding (Telstra) on my Galaxy Tab. I'm rather happy with the Samsung animation and even the on/off sounds.

good work
works beaut on Telstra 8.9.. give or take file names changes of course but the result is spot on...out with Tesltra crap...

rkmj said:
I
Now restart your tab. You will see that the shutdown animation is gone. When the tab restarts, the carrier/default animations are gone.
Click to expand...
Click to collapse
is that work other devices ? mean note 4 etc? and another cariror like sprint verizon etc?

Build.prop Edits (Stock ROM)

I wanted to start an official thread on performing build.prop edits on KFHD since no one has of yet. I have tinkered for several hours yesterday trying to get one that allows Google Play apps to install that show "unsupported device". I have had zero luck unfortunately, and am hoping some others want to take up the challenge and find a solution.
I suggest you get busybox before attempting this, it makes copying files easier. Get it in the GooglePlay store:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Make sure you back up your file first!!! I did these steps:
Code:
# adb shell
# su
# mount -o remount,rw /system
# cp /system/build.prop /system/build.prop.orig (cp comes with busybox see link above)
# cp /system/build.prop /sdcard/build.prop.orig
# exit
NOTE: If you didn't install busybox, then you can do the cp commands as below:
Code:
# cat /system/build.prop.orig > /system/build.prop
Word of caution, I have managed to get my Kindle into a boot loop several times through this, but fortunately have been able to recover (details below). I cannot guarantee that you won't damage your Kindle in the process, and prevent it from booting.
I am also attaching a copy of the stock build.prop in case you manage to damage yours. I can't guarantee you will be able to put it back if you get in a boot loop, but you should be able to at minimum "vi" the existing one and manually enter everything to fix you up.
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.

nvrmore100 said:
I wanted to start an official thread on performing build.prop edits on KFHD since no one has of yet. I have tinkered for several hours yesterday trying to get one that allows Google Play apps to install that show "unsupported device". I have had zero luck unfortunately, and am hoping some others want to take up the challenge and find a solution.
I suggest you get busybox before attempting this, it makes copying files easier. Get it in the GooglePlay store:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Make sure you back up your file first!!! I did these steps:
Code:
# adb shell
# su
# mount -o remount,rw /system
# cp /system/build.prop /system/build.prop.orig (cp comes with busybox see link above)
# cp /system/build.prop /sdcard/build.prop.orig
# exit
NOTE: If you didn't install busybox, then you can do the cp commands as below:
Code:
# cat /system/build.prop.orig > /system/build.prop
Word of caution, I have managed to get my Kindle into a boot loop several times through this, but fortunately have been able to recover (details below). I cannot guarantee that you won't damage your Kindle in the process, and prevent it from booting.
I am also attaching a copy of the stock build.prop in case you manage to damage yours. I can't guarantee you will be able to put it back if you get in a boot loop, but you should be able to at minimum "vi" the existing one and manually enter everything to fix you up.
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.
Click to expand...
Click to collapse
Do you means that if we get stuck in the boot loop, we can try the third code to recovery?

It should let you get back to the device if you are in a loop like you would experience with the build.prop edit. Meaning you can still use adb shell to access the system even though its not entirely booted up, and you can't use SU.

No one willing to try more build.prop edits? I spent another few hours at this, I'm still no farther. I am able to trick play.google.com into thinking I have a different system (Nexus S in this case) but the play store on the kindle doesn't allow me to install several apps. If I tell it to download via the web site, it does not push them down to my device. Also, if I try to do a combination of website / play store app at various stages of the process, I can get all the way to install portion and then it tells me its not compatible...

Does anyone ever try to change DPI to 160 or lower?
Sent from my KFHD rooted

Yes, with a lower dpi, the normal android lock screen returns, however, the keyboard gets seventy messed up and becomes unusable. This was at 130 dpi.
Sent from my KFTT using XDA Premium HD app

Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app

madddoggj said:
Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
use market unlocker.its ok.

madddoggj said:
Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Yes, when Google says no, I go look for the apk and download it anyways. So far nothing has crashed. But I try to stick with things for ICS.

I messed with the ro.product.board entry... and now when reboot it got stuck at "Kindle is Upgrading... Starting application..."
Tried adb but device not attacked.
Is there a way to boot it up again?

dexd, http://forum.xda-developers.com/showthread.php?t=1930656

nvrmore100 said:
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.
Click to expand...
Click to collapse
Worked like a charm on 7.2.1 jcase and sparkym3 are brilliant. I have no idea how this code works or what makes sense about it, but it's fantastic. Also, since this code lets you copy files without root, could this be another method for rooting my device?

Yuretz said:
dexd, http://forum.xda-developers.com/showthread.php?t=1930656
Click to expand...
Click to collapse
I followed the guide and got myself this factory cable and I can boot it up again

My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother

Thank you for your post, this thread may be quite useful for who has had a bricked device.

Yuretz said:
My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother
Click to expand...
Click to collapse
I don't know what the other two things mean, but the "No need to block accelerometer in games" is something I need! Are you sing a Kindle Fire HD 7"? If so, I'm definitely doing this!

macravin said:
I don't know what the other two things mean, but the "No need to block accelerometer in games" is something I need! Are you sing a Kindle Fire HD 7"? If so, I'm definitely doing this!
Click to expand...
Click to collapse
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support

Yuretz said:
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support
Click to expand...
Click to collapse
So you can download apps from marked which are marked as "incompatible device" with stock build.prop ? Thank you for your answer! :fingers-crossed:

Yuretz said:
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support
Click to expand...
Click to collapse
I did this, but the dpi made my keyboard unuseable (the keyboard doesn't fit on screen idk why it became big when everything else became small)... does anyone know of a fix for this? That would be really great!

Does this work on Kindle Fire HD 8.9?
Yuretz said:
My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother
Click to expand...
Click to collapse
Ok I am very excited.I saw this possible solution to my problem, as I would like to download NBA Jam for android (that I modded with Jordan in it that I have working on my rooted Kindle Fire with CM10 linaro on it, but what I wonder is if this will work for a rooted Kindle Fire HD 8.9 as well as a Kindle Fire HD 7? Thank you in advance.

[Q] is replacing fonts on the nook dangerous?

I have replaced some fonts on the nook and everytime at some point, i get issue with it.. it does not boot anymore... and every time i need to do a factory reset, re-root. Is there steps/precautions i need to be aware when replacing fonts on the nook or adding apps in system/app??
I have an htc desire rooted and i have never had issues like that on it; i have replaced fonts, edited files like build.prop or key mapping, added/deleted/renamed apps in system/app and i never had a single issue... maybe the nook is different i don't know

To answer your question, no, it's not dangerous.
Linux doesn't care at all about fonts.
So if you have a problem with fonts, use ADB and logcat and actually figure out what the problem is.
Even with flashing dots, ADB and logcat (and dmesg) work.

Renate NST said:
To answer your question, no, it's not dangerous.
Linux doesn't care at all about fonts.
So if you have a problem with fonts, use ADB and logcat and actually figure out what the problem is.
Even with flashing dots, ADB and logcat (and dmesg) work.
Click to expand...
Click to collapse
adb does not detect the nook while it is booting... it only detects when it's booted or when i use cwm

Well, apparently you are bashing some non-font thing.
How are you copying over the font?
Are you using some wonderful "Insta-Mega-File-Masher-Omatic"?
Which font are you replacing?
Stick to basics.
Get your Nook working with 1.2.1 since that is where you should be.
Get ADB working.
Remount /system r/w, adb reboot, still working? Yup.
Remount /system r/w, adb push your font to /system/fonts/temp.ttf, adb reboot, still working? Yup.
Remount /system r/w, then:
Code:
stop
mv whatever.ttf old.ttf
mv temp.ttf whatever.ttf
reboot

Renate NST said:
Well, apparently you are bashing some non-font thing.
How are you copying over the font?
Are you using some wonderful "Insta-Mega-File-Masher-Omatic"?
Which font are you replacing?
Stick to basics.
Get your Nook working with 1.2.1 since that is where you should be.
Get ADB working.
Remount /system r/w, adb reboot, still working? Yup.
Remount /system r/w, adb push your font to /system/fonts/temp.ttf, adb reboot, still working? Yup.
Remount /system r/w, then:
Code:
stop
mv whatever.ttf old.ttf
mv temp.ttf whatever.ttf
reboot
Click to expand...
Click to collapse
I am replacing Caecilia, HelveticaNeue and Trebuchet.... i using adb push to replace the fonts .. i use these commands
adb shell
#su
#mount -o rw,remount /dev/block/mmcblk0p5 /system
adb push myfont.tff /system/fonts
adb reboot
sometimes, every fonts is replaced properly... and everything is alright.. sometimes, replacing the 3rd font and i reboot .. i gets locked.. sometimes it's the 2nd font, it's random.. or sometimes i push an app to system/app.. everything is alright... then i push the same app, it does not boot.. it's all random
how do you activate adb while booting... adb does not detect my nook while booting...

A comment; I have done some playing around with fonts over a year ago and if I recall correctly, the system needs fonts files with names Caecilia, HelveticaNeue and Trebuchet. You can rename other font files to have those names, but those names must exist.
Next, a question; Is it possible that the font files you are attempting to use are so big that they are filling up the file system?

Filling up the partition was one thing I thought of, but since /system is normally ro that didn't seem like it could affect anything.
Do a df and see what space you have left.
How big are the files?
If you are trying to make this do Chinese, just replace one file.
Linux doesn't use fonts.
Android only uses the Droid fonts.
Opera Mobile will use DroidSansFallback.ttf
ReaderRMSDK.apk uses the rest of the fonts.

[Q] How do I delete system apks?

I can't figure out how to delete some of the system apks off my rooted Nook Simpletouch. Running 1.2.1, and Nootered it. Tried to ADB uninistall Phone.apk, but it just reports failure. I could use some help.

/system is usually read-only.
To make changes in its content you need to remount it read/write:
Code:
stop
mount -o rw,remount /dev/block/mmcblk0p5 /system
The stop is to be on the safe side, it stops the android subsystem.
After you are done making changes it's best to:
Code:
reboot

Renate NST said:
/system is usually read-only.
To make changes in its content you need to remount it read/write:
Code:
stop
mount -o rw,remount /dev/block/mmcblk0p5 /system
The stop is to be on the safe side, it stops the android subsystem.
After you are done making changes it's best to:
Code:
reboot
Click to expand...
Click to collapse
Just rename them. add ",bak:" to the end or similar. This will disable them, and if you notice instabilities because of getting rid of them you can just remove the appended extension. If everything runs well, you can then delete them with no worries.
I've renamed some of the recommended ones and have an error that comes up. "A problem has occurred, contact support". I need to figure out what is causing that to happen. its annoying but doesn't seem to be an actual problem.

What does "mmcblk0p5" represent?

mmcblk = multimedia card block device, 0 = first device, p5 = fifth partition

Thanks Renate, but It's not working. In order to rename or delete an apk off my Nook simpletouch, would someone please give me step instructions? I feel I'm missing something.

Code:
stop
mount -o rw,remount /dev/block/mmcblk0p5 /system
cd /system/app
mv BoringApp.apk BoringApp.bak
mv TediousApp.apk TediousApp.bak
reboot
And don't tell me that you have no boring or tedious apps!

The advice here is correct, better to rename sysapp extensions (.bak or .ap_) than delete as some might be needed by future apps/sys hacks/kernels. For those who can't adb by cable or keep it up wifi-wise, this is the easiest way even easier than root explorer:
https://play.google.com/store/apps/details?id=com.ghisler.android.TotalCommander
for sys or user app removal if you have to and can't use adb or even total commander, but then you shouldn't if not knowing sys file structures (I use Pro version, for removing many apps i just tested in a batch, sorted reminder):
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I renamed talk telephone music audio etc apks on nst but Gallery is the only one I removed on all android devices & nst as it's just nasty which has never been missed by later hacks and quickpic is much better anyway:
https://play.google.com/store/apps/details?id=com.alensw.PicFolder

I created another directory under /system called archive. I move apps I don't what to use and fonts I change into /system/archive then I can just move them back if I have issues.

This still isn't working. My commands keep getting rejected. It isnt allowing stop to work. Also, I tried "adb cd /system/apps" and when that didn't work, I tried
"adb shell"
"#cd /system/apps"
No dice.
EDIT: Got it. needed to call it shell instead of adb. I also accidentally wrote "apps" instead of "app".

Edit build.prop on rooted Moto X Pure MM

Am trying to set up a new property in build.prop but am running into issues with not being able to save the edit properties.
Some things we tried:
mount -o remount,rw /system (BTW we never took it out of this state)
Somehow, during our various futzing, ADB no longer work (we are using Minimal ADB and Fastboot), but was working previously. Fastboot works fine.
Was going to try this in shell, with the following
adb shell mount /system
adb shell
echo "net.tethering.noprovisioning=true" >> /system/build.prop
but without being able to do adb, that won't work...
We did make a copy of the build.prop and moved it to the sdcard, but if I wanted to get it back to /system with the modifications, what do I need to do?
BTW, I remember when I first set this up before current security update (which wiped the prior changes), there was something about the system apps being the issue and we had to remove YouTube. I don't remember how we did that.