Develop Bugs

[Q] De-Odex Stock Rom?

Hi, I would like to De-Odex the rom I currently have on my phone.
Is there an easy way to do this?
I've read:
http://www.droidforums.net/forum/xeudoxus/47283-release-xultimate.html
and
http://www.droidxforums.com/forum/droid-x-themes/4620-how-manually-deodex-your-phone.html (there is also a post about this on here)
The xUltimate tool will not work for me, so I need another option.
Phone: HTC Evo
ROM: Stock 3.29 OTA
Rooted (ofc)
Thanks for the help.

Sorry if this is no help, but a deodexed version of the 3.29 OTA is posted somewhere in the dev section. Is there a particular reason why you want to deodex it yourself?
Sent from my PC36100 using XDA App

TheMagicalSock said:
Sorry if this is no help, but a deodexed version of the 3.29 OTA is posted somewhere in the dev section. Is there a particular reason why you want to deodex it yourself?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I've been switching between roms but I keep coming back to my original stock one. It's still odex'd and I would like to theme the battery icon on the status bar without having to set everything back up on a fresh rom. Since it reads half when 80% of my battery is remaining.
Thanks for the quick response.
Sent from my Evo using XDA App.

and you said this didnt work for you?
i didnt even know you could deodex your own rom!
going to try this soon!

Max_Pain said:
and you said this didnt work for you?
i didnt even know you could deodex your own rom!
going to try this soon!
Click to expand...
Click to collapse
It wasn't that it didn't work.
I just got an error with Java, not sure how to fix it. Some said to re install java, but i've installed JRE and JDK from 5u20 to 6u21 (32 and 64 bit). Everything I tried gave the same error.
I am going to try asking on their forum and see if they can tell me what I did wrong.
I have a feeling it has to do with the 3.29 OTA update. :-/
Good luck and if you get it to work please let me know your setup.
and if you can't run step 3 let me know... that way I am not the only one to seem that crazy.
option 1 and 2 just adb pulls your /system/apps and your framework.

just got stuck starting option 3:
Starting AccountSyncManager.odex
*Deodexing...
Error occurred while loading boot class path files. Aborting.
org.jf.dexlib.Code.Analysis.ClassPath$ClassNotFoundException....
lower it says
at org.jf.baksmali.baksmali.dissambleDexFile(baksmali.java:103)
and it just gives some more errors until i close it down
i was sooo excited to get this done!

Ahhh! I'll see what I can find out on their forums.
Despite the tutorial saying "Manually De-Odex Your Phone" I think it may be just for droid phones. It was posted in the Moto Droid sections of the forums.
Here is the error I was getting:
Code:
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: java.lang.NullPointerException
at java.util.Properties$LineReader.readLine(Unknown Source)
at java.util.Properties.load0(Unknown Source)
at java.util.Properties.load(Unknown Source)
at org.jf.baksmali.main.<clinit>(main.java:69)
Could not find the main class: org.jf.baksmali.main. Program will exit.
Press any key to continue . . .

dang it...
i just updated my java and nothing, still same error. well let me know what they say. i was about to make an account to post over there but i'll let you do it then.
keep me updated!

Max_Pain said:
dang it...
i just updated my java and nothing, still same error. well let me know what they say. i was about to make an account to post over there but i'll let you do it then.
keep me updated!
Click to expand...
Click to collapse
If you want to add anything my post is located:
http://www.droidforums.net/forum/xeudoxus/85223-xultimate-errors.html
Both our problems have "org.jf.baksmali" involved.
Hopefully we'll have some answers soon.

well i ran a test and everything said pass, including the odex and deodex. i installed the latest java, and same problem. i had the phone originally as mass storage, so i tried under charge only, and still same problem.
i really hope we get a solution to this

I did some more reading and it seems that app is designed specifically for droid x phones.
I'm now going to try a more hands on approach using avabox...will update tonight.
Swyped from an HTC Evo on MetroPCS...

