Does anyone have any idea how to enable custom bootanimations on the Find 7a? I know that when I was still using my Nexus 4 and GS3, I had to download a patch to enable custom bootanimations to work, but I haven't found a way to enable it on the Find 7a yet. I've already replaced the original bootanimation in system/media and I even placed a custom bootanimation in data/local, but no matter what I do it keeps booting the stock bootanimation. How is that even possible, I already replaced the original bootanimation, just how in the world is it still able to boot the stock -_-... I mean normally, even if custom boot animations are not supported it should show at least a balck screen at boot up since I deleted the original bootanimation. Need some help here guys. I am fully rooted, SuperSU, busybox installed, etc.
Related
This is my first time modifying a rom, but unfortunately it didn't work out.
After trying the 2.73.751.4 rom, I decided that I like the traditional chinese support of this rom, but I like the look of the old people widget more (2.73.751.4 change the look of the people widget slightly).
So I took the htccontactwidgets.apk and htccontactwidgets.odex from system\app of the 2.73.405.5 rom and replace the two files in the 2.73.751.4 rom with these. Then I re-sign the zip file of the new rom following the instruction here:
http://forum.xda-developers.com/showthread.php?t=473580
Everything seemed to work fine as the signing process resulted 0 error. I installed the new rom with Cyanogen recovery image and it reported installation success.
However, upon reboot, my Hero got stuck in the screen showing the HTC logo (waited like 20+ minutes), never got to the point where it should play the boot up sound, and I had to pull the battery to turn it off.
Luckily I could still enter the Cyanogen recovery image and did a nandroid restore. I tried repeating the process again but also got the same result - stuck at the HTC logo. Did I miss something when re-signing the room?
I downloaded all the rom zip files from here:
http://android.modaco.com/content/h.../03-09-hero-roms-radios-in-update-zip-format/
and previously I had tested that both 2.73.751.4 and 2.73.405.5 worked fine on my (unbranded Hero).
I have a gsm galaxy nexus rooted. I recently changed the font only to find that as a result i was unable to update from 4.0.2 to 4.0.4 ethier OTA of via .zip using CWM and had to flash stock 4.0.2 factory image. I have searched and found threads relating to the font issue, this is not what i am doing. I wish people to post changes theyve made to there phone (changes that need root of course i.e. theme, boot animation etc) and weither they were still able to update or not afterwards, as i had used set cpu, changed boot animation and used volume+ and changed font at the same time i am unable to confirm if these changes made a diffrence as the check may have stopped before it could check these due to the system/fonts/robot error coming up first.
So to start do NOT change font as to update you will need to flash stock factory image first
II'm having trouble changing the bootanimation on my s3 t999, I do have touch recovery, umd5, I am on 4.1.2, I tried installing the zip for the Google edition bootanimation into system/media/ and also data/local n changed mermissisions to rw-r-r-- and still won't boot into the new bootanimation, I still get that Samsung animation
Nevermind I got it
Just curious if anybody has some insight here...
I have a XT1710-09 which I have unlocked the bootloader and went to Lineage, only to find that the moto mods I use aren't working. So I've reverted back to the stock ROM. Everything works, but if I try and flash any version of Magisk (17.3 through 19), my phone will boot loop. I have tried the below items, but they all result in a boot loop:
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I can recover from the bootloop by reflashing the boot.img, but I obviously don't have any modification support. I've also noticed the boot.img seems to overwrite my TWRP install on the first boot when applying the encryption.
My phone is currently being flashed with ALBUS_OPS27.76-12-25. Does anybody have any guidance on getting this working? Sadly, I want to get the AAC codecs installed, otherwise my bluetooth system keeps falling back to sbc. Worked great in Lineage, but I have too many moto mods that wouldn't work (including the JBL and Hasselblad).
Thanks!
Are you sure you executed the two commands for keeping force encrypt and keep dm-verity before flashing on TWRP terminal? Because the only reason Magisk ever gives me bootloop on stock is because it automatically sets keep force encrypt, but not the other one.
And of course use v19
I am preparing to use this phone as a dedicated display on a custom embedded system. Changing the boot logo is a must. I have been playing around with it and reading threads for hours and no luck.
Rooted with the latest Magisk, TWRP, unlocked bootloader, the whole 9 yards. A10 Stock ROM. I don't care I break SafetyNet, just need this to work.
I can't put the new bootloader on the system partition because it's mounted as read only. Since it's A10, I haven't found a working way to modify it with TWRP or within the ROM. Has anyone been successful yet?
There are existing Magisk modules for boot animations, but I need a custom one, and I don't know how to make it into a flashable ZIP. How do they do this?
I also tried a Magisk module that is supposed to let you put the boot animation on /sdcard, and it gets overridden on boot by the module, but that did nothing. But it was on a OnePlus forum, so maybe incompatible.
Thanks!
Hi
I think since A10 you can't mount the system unless in certain ROMs. You can try flashing Lineage OS 17.1 ROM since it allows you to mount the system partition.
I'm not sure about how to compile a magisk module. But you can Google it or search it here in xda, I think you might find a post about that.