Hello i've installed EVO - X4 in my galaxy y, but theres no boot animation when booting, i've try to flash via cwm with custom bootanimation, but nothing, still no have bootanimation,, please give me trick or the answer :angel:
-thanks / gomawo / terimakasih
May be boot animation is disable via build.prop or this don't have no any bootanimation.zip in system > media !!
If u have bootanimation.zip in system > media then
In build.prop u will find something like
xx.nobootanimation.xxx=1
Change 1 to 0 to enable bootanimation!!
Flash the stock rom boot enabler by deathnotice
iv posted it too many times as this question has been asked so many times so search for it
(hint check dev thread for original post)
(2nd hint check my posts to answers to this same question in q & a)
Related
All,
I followed the below instructions to change the Boot Animation on my Vibrant, but have run into a problem. I see the Galaxy S logo swirling, but i also see ANDROID flashing in every frame.
I even deleted the bootanimation.zip but stil i see the same thing. I have attached my inti.rc file so tat maybe someone can see if i missed something? Please help if you can!
Changing Boot Animation:
1. Stock Android is Default!
2. If you wish to Change to Nexus boot or something else.. place the .zip into /system/media/bootanimation.zip
3. Changing Back to Stock Vibrant Boot Screen Do the Following.
3.1. Adb pull /system/init.rc
3.2 Find bootanimation & change to the Following.
#service bootanim /system/bin/bootanimation
# user graphics
# group graphics
# disabled
# oneshot
3.3 Next you need to Push samsungboot.qmp & samsungbootloop.qmp into /system/media
4. Push the edited init.rc back to /system/init.rc
5. All Done, Enjoy!
I have also run into the same problem, but with a different method for changing the boot animation. When I go into change it by replacing the boot animation files in system/media, i get the same result. I also get the same result when I use one of the older flashable zip files. Does anyone know what we're missing? I didn't have this problem until recently so was something changed? I've tried it with several roms with the same results including but not limited to Onyx 5 beta, as well as froyo jk6 no bloat.
Anyone? I also want to know
You cwn get boot animations app and choose from like 100 of them..I use the android peeing on the apple!
Sent from my T-Mobile Galaxy Tab
I tried the boot animation app as well and it essentially replaced the flashing 'android' instead so something has got to have changed somewhere because it changed something else...
I would also like to know this. I actually happened to like the bootup screen for the i9000 that I had on J16.
That's because it all depends on the kernel you guys are using and what the init script for the ROM calls for.
If you searched you would also find out that bootanimations are changed in most kernel's under /data/local instead of /system/media
Still no luck.. any other ideas??
Sent from my Samsung Vibrant using XDA App
All,
I followed the below instructions to change the Boot Animation on my Vibrant (using the qmp files, since i cant find a the same in bnootanimation.zip form), but have run into a problem. I see the Galaxy S logo swirling, but i also saw the MACNUT R14 bootanimation flashing in every frame.
I even deleted the bootanimation.zip but then see the ANDROID logo every other frame. I have attached my inti.rc file so tat maybe someone can see if i missed something? Please help if you can!
Changing Boot Animation:
1. Stock Android is Default!
2. If you wish to Change to Nexus boot or something else.. place the .zip into /system/media/bootanimation.zip
3. Changing Back to Stock Vibrant Boot Screen Do the Following.
3.1. Adb pull /system/init.rc
3.2 Find bootanimation & change to the Following.
#service bootanim /system/bin/bootanimation
# user graphics
# group graphics
# disabled
# oneshot
3.3 Next you need to Push samsungboot.qmp & samsungbootloop.qmp into /system/media
4. Push the edited init.rc back to /system/init.rc
5. All Done, Enjoy!
GameOver69 said:
All,
I followed the below instructions to change the Boot Animation on my Vibrant (using the qmp files, since i cant find a the same in bnootanimation.zip form), but have run into a problem. I see the Galaxy S logo swirling, but i also saw the MACNUT R14 bootanimation flashing in every frame.
I even deleted the bootanimation.zip but then see the ANDROID logo every other frame. I have attached my inti.rc file so tat maybe someone can see if i missed something? Please help if you can!
Changing Boot Animation:
1. Stock Android is Default!
2. If you wish to Change to Nexus boot or something else.. place the .zip into /system/media/bootanimation.zip
3. Changing Back to Stock Vibrant Boot Screen Do the Following.
3.1. Adb pull /system/init.rc
3.2 Find bootanimation & change to the Following.
#service bootanim /system/bin/bootanimation
# user graphics
# group graphics
# disabled
# oneshot
3.3 Next you need to Push samsungboot.qmp & samsungbootloop.qmp into /system/media
4. Push the edited init.rc back to /system/init.rc
5. All Done, Enjoy!
Click to expand...
Click to collapse
Android stores boot animations in two places, not just one. Go to data/local and you should see another bootanimation file in there. That is the stock android bootanimation. Delete that and it should run normally. That's why you're seeing the ANDROID logo every other frame.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant General
Did you Ever Wanted your Own Custom ROM? Did you don't understand other Guides? Do you don't Like ROM Kitchens? Than this Guide is the right Guide for you! Just Try It and you can create your Own Custom ROM!
General Information
So, Before we start with this Guide, i just want to tell you some General Informations about [highlight]Custom Roms[/highlight]. When you buy your phone, you will have a [highlight]Stock ROM [/highlight]installed. A [highlight]Stock ROM [/highlight] is just that Software, your Company has created, especially for your phone. It's a Software like Android 2.3.4 with Touchwiz 4 or Android 4.0.4 with Sony UI. Those Softwares may be good, but there are many Things to Improve, for the Best Xperience, while using your Phone. A [highlight]Custom ROM [/highlight]can be complete different to [highlight]Stock ROM [/highlight], like [highlight]Cyanogenmod 10 [/highlight], or be just a improved Version of the [highlight]Stock ROM [/highlight]. To Build a [highlight]Custom ROM [/highlight] you need to know a few Words, and have a Phone with Root Acess + S-OFF / Unlocked Bootloader. So in this Guide we will concentrate on the Easy Way, the [highlight]Improved Stock ROM [/highlight]. You Can also Build a [highlight]ROM [/highlight] out of Source from Google, but thats too complicated for beginners. Setting up compile envirment can be quite complicated . So let's take a look at stuff you need to know:
[highlight]Root Acess[/highlight]
Complete Acess to all System Files, like Administrator on Windows. To Root Your Phone, search XDA. Rooting your Phone is done by putting su library to /system and manage acess with SuperSu or Superuser. When you buy your Phone, it doesn't have Root Acess. Root Acess is needed for installing CWM, mount your /system as Read & Writeable ----> You can delete system files, and installing apps to /system/app, by copying them to /system/app. By Rooting your Phone you loose Warranty, but you can reinstall stock software and no one will notice
[highlight]ClockWorkMod Recovery (CWM)[/highlight]
Recovery Mode of your Phone. In Recovery you can install flashable zips and roms, wipe and format your device, mount different partititons and fix permissions... To Get CWM search XDA. There are different Ways for every Device. You can enter recovery before your device is fully booted, and since touchscreen drivers are not yet available you need to use the volume buttons for controlling the recovery. There are different ways of entering cwm for every device.
[highlight]Rom & Kernel[/highlight]
ROM means: [highlight] Read-Only-Memory[/highlight] . The Funny Thing is that we can Read and Write on our Read-Only-Memory. Anyway, its a partition which includes large parts of the OS ----> operating system of your Phone. In a [highlight]ROM[/highlight] for Android Phones are included apps, framework, libs & many more and since android is modular, there is an app for everything (keyboard, launcher, statusbar). Together with a [highlight]Kernel[/highlight] it's the "Life" of your Phone.
The Kernel is needed for a working Phone. You Can Install Stock or Custom Kernel. When you buy a Phone Stock Kernel is preinstalled of course. The kernel includes many drivers, controlls the cpu and does many more... Just rember that word
General Information
1. Install Stock ROM to your Phone - This Can be Done by Flashing via Flashtool or Odin. You Need a Clean Base to Start. Recomnend is a Stable, Official ROM, like Gingerbread, Ice Cream Sandwich or maybe Jelly Bean.
2. Root the ROM. This Can be done with Different Tools, Very Popular is for Example SuperOneClick Tool.
Just search for "my device name root" in xda if your not sure
3. Improve Stock ROM on Your Phone. So, After You Have Installed the Stock ROM and Rooted the ROM You Can Start. Now You Need To Change Some Things, To Make the Stock ROM to a Customized ROM. You Can do a lot Things, Here are a Few Examples:
- Install Latest Superuser SuperUser
- Install Latest BusyBox Auto-Installer
- Supercharge the ROM, enable Zipalign etc.. ----> here
- Remove Bloatware. Use Es File Explorer to remove not longer needed apps in system/app partitition
- Tweak Build.prop by going with ES File Explorer to /system and editing your build.prop. now you can change the Name shown in Settings and do a lot more ----> http://forum.xda-developers.com/showthread.php?t=1227269
- Change the Bootanimation. You can find a lot of them by Going to themes and apps of your own device.
- Add or Change Apps. Check out Themes and Apps Selection of Your Device and Install a few Of Them, If You Are Allowed to use MooDeD Apps created by other Users
3.1 Now Delete/remove all backups in clockworkmod/backup folder
4. Now Make Sure You Have Installed CWM. If You Have Changed a Lot Things and You Think Your ROM is good enough, Boot to CWM, select wipe data/factory reset and Boot up again. If You Are Still able to Boot, Check the ROM for Bugs or Problems. Write them Down. Try to fix them. You can always take a logcat (adb logcat)
Than Boot again to CWM select wipe data / Factory reset ---> yes advanced ---> wipe battery stats ---> yes. Now Select backup & Restore ---> Backup.
5. Connect Your sd card to PC and go to Clockworkmod/backup folder. Now Go to the only 1 backup folder and copy "system.img" to your PC.
6. On PC Open Yaffey and Choose Open ---> system.img and than extract to empty folder called system.
7. Now You Will Get a Folder "system" which contains the System of your Phone. Now Create an Empty .zip file and paste in extracted Meta-inf folder Download and copy folder "system" inside. ROM should be flashable for NOW!
Remeber to mount /system before flashing // replace with mount Script for ur device... You can check this by dowoading any rom 4 ur device
NOTE: This has nothing to do with developmemt or original development in any way. Its theming a stock ROM in the simplest way...
Just Press thanks if this was helpfull in any way...
How to
[[ Placeholder ]]
[[ Placeholder ]]
[!][RESERVED][!]
[[ Placeholder ]]
1 year later:laugh:
Sorry... I will finish this guide later...
And so on...
Sent from my GT-S7500 using xda premium
To infinity and beyond!
saiz136 said:
To infinity and beyond!
Click to expand...
Click to collapse
Beyond Smart xD
Updated Thread and Added a First Guide
so where is the guide ? lol ...
maybe make the guide before in PC and the create the thread ? .. just sayin
ruizit0 said:
so where is the guide ? lol ...
maybe make the guide before in PC and the create the thread ? .. just sayin
Click to expand...
Click to collapse
There is a guide lol
jader13254 said:
There is a guide lol
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
ahaha sorry .. i was thinking that was a little intro explaining clocklowrk and stuff .. to a coocking tutorial ahaha
maybe you can expecify more in title or something
nice tutorial to create a rom this way .. i read somewhere that the next clockwork will have this feature
Will try..
Sent from my GT-N8000 using Tapatalk 2
kaipro said:
Will try..
Sent from my GT-N8000 using Tapatalk 2
Click to expand...
Click to collapse
You need different commands for wiping on g Note, just search your device forum
Sent from my LT18i using xda app-developers app
Where is the system.img? I didnt have one when i backed up with cwm
very noob-friendly !
CovXX said:
Where is the system.img? I didnt have one when i backed up with cwm
Click to expand...
Click to collapse
check clockworkmod/backup folder... there should be system.xxxx.img
1. how do you enable zram?? copying all the text on whitexp's thread in a script and putting it in init.d will make it work or it needs activation? also is the compcache ram usage in performance under CM settings in CM7 is the same thing?
2. how do you create a simple cwm flashable zip?? like if i want to mess up some files i can place them in zip and reflash if anything goes wrong how do i create the update binary and updater script for the zip??
No offense but answers to both your questions can be found by doing a simple search .
If i were on pc i would have typed it down hope some one else does
OK . We all i believe find it chaotic to organize in forums now. So this is a thread just for ideas and problem with cwm or twrp on our device.
All that i have found now is that recovery.img is somehow backed with boot.img. So i have to ask if there is any developer that can look inside this.
Help appreciated. We (developers) have already compiled TWRP and CWM ( me via ubuntu and clockworkmod recovery builder) and none of them is booting.
You might want to look at xperia p boot.img??? Same processor u8500 same screen size. I'm a noob. Just said what I felt. Coming from xperia device where our recoveries are always packed inside boot.img
In ramdisk . /sbin/recovery is where our recovery binary is present.
#pitchblack5691#
thanks for help ! i will definetely looo for it
Might be useful
http://forum.xda-developers.com/showthread.php?t=2020895
http://forum.xda-developers.com/showthread.php?t=1903017
#pitchblack5691#
also coming from xperia forum and for My xperia U and have also novathor u8500 and i have asked dev to explain mothod used in XU for port this method to GIII mini but no reply from him now in XU the recovery are in tar and flashable to phone without odin or another flash only by ADB + run me script in commande window inside recovery tar we have unziped recovery ( icone ....) and some files relative to phone ( fstab ..... )
How is it going? Did everyone stop developing or are you guys just moving in silence trying to figure things out?
Sent thru time and space from my s3mini.
silently moving
Shapeshift said:
silently moving
Click to expand...
Click to collapse
Good to know! Give us a shout if we can help somehow.
currently working on cwm 6. dont know why i cant boot
Perhaps need to no only make recovery but also kernel ?
If this 2 filz run together
Sent from my GT-I8190 using xda app-developers app
From what I understand, You just need to write a piece of code in the ramdisk init files to execute the recovery during boot. No need to modify the kernel.
#pitchblack5691#
If any one is interested i got a dumped ram disk also a got it rebuild-ed,
and yes the recovery scripts are there plus the pngs etc.
I also believe that the device has 2 recovery's, they are the same one just acts as a backup.
is an idea
i explain when you make recovery and extract it you find some files inside ( fstab , RC , init , propr ...
now we have also one with CM device info the device have not CM rom and also have not CM kernel her why i posted this comment because when you extract stock recovey you find kernel part and when you extract boot.img find recovery part now this 2 files perhaps have dependency to work together ? is an idea do not yell at me :silly:
spawk said:
is an idea
i explain when you make recovery and extract it you find some files inside ( fstab , RC , init , propr ...
now we have also one with CM device info the device have not CM rom and also have not CM kernel her why i posted this comment because when you extract stock recovey you find kernel part and when you extract boot.img find recovery part now this 2 files perhaps have dependency to work together ? is an idea do not yell at me :silly:
Click to expand...
Click to collapse
They had the internet in 1969?
Take your time. We have root and what roms we have are stable.
Sent from Spaceball One.
Hahaha!
Sent thru time and space from my s3mini.
xd the error is not from me haha i have corect date and time
is new technologie hahahaha retoure backwards in android
and if you see here you can read need new builded kernel to make CWM just read thread 2# and 3# http://forum.xda-developers.com/showthread.php?t=1771347
Help ful apps find on playstore this apps need busybox 2.1 and rooted rom and he let you backup your rom but without boot.img and recovery.img but bacup all system data ..... here is https://play.google.com/store/apps/details?id=com.pommedeterresautee.twoborange3
spawk said:
Help ful apps find on playstore this apps need busybox 2.1 and rooted rom and he let you backup your rom but without boot.img and recovery.img but bacup all system data ..... here is https://play.google.com/store/apps/details?id=com.pommedeterresautee.twoborange3
Click to expand...
Click to collapse
I sent info about device to that developer. That app is now supporting our golden for full backup incl boot & recovery.img with .zip from here. Only problem is we dont have a working custom recovery to flash that .zip with :/
as Faria wrote above should change the recovery that is in the kernel and the same meter and the same rom in it and in the kernel for which you go just tell me that the two are complementary if a move (size , addition, retirees), the other answers are more about the two is that one feature that the other is that we will say to his control as .
now change I believe that both will adjust in any case theoretically