Max_Pain said:
I did some more reading and it seems that app is designed specifically for droid x phones.
I'm now going to try a more hands on approach using avabox...will update tonight.
Swyped from an HTC Evo on MetroPCS...
Click to expand...
Click to collapse
Were you able to get it DeOdexed?
I found this after some searching... It seems to be the LONG way to deodex an apk. It was written in 2009 so idk how reliable it will be.
http://androidnetwork.org/forum/viewtopic.php?f=11&t=55
Edit: Link to Avabox: http://forum.xda-developers.com/showthread.php?t=697459
[UPDATE] I tried Avabox and it de-odexed all of the files that I adb pulled. I copied the De-Odexed files back to their respective folder on the /system/, and deleted "rm /system/app/*.odex" (Removing all the .odex files) and rebooted.
I got stuck on the white "HTC Evo 4G" screen and could not get passed it.
I am not sure what I messed up. Maybe I need to resign the files? I'll try that tomorrow.
Let me know how your attempt went. :]

When I left for school I left the script deodexing my app folder...it seems to have done the job and there were no errors. It's doing the process for the framework files now.
Once I move it over to the phone we 'll see if it worked...
I'll update here when I find out...
Swyped from an HTC Evo on MetroPCS...

i just tried that too and i got stock in a bootloop.
the avabox script does deodex all the app files. it doesn't do that for the framework files...it seems it'll only deodex .apk files.
anyways, i deleted everything from my /system/app folder and then pushed over the deodexed apks...i also did this for the two apk files from system/framework and the phone did the bootloop thing. so i put back the original /system/framework files, effectively only leaving changed the contents of /framework/app/ and still, bootlooping.
i'm restoring right now...i'll try it some more at another time.
let me know if you figure it out!

I was reading some of the comments on this thread(http://forum.xda-developers.com/showthread.php?t=598026) They we're saying about problems with de-odexing the framework.
Do we need to resign system apps before we push them back?
I am optimizing my apks now, going to batch resign then try putting just the apks back on.

Well I messages avalaunchmods asking the same thing...if anyone knows it should be him...
Update if you get it working please!
Swyped from an HTC Evo on MetroPCS...

Unfortunately, I still don't have any good news. :[
I tried resigning the de-odexed apk's and replacing the ones on my phone.
This got stuck at the white HTC Evo 4G screen.
This failed
Then I optimized, signed, and zipaligned.
This threw me into an actual boot loop. (I was excited... It's the first boot loop i've gotten.)
This failed.
Here is some semi-less-bad news.
I used http://circle.glx.nl/ to make a flashable update.zip for theme-ing. I Flashed it with success and was able to get to the lock screen. Sense UI along with just about every other system app kept force closing.
But I was able to successfully (even though I got FC's) theme and boot using that kitchen.
I am going to mess around with the different settings there and see if I can atleast theme my phone.
Any luck with your attempts?

i was at school all day - no news from me. this is very discouraging though.
i'm surprised nobody else has chimed in! considering how many people are making and releasing roms, some people must know what's going on here

Good news (kinda)
I was able to theme my framework-res.apk without any errors or FC's.
I didn't do anything to De-Odex it but it accepted the theme when I manually edited it.
There must be an xml that scripts how the battery is displaying %'s
since I have 89% of my battery remaining but the themed battery is showing 80%.
I'll dig around and see where it is and add it to my next framework recompile.
We're you interested in just themeing or the whole de-odexing (apps & framework)
If you want to theme it i'll write up a decent tutorial on what I did.
If not I'll write up a quick tutorial for the next root newbie who wants to theme.
Going to test run it and make sure I didn't mess much up.
Edit3: The bad, it would appear that you can't modify the .xml's of the framework. You can only change the pictures.
So the battery wont be able to have the exact %.
Modifying of any .xml leads me to a boot loop.
Tips are appreciated on fixing this.
I'll keep trying.

so here is what i've learned.
i had modified both .com.htc.resources and framework-res before. those files, at least in my rom, are not odexed. everything else in the framework folder is a mix of files, .jar files and other formats, including services.jar, which is odexed. that's why if we change the services.jar file, without the phone being deodexed, it wont work.
that's why i want to deodex my rom. i have too many changes already and dont want to re-do them in another, deodexed rom.
my main interest in deodexing the rom is to have the working battery percentage on top (which used to work on THIS rom before, without deodexing???) and to have a transparent notification tray.
and from there being able to make any other changes as they come up...
i'll see when i have some more time to try out other options, but chances are you will have time before me, so keep updating!

[ROM] CM 7 for BRAVO (No modifications) Camcorder working!

CM7 for BRAVO (No modifications)!!
http://www.megaupload.com/?d=HKY4OVEI
Try it and post any issues or problem!!
Well all this is thanks to rdannar, I just take his lastest CM7 rom (CM7 V5) and changed everything back to stock, accelerometer and backlight buttons are working also.
No action snap is installed, to install Fast burst Camera (zoom and autofocus) go to this thread to download it: http://forum.xda-developers.com/showthread.php?t=1272161
I used 2nd init defy and remember to follow the next (always used) steps:
1) copy the rom to your sdcard
2) boot into 2nd init defy -> recovery -> stable recovery
3) wipe data/factory reset
4) wipe cache partition
5) advance -> wipe dalvik cache
6) install zip from sdcard -> choose zip from sdcard
7) reboot
To take photos use Fast Burst Camera.
Do not use Defy Baseband Switcher if your 3G is working!!

