XDA-Developers Splash screen - P3600 ROM Development

Since I'm not ready to fully reverse engineer a ROM and create my custom version of it and DO want to show my appreciation to all people supporting this great forum, I created a custom XDA-Developers splash screen. If you like it, you can download it here.
The update will NOT delete any files on your device and your existing ROM will be untouched. The only thing that is replaced is your MainSplash and SubSplash.

Nice... Thanks!

Related

Theme

just to make sure... If i want a theme- put it on sd card, rename it to update, apply update, and reboot??? It doesn't work for me. It stays stuck on the G1 screen. Does it have something to do with rom i'm using: update-cm-4.1.9.2-signed???
Just in case... Yes its rooted, I've even tried other HERO ROMS(and i have successfull), but 4 some reason I don't know how to apply a theme. And YES!! I'm a n00b.
Thanx in advance
yes your process is correct, BUT you have to make sure the theme you apply is matched with your rom. if you have cm 4.1.9.2 rom, you have to make sure you get the 4.1.9.2 compataible theme. also some themes may take up to 10 minutes to fully boot up.
-insert flame here-
the theme must be compatible with the rom like for 4.1.9.2 the theme has to be based off of the 4.1.9.2 theme template. the same goes for any rom and theme. as long as they are compatible then there shouldn't be any problems. if you want a bigger choice of themes then the stable roms are better.
but yeah, check to see if your theme is compatible with 4.1.9.2, if it isn't then that is the problem.
also you have the process correct.
This should really be in the Q&A section, it seems you haven't really read much of what themes are about. You can only flash themes made SPECIFICALLY for the rom you are running (In your case cm 4.1.9.2) Since I don't see too many themes around made for that rom, I'll assume you're flashing a theme not made for the rom this will cause the G1 screen loop.
To get back to your old system, just flash the rom OR the theme template again and you should be good to go. Next time match the theme versions with rom versions before you go flashing.
Dfanzz said:
just to make sure... If i want a theme- put it on sd card, rename it to update, apply update, and reboot??? It doesn't work for me. It stays stuck on the G1 screen. Does it have something to do with rom i'm using: update-cm-4.1.9.2-signed???
Just in case... Yes its rooted, I've even tried other HERO ROMS(and i have successfull), but 4 some reason I don't know how to apply a theme. And YES!! I'm a n00b.
Thanx in advance
Click to expand...
Click to collapse
First, even though your question is about a THEME, it's still a question and should go in the Q&A section.
In response, your theme MUST be compatible with your rom. So if the theme you are trying is not CM 4.1.9.2 compatible, then you COULD get problems.
EDIT: DAMN, did it really take me so long that 4 people answered before I did? geez lol
Fast guns around here, I think he gets the point though :]
slow pokes =)
Just to clarify to further help you understand, a theme is composed of many of the same files as the original ROM. However, this time around they have been modified to look like what you see as the theme. Therefore, when you install a theme, you are actually replacing those files with the ones with different looks. That is why you need to make sure your theme is made for the ROM, because different programs and files, chances are, will not work and will result in a bootloop.

[APP][SNAPSHOT]Dual-Boot Patcher - Even On /Data!

