Here is a CWM zip file to change your boot logo (the red M when you first start up your phone before you get the boot animation.
For EXT4 ROMs: http://db.tt/SGYWlaCL
For non EXT4 ROMs like stock: http://db.tt/BMYWXf2
Thanks to a couple of devs I figured it out! Thanks to NFHimself for the script.
i would like to know how to do this too, ive been searching and havent come across much yet, will update if i find out how.
kinda helped understand CWM scripts better.
[INFO] Edify scripts in CWM recovery
Then i found this and used it as a base idea. so it can be done! ("for zoom")
[INFO] Edify scripts in CWM recovery
And i used this to compile the CWM file
[INFO] Edify scripts in CWM recovery
hopefully you'll be able to figure it out or at least get started.
DarkSim2o9 said:
i would like to know how to do this too, ive been searching and havent come across much yet, will update if i find out how.
Click to expand...
Click to collapse
Find an existing CWM boot logo zip package, substitute their boot animation and sound for your boot animation and sound. Zip it and set compression to "store".
xploited said:
Find an existing CWM boot logo zip package, substitute their boot animation and sound for your boot animation and sound. Zip it and set compression to "store".
Click to expand...
Click to collapse
No no no not the boot animations... the boot logo like the red M when you first start the phone
Sent from my Alien MB860
xploited said:
Find an existing CWM boot logo zip package, substitute their boot animation and sound for your boot animation and sound. Zip it and set compression to "store".
Click to expand...
Click to collapse
Yeah, he's referring to the boot logo, this being the red M you see prior to the boot animation. This would be the screen where you see Unlocked, Fastboot, etc.
care to share what you figured out?
Here is the file that is flashable through CWM recovery. The logo in it currently is the stock logo but you can just unzip it replace the logo.bin file and zip it back up and flash away.
Download here:http://db.tt/BMYWXf2
Download here if your running CM7 or another EXT4 ROM: http://db.tt/SGYWlaCL
Sent from my Alien MB860
Seadub2 said:
Here is the file that is flashable through CWM recovery. The logo in it currently is the stock logo but you can just unzip it replace the logo.bin file and zip it back up and flash away.
Download here:http://db.tt/BMYWXf2
Sent from my Alien MB860
Click to expand...
Click to collapse
Didnt work for me, even tried CWM loading the original file says same thing.
CWM reports: (Status 7)
and something about mount expecting 3 args but theres 4
I tried to change some of it and i still got the same thing (Status 7) Error.
reference to what i tried changing.
mount(TYPE, DEV, PATH); This is one version of the mount command. The TYPE arg is usually "MTD", which refers to memory technology device. The DEV for a MTD would be something like "system", "userdata", "cache", and the PATH would be "/system", "/data", or "/cache". You will also see TYPE be "vfat".
mount(FSTYPE, TYPE, DEV, PATH); This seems to be the more current mount command. It adds in the file system type. Ex. "ext3", "yaffs". TYPE with this command can be "MTD" or "EMMC". You would use "EMMC" with "/dev/block/mmcblk0p8".
So darksim do you get those errors if you try to change something because I have tried four different logos and they worked. Now I did get the status 7 error before when I tried to add text to it but when I left it alone it works perfectly.
Sent from my Alien MB860
Can anyone else test this
Sent from my Alien MB860
Been looking for something like this after flashing a custom boot which changed my original boot logo big thanks to the poster
Sent from my MB860 using XDA App
Seadub2 said:
So darksim do you get those errors if you try to change something because I have tried four different logos and they worked. Now I did get the status 7 error before when I tried to add text to it but when I left it alone it works perfectly.
Sent from my Alien MB860
Click to expand...
Click to collapse
Could be my CWM version or its a modded one... CWM-Based Recovery v4.0.1.4-atrix3
I think this is the one im using, not 100% sure.
***UPDATED CWM to 3.1***
and its working now
[Unlocked Only][RECOVERY][2011-08-14] Custom CWM-based Recovery 4.0.1.4-atrix3.1
Alright updated my CWM to 3.1 and now the FILE works...
i was running v3 i guess they fixed something and NOW IT WORKS
AWESOME THANK YOU!!!
O ok I was running version 2 still never got around to updating. Lol
Sent from my Alien MB860
Yeah After updating to 3.1 it fix the problem. if you would like to see the final result.
M-Atrix Boot Logo and Animation for the Atrix
Related
I had issues with my recovery ever since updating to DL30 and continuing until EB01. I attempted to install red recovery but I would always boot in blue then had to select apply sdcard: update.zip. This did not make me feel safe so these are the steps I followed in order to fix and update my recovery. This thread is mainly for "newbs" that have a diffucult time understanding what older users are trying to say.
Before you begin, download the cwm-recovery-ALL zip file from jt1134's thread:
http://forum.xda-developers.com/showthread.php?t=942021
and
http://dl.dropbox.com/u/17566514/update.zip
STEP 1:
Place the "cwm-recovery-ALL" file in the clockwork mod folder on SD card and rename it "recovery-update" replacing the old one already in this folder.
STEP2:
Place the "update" file on the root of your SD card replacing any current "update file".
STEP3:
Reboot into recovery and if you boot in blue select "apply sdcard:update.zip"
STEP 4:
You should be in green recovery now and select "install zip from SD card" then select "choose zip from SD card"
STEP 5:
Navigate to the clockworkmod folder on your SD card and install the "recovery-update" that you placed in there earlier.
STEP 6:
Once "recovery-update" is done installing, go back to the main menu in green recovery and select "apply sdcard:update.zip".
STEP 7:
You will still be in green recovery but on next reboot you should boot into red. If you are still booting into green, copy the "update" file on the root of your SD card and paste it in the clockworkmod folder on your SD card. Delete the existing "recovery-update" and rename the "update" file you just placed in there "recovery-update".
-Try booting to recovery once more and you should now boot directly to red recovery. If not, please start over and go step by step.
-If you still have issues with booting to red recovery after following these steps, please flash http://db.tt/6dZUc7d in Odin and start steps over. (Thank you Takafiji)
NOTE:
I am not responsible for anyone who destroys their recovery by not following the steps provided. Please, please read carefully.
Credit to jt1134 and Takafiji for providing the recovery files.
Thanks, I was tired of using Odin to get Red recovery mode every time I wanted to flash a new ROM. For some reason I still find myself needing to reflash the eb01-modem.tar everytime I want to install a new superclean eb01 build.
also i think the sammy kernel sneaks in and replaces cwm with there stock (blue) recovery. so i recommend on first flash using odin, then boot directly to recovery, (not going into bootscreen) then follow his directions.
Also thats not my dropbox link its another guys, ill find the name, i just used it because it did the job.
Blue recovery does "sneak" in it seems. I have red recovery but blue does load sometimes with a "failed" message. If I apply "update" it goes to what looks like download mode. From there nothing works. Hold down volume keys and power reboots into red. Sometimes recovery goes directly to red? Trial and error....
40kalkillah said:
Blue recovery does "sneak" in it seems. I have red recovery but blue does load sometimes with a "failed" message. If I apply "update" it goes to what looks like download mode. From there nothing works. Hold down volume keys and power reboots into red. Sometimes recovery goes directly to red? Trial and error....
Click to expand...
Click to collapse
That happened to me as I was following these steps the first time. Turned out I had a bad update.zip file. Make sure your files are named correctly and not "update.zip" as it will show up in your system as "update.zip.zip". Should just be named "update" on root of SD card and "recovery-update" in clockworkmod folder. If you haven't followed the steps I provided please do as I haven't had any issues yet with it. Maybe try Takafiji's advice and flashing the Odin files first.
if using windows the way to change and see the extension of a file such as .zip open up "my computer" click "tools" (if you cant see it hold the "alt" key) then click "folder options" hit the "view tab" and uncheck "hide extensions for known filetypes" hit ok and your set! Now you can see .zip, .java, or whatever the extension is!
I folowed this procedure. It worked. Except when rebooting to recovery from rom manager it reverts to blue recovery and cant go any further. When i use the startup volume keys and power it goes to red. When i use the shut down and recovery from the power off screen it goes to red. Only when I use rom manager it goes to blue. Normally I wouldn't mind because i can still get to it to flash roms but trying to use the blackhole custom rom it would be much easier if I let rom manager flash all the files in a row instead of manually flashing one by one. Any help on this matter would be greatly appreciated. Thank you.
Great info - Thanks!
A couple of questions:
Can the Red CWM restore backups taken with the Green CWM?
The Reset Battery Stats command does not give any indication that it worked. I select it, say Yes, I really want to reset battery stats, then I am back at the Advanced menu. Did the reset work?
acuralegendz said:
I folowed this procedure. It worked. Except when rebooting to recovery from rom manager it reverts to blue recovery and cant go any further. When i use the startup volume keys and power it goes to red. When i use the shut down and recovery from the power off screen it goes to red. Only when I use rom manager it goes to blue. Normally I wouldn't mind because i can still get to it to flash roms but trying to use the blackhole custom rom it would be much easier if I let rom manager flash all the files in a row instead of manually flashing one by one. Any help on this matter would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
I think its the kernel to tell you the truth. I saw it in another cwm post that the sammy kernel will replace cwm. Try following this method but add in an odin flash of http://db.tt/6dZUc7d then on first boot go directly to recovery if you get to boot screen start over, once in recovery follow the steps in the first post.
acuralegendz said:
I folowed this procedure. It worked. Except when rebooting to recovery from rom manager it reverts to blue recovery and cant go any further. When i use the startup volume keys and power it goes to red. When i use the shut down and recovery from the power off screen it goes to red. Only when I use rom manager it goes to blue. Normally I wouldn't mind because i can still get to it to flash roms but trying to use the blackhole custom rom it would be much easier if I let rom manager flash all the files in a row instead of manually flashing one by one. Any help on this matter would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
Rom Manager uses the recovery-update.zip file in the clockworkmod folder. After installing recovery-update.zip in step 5, did you copy the update.zip file on the root of your SD card and paste it over in the clockwork mod folder and rename it recovery-update.zip? It should replace the recovery-update.zip you placed in the folder on step 1. I just used RomManager to boot to recovery and it took me directly to red.
Pfredd said:
Great info - Thanks!
A couple of questions:
Can the Red CWM restore backups taken with the Green CWM?
The Reset Battery Stats command does not give any indication that it worked. I select it, say Yes, I really want to reset battery stats, then I am back at the Advanced menu. Did the reset work?
Click to expand...
Click to collapse
Yes, it can restore backups from green.
Personally I have the same question about wiping battery stats. I believe there is an issue currently with wiping on FROYO because I have noticed even though I wipe data and cache multiple times before installing any Rom, I still seem to have leftover data from the previous Rom such as wallpapers. I tried wiping on green before I installed red and it did the same thing, so I do not think it's limited to red but rather an issue with FROYO support.
I had to use the odin file first. It booted into red.
Then when I tried it through RM. I went to blue and couldn't verify the signature?
And I when I enter recovery mode manually, and try to select update.zip, it begins but gets about 25% and then the triangle with the exclamation point appears.
It works through odin, but never any other time.
Any help? All is appreciated.
lfrench0 said:
I had to use the odin file first. It booted into red.
Then when I tried it through RM. I went to blue and couldn't verify the signature?
And I when I enter recovery mode manually, and try to select update.zip, it begins but gets about 25% and then the triangle with the exclamation point appears.
It works through odin, but never any other time.
Any help? All is appreciated.
Click to expand...
Click to collapse
The Odin file just places update.zip on the root of your SD card but you must still follow all of the steps for it to function properly. If it couldn't verify signature something is wrong with the update.zip file on the root of your SD card. Try deleting that and flashing the Odin file again. Then proceed to follow all of the steps again.
I installed it and can reboot into green recovery but when installing anything from the rom manager I get a invalid certificate message...
Sent from my SCH-I500 using XDA App
Zacisblack said:
The Odin file just places update.zip on the root of your SD card but you must still follow all of the steps for it to function properly. If it couldn't verify signature something is wrong with the update.zip file on the root of your SD card. Try deleting that and flashing the Odin file again. Then proceed to follow all of the steps again.
Click to expand...
Click to collapse
It didn't put it on the sd card. It just rebooted. Seems like nothing changed. I was closer when I put the update.zip on the sd.
ilogik said:
I installed it and can reboot into green recovery but when installing anything from the rom manager I get a invalid certificate message...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You shouldn't be in green you should be in red. Adrynalyne recently stated that he does not condone the use of Rom Manager since it does not support us very well right now. Though I have used Rom Manager after installing this and everything works. If you are booting into green you must follow the steps after to boot into red and then everything should work except wiping battery stats.
alright folks try this after you flash red cwm vid http://forum.xda-developers.com/showthread.php?t=942021 using odin or the zip file, delete both update.zip from root and recovery-update.zip from clockworkmod.
This may sound crazy, but i've found out cwm red gets flashed to the boot partition,so theres no need for update.zip anymore.
grab http://forum.xda-developers.com/showthread.php?t=958209 its the new rom manager that will allow you to fix permissions.
Takafiji said:
alright folks try this after you flash red cwm vid http://forum.xda-developers.com/showthread.php?t=942021 using odin or the zip file, delete both update.zip from root and recovery-update.zip from clockworkmod.
This may sound crazy, but i've found out cwm red gets flashed to the boot partition,so theres no need for update.zip anymore.
grab http://forum.xda-developers.com/showthread.php?t=942021 its the new rom manager that will allow you to fix permissions.
Click to expand...
Click to collapse
Are both links supposed to be the same? Also what am I supposed to get from the second link?
Takafiji said:
alright folks try this after you flash red cwm vid http://forum.xda-developers.com/showthread.php?t=942021 using odin or the zip file, delete both update.zip from root and recovery-update.zip from clockworkmod.
This may sound crazy, but i've found out cwm red gets flashed to the boot partition,so theres no need for update.zip anymore.
grab http://forum.xda-developers.com/showthread.php?t=942021 its the new rom manager that will allow you to fix permissions.
Click to expand...
Click to collapse
Thanks so much. This solved my problem and I am now able to backup my phone.
lfrench0 said:
Are both links supposed to be the same? Also what am I supposed to get from the second link?
Click to expand...
Click to collapse
no dang, i changed the second link, here it is for ya
http://forum.xda-developers.com/showthread.php?t=958209
So i updated OTA to 2.2 and then rooted my Fascinate. Now I'm trying to flash a new rom using Rom Manager but whenever I try to install a rom or reboot into recovery i get the error
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
And then it puts me in Stock Android Recovery. Any ideas on why this is happening and how I can fix it? Thanks
RepAZ said:
So i updated OTA to 2.2 and then rooted my Fascinate. Now I'm trying to flash a new rom using Rom Manager but whenever I try to install a rom or reboot into recovery i get the error
And then it puts me in Stock Android Recovery. Any ideas on why this is happening and how I can fix it? Thanks
Click to expand...
Click to collapse
The consensus seems to be not to use ROM manager and to ODIN Clockwork Recovery Manager. Unfortunately there seems to be a little mentioned bug where CWM won't stay after the 1st time you reboot and I can't find a solution to this yet.
phonefiend said:
The consensus seems to be not to use ROM manager and to ODIN Clockwork Recovery Manager. Unfortunately there seems to be a little mentioned bug where CWM won't stay after the 1st time you reboot and I can't find a solution to this yet.
Click to expand...
Click to collapse
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
islandtime said:
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
Click to expand...
Click to collapse
Island beat me to it but he is exactly correct. I kept the stock kernel at first but i had to ODIN CWM 2 times as the first time it was blue but after 2nd time it was red. But the best way is to flash a custom Kernel which will keep it red
islandtime said:
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
Click to expand...
Click to collapse
What I meant to say is what you said above: you can boot into CWM right after you flash it, but if you restart again it will go into stock recovery.
fitti28 said:
Island beat me to it but he is exactly correct. I kept the stock kernel at first but i had to ODIN CWM 2 times as the first time it was blue but after 2nd time it was red. But the best way is to flash a custom Kernel which will keep it red
Click to expand...
Click to collapse
I've ODIN'd CWM multiple times but it still gets overwritten with the stock recovery. I'd like to stick with the stock ED01 kernel but can't find any ZIPs to flash this kernel via CWM.
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Allmaechtig said:
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
I can't find anything on that, can you point me to the thread you followed?
Allmaechtig said:
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
No, what is needed to get into CWM is you need to flash CWM via Odin. Take the battery out when going into download mode. After flashing, unplug the USB cable and put the battery back in. When you go to start the phone, boot straight into recovery. The stock kernel reflashes recovery on every boot, so if you boot the phone normally, the phone will continue to have stock recovery. Once in CWM, flash a custom kernel and you'll be set as the custom kernels don't reflash recovery on boot.
imnuts said:
No, what is needed to get into CWM is you need to flash CWM via Odin. Take the battery out when going into download mode. After flashing, unplug the USB cable and put the battery back in. When you go to start the phone, boot straight into recovery. The stock kernel reflashes recovery on every boot, so if you boot the phone normally, the phone will continue to have stock recovery. Once in CWM, flash a custom kernel and you'll be set as the custom kernels don't reflash recovery on boot.
Click to expand...
Click to collapse
This is unfortunate because I used to run a version of CWM just fine with the stock EB01 kernel. With the current CWMs I finally found a way to get it to work with the stock kernel: rename /system/etc/install-recovery.sh.
got it working yay
BlackHoleSlam said:
got it working yay
Click to expand...
Click to collapse
Tell us how.
i just waited some time and placed the debinged rom from adrenylne on my sd card then used the 3-30 tar and put my self in red voodoo flashed a different kernel theme then rom and all is good
Ok so I used dos program to unlock bootloader then selected to flash recovery and root through dos then downloaded rom manager flashed Cwm and when I go to recovery it shows an exclamation point but if I flash it and reboot in rec through rom manager works do I need to flash the recoveries.img that have the many different colors to choose from and flash that then rom manger and flash Cwm im not really sure where to go I've looked and looked im trying to install cyanogen mod and the recovery debacle is holding me up
SENT FROM AN ATRIX THAT ATE STEVE JOBS
Just follow the instructions . (Installation Instructions section)
http://forum.xda-developers.com/showthread.php?t=1257574
twayneo said:
Ok so I used dos program to unlock bootloader then selected to flash recovery and root through dos then downloaded rom manager flashed Cwm and when I go to recovery it shows an exclamation point but if I flash it and reboot in rec through rom manager works do I need to flash the recoveries.img that have the many different colors to choose from and flash that then rom manger and flash Cwm im not really sure where to go I've looked and looked im trying to install cyanogen mod and the recovery debacle is holding me up
SENT FROM AN ATRIX THAT ATE STEVE JOBS
Click to expand...
Click to collapse
The recovery with all the colors is romracer's, which can be downloaded here. It's generally the one most people recommend using. It sounds like you need to delete your install-recovery.sh file to get rid of that exclamation point. Try the following from romracer's thread:
Thanks to mrinehart93 for pointing this out.
The system runs /system/etc/install-recovery.sh on boot with its stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it. Rename or delete the file and the CWM should stick.
Click to expand...
Click to collapse
I had the same problem before I installed romracer's CWM. It's the only one I've used since. If you decide to install his, Rom Manager should recognize it and allow you to use it instead of its stock one. Just don't flash CWM from within the app after that, or I think it will overwrite romracer's with the stock Rom Manager one.
hellow dev...
please help me..
asking someting...
how can i install this rom? Atrix 4g ICS Codename..
you can see this http://cna.exynos.co/olympus/
it have update till 28.03.2012...
so when i install it...it come back to recovery...
im love ICS..
tq..please help me...
you have to choose one version, download and copy to your device
1. run recovery
2. wipe data, cache, dalvik
3. install zip from your device
4. reboot
i do step by step...still reboot recovery...
have u try it?
Did you install CWM? My buddy had the same problem with rebooting into recovery.
Sent from my MB860 using XDA
I tried flashing it and it does indeed just reboot to recovery. Have no idea why.
What it actually does is sits at boot logo screen, then reboots to recovery, so it actually bootloops once into recovery each time you try to boot it up.
CaelanT said:
I tried flashing it and it does indeed just reboot to recovery. Have no idea why.
What it actually does is sits at boot logo screen, then reboots to recovery, so it actually bootloops once into recovery each time you try to boot it up.
Click to expand...
Click to collapse
need the bins files and libcxxx from cm9 to stop reboot to recovery
stevendeb25 said:
need the bins files and libcxxx from cm9 to stop reboot to recovery
Click to expand...
Click to collapse
Cheers. I just tried flashing it to see if I got same issue as OP. Hopefully your comment will help him/her.
Sent from my MB860 using xda premium
need the bins files and libcxxx from cm9 ???
can i just take from cm9 source??
I got it booting using cm9 as base.
All you gotta do is delete app/framework from cm9 then push all app/framework of codename to see at least what the ui looks like and what options and features it has
Sent from my MB860 using XDA Premium App
rickriego replaced the bin/libs in the CNA zip with the ones from cm9 and posted a flashable zip over in the dev section for anyone interested.
I know there is a version using Jokersax's files but has anyone gotten it to work with Turl's files. The camera does not work with the newest jokersax as Rodriego uses, so I tried to use Turl's, and it just got stuck on the bootscreen. Thanks in advance.
fl1p1slander said:
I know there is a version using Jokersax's files but has anyone gotten it to work with Turl's files. The camera does not work with the newest jokersax as Rodriego uses, so I tried to use Turl's, and it just got stuck on the bootscreen. Thanks in advance.
Click to expand...
Click to collapse
same way, merge turls bin/lib folders into the zip using 7zip
stevendeb25 said:
same way, merge turls bin/lib folders into the zip using 7zip
Click to expand...
Click to collapse
Yeah I thought it would be pretty easy. I used winrar to move the folders to the cna rom zip but still stays on boot animation.
Thought I was going crazy bit other people could not make it work with turls1's files
ovitz said:
you have to choose one version, download and copy to your device
1. run recovery
2. wipe data, cache, dalvik
3. install zip from your device
4. reboot
Click to expand...
Click to collapse
No, the above WILL NOT WORK!!!
However, doing this will work:
get the nightly from
http://cna.exynos.co/olympus/
get the
beta 0.4.3
faux’s 1.0 kernel -outdated (ignore outdated, it´s the right one)
from
http://www.jokersax.com/developer-pages/jokersax/cyanogenmod-9-atrix/
get jokersax gapps v11
from
http://www.jokersax.com/developer-pages/jokersax/cm9-gapps/
in linux, using Q7Z, unzip the CNA nightly and replace the following folders by the ones from Joker´s beta 0.4.3:
bin
lib
xbin
Re-Zip. Be careful not to alter the zip structure or permissions.
In Recovery, flash your modded CNA.zip, THEN flash faux´s kernel, THEN flash gapps.
Enjoy
Hi All, recently I went back to stock ICS from Omega v27, and then rooted with CF 6.4 and installed Siyah 1.53.
On v27 custom bootanimation enabling zip file was there on my exSD card. Today by curiosity I flashed that Zip file using CWM and since then when the phone boots I just hear the sound but cannot see the boot animation. What should I do now to make it visible ?
Regards,
Flash Omega V27.1 which uses a custom boot animation by default.
Sent from my GT-I9300
thekoRngear said:
Hi All, recently I went back to stock ICS from Omega v27, and then rooted with CF 6.4 and installed Siyah 1.53.
On v27 custom bootanimation enabling zip file was there on my exSD card. Today by curiosity I flashed that Zip file using CWM and since then when the phone boots I just hear the sound but cannot see the boot animation. What should I do now to make it visible ?
Regards,
Click to expand...
Click to collapse
Did you enable Custom Bootanimation Zip or did you just flash the bootanimation directly, because if so that will end up with infinite bootloop.V27.1 Bootanimation enabled by default and implemented inside the ROM.
nhariamine said:
Did you enable Custom Bootanimation Zip or did you just flash the bootanimation directly, because if so that will end up with infinite bootloop.V27.1 Bootanimation enabled by default and implemented inside the ROM.
Click to expand...
Click to collapse
Dear, I rebooted into Cockworkmod recovery. Then chosen the custom bootanimation enabling zip file That Came with the Omega Rom Files Menu that I installed previously. That zip file was left on the ext SD card and then by enough stupid curiosity I flashed that Zip file using CWM which resulted in no infinite loop but a blanc screen with default Samsung Animation sound and the phone gets into the home screen. This is uncomfy. I can hear the sound but see no animation. I really like to get back the stock animation working. I even factory reset the phone, but of no vail.
thekoRngear said:
Dear, I rebooted into Cockworkmod recovery. Then chosen the custom bootanimation enabling zip file That Came with the Omega Rom Files Menu that I installed previously. That zip file was left on the ext SD card and then by enough stupid curiosity I flashed that Zip file using CWM which resulted in no infinite loop but a blanc screen with default Samsung Animation sound and the phone gets into the home screen. This is uncomfy. I can hear the sound but see no animation. I really like to get back the stock animation working. I even factory reset the phone, but of no vail.
Click to expand...
Click to collapse
hi mate,
its your animation that need some modification..
inside the bootanimation.zip there is a file named "desc.txt", just open that with notepad++, and edit the last line that probably says something like this:
p 0 0 Part1
Click to expand...
Click to collapse
and change the 0 (zero) after "p", to 1 or more (depends on how many times you want it to loop)
so it looks something like this:
p 1 0 Part1
Click to expand...
Click to collapse
ICS dosent support looped animations, and therefore youll end up having the animation showing forever.. its only JB that supports looped animations.
you could read this thread for further information:
Custom Bootanimations Collection + How To Install + Enable/Disable
and especially check post #5
EDIT:
btw, you need both CF-root with CWM and Busybox for it to work on stock roms.
hi anbech, the prob is fixed. Thank you for the extensive help and others too. Yes, I've read your thread. Infact we should (not could) read your thread when it comes about first time custmizing the bootanimations.