I'm liking it so far!
Is there any way future ones (at least once you get to "production" runs) could NOT include the old swype? Sort of a pain to remove it to install Swype beta...

great rom! at the moment after two days of use I have not found still no defect. (before I used the rom v2 of rdannar). thanks

This is sweet. Camera works fine, camera advanced lite also works like a charm.
https://market.android.com/details?id=com.mnapps.cameraadvancelite
Sent from my MB520 using xda premium

mikiemc73 said:
This is sweet. Camera works fine, camera advanced lite also works like a charm.
Click to expand...
Click to collapse
With auto-focus? What resolution?

mikiemc73 said:
This is sweet. Camera works fine, camera advanced lite also works like a charm.
https://market.android.com/details?id=com.mnapps.cameraadvancelite
Sent from my MB520 using xda premium
Click to expand...
Click to collapse
Im using it now in gingerblur and no success, can you tell us if we have to change something?

is there any way i can have live wallpapers back
edit: i cant get cam corder to work and advance camera lite jsut takes the picture but doesnt save it correctly it just makes it corrupt besides that the rom is awesome

mikiemc73 said:
This is sweet. Camera works fine, camera advanced lite also works like a charm.
https://market.android.com/details?id=com.mnapps.cameraadvancelite
Sent from my MB520 using xda premium
Click to expand...
Click to collapse
Camera adv lite did not save pictures when i tried it with this CM7. can anyone confirm?

snnyby said:
Camera adv lite did not save pictures when i tried it with this CM7. can anyone confirm?
Click to expand...
Click to collapse
I confirm its not working

I'm working on getting camera and camcorder working with the stock camera app. I'm using the CM7 v2 rom from rdannar but adjusting some of the files in the system/framework folder. Anyone else tried this?
http://forum.xda-developers.com/showthread.php?t=1326718 Link to thread I was using.

Junkyardjames87 said:
I'm working on getting camera and camcorder working with the stock camera app. I'm using the CM7 v2 rom from rdannar but adjusting some of the files in the system/framework folder. Anyone else tried this?
http://forum.xda-developers.com/showthread.php?t=1326718 Link to thread I was using.
Click to expand...
Click to collapse
Nice, I think everybody should help so we get camera working.
Thats the only issue we have to work with.
Defy developers do the rest!!

