Related
Hi,
I have rooted my Hero with the tutorial on villainroms page but when I try to delete the bootanimation.zip with astro file manager it doesn't work.
zulu1 said:
Hi,
I have rooted my Hero with the tutorial on villainroms page but when I try to delete the bootanimation.zip with astro file manager it doesn't work.
Click to expand...
Click to collapse
Did you remount the system partition as RW first? The app should let you do this
I have just done what was said in the tutorial so I don't think that I have done what you say and actually I don't quite know what that is.
I made myself a bootscreen and I tried to use that but it didn't work so I downloaded a bootscreen available on the web but that didn't work either.
The bootscreen I have at the moment is from here called drawing-froyo maybe it has to do something with that.
Nah, nothing to do with which one you have.
You need to find out how to remount system in astro (google maybe) and do that.
It will then be easy to overwrite
You could use adb, or downloader a popular root explorer for your pc to browse your phone
MacaronyMax said:
You could use adb, or downloader a popular root explorer for your pc to browse your phone
Click to expand...
Click to collapse
Could you provide the adb command to remount with the proper permissions?
Command prompt:
C:\ ..\> adb devices <-- this will detect your phone connect to pc
C:\ ..\> adb remount <-- remount the phone
C:\ ..\> adb shell <-- command to enter shell command, the drive letter C change to # meaning u have enter shell mode
# su <-- superuser permission
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system <-- changing permission of read/rewrite
# cd /system/media/bootscreen/ <-- change directory to /system/media/bootscreen/
# ls -l <-- list of apps/files in current directory, this is not important, just to ensure the file u seek is there..
# rm any_files_u_wanna_delete <-- remove aka delete command(make sure u already backup or pulled it before doing this)
# exit <-- exit shell command, type it again until the # change back to "C:\>"
C:\ ..\> adb push C:\any_files_u_wanna_push /system/media/bootscreen/ <-- push ur files, with directory of the file to push then directory of where the files should be pushed in
C:\ ..\> adb reboot <-- reboot command, reboots the phone, unplug it and see it runs.. if the bootanimation didn't play/just stalled, try redoing all these steps with the old bootanimation, or do a nandroid restore.
as far as I know, bootanimation in /system/media/bootanimation/ folder is not in zip files, it's in multiple files(in my stock 2.1, it's boot.gif, boot.mp3, boot2.gif, boot_animation.xml and boot_bg.gif). so I bet, u have to extract these files from the zip and push it one by one.
Good luck on adb
I created script to change framework-res.apk
--New-- Script with safer operation uploaded.
Requirements
-rooted
-busybox installed
1-copy framework-res.apk that you want to replace to the root of your sdcard (make sure it's in root)
2-extract reframe.zip(attachment) to root of your sdcard
in adb shell, use this command:
Code:
su
cd /sdcard
sh reframe.sh
your phone will reboot. and done! your framework-res.apk replaced safely.
Original framework-res.apk backed up as framework-res.apk.orig in /sdcard
Is there any method to get back original framework from SDCard, and paste it to /system, when my phone doesn't want to boot?
hugerth said:
Is there any method to get back original framework from SDCard, and paste it to /system, when my phone doesn't want to boot?
Click to expand...
Click to collapse
Use xrecovery..
Sent from my E15i using XDA App
Can't install... ok... I reflash 1.6 and root it again, install 2.1 and xRecovery for the future...
hugerth said:
Can't install... ok... I reflash 1.6 and root it again, install 2.1 and xRecovery for the future...
Click to expand...
Click to collapse
ops.if you have working rootshell, you can replace it using rootshell. but, since you've go back to 1.6, it doesn't matter. just install xrecovery in the future, quite useful.
Now I have system back (after about 2h) with working xRecovery and... God!.. why I haven't noticed it before...
i wanna ask how to recover the framework-res.apk from the xrecovery??
mount /system and use adb push
edit: new script. revised operation
D:\adb>adb remount
remount failed: Operation not permitted
any help here? I need to replace the framework
nm, forgot to chmod 06777 /system/framework
Thank you for you work. I hope to see this work Just rebooted my phone after applying your script.
propc said:
I created script to change framework-res.apk
--New-- Script with safer operation uploaded.
Requirements
-rooted
-busybox installed
1-copy framework-res.apk that you want to replace to the root of your sdcard (make sure it's in root)
2-extract reframe.zip(attachment) to root of your sdcard
in adb shell, use this command:
Code:
su
cd /sdcard
sh reframe.sh
your phone will reboot. and done! your framework-res.apk replaced safely.
Original framework-res.apk backed up as framework-res.apk.orig in /sdcard
Click to expand...
Click to collapse
Can u tell me where to find the adb shell
Sent from my E15i using XDA App
Use Super One Click, it comes with adb. Copy cmd.exe to SOC folder. Now start cmd, now type 'adb shell' (click enter) and then the other commands.
Sent from my E15i using Tapatalk
you can always change a framework by installer from available theme
mzmz83 said:
Use Super One Click, it comes with adb. Copy cmd.exe to SOC folder. Now start cmd, now type 'adb shell' (click enter) and then the other commands.
Sent from my E15i using Tapatalk
Click to expand...
Click to collapse
This is what I see when I open superoneclick t shows Root, shell Root, Unroot, allow non market apps....
Now in superoneclick folder that it comes in when u open it this is what u see
Superuser.apk
Superoneclick
Su
Sqlite3
Regeagainsttecage
Bushels
Addbwinusbapi
Adbwinapi
Ashland
Adblinux
Adb. Application
But when I try to open adb app it does not open a screen comes up then it closes so there is where am stuck at:-( :-( can u help me out from there??????
Sent from my E15i using XDA App
adb won't stay open if you click it, it will just flash out on the screen.
it was supposed to be somekind of a "bridge" for the cmd and the phone...
correct me if i'm wrong please...
You have to copy cmd.exe to the SuperOneClick folder, then you have to open the cmd.exe, not the superonecklick.exe.
I'm trying to replace framework and when I type in shell I got:
cd /sdcard
#
sh reframe.sh
sh: Can't open reframe.sh
#
oubsty, Thanks you
Boshe said:
I'm trying to replace framework and when I type in shell I got:
cd /sdcard
#
sh reframe.sh
sh: Can't open reframe.sh
#
Click to expand...
Click to collapse
I think it works if your phone is charged by your laptop/computer only. You do not allow it to connect. I mean you can not reach SDCard through Total Commander, etc. only charging.
Help
# sh reframe.sh
sh reframe.sh
sh: Cannot open reframe.sh
#
any ideas
got SuperOneClick 1.5.5 ( busybox )
root explorer ( only thing in superuser )
SE's PC companion running in background [ keeps asking for mount, but is ignored ]
got Android full SDK installed - drivers, ADB, 'the works'
root'd succesfully -(( WORLD-1-8_2.0.1.A.0.47 )) White-DarkBlue / Pink
4Gb Kingston HC4 sdc4/4gb 18 - un partitioned.
I wish to remove some bloat, and change to a custom theme.
{EDIT} - how to access recovery mode?, got customization = home-back-back-home-back-home-home-back
Dalvik Debug Monitor won't run, adb error2
thanks in advance.
This requires root and ADB knowledge. The method will work for any boot animation, reference Xoom forums for additional resources.
I'm not responsible if you brick your Galaxy Tab 10.1!!!!! This has only been tested on a USA White 16GB Galaxy Tab 10.1
ADB METHOD:
Code:
Download bootanimation.zip from the bottom of the post, and copy it to your directory where adb.exe is located. The included boot animation is a stock honeycomb from the Xoom animation.
adb push bootanimation.zip /sdcard/bootanimation.zip
Next, get into ADB shell and mount system as writeable:
adb shell
mount -o remount,rw /dev/block/mmcblk0p4
Here is where it gets funny, in order to make the bootanimation.zip play correctly you will need to rename the program which calls the default animation to "playsoundBACKUP" and then copy/rename bootanimation to playsound. MAKE SURE YOU BACKUP JUST AS I TELL YOU TO:
cd /system/bin
mv playsound playsoundBACKUP
cp bootanimation playsound
Okay, now all that is left is to copy the bootanimation.zip to the proper directory:
mv /sdcard/bootanimation.zip /system/media/bootanimation.zip
ROOT EXPLORER METHOD, thanks Berner:
Code:
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
TO REVERT:
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk0p4
cd /system/bin
rm playsound
mv playsoundBACKUP playsound
cd ../media
rm bootanimation.zip
Go ahead and reboot your tablet, and enjoy the boot animation. There are literally hundreds of animations available, and if you search through the Xoom forum you can download whichever.
Edit: Attached are the two files which are being manipulated, for those who accidentally delete playsoundBAK and want to revert. Note, "playsound" is the actual modified file where playsoundBAK is the original stock file.
Also too, the following animation is unbelievably awesome:
http://youtu.be/TxQ1DZHi1OA
download here : http://www.mediafire.com/?6aen7nlgelzgu6j
thanks for this ... fun to play with ...any link/intro to the animation file (video) format ? just curious if ican make one of my own ..
Sent from my SHW-M110S using XDA App
Instructions work fine. ADB not required -- everything can be done with Root Explorer. Thanks for the post.
Thanks for this, mang I've been dying to mod my boot screen!
it says failed cross device link...
actually i got it but i accidently delete the playsound can you hook me up with yours?
its weird, i still get the samsung bootloader........sits for a good minute then for like 5 seconds the stock honeycomb comes up and plays then lockscreen shows up. should the samsung screen be up that long if at all?
Riztnack said:
its weird, i still get the samsung bootloader........sits for a good minute then for like 5 seconds the stock honeycomb comes up and plays then lockscreen shows up. should the samsung screen be up that long if at all?
Click to expand...
Click to collapse
Please run these commands and post the file as an attachment in your reply:
Open up windows command prompt, navigate to the directory which contains adb.exe,
adb shell
cd /
echo system.media >> /sdcard/LOG/BootAnimation.txt
ls /system/media > /sdcard/LOG/BootAnimation.txt
echo system.bin > /sdcard/LOG/BootAnimation.txt
ls /system/bin > /sdcard/LOG/BootAnimation.txt
G1_enthusiast said:
it says failed cross device link...
Click to expand...
Click to collapse
Where does it say this? Please post some type of screen shot and method to reproduce. What operating system are you using, what folder are you located in when you're executing adb.exe, what Galaxy Tab are you using?
G1_enthusiast said:
actually i got it but i accidently delete the playsound can you hook me up with yours?
Click to expand...
Click to collapse
I've attached it to the OP, both playsoundBAK (original file, which executes stock boot animation) and playsound (modified file). Please be careful in the future to make a backup
anyway to get rid of the samsung begining? it still show up but after that it show your custom booot animation
Berner said:
Instructions work fine. ADB not required -- everything can be done with Root Explorer. Thanks for the post.
Click to expand...
Click to collapse
Hey man, if i'm doing this with root explorer what do i do with the playsoundBACKUP file in the /system/bin folder? His adb commands arent very clear if using root explorer. Also what do i do with the copied bootanimation playsound? Any help would be greatly appreciated.
wesbalmer said:
Please run these commands and post the file as an attachment in your reply:
Open up windows command prompt, navigate to the directory which contains adb.exe,
adb shell
cd /
echo system.media >> /sdcard/LOG/BootAnimation.txt
ls /system/media > /sdcard/LOG/BootAnimation.txt
echo system.bin > /sdcard/LOG/BootAnimation.txt
ls /system/bin > /sdcard/LOG/BootAnimation.txt
Where does it say this? Please post some type of screen shot and method to reproduce. What operating system are you using, what folder are you located in when you're executing adb.exe, what Galaxy Tab are you using?
I've attached it to the OP, both playsoundBAK (original file, which executes stock boot animation) and playsound (modified file). Please be careful in the future to make a backup
Click to expand...
Click to collapse
http://img.photobucket.com/albums/v643/Riztnack/1.jpg
I am using windows 7
jman391 said:
Hey man, if i'm doing this with root explorer what do i do with the playsoundBACKUP file in the /system/bin folder? His adb commands arent very clear if using root explorer. Also what do i do with the copied bootanimation playsound? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Keep the playsoundBACKUP in /system/bin so you can revert if you want. The copied (and renamed) bootanimation playsound also stays in /system/bin.
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
G1_enthusiast said:
anyway to get rid of the samsung begining? it still show up but after that it show your custom booot animation
Click to expand...
Click to collapse
What do you mean? The initial Samsung Logo
Berner said:
Keep the playsoundBACKUP in /system/bin so you can revert if you want. The copied (and renamed) bootanimation playsound also stays in /system/bin.
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
Click to expand...
Click to collapse
Thanks bro, I've never used Root Explorer. I'll add this to the OP.
Riztnack said:
http://img.photobucket.com/albums/v643/Riztnack/1.jpg
I am using windows 7
Click to expand...
Click to collapse
Very strange. I've never seen that error on any of the 30+ Android devices I've rooted.
Please confirm, are you on a 10.1 or 10.1v (as I really don't know the differences yet).
Please try the following:
adb shell mount -o remount,rw /dev/block/mmcblk0p4
adb push bootanimation.zip /system/media/bootanimation.zip
Berner said:
Keep the playsoundBACKUP in /system/bin so you can revert if you want. The copied (and renamed) bootanimation playsound also stays in /system/bin.
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
Click to expand...
Click to collapse
Very cool man! Thanks for putting it in laymen's terms for dummies like me.
I don't know what I'm doing wrong but I can't get it o work. I've changed the files and copied the bootanimation.zip to /system/media. The original is gone however the bootanimation is just the default android boot. The one with "android" (i.e the animation we get when using the android emulator)
EDIT: Got it to work, just needed to set the permissions.
[X][X][X]
[X][O][X]
[X][O][X]
I would also like to know if there is a way to remove the initial samsung animation the one where the sound used to play. Since the new animation plays afterwards where the bland samsung logo used to play.
Same here......
I also get the original 'blue circling-Samsung' followed by the white 'SAMSUNG' letters on my screen...Then only do I see the HC bootanimation.
Also - only after I set the permissions to 755 - maybe you should include this in your OP ?
Thanks anyway!
bert269 said:
I also get the original 'blue circling-Samsung' followed by the white 'SAMSUNG' letters on my screen...Then only do I see the HC bootanimation.
Click to expand...
Click to collapse
I renamed the bootsamsung.qmg file to bootsamsung.backup and that seemed to get rid of it, but the custom animation still only shows for the few seconds when the tablet buzzes before the lockscreen comes up.
I viewed the zip file and that is not the one that plays I set permissions but still no honeycomb boot animation! any ideas? will this work on custom rom?
step 4,5,6
use rootexplerer but somehow lose in step 4,5,6 thanks
Hi, I just read some tips about using script for enhancing performance.
It says that the script must be places in system/etc/init.d
But in stock rom P500 (GB 2.3.3 v20G) I can't find folder init.d
The questions:
1. Is the stock rom already support init.d script execution?
2. If yes, will it works just by creating folder init.d and place script there?
3. If not, how to enable support init.d for Optimus One, stock ROM rooted?
I search this forum and find some guide about init.d support in other phone models, will it works on Optimus One too, or perhaps it needs particular way to do it?
1. No
2. If you have init.d support in rom.
3. Only way to do it is cook a custom rom through kitchen to add init.d support
terratrix said:
1. No
2. If you have init.d support in rom.
3. Only way to do it is cook a custom rom through kitchen to add init.d support
Click to expand...
Click to collapse
3. answer is some wrong:
you doesnt need to cook a custom rom, you only need the adb (android debug bridge) to "speak" with your phone:
0.) on your phone download busybox from market
1.) install android sdk on your computer
2.) install LG usb drivers on your computer
3.) open a console (on windows use the "cmd" command)
4.) remount "root" to read/write (type following commands in the cmd)
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk1 /
exit
5.) retrive the init.rc file from your device: (type the command in the cmd)
Code:
adb pull /init.rc C:\users\XXXXX\Desktop\init.rc
6.) open the init.rc file and add the busybox command to execute scripts in the /system/etc/init.d folder
after the lines that does mkdirs etc but BEFORE zygote starts (this stars the whole android)...
Code:
service userinit /system/xbin/busybox run-parts /system/etc/init.d
oneshot
7.) close and save the file, push it back to your device, than reboot:
Code:
adb push XXXX\XXXX\init.rc /init.rc
now you can use the init.d folder as in CyanogenMod / other custom roms.
andy572 said:
3. answer is some wrong:
you doesnt need to cook a custom rom, you only need the adb (android debug bridge) to "speak" with your phone:
0.) on your phone download busybox from market
1.) install android sdk on your computer
2.) install LG usb drivers on your computer
3.) open a console (on windows use the "cmd" command)
4.) remount "root" to read/write (type following commands in the cmd)
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk1 /
exit
5.) retrive the init.rc file from your device: (type the command in the cmd)
Code:
adb pull /init.rc C:\users\XXXXX\Desktop\init.rc
6.) open the init.rc file and add the busybox command to execute scripts in the /system/etc/init.d folder
after the lines that does mkdirs etc but BEFORE zygote starts (this stars the whole android)...
Code:
service userinit /system/xbin/busybox run-parts /system/etc/init.d
oneshot
7.) close and save the file, push it back to your device:
Code:
adb push XXXX\XXXX\init.rc /init.rc
now you can use the init.d folder as in CyanogenMod / other custom roms.
Click to expand...
Click to collapse
Ah thanks for correcting my answer ^^
Dear Andy,
Thanks 4 the procrdure, however i wanted to ask you whether there is any tool to check that the scripts in the init.d folder r getting executed?
andy572 said:
.....guide...
Click to expand...
Click to collapse
That works? I mean init.rc is in ramdisk in boot partition, and gets unpacked on boot, so any changes in / are lost on reboot - at least that is what was told to me.
Kanad said:
Dear Andy,
Thanks 4 the procrdure, however i wanted to ask you whether there is any tool to check that the scripts in the init.d folder r getting executed?
Click to expand...
Click to collapse
Option 1 - run logcat during boot (Trough ADB, type logcat in adb shell, a little simpler if using Droid Explorer)
Option 2 - Run a script that changes something that was previously different. Try installing the supercharger (with different from normal minfree values), rebooting and running the script again to make sure the minfree values are modified. If so, init.d is working and vice versa.
andy572 said:
6.) open the init.rc file and add the busybox command to execute scripts in the /system/etc/init.d folder
after the lines that does mkdirs etc but BEFORE zygote starts (this stars the whole android)...
Code:
service userinit /system/xbin/busybox run-parts /system/etc/init.d
oneshot
Click to expand...
Click to collapse
I go directly to this step, using root explorer on phone (not using PC+ADB)
But after reboot, init.rc i've already edited before has been restored again to original value, as said by Tasssadar.
Maybe I should do it using PC+ADB instead of direct edit on phone?
optimuswhite said:
I go directly to this step, using root explorer on phone (not using PC+ADB)
But after reboot, init.rc i've already edited before has been restored again to original value, as said by Tasssadar.
Maybe I should do it using PC+ADB instead of direct edit on phone?
Click to expand...
Click to collapse
you are trying to modify a running system, sure - you have to do such things
in the boot.img file and have to re-flash it. there is no way to modify a running
system, sorry for misunderstanding.
andy572 said:
you are trying to modify a running system, sure - you have to do such things
in the boot.img file and have to re-flash it. there is no way to modify a running
system, sorry for misunderstanding.
Click to expand...
Click to collapse
I see.
so, is someone can guide me how to deal with boot.img on stock rom?
optimuswhite said:
I see.
so, is someone can guide me how to deal with boot.img on stock rom?
Click to expand...
Click to collapse
go to your recovery, make a backup of your current system and connect the
phone via usb to your computer and copy the rom from the phone to your computer.
then, use the htc kitchen to modify the created rom / or the boot.img
I have used these effects to add transition effect but the transition effect didn't work.there was no change
I used these steps
1. Simply get ahold of the anim folder with the animations you want to use and the framework-res.apk from the rom you're interested in modifying (/system/framework/framework-res.apk).
2. Open up the framework-res.apk in 7zip (right click on it, and select "open archive").
3. Drag the anim folder with the animations (which you can download below) into /res folder in your framework-res.apk. This will replace the files currently in /res/anim.
4. Exit out of 7zip.
5. You now need to push the modified framework-res.apk onto the phone. You can do this by placing the modified framework-res.apk in the root sdcard folder, and entering the following into terminal emulator on your phone or using ADB when the sdcard is mounted:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/framework-res.apk /system/framework
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
pls help why its not working in my deodexed custom ics based rom?
You have to make sure the animations are compatible with the OS version. Each one uses a different set of animation files and settings
Wayne Tech S-III
So how to conform about it?
smartyyadav said:
So how to conform about it?
Click to expand...
Click to collapse
Your best bet would be to decompile the framework Res and compare the animation files. You maybe able to rework them if you have a decent understanding of xmls
Wayne Tech S-III
Ok thanks I will try and reply