Related
Hello my name is P3Droid,
We (TBH) have a lot of experience in Motorola phones and hacking. This experience dates back to the Razr days.
Here is a word of caution. Do no delete apps from the System partition, I would suggest you only rename them to .bak. When Motorola pushes updates each of the files undergoes a hash check, if the file has been manipulated or is missing the entire update will fail.
Until a system only sbf or similar is released, unless you make a back up with bootstrap and recovery, you will eliminate your ability to take updates moving forward.
You can remove many of the stock apps without rooting just by using the built in app manager.
Those apps are in /data it is the apps that are in /system that count.
jimmydafish said:
Hello my name is P3Droid,
We (TBH) has a lot of experience in Motorola phones and hacking. The experience dates back to the Razr days.
Here is a word of caution. Do no delete apps from the System partition, I would suggest you only rename them to .bak. When Motorola pushes updates each of the files undergoes a hash check, if the file has been manipulated or is missing the entire update will fail.
Until a system only sbf or similar is released, unless you make a back up with bootstrap and recovery, you will eliminate your ability to take updates moving forward.
Click to expand...
Click to collapse
i take it that all the apps you can delete through app manager are on /data therefore are safe to delete right?
This should definitely be sticky'd.
franciscojavierleon said:
i take it that all the apps you can delete through app manager are on /data therefore are safe to delete right?
Click to expand...
Click to collapse
Yes anything that you can delete through the application manager is okay to remove, those have no impact on the update process.
And to complete my thought above. When an update is released, and they are coming, then you need to just change the file names back to normal to take the update.
Sound to me like we ned an ap that lets toys select programs to rename and then can change then back when needed. Would make it alot easier. Ill look onto this...also if some one else can confirm this info I might stick it.
Sent from my MB860 using XDA App
I can confirm that what p3droid is saying is true for all recent Motorola devices, but the point is really that you won't know until an OTA update is released how they have written the updater script in the zip file.
We have been through this with releases for every phone since the Droid X and many people got caught out by it and were stuck until we released SBF files that could safely restore the stock configuration and allow updating to official release versions.
This brings up another important point about modding your phone at this stage in the cycle. Without a full SBF to recover with in the event of a problem that renders the phone unbootable or unable to access recovery, or if you haven't made a complete nandroid, you will be again be stuck and have to return your phone to AT&T/Motorola for warranty replacement. This is never good for anyone.
When we mod our phones against the wishes of the carriers and manufacturers, we should really take responsibility for those actions and not produce a mountain of bricked phones whose cost is passed along to everyone in the form of higher ETFs for smartphones and other ways.
So, until a full SBF is released of the current build, people should be very careful what they change or remove from their phone's system and/or NVM and radio.
I also tried to warn users about this in another thread that was locked before p3droid started this thread. We have watched hundreds or even thousands of users destroy their phones in myriad ways and helped many of them recover them by providing SBF files as a safety net. It's not fun and if it can be avoided it is to everyone's benefit to do so and only requires care and forethought.
Is there anyway we could make a backup of this partition for later use? would each user need to make one or would one for all users suffice?
Assuming a bootstrapped custom recovery is possible, and we know Koush is already working on it, then a nandroid backup of at least the system, userdata and cache partitions would be the first and best step to take. Also assuming that the bootloader is locked/signed and true recovery is not possible, then the boot image and kernel will not be able to be backed up or written to by the bootstrapped recovery. It is always best to make your own backup for your device and store it on the sdcard where you have easy access, but users have also been able to use someone else's nandroid backup to restore their device in many cases as well. The recovery will give you the option to restore each partition separately in the advanced options so that you won't be restoring someone else's data to your phone.
We at TBH have also been able to create our own update.zip files and SBF files to help users recover from various mishaps.
This was because we had access to both official and unofficial files and tools to accomplish those things.
We have no idea if that will be the case here and we will not likely have the device ourselves to work with given we are VZW users primarily.
Again, there are many variables here that are yet to be determined and modes of access to the various partitions and radio baseband will be different with this phone as opposed to previous Qualcomm chipset devices.
All of this means that at this stage extreme caution is advised and being overzealous with root access is very dangerous right now.
I suggest everyone that is rooted use TITANIUM BACKUP to deal with their bloatware issues. The pro version, which you will need, is only a few bucks and is worth it. TB allows you to 'freeze' bloatware apps, which to my knowledge just blocks it fro the system, but does not delete it. The apps you choose to freeze are also removed from the app tray - so no more clutter. This way when an update rolls around, you can run down the list and simply touch 'thaw' to bring those apps back to recognition. This seems like a much more efficient and easy way to go back and forth, rather than renaming the .apk's.
I apologize if someone already mentioned TB in this thread - I just skimmed quickly.
I deleted all the bloat apps using the app manager without root. They were gone!
I did a factory reset on the phone and *surprise* the apps were back!
The things that were not part of the system come back during reset. On the other hand, im ****ed because I went crazy and deleted some actual apps that the system will check. Yay me.
pwndrone said:
The things that were not part of the system come back during reset. On the other hand, im ****ed because I went crazy and deleted some actual apps that the system will check. Yay me.
Click to expand...
Click to collapse
Ouch. Might not work, but have you tried a hard reset?
We should make a list of what's safe to remove like we did for the Captivate. Might be helpful.
I did a full factory reset and those apps that weren't part of the system came back but stuff like the help center are still missing.
Hopefully there will be a way to load the stock firmware sometime in the future.
Sent from my MB860 using XDA App
Would an app like "Autostarts" work in this case?
Guys, I can't emphasize this enough: use Titanium Backup to freeze the apps rather than deleting them, it will make your life much easier.
does this apply to using different font files as well? I'd like to use a ttf font that's a little larger than DroidSans. if i rename and use a different font will that impact OTA updates or anything else for that matter? thanks!
before reading about "freezing" apps, i reset my atrix back to factory settings. i need help rooting my atrix again. it keeps me in "Waiting for Device" where before i had no problem rooting. and another thing, when i had reset back to factory settings...i still have superuser installed. do i uninstall superuser in order to gain root access again?
I have not rooted yet. My question is can we use freeze to turn off BlurAccounts or is it fully baked into the Rom?
First off, thanks to everyone for helping make the Nook Color such a vibrant community. There's a wealth of information here and I'm really grateful for it. I love the NC and it's great that we can unlock its full Android potential thanks to the hard work of the folks here... both the people that make the tools, and the people that help support it.
I am curious to know if anyone out there has some custom boot animations that aren't so flashy. Both the wife (who also rooted her NC) and I suffer from migraines, and the bootup sequence can be really painful with the bright flashing colors. Something a little more subdued would be preferable.
I'm also not sure if I can run a custom boot animation on the NC without using Cyanogen? I've upgraded to 1.4.1 today (which promptly went into a boot loop which MN 4.6.16 didn't solve, so I reverted to 1.2 and then went back to 1.4.1 and got it re-rooted with MN 5.12.20 properly... thanks again for all the info here!), so I'm just using a rooted stock system. I searched for boot animations on the forum but most of the results were pages of people mentioning which animation they got stuck on while trying to root
Also, does anyone know anything about NookDevs.com going dark? Their site just shows a blank HTML page and any old links give a 404. It's a pity, because their wiki was a bit more in-depth than the NC wiki here.
stormerider said:
[...] I am curious to know if anyone out there has some custom boot animations that aren't so flashy. Both the wife (who also rooted her NC) and I suffer from migraines, and the bootup sequence can be really painful with the bright flashing colors. Something a little more subdued would be preferable.
Click to expand...
Click to collapse
I'm also not a fan of the early MN startup screens, but there's an easy fix (see below).
I'm also not sure if I can run a custom boot animation on the NC without using Cyanogen?
Click to expand...
Click to collapse
Yes, you can. MN changes it on B&N firmware.
If you've already over-written the boot animation by running MN, you'll need to find a replacement somewhere. Not sure how to do that. However, if you either haven't replaced it yet or are willing to do a factory reset, you can tweak the ManualNooter scripts. If you open the MN .zip file, go into /META-INF/com/google/android/ and edit the updater-script file with a text editor. Look for the 3 lines that begin with "ui_print("Installing Boot Animation...");" and comment them out by putting '#' characters at the start of each line. There are 3 lines in 5.12.20. Write the modified version to that same location, and then run it to (re)root your unit.
Alternately, you could modify /data/local/bootanimation.zip in manualnooter-5.12.20.zip. Hack down the updater-script, and you can have it install ONLY the boot animation if you want to try a few variations.
Finally, if you've already rooted, you could try plugging a replacement in to /data/local/bootanimation.zip directly. No guarantees on this one, though.
bobstro said:
I'm also not a fan of the early MN startup screens, but there's an easy fix (see below).Yes, you can. MN changes it on B&N firmware.
If you've already over-written the boot animation by running MN, you'll need to find a replacement somewhere. Not sure how to do that. However, if you either haven't replaced it yet or are willing to do a factory reset, you can tweak the ManualNooter scripts. If you open the MN .zip file, go into /META-INF/com/google/android/ and edit the updater-script file with a text editor. Look for the 3 lines that begin with "ui_print("Installing Boot Animation...");" and comment them out by putting '#' characters at the start of each line. There are 3 lines in 5.12.20. Write the modified version to that same location, and then run it to (re)root your unit.
Click to expand...
Click to collapse
I just finished getting everything set back up (I hit a setting page that did a reset on my unit... not so happy. Running Titanium Backup now...), so I'm not really keen on re-running MN. I'd rather just tweak what needs to be done, as things seem to be a little bit fragile and breaking things requires a lot of time to get back up and running.
Alternately, you could modify /data/local/bootanimation.zip in manualnooter-5.12.20.zip. Hack down the updater-script, and you can have it install ONLY the boot animation if you want to try a few variations.
Finally, if you've already rooted, you could try plugging a replacement in to /data/local/bootanimation.zip directly. No guarantees on this one, though.
Click to expand...
Click to collapse
Does MN override the bootanimation binary to support /data/local, or does bootanimation support that location directly? I did some searching and it looks like some people are patching the binary so it works with more standard Android boot animations and it was unclear to me if the /data/local path was part of that customization as well or not.
Also, I was in part posting to see if anyone had any recommendations for the animations themselves. Graphics work is definitely not my forte, I'm more of a server guy
bobstro said:
I'm also not a fan of the early MN startup screens, but there's an easy fix (see below).Yes, you can. MN changes it on B&N firmware.
If you've already over-written the boot animation by running MN, you'll need to find a replacement somewhere. Not sure how to do that. However, if you either haven't replaced it yet or are willing to do a factory reset, you can tweak the ManualNooter scripts. If you open the MN .zip file, go into /META-INF/com/google/android/ and edit the updater-script file with a text editor. Look for the 3 lines that begin with "ui_print("Installing Boot Animation...");" and comment them out by putting '#' characters at the start of each line. There are 3 lines in 5.12.20. Write the modified version to that same location, and then run it to (re)root your unit.
Alternately, you could modify /data/local/bootanimation.zip in manualnooter-5.12.20.zip. Hack down the updater-script, and you can have it install ONLY the boot animation if you want to try a few variations.
Finally, if you've already rooted, you could try plugging a replacement in to /data/local/bootanimation.zip directly. No guarantees on this one, though.
Click to expand...
Click to collapse
No need to go through all of that trouble. If you don’t like the boot animation in MN, simply go to /data/local, and delete or rename bootanimation.zip to bootanimation.zip.old, this will take you back to the factory boot animation.
The NC will work with any boot animation you can think of, you just need to follow a few basic rules. The rules are outline at nookdevs.com, Link, the site is down at this time, so here is a link for the cached site, Link.
If you are going to take a boot animation from another device, or from online, and edit it for the NC, the most important step is to NOT use any compression when you zip it back up. You can screw-up almost every other step, and still have a working boot animation, but if you compress the zip, it will not work at all.
CM 7.1.0-encore note
FYI: After putting CM 7.1.0-encore on my NC (and then wanting to change the boot animation), I discovered that the path is: /system/media/bootanimation.zip
Awesome. thanks for the info. Starting to build my own intro...
All,
I have an HD+ running 2.0.5 and its rooted. When I've turned on wifi, half the time it tries to update to 2.0.6. It always goes through its process then dies at 99% and drops back telling me that something is wrong. The first time I freaked out and thought something really WAS wrong.
Boy was I relieved to see that I still had my stock root.
I was just thinking that maybe I should update to 2.0.6 just to keep it current. I use the Nook side for reading and stuff as it is. Can I just rerun the root process like I did for 2.0.5?
Also what is the best way to make it not fail the update?
I did the white-on-white fix, but changed it back.
Please don't tell me I need to do the 8 boot factory reset.
Thanks,
-Jeff
How did you change back the white on white? I suspect that is what is wrong.
Sent from my Nook HD+ running CM10 on Hybrid SD
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
js5752 said:
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
Click to expand...
Click to collapse
No, I understand what you did. You left the symlink in /system and just manipulated the files in /data. That works to get rid of white on white, but does not put framework-res.apk back in /system. And the update zip needs framework-res.apk there. That is why it was failing.
Did you do a back up of your system before you added white on white like I recommended? If so, restore that and then update. If you did not, you can try putting that original framework-res.apk back in /system/etc via ADB. Doing it with ADB prevents that crashing you experienced the first time.
As a last resort go back to 2.0.0 with my plain stock zip in my HD/HD+ CWM thread. You can flash that and it will not erase your media files. You should backup your system with CWM first. Then wipe /data, then flash the zip. Then sign on, register and it will update you to 2.0.6. Then go to CWM and do an advanced restore of /data. Then flash again the zips you want, like root or gapps. Then you should be ok.
Edit: If you want to keep 2.0.5 and not be bothered by those attempts to update, I just added to both my Tips thread and my CWM thread linked in my signature a method to stop those updates.
Sent from my Nook HD+ running CM10 on Hybrid SD
Thanks for the reply.
I expected the crash from what I had read. I just decided that ADB was more hassle than it was worth for a quick change. That and I like to live dangerously
Ok, the symlink vs the data file makes sense. Now I understand why it wasn't working. Thank you, because I thought all was back where it should be.
As for backups, I did one before rooting, and I've done a couple since just to make sure I've got backups. That plus titanium, I figured I should be able to recover if the worst happens.
Thanks for the tips, and for all the work you've done on rooting these devices. It was the option to root that tipped me over the edge to buy one, and I'm glad I did.
-Jeff
Please find at the URL below my copy of the stock ROM (Version C) for the D415, with my modifications included.
The D415 is a great phone for the price, and it came with many cool features. However, the phone still has an amateur streak running the stock ROM. Some of LG's apps are great on this phone, but some of them are downright useless for most of us. T-Mobile added their own pushy bloatware to the mix as well. The end result, as we all know, is a usually fluid, but at times clunky and awkward experience using the device. I was impressed the first day I had it, but I wanted to make it better that first day as well. I wanted to get rid of all the useless stuff, and polish it into something I wouldn't be embarrassed to pull out in front of a client. I liked a lot of what LG did here, and wanted to hold on to that, but I also wanted a few changes:
Root:
FOTAkill
SuperSU installed on first boot
Polish:
Small UI sounds changes
Boot Animation
Replaced Flashlight App (thanks to xbmi, consider a donation in the app)
Added Heads Up
Removed foo foo themes
Added Bookmarks Sync
Replaced Stock Messenger with AOSP MMS
Debloat:
LG Memo & Widget moved to user apps
LG Music & Widget moved to user apps
Visual Voicemail moved to user apps
Weather widget moved to user apps
Apps removed completely:
LG Contacts widget
TMobile TV
Lookout
CarrierIQ
Maps
Mobile Life
Streetview
Talkback
T-Mobile My Account
T-Mobile Name ID
Voice Dialer
Youtube
Amazon
Chrome
Cloud Print
Drive
Easy Home
Gmail
Google Plus
Google Calendar
Play News Stand
Play Books
Play Game
Play Movies & TV
Play Music
Google Search
Google TTS
Hangouts
Stock Calendar
To do:
AOSP Keyboard (IDK what I'm doing here yet. It's crashing when I put it in now).
Version E (need to learn how to extract KDZ)
Instructions:
Download zip to SD
Reboot to Recovery
Wipe Dalvik, cache, data, system.
Install zip
Reboot and enjoy
Thanks to @Daisuke1988 for the original flashable stock rom.
Feedback welcome in replies!
I just got this phone today. I hate it but this should make it much better. Thanks guys!!
Sent from my SGH-M919 using XDA Free mobile app
Keep poking around with it. There are a lot of hidden gems sprinkled in by lg that will really cause you to like this phone. I came off of a nexus 5 to this. I chose it for the price tag, you can't beat $7 a month and get the build quality and battery life. I would buy again. The only thing I miss is a decent camera. But the stock camera app helps with auto focus mode.
Will it work on d405?
catbro said:
Will it work on d405?
Click to expand...
Click to collapse
Good question, it would be nice
Sent from my LG-D405 using XDA Free mobile app
I guess I have to try this evening, if nobody's trying till then I will report back
If the pure stock ROM works in the 405, this one should as well. I'm not sure myself without looking it up.
I have a D41510c and when I tried to install this rom, it failed. I'm restoring a backup, but I will try again in a while.
Sorry to hear that, I tried very hard to make the cuts fine in this. Without further info I'm gonna guess the download got corrupted. The zip itself is really straightforward (simple script, boot and system imgs.) The only part I would have thought would have failed the installer was that I repacked the system IMG (saved a few hundred MBs) instead of simply unmounting it after my changes. Otherwise, if its going to break, it should be upon first boot. Let me know what happened if it doesn't work again.
jb3p76 said:
Sorry to hear that, I tried very hard to make the cuts fine in this. Without further info I'm gonna guess the download got corrupted. The zip itself is really straightforward (simple script, boot and system imgs.) The only part I would have thought would have failed the installer was that I repacked the system IMG (saved a few hundred MBs) instead of simply unmounting it after my changes. Otherwise, if its going to break, it should be upon first boot. Let me know what happened if it doesn't work again.
Click to expand...
Click to collapse
I'm re-downloading, hopefully this will work!
I can deodex this but you will have to wait till Tuesday for me to upload it. or is it already deodexed?
I had thought about it but honestly haven't learned how to yet. Was I mistaken to think the payoff would not have been that great? Either way, I can wait til Tue, I know others will want it deodexed. Thanks!
I tried again, but it failed...
E:Error executing updater binary in zip
E:Unable to mount '/system'
EDIT: I was able to boot into the rom, but it's extremely slow
Wondering if it has to do with first botched install now that it went. Were you able to format /system again? My other thought was repairing permissions. When it failed the first time, was it before "Setting permissions for root" was displayed? If so it was in the middle of flashing /system. I flashed this on mine using twrp. IDK that I will be much help but I think if we can figure out the variables Google should at least point us in the right direction...
Before I get too far down the rabbit hole can anyone confirm they have successfully flashed this and its working out for them?
jb3p76 said:
Wondering if it has to do with first botched install now that it went. Were you able to format /system again? My other thought was repairing permissions. When it failed the first time, was it before "Setting permissions for root" was displayed? If so it was in the middle of flashing /system. I flashed this on mine using twrp. IDK that I will be much help but I think if we can figure out the variables Google should at least point us in the right direction...
Click to expand...
Click to collapse
Well, I rebooted and it's faster now. I used towelroot to get root. Nohing appeared about the permissions. I was able to update the binaries using TWRP.
It's should have already had root and SuperSU installs on first boot. Did that not happen? I'm glad your phone is doing better! So many weird things going on there!
jb3p76 said:
It's should have already had root and SuperSU installs on first boot. Did that not happen? I'm glad your phone is doing better! So many weird things going on there!
Click to expand...
Click to collapse
I use ROM Toolbox Pro, and when I went to start it the first time, it said root check had failed. That's why I used towelroot. I'll continue to test things and report back to you. So far, it's pretty smooth.
Weird. Can you tell me if the SuperSU apk is to be found in /system/apps/bootup?
I'm doing a backup so i can wipe and install fresh again. I'd like to mess around with the root stuff and see if I can figure that out. Did you happen to get a listing of which files are missing?
I want to further u dressed what I'm doing wrong in changing lock.ogg and other sound and animation files. I understand that the qmg files are made in a way to make it more difficult to change but I'm doing something wrong. Even completely deleting the stock mini loop animations with my root browser has No effect. They aren't their but they continue play on every boot. I recently flashed a lollipop animation that is working but upon looking at the way the the files were done using .Baker did not work for me. I just want to understand what exactly I'm doing wrong. Existing file rename with .bak place new file in required location renaming to Samsung miniloop etc. Change permissions to match making sure the root browser is in r/w. AND NOTHING.... I really want to understand r/w and later decompose/recompile but this first hurdle with file changing is really messing with me. Any help is appreciated
pyroman2425 said:
I want to further u dressed what I'm doing wrong in changing lock.ogg and other sound and animation files. I understand that the qmg files are made in a way to make it more difficult to change but I'm doing something wrong. Even completely deleting the stock mini loop animations with my root browser has No effect. They aren't their but they continue play on every boot. I recently flashed a lollipop animation that is working but upon looking at the way the the files were done using .Baker did not work for me. I just want to understand what exactly I'm doing wrong. Existing file rename with .bak place new file in required location renaming to Samsung miniloop etc. Change permissions to match making sure the root browser is in r/w. AND NOTHING.... I really want to understand r/w and later decompose/recompile but this first hurdle with file changing is really messing with me. Any help is appreciated
Click to expand...
Click to collapse
Maybe you need to not leave that renamed file in the same directory?
SiNJiN76 said:
Maybe you need to not leave that renamed file in the same directory?
Click to expand...
Click to collapse
I tried deleting them altogether and they still play. And this really isn't matter of just having a custom boot animation because I can easily flash a zip file but I want to do it myself. Is it really necessary to use the Samsung theme to recreate a working animation for my phone
pyroman2425 said:
I tried deleting them altogether and they still play. And this really isn't matter of just having a custom boot animation because I can easily flash a zip file but I want to do it myself. Is it really necessary to use the Samsung theme to recreate a working animation for my phone
Click to expand...
Click to collapse
I would recommend downloading a boot animation that works on this phone and see what files you have to modify. I know for sound it is 3 of them.
BAD ASS NOTE 4
I did with a custom matrix boot animation and went and looked at all the files and tried my best to recreate what had already been done but all it did was take the animation away completely and put me in bootloop
pyroman2425 said:
I did with a custom matrix boot animation and went and looked at all the files and tried my best to recreate what had already been done but all it did was take the animation away completely and put me in bootloop
Click to expand...
Click to collapse
Link me to this and I will see what is up. I know of only one boot animation that was made for this phone. I could be wrong but let's check
BAD ASS NOTE 4
---------- Post added at 12:26 PM ---------- Previous post was at 12:16 PM ----------
http://forum.xda-developers.com/showthread.php?t=2943808
BAD ASS NOTE 4
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
That be the only one I came across that was done right without having to go in and change things
BAD ASS NOTE 4
http://forum.xda-developers.com/note-4/themes-apps/bootanimation-matrix-flash-recovery-t2952816
All of the boot animations and the certain shutdown animation work flawlessly on my sm-n910t running on hyperdrive RLS3. I used that lollipop animation until I found these it was jumpy but better than stock
pyroman2425 said:
http://forum.xda-developers.com/note-4/themes-apps/bootanimation-matrix-flash-recovery-t2952816
All of the boot animations and the certain shutdown animation work flawlessly on my sm-n910t running on hyperdrive RLS3. I used that lollipop animation until I found these it was jumpy but better than stock
Click to expand...
Click to collapse
If these work what is it that you are trying to do? I think I missed something.
BAD ASS NOTE 4
In the original post I inquired on what issue I'm having with moving/changing/renaming files and their permissions. I have tried everything I have seen on the the forums ie. Renaming original ending with .bak placing new file within the directory and renaming to match the original file. Changing permissions then reboot into recovery. Wipe dalvik and cache (even tried not wiping) reboot system anf either nothing at all or the original samsung boot. Ive tried boot animation changer and six different types of file explorers (2 paid versions) hours and hours of youtube videos and thread after thread to find my solution. I see that qmg files most likely can only be exchanged with qmg files created via samsung themer. Im currently using an sm-n910t on the hyperdrive rls3 rom and just recently flashed the bioshovk kernel in the hopes that it would support .zip boot animations but it doesnt quite work like that. I tried the starkissed kernel and the nadia kernel to end in softbrick. I am extremely interested in all of these things and eagerly look forward to decompile/recompile but as it stands im stuck at unchangable boots lol. Im really hoping to see possibly a video of the changes being done on an actual note 4 not an s5 or anything else. As always any info is greatly appreciated