STUCK!
Ok I got the camera to preview and it clicks if i use the settings that match the stock Bravo but all it saves as a file is a black screen. Can somebody please give me the stock 2.2.1 sbf file decompiled and changed to a .zip or something.
For something at least I have fast burst camera up and working. Now that I think, I need to get source codes. All of the codes for 2.2.1 camera for bravo, and the codes that are in the gingerbread CM7 rom.

Junkyardjames87 said:
Ok I got the camera to preview and it clicks if i use the settings that match the stock Bravo but all it saves as a file is a black screen. Can somebody please give me the stock 2.2.1 sbf file decompiled and changed to a .zip or something.
For something at least I have fast burst camera up and working. Now that I think, I need to get source codes. All of the codes for 2.2.1 camera for bravo, and the codes that are in the gingerbread CM7 rom.
Click to expand...
Click to collapse
Let me tell you about the source code first:
http://sourceforge.net/projects/bravo.motorola/files/BRAVO ATT/
Get it there.
Once I deodexed a rom but I lost some of the apps to do it, I'll try to do it.
but BravoX RC2 rom's is deodexed:
http://forum.xda-developers.com/showthread.php?t=1065767
I think that could help you, thanks for being working on it.
Im always here

josuearisty said:
Let me tell you about the source code first:
http://sourceforge.net/projects/bravo.motorola/files/BRAVO ATT/
Get it there.
Once I deodexed a rom but I lost some of the apps to do it, I'll try to do it.
but BravoX RC2 rom's is deodexed:
http://forum.xda-developers.com/showthread.php?t=1065767
I think that could help you, thanks for being working on it.
Im always here
Click to expand...
Click to collapse
Thanks! But I'll have to unzip it and see what it all is. I'm not caring about deodexed files I just want something that I can look at on my computer just like the CM7 mods that are zipped and archived. Easier to look at for hours.
Umm, all it gave me was a file called external.tar. What do I do with it? took me two hours to download.
*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*
Ok this is what i'm looking for. Froyo 2.2.1 for the bravo, not in .sbf but in the way it would be if we were using it like the CM7 rom. Opened and in the order just like I can see it on my phone with Super Manager in File Explorer rooted mode. And need to know if some of us want CM7 WITH or WITHOUT BLUR.
I'll just see if I can make two versions. One with and one without so no fighting. But i will need testers.

Junkyardjames87 said:
Thanks! But I'll have to unzip it and see what it all is. I'm not caring about deodexed files I just want something that I can look at on my computer just like the CM7 mods that are zipped and archived. Easier to look at for hours.
Umm, all it gave me was a file called external.tar. What do I do with it? took me two hours to download.
*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*
Ok this is what i'm looking for. Froyo 2.2.1 for the bravo, not in .sbf but in the way it would be if we were using it like the CM7 rom. Opened and in the order just like I can see it on my phone with Super Manager in File Explorer rooted mode. And need to know if some of us want CM7 WITH or WITHOUT BLUR.
I'll just see if I can make two versions. One with and one without so no fighting. But i will need testers.
Click to expand...
Click to collapse
But I think bravox rom is like that. What do you exactly mean?
------------------------------------------------------------------
About external.tar, I havent worked with that before, no codes for me by now, I have just changed files and zipped roms.
Im here to try, my two bravos are fine to test everything.
For me it doesnt matter about having blur or not, but I prefer GINGERBLUR , anyway we need a fully working gingerbread rom. (everthing will come after it)

What I need.
Ok. I need to have the regular 2.2.1 for the bravo in the exact same way as if we downloaded the CM7 rom that is 2.3.4. The regular 2.2.1 that I have now is just the .sbf file for use with RSD Light just in case I really screw up my phone. Just like windows restore............ Anywho i'm working on right now building the stock 2.2.1 bravo file system by using a stock factory bravo and copying all of the root files onto the SD card to put them on my computer. I'll be going through all of the crap and looking at the CM7 roms to find out what is diffrent. I need somebody who can zip the stuff so it can be loaded with 2ndint. This will then allow me to put this newish rom into beta. Or if someone can find or give me the program that zips everything for 2ndint to use. I will attach sometime what I pulled off of my Bravo for a better understanding of what I want.

