Ive done the usual steps to replace the hideous Samsung Boot Animation with my own as I have successfully done previously on my Galaxy Tab 7.0 and Galaxy Note (both with Gingerbread) but it seems I can't do it on the the 7.7.
On my rooted 7.7 I deleted both:
/system/media/bootsamsung.qmg
/system/media/bootsamsungloop.qmg
and pasted there my own bootanimation.zip
However, the Tab now boots with no Samsung animation anymore, but mine isn't displayed either.. I just get a black screen for about 10 seconds while the Tab boots up, then the homescreen starts normally.
Is this an issue of Honeycomb 3.2 or did Samsung change something in this regards with the 7.7 tab or, am I missing something?
Thanks for your feedback
this is because you would need a custom kernel to do so.
stock kernel doesn not support bootanimation.zip 's anywhere.
however you can try other devices .qmg files although they will likely be distorted.
highly recommend a custom kernel that supports this.
Related
ive benn doing my own builds of cm 10 for my i9300 for about 3 weeks and haven't hag any problems with it, i purchased a N7 at the weekend and thought i would do my own build for this device too, i got the proprietary files from github.com/themuppets and placed the in the vendor folder just like i had done with my i9300. my build finishes with no errors, but when i've flashed it and try to boot i get the google logo then it flashes and doesn't get any futher (no boot animation). any advice would be appreciated.
Hello , like many of you , i got the flickering screen / jumping screen after unlocking my screen. Rebooting works but as soon as i close the screen or it shuts itself, unlocking it will cause it to flicker / jump like if the resolution was bad or something.
Installing ANY rom from the developpers did not work. From jellybean to revolution , to any popular modified rom.
My tablet is the galaxy 10.1 P7510 , here's what i did.
Updated clockworkmod from 4.0.04 to 5.5.0.4
Restore tablet to the day 1 when you unrooted it (instructions clearly told you to make backup, remember?)
Install Kies official by samsung
Update your tablet , you will now gain the newest version , official by samsung
Your tablet will now be rooted by samsung though , few components of the CWM remains.
Download clockwork mod 5.5.0.4 recovery file , flash it through Odin3 through PDA section
You will now gain back Clockworkmod but yout CWM will flicker / jump like crazy
Make your way through wipe
You may now try to install any modified ROMs, me i installed Revolution 1.0
Make your way through installing the ROM , i put it in ALARM folder because its the easiest to reach , choose your ROM , then press down 6 times to be able to press on YES to installt he rom
RESULT : CWM flickers / jumps but my modified ROM FINALLY does not jump / flicker after unlocking the screen
Good luck everyone!!!!!!!!!!!!
Hello,
this doesent work for me.
My tab cant be updatet with Kies. ist only 3.1.
When i flash the 4.0.4 open Austria with odin i will have the flickering screen.
First off, if this is in the wrong section, I'm sorry. This is only my second day here.
So the other day I rooted, and installed Eclipse ROM on my Verizon S5. I thought it would be fun to change the boot animation and installed CWM_CustomBootanimation_44_Enable.zip, but all that it did after multiple attempts to add an animation (Through 3 different root file managers) was get rid of the animation. How can I get it working correctly, or at the very least uninstall it?
Hi, I attempted to put a custom boot animation on my phone without making backups of the original files, like an idiot, and now my phone boots up to black screens with the AT&T sound still playing, and goes to my lock screen where I can't swipe in until the phone screen times out and I can turn it back on and swipe in normally. I removed the bootsamsung.qmg, the bootsamsunglogo.qmg, and the shutdown.qmg. I am on the stock lollipop OC3 firmware, with root enabled. Does anyone have the original files they can post, and I can replace them, or anyway to get a custom boot animation to work on the OC3 firmware? Thanks in advance!
Wow, I have the exact same problem. I tried to do those mods so I could use regular bootanimation.zips didn't work. Now I need the file located here: "/system/bin/bootanimation"
I'm also on OC3
Hello XDA! I recently came into ownership of two Galaxy Tab 4 10.1 WiFi tablets that came factory reset with Android 5.0.2, they are the SM-T530NN variant for education as these came from a school - and I wanted to flash them with LineageOS. I had already rooted and flashed my Nexus 7 with LOS with no issues and really like it, so I figured I would do that too on these Tab 4's.
The problem I am running into is once I install LineageOS and Supersu from TWRP, the tablet reboots and can't get passed the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: Kernel
I've read that this is not an error, and has something to do with the rooting process or possibly the ROM that I used itself, but nonetheless, it just sits at that error and never fully boots, hence why I can't just ignore it. My OS appeared to install with no errors. Other posts that I have researched on this forum concerning that message don't fully provide me with a solution I can replicate. However, I still have access to download mode and TWRP recovery upon boot so all does not appear to be lost.
I started with thisisapoorusernamechoice's guide (which was awesome by the way) for rooting and have kinda gone from there, trying newer version's of TWRP but am still stuck at boot.
Here are the files/versions I have used:
Odin 3.11.1
twrp-3.0.0.9_matisse_20160314-0843.tar (and 3.0.3.0)
lineage-14.1-20170319-UNOFFICIAL-matissewifi
supersu 2.79
Any help would be greatly appreciated.
***UPDATE***
Never saw any replies to this post so I decided to just try a different ROM, went for Bliss 6 to see if it would boot. Sure enough I still get the same message as before but it does boot up and is usable! Some minor things are not working like the camera app crashes upon opening, and the lock screen date and time are all smashed together - but these are minor inconveniences as these tablets will only be used for Plex, not taking pictures. Plus I still have a TWRP backup of the stock ROM should I choose to go back to that.