REMEMBER THIS IS A SNAPSHOT BUILD, THAT MEANS THE APK IS BUILT AS SOON AS CHANGES ARE PUSHED FROM THE MASTER HIMSELF @chenxiaolong
I'm proud to present the first dual boot project for the Qualcomm-based Samsung Galaxy S4! This project started off as a feature in my ROM, but not anymore. This will allow any two ROMs (soon, three) to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/dual, /cache/dual, and /data/dual). Because of the way this is implemented, no changes to the primary ROM are necessary
Click to expand...
Click to collapse
By @chenxiaolong
Tested Personally myself @ktetreault14 with the G920T Xtresolite 5.0.2 ROM (found here) as my primary rom. I then used @eousphoros 5.1.1 Debloated V2 ROM (found here) as my secondary. I even have a Sprint OE2 rom I was testing in a third slot. You might wonder how this is possible. All thanks to chenxiaolong's brilliant multibooting system. He has now added in the ability to install roms straight from your /data partition All without touching your primary rom. You could be stock rooted and have no problems as long as it isn't aroma. (In which case I think you could alwasys use flashfire) The S6 Edge didnt have a very large /system partition (only 4.05 gb ) and /cache was nothing to brag about either (for those inquiring minds it is 304.7mb) So naturally I asked the amazing quick chen if there was any way I could Install it to my ~25gb /data partition, within days he whipped something up... But enough with the story get on with the tutorial and show me the downloads... Ok Fine.. Here. We. Go!!!!!!!!!!!! :fingers-crossed:
TUTORIAL AND PICS AND VIDEOS
I'm Assuming you have the apk downloaded and installed. Also you have the rom and, if you need it, the kernel already downloaded on placed on your phone's memory.
Step 1| Open the apk, Swipe right from left edge, Patch Zip File.
Step 2| That is obvioulsy not your phone so lets change that. Click jflte and select zerolte in the dropdown. (BTW all those other phones are supported too.)
Step 3| Change where you would like it to install too. (Most likely going to be /data unless the roms are heavily debloated or AOSP) For the purposes of this tutorial it is going to /data
Step 4| Name your ROM. Pick Your ROM.
Step 5| Ignore The Information Here, Scroll down, Tap to begin patching. Do as many times as you would like
Step 6| Open hamburger menu, ROMs, click the FAB (Floating Action Button), click +, pick patched rom.
Step 7| Keep Installation Location or change if you are not sure. Do as with many zips you would like to install.
Step 8| Click checkmark in top left corner.
Step 9| Reboot and you will boot up into new rom
IF YOU WOULD LIKE TO SWITCH ROMS
Step 1. Open App
Step 2. Click ROMs
Step 3. Click Rom you want to boot to
Step 4. Reboot
Dual-Boot Patcher Thread
DISCLAIMER: We are not responsible for any issues, problems, or broken phones, which may have come from using any data or information you receive from this thread. Using anything here, will most likely violate your cell phone's warranty or contract. That is also your 100% responsibility, to know, and your responsibilty if you do. If you don't know what you are doing, or you think you do, and you brick your phone, or something POSITIVE OR NEGATIVE changes with your phone, it is all 100% your responsibility. Use the following data, information, and links at YOUR OWN RISK!
SNAPSHOT BUILDS
HERE @chenxiaolong
Dual-Boot Switcher.zip Alpha
USE THIS TO SWITCH BETWEEN ROMS IN RECOVERY
Get The Latest Version In Chen's Thread
CREDITS
@chenxiaolong - He is the maker and current maintainer
Thanks for making this thread!
PSA
If you are on tge unrooted 5.1.1 rom, after you patch the zip just flash from recovery.
ktetreault14 said:
No problem I need to get the word out. Lol
Click to expand...
Click to collapse
If I'm running the eousphoros 5.1.1 Debloated V2 ROM as my primary, I would need to start over, correct? (since this ROM doesn't have root and has stock recovery)
whittikins said:
If I'm running the eousphoros 5.1.1 Debloated V2 ROM as my primary, I would need to start over, correct? (since this ROM doesn't have root and has stock recovery)
Click to expand...
Click to collapse
Nope. You only need root for the app if you want to flash in-app. Just patch rom and install from recovery
Nice Thread
Thanks for usefull thread
No problem. It's even another now
I couldn't get the 5.1.1 ROM to work. It says it's unsupported and fails to flash.
Sent from my SM-G925T using Tapatalk
Hopefully we get more Roms options soon, loved this on my S3 switching between 2 different setups, currently we have what, one Rom 5.02 and a stock 5.1.1 without root?
Sent from my SM-G925T using XDA Free mobile app
Yes I agree thanks for making this thread!
App sharing problem
I didn't check the box that it says to check if you want to share info from one partition to another but it is sharing. How do I stop that? I want to have one ROM for work and one for personal without the info of pics crossing over.
s6 edge?
This is posted in the tmobile s6 edge forum but you only mention using this with the s4. Is this actually usable on the s6 edge? I checked the threads of chenxiaolong from post #1 but I only saw reference to the s4 in his threads as well.
I'd like to dual boot my phone but this thread doesn't make me believe it works for us s6 edge users.
Yeah using it noe
It seems arter kernel not supported.
eweo911 said:
This is posted in the tmobile s6 edge forum but you only mention using this with the s4. Is this actually usable on the s6 edge? I checked the threads of chenxiaolong from post #1 but I only saw reference to the s4 in his threads as well.
I'd like to dual boot my phone but this thread doesn't make me believe it works for us s6 edge users.
Click to expand...
Click to collapse
Jsut need to know if this is currently working for S6 Edge
I have the g920 flat s6t and haven't have any issues duel booting. Always had Sickness roms as my primary and with all his versions i had no issues with duel boot but now in his latest v9 built i am unable to duel boot. When i reboot secondary rom it stays at samsung boot logo, it does not go into recovery. When i flash the utility zip to switch to primary rom it boot loops and goes to recovery and none of the roms boots..so i reflashed sick as hell v7 and its duel booting good. The rom developer told me he have no change anything from v7 to v9 he just added some tweaks and xtra apps, don't understand why is not duel booting with latest rom. I did flashed the log file. I will attach it.