Junkyardjames87 said:
Ok. I need to have the regular 2.2.1 for the bravo in the exact same way as if we downloaded the CM7 rom that is 2.3.4. The regular 2.2.1 that I have now is just the .sbf file for use with RSD Light just in case I really screw up my phone. Just like windows restore............ Anywho i'm working on right now building the stock 2.2.1 bravo file system by using a stock factory bravo and copying all of the root files onto the SD card to put them on my computer. I'll be going through all of the crap and looking at the CM7 roms to find out what is diffrent. I need somebody who can zip the stuff so it can be loaded with 2ndint. This will then allow me to put this newish rom into beta. Or if someone can find or give me the program that zips everything for 2ndint to use. I will attach sometime what I pulled off of my Bravo for a better understanding of what I want.
Click to expand...
Click to collapse
Ok, I understand now what you mean.
You want to zip the rom and sign it. It is not that?
If you want you can download Cygwin the kitchen its very easy to work with it, but if you want upload some files and let me know where to copy them.
I'll post in some hours where did I get the THE KITCHEN Cygwin, Im going out now!

josuearisty said:
Ok, I understand now what you mean.
You want to zip the rom and sign it. It is not that?
If you want you can download Cygwin the kitchen its very easy to work with it, but if you want upload some files and let me know where to copy them.
I'll post in some hours where did I get the THE KITCHEN Cygwin, Im going out now!
Click to expand...
Click to collapse
Ok i'll do a google search and see what I can do.

CRAP!
Well we'll all have to wait for a while until I get another Bravo. Something, well, someone, who will remain nameless (really not me) decided to wake up in the middle of the night and play with daddys phones on HIS table and CONNECTED to HIS computer. Well it got unplugged and found it's way to another play spot in the bathroom. Can anybody tell me the rest of the story??

Junkyardjames87 said:
Well we'll all have to wait for a while until I get another Bravo. Something, well, someone, who will remain nameless (really not me) decided to wake up in the middle of the night and play with daddys phones on HIS table and CONNECTED to HIS computer. Well it got unplugged and found it's way to another play spot in the bathroom. Can anybody tell me the rest of the story??
Click to expand...
Click to collapse
Oh man, I dont believe it
Now what will we do? Will you buy another one?
---------------------------------------------------------
I dont wanna laught, but was that your wife? did she find something about another woman in your phone?
Women are like that, once something like that happen to me!!

[Q] Installing .zip files in recovery

There are some .zip files that I will install in recovery mode and will confirm installation. When I reboot the phone, the apps or mods that I install will not have installed. I am stock rooted on Galaxy Note 2 on JB. Any ideas or suggestions?
Thanks

Need more info.. and re word it a lil..and what mods are u flashing in what sequence?

twanskys204 said:
Need more info.. and re word it a lil
Click to expand...
Click to collapse
Ok. Example: Say I take a .zip file that you have made for me and I download it. I boot into recovery mode and find the file and flash it, gives me the message that it has completed but when the phone reboots it's no where to be found. Did it not install or is there a place I need to look on my phone that it might be hidden?

just because its a zip file, doesnt mean it has the install routine baked into it..
As Twansky said, what is the file, and what is it for?

wase4711 said:
just because its a zip file, doesnt mean it has the install routine baked into it..
As Twansky said, what is the file, and what is it for?
Click to expand...
Click to collapse
Ok. The files that I've tried would be mods for toggles, keyboards, and different add ons. For the most part, all of the files that I've flashed have worked. The ones that didn't work I'm not disappointed that they didn't, I was just wondering if possibly there was something or somewhere that I needed to look to see if they actually did but needed to activate per say. Could you explain what you mean by "install routine baked in" please. I'm a noob and learning everyday.
Thank you

