[HOWTO] Revert to old touch sounds - Galaxy Tab 2 General

The 4.0.3 ROM had a pleasant click when you touched the screen if you turned it on in sound settings. The 4.0.4 ROM sounds like water drops.
Thanks to: http://forum.xda-developers.com/showpost.php?p=27447853&postcount=1
Get those two files from that post and try this (assume you are rooted):
Code:
adb push TW_Touch.ogg /sdcard/TW_Touch.ogg
adb push S_HW_Touch.ogg /sdcard/S_HW_Touch.ogg
adb shell
su
mount -o remount,rw /system
cd /system/media/audio/ui
cp TW_Touch.ogg TW_Touch.ogg.original
cp S_HW_Touch.ogg S_HW_Touch.ogg.orginal
cp /sdcard/*_Touch.ogg . # really? You have more files named this?
rm /sdcard/*_Touch.ogg # ok then don't do this if you do!
exit
exit
Now turn touch sounds off and back on (or just on if they were already off).

Related

cp: write error: no space left on device in system

I have been having this error message come up using the terminal. I was attempting to add the volume enhancements via Lucid's script on the hybrid JF 1.51 with the HTC apps. I have asked Lucid if he knew how to solve this, but i wanted to see if anyone else might know the solution. I have been searching on here and also on google and yahoo but I have yet to find anything. I even took out my sd card to see if that would help after restarting my phone but nothing. Did i just screw myself?
innerlight said:
I have been having this error message come up using the terminal. I was attempting to add the volume enhancements via Lucid's script on the hybrid JF 1.51 with the HTC apps. I have asked Lucid if he knew how to solve this, but i wanted to see if anyone else might know the solution. I have been searching on here and also on google and yahoo but I have yet to find anything. I even took out my sd card to see if that would help after restarting my phone but nothing. Did i just screw myself?
Click to expand...
Click to collapse
i'm not privvy to lucid's script, but..
remount /system rewrite
do a cp -f to the files you are replacing
remount /system read-only
if you still get no space left, reboot your phone, then try again.
pershoot said:
i'm not privvy to lucid's script, but..
remount /system rewrite
do a cp -f to the files you are replacing
remount /system read-only
if you still get no space left, reboot your phone, then try again.
Click to expand...
Click to collapse
forgive my ignorance but do I type this in terminal as is? Because when I do that it cannot find remount.
I think I found the problem as to why I saw that error. I went from JFs-1.51 US built to the hybrid one that cyanogen did (the JF-1.51 + HTC apps) and I think there maybe something wrong inside there. First wiped and flashed JF's one and then wiped and flashed the cyanogen one and the problem is there.
innerlight said:
forgive my ignorance but do I type this in terminal as is? Because when I do that it cannot find remount.
Click to expand...
Click to collapse
copy the three files needed for the volume increase (2 if your on JF (AudioFilter and AudioPara4)) on to the sdcard in to lets say a directory named 'audio'. make sure you have unmounted the sdcard from within your OS after you have completed the copy, and have unplugged the USB cable.
open up terminal (on your phone)
$ su
# mount -o rw,remount /dev/block/mtdblock3 /system
# cd /sdcard/audio
# mkdir BK
# cp -p /system/etc/Audio* ./BK
# cp -f AudioFilter.csv /system/etc
# cp -f AudioPara4.csv /system/etc
# cp -f AudioPara_TMUS.csv /system/etc
# mount -o ro,remount /dev/block/mtdblock3 /system
# exit
$ exit
bounce your phone.
pershoot said:
copy the three files needed for the volume increase (2 if your on JF (AudioFilter and AudioPara4)) on to the sdcard in to lets say a directory named 'audio'. make sure you have unmounted the sdcard from within your OS after you have completed the copy, and have unplugged the USB cable.
open up terminal (on your phone)
$ su
# mount -o rw,remount /dev/block/mtdblock3 /system
# cd /sdcard/audio
# mkdir BK
# cp -p /system/etc/Audio* ./BK
# cp -f AudioFilter.csv /system/etc
# cp -f AudioPara4.csv /system/etc
# cp -f AudioPara_TMUS.csv /system/etc
# mount -o ro,remount /dev/block/mtdblock3 /system
# exit
$ exit
bounce your phone.
Click to expand...
Click to collapse
Thanks for the reply. I am still getting the same error with the JF-1.51+HTC apps build. I told Cyanogen about it and hopefully he will get it sorted out because his built is faster than the regular JF build. I guess I have to decide if the added HTC apps are worth more than the sound increase.

Is there a way to install a recovery image or root from sd card & android terminal?

Is there a way to install a recovery image or root from sd card & android terminal?
Is there a way to install a recovery image or root from sd card & android terminal?
I can't get adb on mac to recognize my phone.
yes if you are on 2.1 do the
Ok ,I figured this out when I was at work and could not use my company computer.
So we need the download.
DroidXRoot_v2.zip
After you download, use a file manager and extract on the sdcard (not in any folder on the root)
Now put the wifi widget on your home screen
Download terminal emulator from the market
Open the terminal . Now comes the fun part.!
code
type these in and hit enter after each one.
cd /sqlite_stmt_journals
cp /sdcard/exploid ./exploid
chmod 755 exploid
./exploid
Now after typing that last command hurry up and hit the home screen button and turn on wifi. After go back in the terminal and type.
rootshell
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
cp /sdcard/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
rm /system/bin/rootshell
all credit goes to brian from MyDroidWorld for that
2.2 do this ( credit goes to Eousphoros from droidforums)
open up your favorite terminal emulator program
- cd /tmp
- cp /sdcard/rage*.bin /tmp/
- chmod 777 rage*.bin
- ./rage*.bin
- ignore it's output, we are thinking outside of the box here, just wait for it to finish and return a $
- now go to settings -> applications -> manage applications -> running -> terminal and force close that girlie
- relaunch the terminal app and you should be greeted with the friendly # symbol. Toda you now have a root shell
- the rest is pretty much the same.
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
* cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
* chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
b-dub25 said:
2.2 do this ( credit goes to eousphoros from droidforums)
open up your favorite terminal emulator program
- cd /tmp
- cp /sdcard/rage*.bin /tmp/
- chmod 777 rage*.bin
- ./rage*.bin
- ignore it's output, we are thinking outside of the box here, just wait for it to finish and return a $
- now go to settings -> applications -> manage applications -> running -> terminal and force close that girlie
- relaunch the terminal app and you should be greeted with the friendly # symbol. Toda you now have a root shell
- the rest is pretty much the same.
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/superuser.apk /system/app/superuser.apk
- cp /sdcard/su /system/bin/su
* cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
* chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
Click to expand...
Click to collapse
nice. Thank you.
What can i do to root a 2.3.4 with a Mac?

Adding blur alarm to Fission ROM

For those of you that felt in love with the Blur Alarm and looking for a way to add it back. I have figured out the missing files beside the apk that goes in the system\app. This has been tested with sucess for Fission ROM v2.0.1.
Adding Blur alarm
system\app\BlurAlarmClock.apk
framework\blur-res.apk
framework\com.motorola.blur.library.utilities.jar
Hope it help.
nice,
I prefer the blur alarm over the normal one.
but here is my problem, the dock is DeskClock.apk, which is also the Clock and the alarms,
when I replace it with the Dock.apk, then the dock won't start up,
did you try to do that?
I'm getting the following exception, and have no clue on how to fix that Oo
Code:
11-04 00:39:22.031 2063 2063 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.motorola.dlauncher/com.motorola.dlauncher.DLauncher}: java.lang.SecurityException: Neither user 10048 nor current process has android.permission.DEVICE_POWER.
braway said:
nice,
I prefer the blur alarm over the normal one.
but here is my problem, the dock is DeskClock.apk, which is also the Clock and the alarms,
when I replace it with the Dock.apk, then the dock won't start up,
did you try to do that?
I'm getting the following exception, and have no clue on how to fix that Oo
Code:
11-04 00:39:22.031 2063 2063 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.motorola.dlauncher/com.motorola.dlauncher.DLauncher}: java.lang.SecurityException: Neither user 10048 nor current process has android.permission.DEVICE_POWER.
Click to expand...
Click to collapse
What ROM are you using? I renamed the original DeskClock.apk to DeskClock.bak since I don't have a docking station. May be it has something to do with the dlauncher. I also deleted the original launcher2 and replaced it with launcherpro.apk.
Fission 2.0.2
I basically did the same with the DeskClock.apk
but added the Dock.apk from the clean verizon rom (which is basically the "stock" droid2), I guess I'm simply missing something
btw, com.motorola.dlauncher is Dock.apk
I guess something is still missing which would set the missing permission oO
got it to work...
if someone cares:
I had to manually modify the /data/system/packages.xml
it should contain something like this:
Code:
<package name="com.motorola.dlauncher" codePath="/system/app/Dock.apk" flags="1" ts="1288859615000" version="8" userId="10057">
<sigs count="1">
<cert index="1" />
</sigs>
</package>
userId and ts are probably different
change the cert index to 0 !
reboot (right after it, for example with adb reboot)
after reboot, check that your change is still in this file (should be)
put your phone into the docking station, and the blur dock should start
yay
lol, this default blur alarm app is awesome and best I have seen. I was so surprised at what it wanted me to do when I first woke up to it , lol
I am not using fission and I am using Rubix 1.6.
I can only find the bluralarm.apk file and I can't find
framework\blur-res.apk
framework\com.motorola.blur.library.utilities.jar
Do i have to nandroid back to a blurry room to pick these up or are they available somewhere else?
Thanks
rkrasny said:
I am not using fission and I am using Rubix 1.6.
I can only find the bluralarm.apk file and I can't find
framework\blur-res.apk
framework\com.motorola.blur.library.utilities.jar
Do i have to nandroid back to a blurry room to pick these up or are they available somewhere else?
Thanks
Click to expand...
Click to collapse
get the vzw clean rom (or so) from droid2files.com (http://droid2files.com/roms/VZW_2.4.5_Clean_ROM.zip)
everything should be in it...
braway said:
get the vzw clean rom (or so) from droid2files.com (http://droid2files.com/roms/VZW_2.4.5_Clean_ROM.zip)
everything should be in it...
Click to expand...
Click to collapse
Perfect; thanks much.
Question?
How do I add this to my phone and make it work? Do I need to use ADB and move it to the phone or what? I really liked the blur alarm a lot and would like to get that back if I can. Thanks for any help in advance.
You just need a method to transfer the files to the phone to the correct spot
ADB or root explorer can move the files
I will show the adb method below, you can substitute the adb shell, mount, cp (copy), chmod (change permissions), and rm (delete) steps with Root Explorer
ADB
Open a command prompt
cd to the directory where you have the files on your computer
Code:
adb push BlurAlarmClock.apk /sdcard/BlurAlarmClock.apk
adb push blur-res.apk /sdcard/BlurAlarmClock.apk
adb push com.motorola.blur.library.utilities.jar /sdcard/com.motorola.blur.library.utilities.jar
Then adb shell to the phone, mount system as r/w, copy the files to the system
Code:
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/BlurAlarmClock.apk /system/app/BlurAlarmClock.apk
cp /sdcard/blur-res.apk /system/framework/blur-res.apk
cp /sdcard/com.motorola.blur.library.utilities.jar /system/framework/com.motorola.blur.library.utilities.jar
Then set the permissions on these files so they will work
Code:
chmod 644 /system/app/BlurAlarmClock.apk
chmod 644 /system/framework/blur-res.apk
chmod 644 /system/framework/com.motorola.blur.library.utilities.jar
You can then remove the files from the sdcard if you wish
Code:
rm /sdcard/BlurAlarmClock.apk
rm /sdcard/blur-res.apk
rm /sdcard/com.motorola.blur.library.utilities.jar
Now mount the system as read-only again
Code:
sync
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
As for the Blur dock
Use the same steps above to copy the file and move it to the system
Code:
adb push Dock.apk /sdcard/Dock.apk
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/Dock.apk /system/app/Dock.apk
chmod 644 /system/app/Dock.apk
sync
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
rm /sdcard/Dock.apk
Next pull the packages.xml file
Code:
adb pull /data/system/packages.xml
Edit packages.xml as shown in the above post
Then push back
Code:
adb push packages.xml /data/system/packages.xml
When you "install" the blur dock, you might want to remove the standard android dock
Code:
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mv /system/app/DeskClock.apk /system/app/DeskClock.bak
sync
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
Notice I just used mv (rename/move)
This is just in case I want it back later
You may need to reboot the phone when you are finished for this to work.
I never tried without rebooting so I don't know if they will work otherwise.

Change the boot sound w/o re-flash the ROM for G7

1. Prepare a short mp3 and name it android_audio.mp3
2. Put the mp3 under the adb folder
3. Save the following code as !bootaudio.bat (I use this name)
4. Turn your phone into ADB debugging mode
5. run !bootaudio.bat
6. Reboot your phone and have fun!
This should work on almost all G7
Tips: During the boot animation, the volume would change twice. So I suggest insert 1 second before the audio for escaping from the volume changing side-effect.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb shell rm /data/local/android_audio.mp3
adb push android_audio.mp3 /data/local/
adb shell rm /system/customize/resource/android_audio.mp3
adb shell ln -s /data/local/android_audio.mp3 /system/customize/resource/android_audio.mp3
adb shell ls -l --color=never /data/local
adb shell ls -l --color=never /system/customize/resource/
adb pull /system/customize/CID/default.xml
pause
Script description:
Mount the system path to enable writing access.
Remove the original boot sound if it exists.
Push your mp3 into the data/local, where the bootanimation.zip is.
Make a link to data/local/android_audio.mp3
List the two affected pathes for you to confirm the result
Pull the default.xml out from the phone, if you find it not work after reboot, you can check the xml to see what the actural fullpath it is using. And manually change the script to try again.
My current boot sound is attached to the thread.
Hi there, I have an error when trying to link beacause the folder does not exist... may I create it manually?!

Can't Install OPPO ADB drivers, here's the solution

1. Install SDK tools http://forum.xda-developers.com/showthread.php?t=2199526
2. Connect oppo find 5
3. Install driver oppo via disc option "Android Composite ADB Interface", http://www.oppo.com/index.php?q=software/view&sw_id=631 (32/64bits)
4. open adb_usb.ini lacated at "C:\Users\<your username>\.android\adb_usb.ini" with notepad (if doesn't exist create one)
5. copy & paste/replace
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x22D9
For test, conect your phone with adb eneable and type into console:
adb devices
For fastboot usage:
fastboot -i 0x22D9 <command>
ex.
fastboot -i 0x22D9 reboot
eliaspizarro said:
1. Install SDK tools
....
Click to expand...
Click to collapse
Thanks, for the step 1 you should link to http://forum.xda-developers.com/showthread.php?t=2199526
eliaspizarro said:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x22D9
Click to expand...
Click to collapse
0x22D9 is for any Oppo type or just for Oppo Find 5?
Regards
OldClass said:
0x22D9 is for any Oppo type or just for Oppo Find 5?
Regards
Click to expand...
Click to collapse
i don't know if works on other oppo devices, but surely works on oppo find 5, how you can find device ID?
You need to search into device propierties -> Device managment -> select oppo device (or any android device), right click (properties)-> details-> id hardware:
a list appear, look for a number like 22D9, then replace into tutorial, 0x<number>.
ok my bro
but i want ask about push deodex using adb.
can you tell me how to push deodex using adb?
regards
OldClass said:
ok my bro
but i want ask about push deodex using adb.
can you tell me how to push deodex using adb?
regards
Click to expand...
Click to collapse
I haven't tried yet, but maybe:
0) get root AKA SuperSu or ChainfireSu
1) If you are on Oppo Frimware install adb insecure
then open the app and start service.
2) finally conect your phone and:
adb push <file.jar/apk> /system/bin (or wherever)
Note: if you are on CM10.1 skip step 0) and 1).
Universal Deodexer
eliaspizarro said:
I haven't tried yet, but maybe:
0) get root AKA SuperSu or ChainfireSu
1) If you are on Oppo Frimware install adb insecure
then open the app and start service.
2) finally conect your phone and:
adb push <file.jar/apk> /system/bin (or wherever)
Note: if you are on CM10.1 skip step 0) and 1).
Universal Deodexer
Click to expand...
Click to collapse
thanks for your tutorial
i'll try to push deodex (1 file) to /system/app but i got "no left space device", how to repair it?
should i delete some apps? how to delete it?
regards
OldClass said:
thanks for your tutorial
i'll try to push deodex (1 file) to /system/app but i got "no left space device", how to repair it?
should i delete some apps? how to delete it?
regards
Click to expand...
Click to collapse
from windows console CMD / linux terminal console
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
then, you can push
eliaspizarro said:
from windows console CMD / linux terminal console
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
then, you can push
Click to expand...
Click to collapse
ok, thanks
this is right?
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
chmod 644 /system/app/*
chown root.root /system/app/*
chmod 644 /system/framework/*
chown root.root /system/framework/*
exit
Regards
OldClass said:
ok, thanks
this is right?
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
chmod 644 /system/app/*
chown root.root /system/app/*
chmod 644 /system/framework/*
chown root.root /system/framework/*
exit
Regards
Click to expand...
Click to collapse
it's ok, another method is fix permissions through cwm
eliaspizarro said:
it's ok, another method is fix permissions through cwm
Click to expand...
Click to collapse
Thanks a lot for your help...
Sent from my Find 5 using xda premium
I can't get my ADB to work. I followed the steps and got it to saying: Android Composite ADB Interface in the device manager.
But when I cmd: adb devices it just says: List of Devices attached
then nothing..
I have my phone on USB debugging
Please Help?!
NVM Got it to work!
needed to reset the server
adb kill-server
then
adb start-server
Oppo find 5 no system
Hello guys I just reformatting my SDCARD before installing the ROM and am now no operating system installed on my computer ADB fastboot, PdaNet. After I install everything with the command window open and used the ADB PUSH command to copy my ROM to SDCARD, but it comes at a time that is a mistake and does not finish copying. Can someone help me?
After go to fastboot seems i need install some drivers to send commands to device, any help? What drivers i need to fastboot work?

Categories

Resources