[DEV][KERNEL[MOD] Lenovo A6020 L36 / A46 (Vibe K5 / Vibe K5 Plus)

Hello people. My device is not listed in DEVDB options, so I must have to create this thread instead a DEVDB project. If it is wrong, please advice me.
-----------------------------------------------------------------------------------
I'm creating this thread to give us more space to create a ROM for our device, like a step-by-step to things we have to do or not. I'll edit this thread with more details when I have more time, but for now, thats what we have done, and I think we need to do:
Root (Thanks to Chainfire)
Custom recovery (thanks to Shreps)
Choose a kitchen to manage the ROM
Discover kernel options
Choose apps to add/remove
A custom app to manage various phone settings, like kernel options, battery settings, and others
Edit build.prop to get right device management
Edit boot.img to have unsecure boot
Help me to add or remove things to the list above, to have a structured plan to build the whole ROM (boot, recovey, system), because last time I manage a ROM was a long time ago, I think about 2010 (was on Xperia X2), and was only for me (my "project" wasn't public). From that time for actual days, I don't manage/create nothing "solid" and structured anymore... And I'm sure all things have changed/updated/died/etc...
To help start familiar with new kitchens (the last was DSIXDA Kitchen), I have choose SuperR's Kitchen. I try to use it inside Cygwin, but it gives me an error while opening, I'm investigating this. So, I setup a virtual machine with Ubuntu in my house, and I have remote access to it from my work. In this VM, I setup the kitchen and (after a time to setup the right Java) it is running fine.
So, let's go, people. I'll edit this post as news are coming.
[UPDATE]What I have found:
If "Google Photos" is removed, then Gallery don't crop wallpapers, or adds a image to a contact;
Titanium Backup can't uninstall/integrate some apps and updates. It says "apk not found". I'm trying to use Link2SD;
SuperSU "lose" the configuration, forcing me to remove the apps I added, then run the app again. I'm looking for this
If you remove "Theme Center", you can't change wallpaper and Lenovo Home gives an error!
If you remove "Google App", "Now Launcher" gives errors about force close.
If you remove LenovoID, Settings force close when try to enter "accounts".
If we integrate "Google Play Services" and hard reset the phone, it force close at second stage of first registration.
romulocarlos said:
Hello people. My device is not listed in DEVDB options, so I must have to create this thread instead a DEVDB project. If it is wrong, please advice me.
-----------------------------------------------------------------------------------
I'm creating this thread to give us more space to create a ROM for our device, like a step-by-step to things we have to do or not. I'll edit this thread with more details when I have more time, but for now, thats what we have done, and I think we need to do:
Root (Thanks to Chainfire)
Custom recovery (thanks to Shreps)
Choose a kitchen to manage the ROM
Discover kernel options
Choose apps to add/remove
A custom app to manage various phone settings, like kernel options, battery settings, and others
Edit build.prop to get right device management
Edit boot.img to have unsecure boot
Help me to add or remove things to the list above, to have a structured plan to build the whole ROM (boot, recovey, system), because last time I manage a ROM was a long time ago, I think about 2010 (was on Xperia X2), and was only for me (my "project" wasn't public). From that time for actual days, I don't manage/create nothing "solid" and structured anymore... And I'm sure all things have changed/updated/died/etc...
To help start familiar with new kitchens (the last was DSIXDA Kitchen), I have choose SuperR's Kitchen. I try to use it inside Cygwin, but it gives me an error while opening, I'm investigating this. So, I setup a virtual machine with Ubuntu in my house, and I have remote access to it from my work. In this VM, I setup the kitchen and (after a time to setup the right Java) it is running fine.
So, let's go, people. I'll edit this post as news are coming.
Click to expand...
Click to collapse
nice thread
romulocarlos said:
Hello people. My device is not listed in DEVDB options, so I must have to create this thread instead a DEVDB project. If it is wrong, please advice me.
-----------------------------------------------------------------------------------
[*]Titanium Backup can't uninstall/integrate some apps and updates. It says "apk not found". I'm trying to use Link2SD;
Click to expand...
Click to collapse
I randomly found this thread and noted that you are facing this issue with TB being unable to uninstall some apps. I had the same issue with my device. If you are rooted, navigate to /Cust/Channel/Preinstalled/apps folder (sometimes the "channel" folder may not exist) from your file explorer, you will find the apks for the apps that TB fails to find apk for. Remove the APKs that you don't need and/or move them wherever you feel is right for them, all set
nandakalyan said:
I randomly found this thread and noted that you are facing this issue with TB being unable to uninstall some apps. I had the same issue with my device. If you are rooted, navigate to /Cust/Channel/Preinstalled/apps folder (sometimes the "channel" folder may not exist) from your file explorer, you will find the apks for the apps that TB fails to find apk for. Remove the APKs that you don't need and/or move them wherever you feel is right for them, all set
Click to expand...
Click to collapse
Yeah, I already see that folder. Seems TB can't handle with folders different from /system/app and /data/app
romulocarlos said:
Yeah, I already see that folder. Seems TB can't handle with folders different from /system/app and /data/app
Click to expand...
Click to collapse
Yes, that seems to be the case for LP and MM factory images that have this folder, it is a TB limitation even on my device, unless I am running CM or AOSP based ROMs hope the workaround helps
nandakalyan said:
Yes, that seems to be the case for LP and MM factory images that have this folder, it is a TB limitation even on my device, unless I am running CM or AOSP based ROMs hope the workaround helps
Click to expand...
Click to collapse
You have A6020 with CM??
romulocarlos said:
You have A6020 with CM??
Click to expand...
Click to collapse
No, I have an Honor 5x L-22, we have a CM build for our device but I chanced on this issue when I was running stock and wanted to get rid of all that bloat. So just sharing what I discovered
nandakalyan said:
No, I have an Honor 5x L-22, we have a CM build for our device but I chanced on this issue when I was running stock and wanted to get rid of all that bloat. So just sharing what I discovered
Click to expand...
Click to collapse
Ok!! Thanks!
Can you please tell me how the camera quality is..I'm planning on buying this mobile...so please let me know
sudheer4188 said:
Can you please tell me how the camera quality is..I'm planning on buying this mobile...so please let me know
Click to expand...
Click to collapse
It's not great but for the price is quite good
Did you see kernel source code from lenovo's website for Vibe K5?
lucasdeeiroz said:
Did you see kernel source code from lenovo's website for Vibe K5?
Click to expand...
Click to collapse
Yes
Sent from my Lenovo A6020l36 using XDA-Developers mobile app
romulocarlos said:
Hello people. My device is not listed in DEVDB options, so I must have to create this thread instead a DEVDB project. If it is wrong, please advice me.
-----------------------------------------------------------------------------------
I'm creating this thread to give us more space to create a ROM for our device, like a step-by-step to things we have to do or not. I'll edit this thread with more details when I have more time, but for now, thats what we have done, and I think we need to do:
Root (Thanks to Chainfire)
Custom recovery (thanks to Shreps)
Choose a kitchen to manage the ROM
Discover kernel options
Choose apps to add/remove
A custom app to manage various phone settings, like kernel options, battery settings, and others
Edit build.prop to get right device management
Edit boot.img to have unsecure boot
Help me to add or remove things to the list above, to have a structured plan to build the whole ROM (boot, recovey, system), because last time I manage a ROM was a long time ago, I think about 2010 (was on Xperia X2), and was only for me (my "project" wasn't public). From that time for actual days, I don't manage/create nothing "solid" and structured anymore... And I'm sure all things have changed/updated/died/etc...
To help start familiar with new kitchens (the last was DSIXDA Kitchen), I have choose SuperR's Kitchen. I try to use it inside Cygwin, but it gives me an error while opening, I'm investigating this. So, I setup a virtual machine with Ubuntu in my house, and I have remote access to it from my work. In this VM, I setup the kitchen and (after a time to setup the right Java) it is running fine.
So, let's go, people. I'll edit this post as news are coming.
[UPDATE]What I have found:
If "Google Photos" is removed, then Gallery don't crop wallpapers, or adds a image to a contact;
Titanium Backup can't uninstall/integrate some apps and updates. It says "apk not found". I'm trying to use Link2SD;
SuperSU "lose" the configuration, forcing me to remove the apps I added, then run the app again. I'm looking for this
If you remove "Theme Center", you can't change wallpaper and Lenovo Home gives an error!
If you remove "Google App", "Now Launcher" gives errors about force close.
If you remove LenovoID, Settings force close when try to enter "accounts".
If we integrate "Google Play Services" and hard reset the phone, it force close at second stage of first registration.
Click to expand...
Click to collapse
hey can you tell me how root it and install TWRP.. thanks
nayakdinesh said:
hey can you tell me how root it and install TWRP.. thanks
Click to expand...
Click to collapse
Please, do not quote OP. Here is the link for what you requested: http://forum.xda-developers.com/showthread.php?t=3391100
Enviado de meu pac_A6020 usando Tapatalk
is there any custom kernel for this phone which cn provide dt2w ...
heeeelpp
I need rom L35 and not of a40 , my phone is stuck in the screen lenovo without TWRP and without backup
jrfirmino said:
I need rom L35 and not of a40 , my phone is stuck in the screen lenovo without TWRP and without backup
Click to expand...
Click to collapse
Do not spam at XDA or you won't get any help. Search an appropriate thread to make your question AFTER reading all posts from there.
Here isn't the appropriate thread.
Why did the OP marked [kernel] if there's not a kernel available here? That's not fare.
louiscypherbr said:
Why did the OP marked [kernel] if there's not a kernel available here? That's not fare.
Click to expand...
Click to collapse
@romulocarlos
No kernel yet ?
louiscypherbr said:
Why did the OP marked [kernel] if there's not a kernel available here? That's not fare.
Click to expand...
Click to collapse
The original idea was build a kernel, too.
Hnk1 said:
@romulocarlos
No kernel yet ?
Click to expand...
Click to collapse
No. Now we have CM13, thanks to Shreps, so this thread is obsolete.

Minimalistic android Bootlogo (N/A covered with latest bootloader support)

Hello everyone, I know lots of bootlogo for Moto G4/G4 PLUS are available here on XDA which covers N/A. But I've seen most of them are based on Marshmallow Stock Bootlogo, But latest bootloader (v1.06) has an option 'Switch_tools_mode' which was not available in previous bootloaders. AS a result that option was not covered in most of those bootlogos. I have created a very minimalistic bootlogo from scratch based on latest Nougat NPJS25.93-14-10 firmware which only covers the N/A with least possible white area on bootlogo.
As many Moto G4/G4 PLUS users have screen retention/ screen burn issue (including myself), large bright white area on bootlogo causes screen retention after booting into ROM or TWRP. Keeping this on mind, I tried to create an android logo with a pure black background just covering the N/A spot with white.
I made a TWRP flashable zip file which can change bootlogo from TWRP (no need to flash using fastboot from a computer). Still anyone wanting to flash from fastboot or for those who are on stock recovery , the 'logo.bin' file can be found inside the zip.
Anyone can create bootlogo (I'm out of ideas) with the help of this thread https://forum.xda-developers.com/moto-g4-plus/themes/guide-t3588090. And don't forget to use the stock bootlogo from latest Nougat firmware which can be found on this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138.
Hope this helped. Happy flashing.
Can someone please make a TWRP flashable zip bootlogo version of my new designed Motorola g4 plus 2019 bootlogo
https://drive.google.com/file/d/14yRSvlg0C0Bhn2S5unfJeBFklP6UlskS/view?usp=drivesdk
There you go
AdityaCyberpunk said:
Can someone please make a TWRP flashable zip bootlogo version of my new designed Motorola g4 plus 2019 bootlogo
https://drive.google.com/file/d/14yRSvlg0C0Bhn2S5unfJeBFklP6UlskS/view?usp=drivesdk
Click to expand...
Click to collapse
Attached zip is TWRP flashable created from latest stable oreo 8.1 OPJ28.111-22 fastboot image replaced with the requested image. Sorry for being late. Happy flashing. :good:
Thank you!
thanx!
Hi c-sayan thanks for your work. can you make me a stock logo for lastest Oreo official? thanks in advance! :good:
Provide reference image
gambitos said:
Hi c-sayan thanks for your work. can you make me a stock logo for lastest Oreo official? thanks in advance! :good:
Click to expand...
Click to collapse
Sorry for late response, due to a super cyclone in my area internet connectivity was unavailable for several days.
What do you mean by stock logo? It'll be helpful if you could provide the logo image in png or jpeg format but remember it has to be pure white in the area of "id:N/A".
SayanChakroborty said:
Sorry for late response, due to a super cyclone in my area internet connectivity was unavailable for several days.
What do you mean by stock logo? It'll be helpful if you could provide the logo image in png or jpeg format but remember it has to be pure white in the area of "id:N/A".
Click to expand...
Click to collapse
No problem man, i don't know what you mean by providing you the logo file in png or jpeg. The only thing i can get is the original logo.bin. from firmware
Regards
gambitos said:
No problem man, i don't know what you mean by providing you the logo file in png or jpeg. The only thing i can get is the original logo.bin. from firmware
Regards
Click to expand...
Click to collapse
By Logo file I meant the image or picture you want as the logo of your device. You see, the stock logo from Moto does not cover the N/A section which is the sole purpose of this thread. Now I think we are not getting each other, so it would be great if you could explain what you actually want. Do you want the stock unmodified bootlogo file from latest firmware update or Do you want a bootlogo from the latest firmware modified with a different picture?

[BOOT ANIMATION] Motorola Series [Project 9 ¾]

I have made some Boot Animations for Motorola phones 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.​
Don't forget to watch the previews on Imgur before downloading your desired Boot Animations
PratyushJayachandran said:
Don't forget to watch the previews on Imgur before downloading your desired Boot Animations
Click to expand...
Click to collapse
But you do know that Montana doesn't have stable android Q yet? Whatever
Still nice tho!
Some random said:
But you do know that Montana doesn't have stable android Q yet? Whatever
Still nice tho!
Click to expand...
Click to collapse
Actually I didn't know. The project was for Potter originally. Since it's for Full HD display, I made post for all Full HD moto phones. The files can be extracted and applied on Android Pie and below too. Just that the installer I made won't work. I had to pretty much make the installer from scratch and I'm not familiar with edify scripts. Android 10 has system as root so the location was different from all older Androids.
Let's see... I'll update if I can and post here.
Thanks for bringing to notice. I thought everyone was on 10 by now.
Prat.yushJayachandran said:
Actually I didn't know. The project was for Potter originally. Since it's for Full HD display, I made post for all Full HD moto phones. The files can be extracted and applied on Android Pie and below too. Just that the installer I made won't work. I had to pretty much make the installer from scratch and I'm not familiar with edify scripts. Android 10 has system as root so the location was different from all older Androids.
Let's see... I'll update if I can and post here.
Thanks for bringing to notice. I thought everyone was on 10 by now.
Click to expand...
Click to collapse
Well technically we Have Q, it's just not very good (Gsi Roms), still usable, but nothing in comparison (especially with bugs) to lineage or something, also, System as root development is actually main focus for Montana right now, thought I might mention that
Some random said:
Well technically we Have Q, it's just not very good (Gsi Roms), still usable, but nothing in comparison (especially with bugs) to lineage or something, also, System as root development is actually main focus for Montana right now, thought I might mention that
Click to expand...
Click to collapse
The mounting of system partition is different for Android 10 and all the versions before it. The code was already convoluted to address the different locations of boot animation by different ROMs. I'll try. I guess some other Moto phones are also on Pie.
Some random said:
Well technically we Have Q, it's just not very good (Gsi Roms), still usable, but nothing in comparison (especially with bugs) to lineage or something, also, System as root development is actually main focus for Montana right now, thought I might mention that
Click to expand...
Click to collapse
Files updated and now supports all custom ROMs regardless of Android version.
Thanks for helping me test it out
PratyushJayachandran said:
Files updated and now supports all custom ROMs regardless of Android version.
Thanks for helping me test it out
Click to expand...
Click to collapse
No problem

Categories

Resources