some of those zip files, were probably just a bunch of individual files, zipped up to save room, and make them just 1 file insted of many..
a "flashable" zip file will have a few folders, one being meta.inf, another being system, along with some others...
post one of those zips that you are having a problem with here, and we will take a look at it..

what ^^^^^^^^^^ Said....g

Wase, let me see if I still have them on my phone. I know a couple that I tried were rom specific but one worked and one didn't. Those are the ones I expected not to work. Give me a minute to see what I still have.

http://db.tt/kXFyYyIJ
This is one that didn't work that is for ROM XXDLL4. Another file that I downloaded is the glass dialer did work. What I guess I'm asking is, why would one work but not the other. I know these were fir that specific rom, I'm just confused on why one would work and not the other.

twanskys204 said:
Need more info.. and re word it a lil..and what mods are u flashing in what sequence?
Click to expand...
Click to collapse
Sorry, I did not answer that part.
Boot into recovery>Find location where file was downloaded>Click to install>Confirm install>Install confirmed>Reboot.
I have tried wiping cache and not wiping cache.

Open up these "zips" and look inside..

yeah, it was a flashable zip..no idea why it wouldnt work, but, as you said, this is not a mod for our phone specifically, so that might be why..Just like anything else electronic, not every rom/mod/flashable file is going to work on every phone; thats just the way it is...

wase4711 said:
yeah, it was a flashable zip..no idea why it wouldnt work, but, as you said, this is not a mod for our phone specifically, so that might be why..Just like anything else electronic, not every rom/mod/flashable file is going to work on every phone; thats just the way it is...
Click to expand...
Click to collapse
Exactly... use caution flashing "flashable" zips unless you know for a fact it accomodates your specific device. You need to look in the META-INF folder and review the updater-script. In there you will see specific BLKs (partitions) which are mounted/extracted/written/unmounted. Devices don't all use the exact same "/dev/block/mmcblk0xx" for /system or /data partitions. Some of these scripts are fairly universal but I've seen others which call specific devblock partitions.

Thank you everyone for the help on this. I finally got brave enough about a hour ago and flashed a custom rom fir the first time.
Thanks again for all the help and info.

[Q] How To Add Root How A Custom Rom?

Hello Everyone,
I'm ik4evr. (Making the SM-T520 rom) =)
Anyway, i'm trying to add root to my custom rom. However, every time I do it using the kitchen, and flash the rom and try to open SuperSU it says binary not installed. I tried manually putting the root files in my room too. Can anyone out there help me with this. Thanks!

ik4evr said:
Hello Everyone,
I'm ik4evr. (Making the SM-T520 rom) =)
Anyway, i'm trying to add root to my custom rom. However, every time I do it using the kitchen, and flash the rom and try to open SuperSU it says binary not installed. I tried manually putting the root files in my room too. Can anyone out there help me with this. Thanks!
Click to expand...
Click to collapse
welcome to my world...it took me about a week of research before i found anything that helped & dont even remember where i read it at now. Long story short....there seems to be an issue with the binaries that the kitchen uses so in the end i finally just copied the su/busybox/init.d files from cleanrom for the T320 & havent had a problem since

THEDEVIOUS1 said:
welcome to my world...it took me about a week of research before i found anything that helped & dont even remember where i read it at now. Long story short....there seems to be an issue with the binaries that the kitchen uses so in the end i finally just copied the su/busybox/init.d files from cleanrom for the T320 & havent had a problem since
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately, that didn't work still =(
Anything else?

ik4evr said:
Thanks for the reply. Unfortunately, that didn't work still =(
Anything else?
Click to expand...
Click to collapse
If that didnt work then it might be your updater-script...once again just copy the one from a known working deice with an exynos cpu & 4.4.2 (N9000 MAYBE?) then u should be ok. Also...did u swap the daemonsu file in xbin as well? Another thing...delete the su located in "bin" & make sure its in "xbin". The last thing i can think of...did u unpack the boot.img & change the value in the dfault.prop to make it non-secure?
edit: I was just thinking...i noticed u said "supersu" but every guide ive seen added "superuser" instead so swap that too. U should be able to include either but mine didnt work either until i switched them although it could have been coincidence since i also made all of the rest of the alterations around the same time...if u notice in my thread i told users to go download supersu AFTER they flash just to be safe but now that i have it working i'll probably try changing apps again for the next version to eliminate a step

