I have an LG Stylo 2 MS550 running the stock android 7 for Metro PCS.
My bootloader is unlocked, I'm rooted, and the recovery partition is flashed with TWRP.
I originally flashed a custom ROM that upgraded my phone to 7.1.2.
I rooted the phone and copied a custom boot animation to the media folder.
The animation played just fine.
I had to reflash the stock ROM as the custom ROM wouldn't take my carrier's APN settings.
Anyway, the stock ROM won't play my custom boot animation.
I've tried tinkering with the desc.txt file.
I compressed it with winrar in store mode.
Nothing.
Any advice?
Any help, guys?
Related
Hi all,
Let me try to walk you through everything that I've done to try and get some help here.
I have an lg g2 sprint (lg-ls980)
1. When I got it I first upgraded to android 4.4.2
2. Then I rooted using stump root
3. I installed xposed and a few xposed modules....I then decided Id rather have a different rom, so
4. I used autorec (which to my understanding changed my kernel in order to workaround boot loader and install twrp? is that accurate?)
5. Booted to twrp, wiped data and installed cyanogenmod and gapps
After this I get stuck and can't boot past the lg logo, so I booted back to recovery and restored my backup. So I did the same and tried pacrom this time with the same results.
I then decided that if I'm going to be stuck with stock rom I at least want my knock on back, so I flashed the patched kernel and same thing- stuck at lg logo....
I know I downloaded the correct zip files and placed them on the root, and always wiped before flashing.
Then I went into download mode on the lg support tool to try to get back to factory, but it says my firmware and recovery is up to date. The odd thing is that the lg support tool shows my phone as ls740 rather than ls980... is this because of something that autorec changed? Do I need to download zip files for ls740 instead? So confused..
About phone in my g2s settings shows android version 4.4.2 and kernel version 3.4.0
Anyways, if anyone could help me to successfully get one of these roms to flash and get back to the kernel that supports the knock code I would really appreciate it.
Thanks in advance!
I do not know if this question has been brought up before, but I am in desperate need of an answer. I recently got my 6P and immediately proceeded to unlock the bootloader and flash TWRP to start loading custom roms. I decided to start use Pure Nexus with it's accompanying gapps package but when I go to reboot the device, I am stuck at the circles boot animation. I decide to try CM13 nightlies and the same problem occurs. After searching online for some time, I realize I needed to flash a SuperSU file from recovery that flashes a custom boot.img. I flash Version 2.66 and restart the device. After 5+ minutes on the boot screen, I decided I am stuck still. What do I need to do, I am unable to boot the device.
Thanks.
I'd use Nexus Root Toolkit to unbrick your phone just so that it is working to start with. Then follow the steps more closely for installing a rom. You'll be doing something wrong, I've had no issues!! Best of luck with this.
hmm I'm not sure. this is happening to me right now as I try to restore my backups... maybe has to do with twrp's system handling/mounting, but I just don't know.
I have been jumping from custom rom to custom rom for a while and today I tried to put the stock 6.0 odexed rooted with the may security update rom on my mxp. I flashed the mm ota modem so I could use wifi and get a signal. I also installed xposed and the mm boot animation. However, in trying to nandroid back to a cm or aosp based rom I am not able to get past the boot animation. Then I tried installing something new and still could not get past the boot animation. I can go back to the stock rom but not to any custom roms. Has anyone experienced this and have they fixed it? if so, how?
EDIT: I did some digging and was able to solve the problem myself by restoring the stock firmware
I'd like to give this Nuclear ROM a try. My device is bootloader unlocked and currently has no OS on it. My device was rooted and last thing I tried doing with it was installing the recent stock Nougat release. Reading that one thread I never went through the steps of restoring what was needed I believe in step two to be able to put stock Nougat on it.
I don't care about stock anymore and will try out this ROM. Holding Power and Volume Down I can get to the options for recovery mode/etc. When I select recovery mode the device reboots and sits at the bootloader unlocked screen. Regardless of which option I select the device reboots and sits at the bootloader unlocked screen. If it's bricked so be it. If it can be restored can anyone point to a thread or have any suggestions?
Flash full stock Nougat:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Files for fastboot you have to find:
https://forum.xda-developers.com/moto-x-style/general/page1
After one boot you can flash twrp & custom rom, f.e. Nuclear. @lip008
Thanks. I just needed a refresher. Everything for fast boot was installed and TWRP was still in the folder. For some reason i thought i was worse off than i was.
Back up and running with this NucleaROM. I may retire the s8+ and go back to this as my DD.
So I recently rooted my Moto g5 Plus and made a custom boot animation for it. But when I replace my stock boot animation with my new one in system/media, when I go to view the .mp4 file it is the same as my stock animation, and whenever I boot the device, a series of black and white flashing lights just appear on the screen until the boot is finished. (I know how to fix this, I need help stopping the boot animation being replaced by stock.)
Anyone know how to stop the boot animation from being replaced by stock even though it is not stock? Thanks!
Same issue here. Stock Nougat + TWRP + Rooted. Able to hide N/A (unlocked bootloader) with the logo.bin. Can not replace boot animation. Tried Boot Animations for superuser from Google Play market, flashing with TWRP, replacement with Root Explorer. Default Moto animation still runs...
Is it possible to replace it at all? What method (including steps) 100% works?
It may be dm-verity doing this. You could install magisk and see if that prevents it from getting overwritten all the time.
NZedPred said:
It may be dm-verity doing this. You could install magisk and see if that prevents it from getting overwritten all the time.
Click to expand...
Click to collapse
Thank you. I've installed ElementalX Kernel and now boot animation is no longer overwritten.