Hi there,
I have a Samsung Galaxy S2 Skyrocket SGH-I727R from Rogers that I have rooted and want to install a custom bootanimation.zip I found that I want to use but when I tried to install with twrp (that's what it said to do) it said it was successful so I rebooted, but it showed the regular boot screen animation. Does it not work on stock roms or am I doing it wrong???
Bootanimation link: Click Here
Related
I wanted to install RockoDev's and fuss123 Beats Audio profile on to my phone, could'nt do it the zip way so I used Root Explorer to manually move the files to System/bin, system/lib, system/etc. The instructions says to reboot into recovery, fix permissions and then reboot again. I'm running Cyanogen Mod 7.2 KANG for Galaxy Ace, and now It wont boot its just stuck at a black screen with "ANDROID" written on it. I've wiped my user data/factory reset, ive wiped cache partition and done all the other hardware fixes Ive read elsewhere.
How do I fix it?
Please Help, couldnt find anything that really could help anywhere.
-----------------------------
Noob
Samsung Galaxy Ace
Cyanogen 7.2 Mod KANG
try flsh stock rom......
Thanks so Much
So I should Flash a ROM like the one that came with the phone or another Cyanogen Rom will do? Sorry I dont really get what "Stock Rom" means.
hey guys , try to using samsung application to flash it . or you can flash a new firmware . maybe you wrong installing ROM
NOt sure
Which Samsung Application? All I know is ODIN. The other suggestions i just might try it. What I really want is a way to fix it without flashing.
If you have cwm , try to download other cm and copy with cwm usb mount , and then flash the rom , and it will be ok
I've read about half a dozen posts so far regarding flashing the stock Verizon boot animation but nothing has exactly pertained to me. I'm running the latest CM 10.1 nightly with KT747 kernal which supports custom boot animations. I am trying to load the stock Verizon animation. I have used the one from Scott's ROMs previously on other ROMs but when I flash through CWM, all I get is the black Samsung Galaxy SIII image. Goes no further and does not boot. Am I missing something here??
RamHemi said:
I've read about half a dozen posts so far regarding flashing the stock Verizon boot animation but nothing has exactly pertained to me. I'm running the latest CM 10.1 nightly with KT747 kernal which supports custom boot animations. I am trying to load the stock Verizon animation. I have used the one from Scott's ROMs previously on other ROMs but when I flash through CWM, all I get is the black Samsung Galaxy SIII image. Goes no further and does not boot. Am I missing something here??
Click to expand...
Click to collapse
i think you can place the new bootanimation wherever bootanimation is located and do it that way.
just make sure the file you replace is named the same as the one you delete.
not 100 percent sure though.
All the flashing instructions and download can be found here
this zip has been tested on boot strap recovery and bmm(system 1 only)
you should be running a custom rom it does not work if you have a stock rom
here is a video showing what the boot animation will look like
this zip should work with any 540X960 device but is tested only on Atrix 2
Please press the like button
Hi there!
I really loved the preview and so I tried adding it to my atrix 2 on system3 running PAC man. But, the boot animation doesn't display it runs blank.
ANy fixes ?
neelz369 said:
Hi there!
I really loved the preview and so I tried adding it to my atrix 2 on system3 running PAC man. But, the boot animation doesn't display it runs blank.
ANy fixes ?
Click to expand...
Click to collapse
i have tried this on pac running on system 1 worked perfectly but i don't multi-boot so can't say about system 3
Animation caused a bootloop on my system 3, not sure why the flashable zip flashed system framework, but it didn't help. I originally tried just pulling the bootanimation from the zip and pushing it to system/media which made it show fine on boot but resulted in a bootloop. Flashed the flashable zip to see if it would fix it, but the bootloop persisted. Ended up reflashing the rom to get booted again.
I have a Tmobile Galaxy S 4G t959v which is rooted. Today I was reading I could flash kit kat rom on to it but I said I needed CWM 6.0.4.4 So I went on ROM Manager to update it but I couldnt find the proper version for my phone so I flash google nexus S which I think its 6.0.4.3 after I flashed it rebooted but it stays on root page I turn it on recovery mode but it still stays in the boot page. Dont know what to do ?
CartoonsAndCereal92 said:
I have a Tmobile Galaxy S 4G t959v which is rooted. Today I was reading I could flash kit kat rom on to it but I said I needed CWM 6.0.4.4 So I went on ROM Manager to update it but I couldnt find the proper version for my phone so I flash google nexus S which I think its 6.0.4.3 after I flashed it rebooted but it stays on root page I turn it on recovery mode but it still stays in the boot page. Dont know what to do ?
Click to expand...
Click to collapse
You made a couple common mistakes...first of all, you didn't do your homework. If you had read through the threads pertaining to our phone, you would have seen that ROM Manager doesn't work on our phones. Secondly, you tried to flash a recovery for another phone.
Please read Lumin's guide on how to use Heimdall to flash to rooted Gingerbread (http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2)...then read the developer's instructions on how to flash the KitKat ROM of your choice once you are have successfully flashed rooted Gingerbread.
Flashing ROM's requires reading and patience.
I have a Rogers Infuse 4G (i997r) and I have been trying to upgrade it to kitkat by using a unofficial Cyanogenmod rom. More recently have been trying to use Carbon rom to update it. I have been running into problem after problem, error after error and I have finally decided to post something on XDA in hopes that someone with more experience can help me out. More information about the errors and what I have done to the phone below.
About a year ago I got this Rogers infuse 4G from a friend. I messed around with it for a bit but what I really wanted to do with it was install a custom rom and update it to a more recent version of Android (It started out on gingerbread (2.3)).
I had a real hard time getting modified recovery 3e because there was not original recovery file in system>bin to replace.
I forget most of what happened but it ended with me using a application to convert the cwm recovery zip to a md5 because I couldn't get modified 3e to work.
I tried using odin to flash the files I made but odin got stuck (or was just taking forever) and I unplugged my Infuse.
The infuse was bricked and would only show "firmware upgrade encountered an issue please select recovery mode in kies and try again". The phone would'nt enter recovery or download mode. It was recognized by odin but seemed as if it was not responding.
About 3 days ago I finally decided to try to unbrick the phone again (I don't know why just felt like it) and I found GTG ultimate unbrick with a pit file. I tried uploading this using odin and the phone responded and downloaded the files.
The phone showed a AT&T splash screen and then the Samsung logo. It hanged at the Samsung logo for about 3 minutes then would turn off reboot, show the AT&T splash screen then the hang at the Samsung logo for 3 minutes again.
I decided that I didn't actually need to install working android because I just needed CWM Recovery and found a CWM Recovery that was flashable with odin.
Now that the phone would actually show a splash screen I could access download mode and the stock 3E recovery.
I went to download mode and flashed CWM Recovery 6 - Voodoo Lagfix with odin
In the CWM Recovery I clicked install update.zip
The phone said installing and when it finished it rebooted.
It showed the AT&T logo and then the Samsung screen then it started talking (which btw scared the **** out of me) and it said installing voodoo lagfix, estimated time remaining 2 minutes
After it was done installing it rebooted and I had the same problem as before. It would show the AT&T logo then hang at the Samsung screen for 3 minutes.
I reflashed the GTG unbrick with odin then I reflashed the CWM Recovery and I was back into the recovery. (It wouldn't just let me boot into it I had to reflash it which was weird)
This time instead of clicking install update.zip I installed the Cyanogenmod-11-infuse-4g-unofficial-2014(some build number).zip
I got (status 7) installation aborted.
when the phone rebooted it showed a cyanogen mod loading screen and I got really excited
after the loading screen it went straight to proper CWM Recovery then it instantly crashed with a little fallen over Android and a red triangle over it.
It kept boot looping like this so I asked for the unbrick files for a Rogers Infuse 4G and installed those.
Once I installed the Rogers Infuse 4G Rom I set it up but I ran into the same problem I had last time.
I can't install the modified 3E recovery because the recovery file is not system>bin. CWM Recovery also fails to install even though it says it has installed.
It turns out the recovery file is on the root of my phone not /system/bin
Im not really sure what to do and guidance would be appreciated.
It's because the CWM is not only device specific, but carrier specific (at least for the Infuse).
Flash the following file (extracted) with Odin. It will talk to you as well after reboot, but it will give you CWM red which you can use to move on to custom ROMs:
https://www.dropbox.com/s/t0kc92124jat6yt/CWM Infused Kernel.zip?dl=0
Be sure to disable Voodoo Lagfix before installing any ROM's, especially if shortcut'ing directly to CarbonROM (versus installing CM9, then CM10.1 and finally a KitKat ROM).
Good luck, let me know if you have any questions.
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error. Accidentally Double Posted... Im a noob. If someone could delete this repost it would be appereciated
OnfireNFS said:
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Click to expand...
Click to collapse
Just to be clear. With the original ROM file, did you try installing the ROM with this CWM and Voodoo Lagfix disabled? That is go into CWM's options menu, and disable there?
Just trying to pick the low hanging fruit, unfortunately I don't know where to go from there (as this is my only idea now, besides re-downloading the ROM).
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
OnfireNFS said:
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
Click to expand...
Click to collapse
It used to be that in order to get from Gingerbread to say, Jellybean, you needed to install the Ice Cream Sandwich ROM (CM9) first. This gives you a relatively new CWM in order to do your bidding. But you man need to install a Jellybean ROM (I suggest CM10.1) in order to get a CWM that will like the installation of KitKat.
So Stock (Infused CWM) -> CM9 -> CM10.1 -> CarbonROM 4.4.4
Of course, I did say used to. Apparently if you disable Voodoo lagfix in CWM you can go straight to CarbonROM. I never tried it, but it is worth a shot (avoids having to go on a scavenger hunt).
But if you already tried it with no success, now you know the classical way.
Thanks a lot. By upgrading to cm9 then cm10 then finally Carbon Rom I was able to get the phone to kitkat!
Cheers