where do I dl twrp for tab pro 10.1 wifi?
I only see 10.1 tab pro lte ...not wifi?
Thanks

[GUIDE] [MOD] [ROOT] Enable DARK Boot Animation while on Dark mode

Hello.
After testing some custom ROMs I've noticed a feature that I thought it was quite cool... the boot animation changed to dark when the dark mode was enabled while running the system.
Decided to investigate this feature and realized that this could have been already implemented on our devices (at least on Android 10 ROMs) if the "media" folder was present on /product instead of /system. Unfortunately it wasn't so I had to come up with a method to get this running on stock ROMs.
The method I've came up with is not "elegant" at all but, hey, it gets the job done, and also, it will work with any light/dark boot animation already released (Pixel, Evo, Havoc, etc...).
How to:
Download both files, present on this thread attachments, and store them on your device (for instance, on Download folder)
Install any root explorer (I'm using FX File Explorer...but you may use any explorer with root permissions)
Install MacroDroid App
Extract the content of Auto_Dark_Based_On_Daylight.zip file in order to obtain Auto_Dark_Based_On_Daylight.macro
Create a backup of your current bootanimation.zip file (just rename it to bootanimation_BKP.zip or something like that, the original file is on /system/media/)
Install Typhus_Themed_Boot_Animation.zip Magisk module and reboot your phone.
Import the Auto_Dark_Based_On_Daylight.macro to Macrodroid (see the Image Tutorial if you don't know how to do this)
Test the Sunset trigger
Reboot your device
Enjoy your dark boot animation while running your system on dark mode and vice versa
NOTES:
1 - As stated, this method will work with any boot animation out there. You just need to replace the zip files inside the "bootanim" folder you will find inside the zip file
2 - Yes, this WILL break OTA since we're mounting system as R/W to do this. I don't mind...I know how to install an OTA when it arrives, so I'm fine with this. Please don't ask here how to install OTA when it arrives...there are a lot of posts and threads here on XDA where people (myself included) already debated that subject.
3 - Didn't understand the method? Need more help? CHECK THIS Image Tutorial!!
Cheers and enjoy!

Does it work only with stock rom?

giacomo_bragagnolo_02 said:
Does it work only with stock rom?
Click to expand...
Click to collapse
No, this will work with any ROM, any device and for any Android version if running AOSP based ROMs.
BUT it's possible that if, your using a custom Android 10 ROM, this isn't needed since it may be already implemented by the developer.
Check if you have a /product/media folder. If you do, then all you have to do is to put the bootanimation-dark.zip file on that folder and it will work without the need to do all the other things.
Cheers!

It works so good but splash is still in white

alvin182 said:
It works so good but splash is still in white
Click to expand...
Click to collapse
Yes, indeed it is. Don't really know where the splash images are stored on Mi A3. They're not on splash.img. If I knew where they were I would change it, obviously.
Really, this is something that I've been wondering about since day one....where the hell are the freakin' splash images stored!!?? Something so simple for almost ALL other devices out there turns to be a riddle on Mi A3....

Typhus_ said:
Yes, indeed it is. Don't really know where the splash images are stored on Mi A3. They're not on splash.img. If I knew where they were I would change it, obviously.
Really, this is something that I've been wondering about since day one....where the hell are the freakin' splash images stored!!?? Something so simple for almost ALL other devices out there turns to be a riddle on Mi A3....
Click to expand...
Click to collapse
hahaha no worries it's good like this im gonna save up too many white pixels in the boot so xD.... thanks for your work!

Most probably the splash image is embedded in the bootloader or kernel
I've made a Magisk Module with the dark one, it's utterly simple, but this way you can do it systemlessly.

bttcp12 said:
Most probably the splash image is embedded in the bootloader or kernel
I've made a Magisk Module with the dark one, it's utterly simple, but this way you can do it systemlessly.
Click to expand...
Click to collapse
First of all, thank you for your contribution.
I know I could have made a Magisk module to do this. But, that way, the boot animation wouldn't change dynamically, it would be always dark and that wasn't my objective.
Of course, if your goal is to always have it dark, then you can use the module to "replace" systemlessly the bootanimation.zip file.
On a side note, I've tried to include this feature on the Pixel Theme, which is a Magisk module, but, unfortunately, it's not possible to symlink files, or folders, from files, or folders, that only exist "systemlessly" marked as read only. That's why this method has to be done like I've explained on the OP.
I've even tried to include a /porduct/media folder with the zip files inside the module....but that didn't work as well. You see, /product is a read-only file system and, for this to work, it had to be mounted as read write at boot time, so that it could be read while booting, and that would have to be made at kernel ramdisk level. Don't think it's worth the trouble just to have a boot animation that changes dynamically.
Tried, as well, to include the files on any other folder that could be symlinked (like /vendor/overlay/media). They were symlinked all right...but Android doesn't read that folder at boot time....so yeah, I've gave up and came up with the method explained here.
Anyway, thanks for your interest and, regarding the splash image....my knowledge isn't enough to figure out bootloader and/or kernel stuff.
Maybe @paul89rulez could help us with this....
Cheers!

Its looking so tough for me. ??
Is there any easier way?

reyad019 said:
Its looking so tough for me. ??
Is there any easier way?
Click to expand...
Click to collapse
Follow the image tutorial. Have you tried that?

bttcp12 said:
Most probably the splash image is embedded in the bootloader or kernel
I've made a Magisk Module with the dark one, it's utterly simple, but this way you can do it systemlessly.
Click to expand...
Click to collapse
Thanks for the module, but for some reason I'm not able to install via Magisk, so I had to flash it via recovery, btw everything works fine (except for the splashscreen ofc), thanks for your help

Just found where the splash images, as well as battery images, etc are stored.
They're on xbl.elf
Just have to figure out how to unpack and repack this safely in order to change the images.
Cheers!!

Good Luck Man, wish you succeed

Typhus_ said:
Just found where the splash images, as well as battery images, etc are stored.
They're on xbl.elf
Just have to figure out how to unpack and repack this safely in order to change the images.
Cheers!!
Click to expand...
Click to collapse
Sorry for the delay, just read the notification.
Glad you found where the images are stored, but be careful xbl its a bad partition to mess with.
You may want to read this article:
https://worthdoingbadly.com/qcomxbl/
Theoretically, with this tool and 7zip you can extrac the xbl, and if you know wich files you have to swap, repack it fastly. But messing with the bootloader its dangerous.
It's worth it?

paul89rulez said:
Sorry for the delay, just read the notification.
Glad you found where the images are stored, but be careful xbl its a bad partition to mess with.
Click to expand...
Click to collapse
Yes, I know. For the time being I just dropped this subject. It's not worth the risk.
Cheers!

it works
giacomo_bragagnolo_02 said:
Does it work only with stock rom?
Click to expand...
Click to collapse
Yes, it works in my stock rom (11.0.15.0)

New method to achieve this feature by using a Magisk module has been added on the OP.
Enjoy.
Cheers!

Typhus_ said:
New method to achieve this feature by using a Magisk module has been added on the OP.
Enjoy.
Cheers!
Click to expand...
Click to collapse
I can't see the magisk file
Thanks for your work

kosmasgr said:
I can't see the magisk file
Thanks for your work
Click to expand...
Click to collapse
It's on the attachments on the first post.

thanks so much... but 1 q. is it eat battery?? macrodroid?