Pieced this splash together from some random images and a base template from the TWRP Team. I take no credit for the images, just threw it all together because I wanted a custom 6P splash for Nougat.
Related
I've been trying to replace the boring splash MI logo screen. Since firmware update, I could never make it. It looks like the system reflash the original splash.img each time I reboot
Now I'm on Havoc OS 9.0 with costum bootanimation.
I have made some Boot Animations for Moto G5 Plus (Potter) and would like to share them with the community.
They also come with their own set of Boot Logos, so you don't need to flash any Boot Logo separately in case you are using the Boot Logos I made.
Features :
Full screen animations
Boot Logo + Boot Animation Pack
N/A hidden in Boot Logo
Redesigned bootloader menu
Some other minor changes in boot logo images
These Boot Animations can also be flashed to other Motorola Devices with 1080X1920 screen resolution like:
Moto G4
Moto G4 Plus
Moto G5
Moto G5 Plus
Moto G5s
Moto G5s Plus
Moto X4
Moto Z2 Play
Other Motorola phone users may use the version of the boot animation with motorola written on the image instead of moto g5 plus.
Use VX.0_BA+BL_9-3_by_4 Zip for Moto G5 Plus.
Use VX.1_BA+BL_9-3_by_4 Zip for other Motorola devices.
The file names with DT at the end stand for Boot Logos suited for Dark Theme.
All Boot Animations have been posted on SOURCEFORGE and more would be added in the coming future. The designs have been separated into two folders and further organized inside each folder by version numbers starting with V1. All the zips are functionally the same and you can flash whichever version you like. The only difference is in the text shown on the Boot Logo image. Head down for viewing previews and downloading the boot logos.
Specifications
This pack will only work for custom ROMs
This pack will not work on Stock Motorola ROMs
All the packs contain both Boot Animation and Boot Logo that goes along with the animation
If your ROM has Display Theme based Boot Animation, the corresponding Boot Animation will be automatically played
Flashing another ROM or updating your ROM may remove this Boot Animation. Flash the pack again to get your desired Boot Animation
Existing Boot Animation in your current ROM will be backed up before installing new Boot Animation
If you wish to restore your Boot Animation that came with your current ROM, you can flash Restore Previous Boot Animation.zip given in Boot Animation folder
How to Install (via Custom Recovery)
Download the desired ZIP file to your phone
Boot to your Custom Recovery
Go to Install
Go to the location where you have saved the ZIP file
Install the ZIP file and reboot
Boot Animation Previews
Boot Animation Downloads
If you are unable to download from SOURCEFORGE on your phone, request desktop site from your browser menu to enable download.
Disclaimer: Motorola Logo and Batwing Logo is owned by Motorola Inc. Some of the artworks are not entirely my own creation.
Tried Flashing "Havoc-OS-v4.1-20210208-arm64-ab-Official-GApps.img"
was boot looping razer logo
flashed Magisk-v22.1.zip
booted further Secure lock screen no passcode dialer then boot loops.
Can't figure out what's wrong I have arter97 r14.
on a forum somewhere they said to flash through fast boot but whenever I wipe I can't use fast boot so I have to restore to backup not really sure what else to do.
any help is greatly appreciated.
this is where I got the GSI from
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
--edit
so I got havoc os booting and running now
first backed up
wiped through twrp
flashed os
flash magisk and f2fs_fstab from arter 97 and it stalled booting
format device in wipe on twrp and boot do not install twrp app
and I am in
used this post and video for the rest
[GUIDE] Android 11 GSI With GApps and Root (magisk)
DON'T DO THIS ON A RAZER PHONE 1 OR IT WILL BE OMEGA BRICKED! ONLY DO THIS ON A RAZER PHONE 2! This was just an experiment to see if i could cobble together some GSI install guides (that on their own are kinda confusing) to make something...
forum.xda-developers.com
I am no expert so I am not responsible for anything you break in doing this is my first rom on any device Good Luck.
you don't get root from magisk but you need magisk to boot without it goes back to recovery
I used this to get root https://www.recovery-mode.com/root/how-to-root-gsi-android-11-with-magisk-v21.html still don't have magisk working but you can't uninstall it or no boot.
I passed safteynet on my HavocOS install. There is a stupid convoluted method to doing it.
its at the end of my guide: https://forum.xda-developers.com/t/guide-havocos-4-1-with-gapps-and-root-magisk.4351029/
hope this helps!
does the universal safety net fix work on this?
HELLO THERE
Here's a list of all working roms, twrps, kernels and more for MediaPad T5.
If you want a guide of how to install, go to this post.
Report issues to T5 Support group from here
I'm making a MEGA folder with all specific (needed to work) and non-specific zips, kernels and twrps
N-S --> CAN USE NON-SPECIFIC ZIPS (may not work)
S --> NEEDS SPECIFIC ZIPS TO WORK ( can use non-specific compatible too)
PR --> Pre Rooted ROM
PRX --> Pre Rooted but doesn't work
UR --> Un Rooted ROM
U --> Untested ROMs (may work but I've not tested it yet)
M --> MODDED FOR T5 COMPATIBILITY
Modded roms are tested and proved to work. All the roms in the list are
compatibles, but newer versions may cause some installation errors.
Join the telegram group if you have any issue and I'll take a look as fast as I can.
PRX - LineageOS by @DarkJoker360 N-S
LeaOS by @AltairFR S U
PR - CrDroid by @Hami_Do N-S M
I tried the following roms on AGS2-W09
Did not boot:
lineage-18.1-20220224-UNOFFICIAL-iceows-pra
crdrom-v313+211013-arm64-avZ
crDroid_v7.10_11-WAS-21092021
Too large to install:
crdrom-v315+220202-iceows-pra
Works:
lineage-18.1-20211106-UNOFFICIAL-prague
CryptLoad said:
I tried the following roms on AGS2-W09
Did not boot:
lineage-18.1-20220224-UNOFFICIAL-iceows-pra
crdrom-v313+211013-arm64-avZ
crDroid_v7.10_11-WAS-21092021
Too large to install:
crdrom-v315+220202-iceows-pra
Works:
lineage-18.1-20211106-UNOFFICIAL-prague
Click to expand...
Click to collapse
crdroid should work. Go to the telegram grou chat to get the modded version until I release it. crdrom is about to get fixed. Lineage too.
crDroid_v7.10_11-WAS-21092021 does work
same for:
lineage-18.1-20220523-UNOFFICIAL-prague
LeaOS-20220616-UNOFFICIAL-iceows-pra.img (uploaded 1 day ago)
It took me more than a day to figure this out but if you have flashed Magisk in one of these custom ROMs then you need to restore the original KERNEL.img and RAMDISK.img form your stock firmware, otherwise everything will boot loop (even if you restore the initial custom ROM you have flashed first time). This is mostly because Magisk modifies the boot.img to apply the root patch.
As a side note here: you can install magisk.zip through TWRP immediately after reflashing your starting/initial custom ROM to be able to boot as before.
To do this I have used HuaweiFirmwareFinder (website + proxy app) to download update.app and then extracted the imgs with HuaweiUpdateExtractor and then used fastboot to flash the images.
It is useful if you have remembered your previous stock version as there can be conflicts with other images (like erecovery or recovery_ramdisk) if they have different versions.
Also I have never used TWRP to do the inital flashings, just fastboot because I see many threads here with people bricking their tablets.
denzelcris said:
crDroid_v7.10_11-WAS-21092021 does work
same for:
lineage-18.1-20220523-UNOFFICIAL-prague
LeaOS-20220616-UNOFFICIAL-iceows-pra.img (uploaded 1 day ago)
It took me more than a day to figure this out but if you have flashed Magisk in one of these custom ROMs then you need to restore the original KERNEL.img and RAMDISK.img form your stock firmware, otherwise everything will boot loop (even if you restore the initial custom ROM you have flashed first time). This is mostly because Magisk modifies the boot.img to apply the root patch.
As a side note here: you can install magisk.zip through TWRP immediately after reflashing your starting/initial custom ROM to be able to boot as before.
To do this I have used HuaweiFirmwareFinder (website + proxy app) to download update.app and then extracted the imgs with HuaweiUpdateExtractor and then used fastboot to flash the images.
It is useful if you have remembered your previous stock version as there can be conflicts with other images (like erecovery or recovery_ramdisk) if they have different versions.
Also I have never used TWRP to do the inital flashings, just fastboot because I see many threads here with people bricking their tablets.
Click to expand...
Click to collapse
This makes sense as flashing the boot also flashes the KERNEL and RAMDISK (correct me if I'm wrong). But do you know if you should do the same if you flash the system? I'm trying to flash a GSI but my device goes to a boot loop after flashing the system.
crDroid is working...just dont forget to unpack the x.z-file
Hi, anyone can help me?. I'm trying to install leaos on my Huawei Mediapad T5 (i'm not new on this), but everytime i reboot It when It finish installing, It keeps rebooting when It has to show the first configuration screen.
Nevermind, i finally got It to work
TWRP
I can't seem to get TWRP to install on my pixel 5 I boot it then use the installer and it just loops to fastboot mode and I'm in an awwl of why,I've done this many times on my pixel 1 and 2.,also I have bugs with it in the Lineage 19.1 official builds and I can never get TWRP to get pass the splash screen with lineage as lineage has it's own recovery.
idk ive been having real issues with twrp since i put droid 13 on my pixel 5 keep in mind ive thrown almost every custom rom on here once with twrp as my recovery bro idk think it may have to do it droid 13
TWRP isn't offically out for Android 12 or Android 13 for Pixel 5.
However Android 12.1 support is coming soon with A13 WIP,
see here
Aside from custom ROMs, TWRP isn't really necessary on Pixel devices due to the ability to flash partitions directly.
It's also worth noting that the recovery kernel lives in the boot image, which also contains the system kernel, so any time /boot is flashed, TWRP would be wiped out.