Here's a tiny package to be installed with xRecovery, for people who would like to disable the boot animation.
It replaces the animation with a dummy bootanimation.zip (backup your bootanimation.zip if you use a custom animation)
Thanks to Oskar.k for the inspiration.
Tested on WB-XPERIA TW Gingerbread but should work on any rom.
If you install a new rom, theme, or wipe cache, the first boot can take more than 5 minutes. When installing this you will get a black screen instead of a picture from a boot animation, don't mistake it for a crash/freeze.
Installation:
- in xRecovery, install custom.zip, xRecovery-BootAnimationDisable.zip
or
- copy bootanimation.zip to /system/media/bootanimation.zip using a root explorer like Estrongs File Explorer (free from Market)
To install the stock animation, do the same with xRecovery-BootAnimationStock.zip
Apparently the clean way to disable the boot animation would be to add those lines to /system/build.prop:
ro.kernel.android.bootanim=0
debug.sf.nobootanimation=1
It works and it's a cleaner solution but it doesn't seem to be any faster.
I think a xRecovery package is the most convenient to use when installing/updating roms.
I see u uploaded, but there arent any credits for ideas :/
Sent from my own maded GB X10.
Sorry Oskar.k, It's not my style! I did wonder if I should mention it but I didn't think you'd consider it your idea or discovery that messing with the file disabled the animation, it was so trivial... the xRecovery package is so trivial too. To disable something, messing with a file is the first thing someone tries (right after deleting a file). But you did save me a couple minutes to test this for myself because I did open your file to notice why it disabled the animation (no files to be used in the 2MB zip), and your post is the inspiration for making a convenient solution for myself, that I'm sharing here in case it helps others, so I edited the post to mention you. No hard feeling?
ALL IS GREAT
Sent from my own maded GB X10.
Sick of taking huge sized nandroid backups before applying any tiny tweak/MOD and then undergo the long painful procedure of restoring ??
Through this guide , I will tell you about some really simple yet effective ways to unbrick your soft-bricked phone/get out of boot loops.
Our Unbricking Weapon
Android Commander - http://forum.xda-developers.com/showthread.php?t=628138
About Android Commander - Android Commander is windows application to keep control on your android apps and files from PC.
It detects your device even when it is in a bootloop!
Click to expand...
Click to collapse
TIP : You need a kernel/ROM with root enabled for ADB otherwise the AndroidCommander program will give NO root access ( since it is operated via ADB)
Ok so below are some of the most common reasons of bootloops :
1. Incorrect/Incompatible Build.prop Tweaks - SomeBuild.prop tweaks which you add to your Build.prop file located in /system folder might not be compatible with your device's hardware or firmware and this causes bootloops .
For eg - Over Sized heap limit , changing rendering methods to those which are not supported etc.
Solution - Have a backup of your Build.prop file before adding/removing/changing any build.prop tweak (its doesnt even take 2 minutes ) and if you face a bootloop, simply replace your current build.prop file with your backed up one.
2. A corrupt/incompatible System application / jar file (for eg - a wrong framework-res.apk) - Most of the time when theming or modifying, we might replace a system app with a modified app which might not be made for our device/hardware. This can lead to both bootlooping and/or crashing of the app
Solution - Have a backup of the original apk or download it from anywhere and simply replace( delete the apk and push your downloaded apk ) it via AndroidCommander.
3-An incompatible bootanimation - a bootanimation which either has a wrong desc.txt file with wrong resolution or wrongly sized images can lead to bootlooping
Solution - simply replace the bootanimation.zip file located in /system/media folder with any compatible bootanimation.
4An incorrect/corrupt Dalvik Cache - This can be simply solved by wiping the dalvik cache in recovery. Btw, clearing cache and dalvik cache can solve most of the bootloops which are not caused by incompatible mods/tweaks.
5.An incorrect init.d script and/or a system file like a lib/configuration/property/firmware etc( like efg.cfg file missing )
Solution Delete if its an addition , correct it or simply replace it with an original one
Click to expand...
Click to collapse
Note
There are many other ways to get out of a boot loop like flashing a CWM zip to replace your corrupt file / mounting as USB storage via Recovery but personally i feel that this is the easiest and fastest way to recover from a soft-brick.
These are only a few which i remember, i will post more in the future. As you can see that i didnt go into details of each and every category since there are endless problems and solutions which are obviously very specific. My main motive was to spread this idea since it has really saved me the hassles of restoring a backup for every small tweak i apply. All of the above problems have occurred to my device for once at least. This method has saved me a lot of times , Hope this guide helped you :angel: No more getting scaredof Soft-Bricks :laugh:
Press Thanks:good: if this helped you
But i tried it got some data corruption errors. could not find proper guidance / help on that , after few days sold the device.
I am not able to apply any themes downloaded{both from internal memory and sd card},when i apply a theme,the screen just flickers and same old theme is there.
what i noticed is themes from system/themes are working and applied properly and when i copy a downloaded theme and copy to system/themes,it works,so the problem is apart from themes located in System/themes,no other theme is working when applied from HWthemes location{both internal and sd card}.
Mine's rooted and bootloader unlocked.
emui 4.
System/Themes location size is less and hence i am unable to copy big sized themes,is anyone facing same issue?
I use one app called emui theme editor to edit and make my own themes
Is this a known issue,if anyone offers a fix it would be cool,thanks.
Have you changed the "ro.config.hwtheme" line in build.prop? In my case, it must be "ro.config.hwtheme=1" to work fine.
No response from OP?
I have been on XDA for 2 and a half years or so. I have gained a vast amount of knowledge and skills and its all in part due to XDA and the individuals who spend their time helping others who have made this all possible. The list of those to thank is too long. So before you see what I have to offer below, I want to thank everyone around the forums here for your help, or criticism . Without you guys, I never would've learned what I know today.
Most of my hacks for the HD 10 are spread out around several threads. That makes it hard to keep everyone updated when I find or create new goodies. It also makes it hard for users to find these goodies. This thread aims to solve that problem. From now on, I will include, if possible, my tricks and hacks in this thread. This aims to make searching for and installing these modifications quick and simple.
I have created a flash zip that installs all my goodies and hacks I have come up with so far. I just need so others to test it and make sure the installation process works and everything that is installed works. So please report back your findings so I can remove test from the thread.
***IIf this zip doesn't work or if it fails the worst that can happen is you will have to flash back to fresh stock and start all over and re-root. So make note of your Fire OS version before installing this zip. I am not responsible for anything that doesn't work. If you install this zip, you are doing so at your own risk.***
This zip does NOT contain the Google Play Store. By installing this zip, I assume you already have it installed. ViPER4Android requires an extra step or two and SELinux switch. See below.
Requirements:
- HD 10 with Fire OS 5.6.1.0 or 5.6.2.0
- Rooted with Xposed installed and Flash Fire functioning properly. See here to get it up and running.
What this zip includes:
- *ALL* of my framework-res mods including WiFi and location service optimizations.
- My rewritten Settings.apk which also includes all of my mods.
- Stock Basic Dreams and Photo Table screensaver. This was one of my goals when I first signed up on XDA. I knew what needed to be done to get this to work, I just didn't know how. Finally after nearly 4 to 6 months of reading and testing, I was finally able to edit the framework-res.apk to bring you this and other features. I also had to track down a working Basic Dreams and Photo Table APK. That was half the battle. Go to settings -> display settings -> Daydream. You can choose colors, clock or set some custom photos in Photo Table. Tap three dots in upper right to decide when Daydream turns on. (Note: Photo table requires your images be placed in internal storage in the 'Pictures' folder).
- Google Calendar (assuming you have deleted Amazon's calendar).
- DeskClock latest update and APK for Google Clock (assuming you deleted Amazon's clock).
- Google Contacts Sync Adapter (Once installed, you can delete Amazon's contact sync adapter as seen here. Also for non-root users). This allows for a small amount of visual customization when you pull down the notification bar. When you customize your profile in Google Contacts (also included in this zip) with a photo, the icon in the notification panel will change to whatever you upload as your contacts photo.
- Google Contacts (requires sync adapter listed above).
- Google TTS. You can delete PicoTTS in /system/app once Google TTS is installed. It's very outdated. You can also delete both of the Ivona folders in /system/priv-app. Best to delete app data for all three before deleting.
- Latin IME (AOSP replacement for stock keyboard. Will only work when you delete Amazon's keyboard (com.amazon.redstone), any other keyboard you have installed, then perform a factory reset without installing a new one.
- Stock Android Marshmallow boot animation. The zip replaces the bootanimation binary file in /system/bin/bootanimation with one from from @ggow custom ROM for the Fire 7. Amazon had modified the stock bootanimation binary to force the gold 'fire' boot animation. Doing this made it impossible to customize the boot animation. So I replaced it under the assumption the Fire 7 ROM binary is from an AOSP build and is pretty much universal among most custom ROMs. And it worked!
- Gallery3d. Replaces Amazon Photos (You have to delete Amazon Photos on your own) with library injection so it is fully featured. You can edit all images with a full stock of editing options. (does not set lock screen wallpaper. To change lock screen wallpaper, see here. Requires root). I was able to find the APK and libraries in this thread. The flash zip there doesn't work for our devices so I modified the APK to be more tablet friendly, allowing for scrolling and viewing in landscape mode then added the relevant files to this zip. In the APK, I removed the options for a settings menu, because it doesn't function, but the library does a great job at making up for the loss of it.
- CM Browser. I was able to port over this APK along with CM File Manager, CM Wallpapers, Lock Clock and Trebuchet from an official CM Lollipop ROM for the Amazon HD 8.9.
- CM File Manager (Can replace your favorite root explorer).
- CM Wallpapers. Cyanogenmod actually had a few good wallpapers. I wish they had made their own live ones though.
- CM Lock Clock with weather. (Yahoo weather doesn't function. Use Open Weather and set update interval to 30mins).
- Trebuchet Launcher with basic launcher settings. (You have to delete fire launcher on your own for this to take effect. /system/priv-app/com.amazon.firelauncher)
- Google Calculator (assuming you deleted Amazon's)
- Stock Android Live Wallpapers and Live Wallpaper Picker (doesn't include Androids add on wallpapers. For all of Android's stock live wallpaper add ons and stock wallpaper images, see this thread.
What this zip DOES NOT include or do:
- Google Play store is NOT installed. It is best advised to do this manually. Even flashing Gapps doesn't stop you from needing to tweak Secure Settings a little bit.
- Does not delete or remove any files or folders. It does however overwrite some. The framework-res, FireTabletSettings and bootanimation files will all be overwritten.
- Not yet a custom ROM, but it's close.
-Build.prop edits are not included. My WiFi optimizations and ViPER4Android need a few tweaks. Please see the 'build.prop' section below for details.
Installation:
NOTE: If you only wish to install certain packages or tweaks such as ViPER4Android, see instructions below installation guide.
1. Simply place the DragonMods.zip into internal storage.
2. Open Flash Fire and tap the '+' and select Wipe.
3. Make sure ONLY Dalvik Cache and Cache Partition are selected and tap the check mark in the upper right of the pop-up.
4. Tap the '+' again and tap 'Flash Zip or OTA'
5. From internal storage, select my zip package DragonMods.zip.
6. Tap FLASH and wait for everything to happen. This will take upwards of 10 minutes or more, depending on many variables so be very patient.
Install only select packages:
1. Place DragonMods.zip on your PC desktop. For this I use 7zip for Windows. Right click on the zip file and select 7-zip and open as archive.
2. Double click on system folder then double click on the folder you you want to delete. Example: If you do not want to install my framework-res APK, delete the framework folder. If you don't want CM Browser, delete that folder.
3. Once you are happy with your custom installation, replace the zip on your tablet's internal storage and follow installation instructions above.
ViPER4Android:
I have not included this in my zip for a few reasons. The foremost one being it requires you to delete a couple key files so I would rather you make the choice yourself rather than me doing it for you. I confirm it is full operational and functional and doesn't force close once installed properly. If you aren't convinced, just activate the notification.
1. Download the V4A2.3.4.0 Lollipop.zip provided at the Google Drive link below or go to this thread and download it. Make sure Selinux switch is installed, set to permissive with notification enabled. Also make sure BusyBox is installed.
2. On your tablet, go to /vendor or /system/vendor and tap etc.
3. Back up both of the audio files, audio_effects.conf and audio_policy.conf then delete them from the folder
4. Go to storage -> downloads and tap on the V4A2.3.4.0 Lollipop.zip, system, etc, and extract the two .conf files.
5. Go to the folder they were extracted into and copy both of them to /system/etc, overwriting the ones that are located there. Set the permissions (rw-r--r--) and reboot.
6. Go to downloads again, tap the V4A2.3.4.0 Lollipop.zip and system, app and extract the APK.
7. Create a folder in /system/app titled 'ViPER4Android'. Rename the APK 'ViPER4Android.apk' and paste it into the folder.
8. Set folder permission rwxr-xr-x, APK permission rw-r--r-- and reboot.
9. Open App and follow instructions. Tap upper right for menu and set UI to expert.
build.prop edits:
1. ViPER4Android needs a few tweaks to the build prop. If these variables and values already exist in your build.prop, please change them to the ones below. You can use Build Prop Editor or a root file explorer to make the edit:
Code:
Ipa.decode=false
tunnel.decode=false
lpa.use-stagefright=false
2. The WiFi needs a tiny bit more tweaking here too. Locate the following line in /system/build.prop and add the value to it as seen below (there is currently no value set and the best ones are 1, 6 or 11. You can use any number as long as it's 11 or less.
Code:
ro.wifi.channels=11
3. Locate the following lines in your build.prop. Back them up to a text file then delete both lines (numbers might be different):
Code:
wifi rssi->bar thresholds
persist.wifi.rssi.thresholds=-84,-75,-66,-55
Downloads:
DragonMods.zip (the main zip you need) - Current as of November 16, 2018
DragonMods5-6-2-0.zip (for users on FireOS 5.6.2.0)
V4A2.3.4.0_Lollipop.zip
That's all for now. This includes pretty much every hack, trick and tweak I have been able to achieve on these tablets so far. I hope you enjoy all of these and watch out for more of my hacks. Thank you everyone for making all of this possible! Don't forget to hit the thank button
Change Log
- November 22, 2018: Updated links to reflect the following: Fixed issue with Trebuchet launcher missing from zip by readding it to the folder. I don't know How I missed that. Replaced google Clock with correct APK. I meant to put in the DeskClock available from the Play Store. If anyone would like a zip containing the CM/AOSP DeskClock that changes colors as the day and night change, let me know and I will upload the APK. The reason for this mess: I used the wrong zip template I have for this package. The one with the mess was intended for my personal device. My apologies.
Problems:
-If you delete Amazon photos, when you tap settings, display settings, wallpaper, it will kick you back to main settings. Solution: download Amazon photos from the play store as a user app then do this:
Code:
adb shell
su
pm disable com.amazon.photos
pm clear com.amazon.photos
.
Function returns.
not sure how to install this
darkfortedx said:
not sure how to install this
Click to expand...
Click to collapse
Flash it in flash fire...says that in the OP
Be advised
I just downloaded it and realized I didn't put th right folder in for Trebuchet launcher so the folder is empty. So don't flash this zip until I can fix it when I get home later.
Update November 22, 2018 1:42PM:
- Fixed issue regarding launcher. See change log at the end of the OP.
after changing the permissions for /system/vendor/etc to rw-r-r and rebooting, get the boot screen then boot to quick flash on desktop then to black, can only get the power down window to show when holding power. I'm trying to change the permissions back in adb. . can you please send code to do this correctly? if this is the correct approach. i backed up the 2 files in es file explored back up folder.
I got it....
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/vendor/etc
this worked... took me a while to figure it out. But it's all part of learning!
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
I missed that it was for the two files not the folder lol....
nikothebarber said:
I got it....
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/vendor/etc
this worked... took me a while to figure it out. But it's all part of learning!
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
I missed that it was for the two files not the folder lol....
Click to expand...
Click to collapse
I have an update of this I'll upload later. I just want to make sure everything works as advertised. Apologies if not. I made a stupid mistake earlier that I fixed but might have missed a small thing or two.
Sent from my MotoG3 using XDA Labs
When I tried to flash it if flashfire, it will juz stuck in the first black screen for over 15 mins.
I can juz simply quit the app and everything remains the same and work fine though.
What would possibly be the problem?
@DragonFire1024
Tried to Install ViPER4Android with the steps and files you linked but was unsuccessful. When I bring up the Driver status and they all say no to Enabled. It already prompted me to install drivers which I did and re booted and still no go. I'm familiar with installing ViPER4Android and have it installed on my phone but not able to get it going in HD10. This tablet needs some way to higher the sound, sound on this tablet SUCKS. Any help would be greatly appreciated.
Touchpad64gb said:
Tried to Install ViPER4Android with the steps and files you linked but was unsuccessful. When I bring up the Driver status and they all say no to Enabled. It already prompted me to install drivers which I did and re booted and still no go. I'm familiar with installing ViPER4Android and have it installed on my phone but not able to get it going in HD10. This tablet needs some way to higher the sound, sound on this tablet SUCKS. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sorry I've been very sick the last several days and have spent most of it in bed. Until I can look and see what's wrong, I can suggest you try 'volume boost by goodev' on the play store. You may need to make it a system app though.
Sent from my MotoG3 using XDA Labs
jeffreyyip314 said:
When I tried to flash it if flashfire, it will juz stuck in the first black screen for over 15 mins.
I can juz simply quit the app and everything remains the same and work fine though.
What would possibly be the problem?
@DragonFire1024
Click to expand...
Click to collapse
Flash fire will take approx. 10+ mins sometimes to go through the files then about the same time until the red flash fire bar appears at the top. With flash fire you just have to wait.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Sorry I've been very sick the last several days and have spent most of it in bed. Until I can look and see what's wrong, I can suggest you try 'volume boost by goodev' on the play store. You may need to make it a system app though.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
Thanks for your response, get some rest and I'll patiently wait to see what you come up with...Thanks again
Touchpad64gb said:
Thanks for your response, get some rest and I'll patiently wait to see what you come up with...Thanks again
Click to expand...
Click to collapse
Try deleting the viper folder if you installed it via a file explorer. Reboot then install viper as a regular app. Don't open it. In a root file explorer go to /data/app and copy viper folder to /system/app then reboot.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Try deleting the viper folder if you installed it via a file explorer. Reboot then install viper as a regular app. Don't open it. In a root file explorer go to /data/app and copy viper folder to /system/app then reboot.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
I did that the first time. I had to enable Selinux Switch and enable Permissive which it seems like you have to enable each time you want to use Viper. The Driver Status now says NEON enabled, Enabled=Yes, Status=Normal, Audio Format= Supported but it still sounds like it makes no difference in boost in volume. The App you suggested Volume Booster works great. On my phone I can notice the difference on Volume quality and boost but not on the HD10 using Viper. What settings are you using? Maybe it's the settings.
Touchpad64gb said:
I did that the first time. I had to enable Selinux Switch and enable Permissive which it seems like you have to enable each time you want to use Viper. The Driver Status now says NEON enabled, Enabled=Yes, Status=Normal, Audio Format= Supported but it still sounds like it makes no difference in boost in volume. The App you suggested Volume Booster works great. On my phone I can notice the difference on Volume quality and boost but not on the HD10 using Viper. What settings are you using? Maybe it's the settings.
Click to expand...
Click to collapse
Did you rename the audio.conf files in vendor?
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Did you rename the audio.conf files in vendor?
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
No, I didn't see any instructions to do so. Was I supposed to?
Touchpad64gb said:
No, I didn't see any instructions to do so. Was I supposed to?
Click to expand...
Click to collapse
Yes. Rename them. But you should do it before installing viper.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Yes. Rename them. But you should do it before installing viper.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
The original files were named the same as the files copied over that's why you have to allow it to overwrite. Original files and copied files were both named audio_effects.conf & audio_policy.conf. I also edited the build prop entries you mentioned. Can you share your build prop file so I can compare your entries to mine? What were the names you change audio_effects.conf & audio_policy.conf to?
Touchpad64gb said:
The original files were named the same as the files copied over that's why you have to allow it to overwrite. Original files and copied files were both named audio_effects.conf & audio_policy.conf. I also edited the build prop entries you mentioned. Can you share your build prop file so I can compare your entries to mine? What were the names you change audio_effects.conf & audio_policy.conf to?
Click to expand...
Click to collapse
Just put a _ at the end of .conf. I didn't add the removal of the vendor files in the zip and I think I stated that in the OP.
Sent from my MotoG3 using XDA Labs