Icy Fusion ROM
Final: v2.3
~~The best ICS experience..on Gingerbread!~~ Fast and smooth! Crazy battery life!
klin1344 said:
Hi everyone,
I am sorry to say that I will be retiring this ROM. I will be receiving my HTC One S next week, and most of my development efforts will be focused over in those forums. I won't abandon the 4.0 completely, but this will be my last ROM for it, with no more future updates. I also feel that this ROM is pretty complete and definitely usable for a stable daily driver.
I want to thank the community who supported my development, and my ROMs have been a good learning experience for me. But too bad the galaxy players were never very popular with developers...
Anyways, hope you enjoyed my work here. Links will always be available.
Click to expand...
Click to collapse
As you probably all know, I have ditched Klassic and letting hanthesolo continue it. I was going to make a SGS2-styled ROM, but instead I chose a total ICS-styled ROM instead due to the popularity of Android 4.0. I will be maintaining this ROM in two builds--one based on G1UEKI8 (USA) and another based on XXKPQ (INTL). Using an INTL ROM on a US player, and a US ROM on an INTL player caused too many issues (bluetooth, home button, toggles, etc), so I have decided to do it this way for better integration and the best possible experience. As of now it is not very different from Klassic (or Stratus), but as I make new releases it will have more and more features. Also it will be flashable with CWM. Enjoy
Features:
v1 (6/18/12)
- complete ICS theme (even better themed than Klassic, just look at the screenshots)
- swapped internal USB storage and external SD card (see 3rd post on how to revert)
- Holo Launcher installed
- ICS transitions + Roboto Fonts
- ICS clock widget
- deodexed
- zipaligned
- smooth scrolling mod (a.k.a. disabled scrolling cache in framework)
- smooth spinners mod
- CRT screen off animation
- 14 statusbar toggles
- "Device ID" hack ~now apps like XDA, Whatsapp, Tap Tap Revenge, and any app that needs a unique device id will run and not force close~ (XXKPQ uses Meticulus' hack, G1UEKI8 uses a slightly different method, but still same result)
- advanced powermenu with reboot, recovery, and download
- Supercharged with V6 Supercharger
- my own init.d scripts (you can look at the notes in the "55tweaks" file to see what I put in there)
- improved battery life
- I/O performance enhancements
- better performance
- TerraSilent as the default CPU governor
- plus more
- fixed performance and freezing issues from Klassic R5 (note: this ROM is completely made from scratch from stock, not based on Klassic or another ROM)
- fixed bluetooth issues from Klassic R5
- loads of build.prop tweaks
- debloated (I will attach the apps that I removed if you still want them)
- latest SU Binary 3.0.3.2
- BusyBox 1.20.1
- RFS filesystem ---> /system doesn't need to be on EXT4 because you are not constantly writing data on it
Click to expand...
Click to collapse
v1.1 (6/19/12)
- more init.d scripts for unbeatable battery life and performance
- loopy smoothness script
- sysctl tweaks for speed
- added SuperSU
- fixed the busybox symlink problems in v1
- released the INTL build
- busybox 1.19.3
- updated theme (look at screenshots)
Click to expand...
Click to collapse
v2.0 (6/21/12)
- disabled zCache by default --> to enable, go in 55tweaks and delete the '#' in front of "insmod /lib/modules/zcache.ko"
- implemented swipe to remove notifications
- added CRT screen ON animation
- improved touch responsiveness
- disabled start up sounds
- set an ICS wallpaper as default
- added 5 new ICS wallpapers in Wallpaper Gallery
- Galaxy Nexus bootanimation
- improved the implementation of the device id hack
Click to expand...
Click to collapse
v2.1 (6/23/12)
- FIXED BLUETOOTH!! and still Supercharged
- more battery life tweaks
- more performance and responsiveness tweaks
- fixed powermenu "Reboot Download"
- added TouchWiz 4.0 modified by me
- GT-I9000 Settings.apk (more options)
- completely re-designed Settings.apk
- ICS themed + added HoloLauncher Settings (see screenshots)
- "IcyFusion ROM" selection in Settings is a shortcut to device status
- succesfully smali'ed out (removed) "Call Settings" from the Settings.apk
- updated Holo Launcher to v1.0.5
- updated SuperSU to v0.92
- now /system is on EXT4
- ODIN package until CWM /data issues are sorted out
Click to expand...
Click to collapse
v2.2 (6/24/12)
- used stock Settings.apk, but still designed the same as v2.1
- fixed the setup wizard loop
- cleaned up init.d scripts
- added a lot more init.d speed tweaks
- added DSP Manager apk + libs
- added Zeam Launcher
Click to expand...
Click to collapse
v2.3 (6/26/12)
- optimized EXT4 mounts in init.d scripts (fast i/o performance; I got 2300 in Quadrant with only stock 1Ghz)
- added transparent background theme --> see post 3 on how to change the background picture
- optimized auto brightness levels for battery life
- stock sd card and internal storage mounts
- improved ICS theme
- Youtube HD apk
- fixed DSP Manager, and now every feature works
Click to expand...
Click to collapse
Downloads
*Simply flash in CWM*
*v2.1 & up flash with ODIN*
wipe data if you are have issues
USA/INTL:
v1: http://d-h.st/wWE
v1.1: http://d-h.st/jyP
v2.0: http://d-h.st/jGF
v2.1: http://d-h.st/W0I
v2.2: http://d-h.st/WYB
v2.3: http://d-h.st/mPa
INTL
v1: none; look for v1.1
v1.1: http://d-h.st/ILv
v2.0: none
INTL users please try the US version and post here if there are issues
Sorry, I will have to drop support for INTL players because it is too difficult to keep flashing, modding, and testing both builds of the ROM. I understand that 2.3.5 caused a reboot issue on INTL players when the headphones are plugged in. If somebody could please post a logcat, and I will try and see what I can do to fix the issue. Thanks.
Special thanks to:
Dark_Balor for improving the kernel for our device
zeppelinrox for his V6 SuperCharger
Meticulus for his Device ID hack for 2.3.6
Vertumus for some parts of his ICS Domination Theme
dsixda for his kitchen
And many others I probably forgot to mention
ScreenShots
Extras and add-ons
Extras and Add-ons
Here I will attach some miscellaneous add-ons for my ROM.
How to manually wipe and format data into EXT4
1. Boot into CWM recovery. Make sure you are using the latest TerraSilent kernel.
2. Type 'adb shell' in command prompt or Terminal.
3. Type the following code:
Code:
umount /data
umount /dbdata
umount /cache
Then:
Code:
mke2fs -f ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p2
mke2fs -f ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/stl10
mke2fs -f ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/stl11
4. Reboot. Or you can follow below on how to disable EXT4 journaling (don't reboot), which GREATLY improves i/o performance. Note that every time you boot into recovery, /data get wiped into RFS again due to a CWM bug. I suggest that you do not boot into recovery again after rebooting unless you really need to.
To disable EXT4 journaling
1. Make sure you have flashed my ROM, as it includes some tools for this procedure.
2. Unmount the partitions if they aren't already:
Code:
umount /data
umount /cache
umount /dbdata
4. Follow:
Code:
tune2fs -O ^has_journal /dev/block/mmcblk0p2
tune2fs -O ^has_journal /dev/block/stl10
tune2fs -O ^has_journal /dev/block/stl11
5. You're done! Now you can reboot, and see the massive jump in Quadrant, especially if you're using ROM v2.3 and up.
How to change the background wallpaper theme
For v2.3, I've enabled the use of a custom wallpaper theme, which will show up in many apps. If you don't like the picture I used, you can replace it yourself with these very simple instructions.
1. Copy the /system/framework/framework-res.apk from your player.
2. Using an archiver, like winzip or 7zip, open the apk.
3. Find any 480x800 png image that you like, and name it screen_background_dark_transparent.png
4. Drag it into the res/drawable-hdpi/ folder of the apk. It will replace the original one in there.
5. Copy framework-res.apk back, and make sure to set permissions rw-r--r--. Reboot.
Extras
- Stock vold.fstab (for stock usb storage and sd card mounts): http://d-h.st/FKL
This is how to install
Code:
cd [B]*directory of the file*[/B]
adb remount
adb push vold.fstab /system/etc
Or simply just copy/paste with root explorer and reboot.
reserved again
It looks nice. I have 1 suggestion. It is possible to put the SGSII lockscreen into it? It would be perfect! (for me though I don't know for the others)
zaclimon said:
It looks nice. I have 1 suggestion. Is it possible to put the SGSII lockscreen into it. It would be perfect! (for me though I don't know for the others)
Click to expand...
Click to collapse
I could try, and maybe upload a framework-res specifically for people who want an SGS2 lockscreen.
I am trying to get INTL support for this ROM, but unfortunately I noticed that with XXKPQ if I use dsixda's kitchen I get this error when trying to use busybox:
Any busybox applet will result in the same...
It doesn't happen on 2.3.5 G1UEKI8 though.. I have tried unrooting and rerooting, using the install busybox option with kitchen, reinstalling busybox, but nothing seems to work.
So..for now I will only be supporting US devices until someone can either help me get rid of this error or at least help me find another INTL ROM that I can base my work off of.
Nice! It seems we are branching off, you to theming and features, I to raw performance . Just from one dev to another, did you fix bluetooth by unullifying? Also, how did you get framework-res to successfuly recompile without FC's? I tried doing it, and it basically blew up my Gplayer. Maybe using a apk decompiler is not the way to go...Argh, I hate windows, I never have these issues in Ubuntu...
Finally, where did you find his deviceid hack? when I got to his thread he had nuked all of his work...sad that someone would try and rip off his hundreds of hours of work.
hanthesolo said:
Nice! It seems we are branching off, you to theming and features, I to raw performance . Just from one dev to another, did you fix bluetooth by unullifying? Also, how did you get framework-res to successfuly recompile without FC's? I tried doing it, and it basically blew up my Gplayer. Maybe using a apk decompiler is not the way to go...Argh, I hate windows, I never have these issues in Ubuntu...
Finally, where did you find his deviceid hack? when I got to his thread he had nuked all of his work...sad that someone would try and rip off his hundreds of hours of work.
Click to expand...
Click to collapse
I use apkmanager to modify my apks if I'm on windows, but if I just happen to be using Linux and I'm too lazy to reboot I use apktool (which requires more work though). For the device id hack, it was a method in framework.jar. Copying and pasting that method from Meticulus's worked for 2.3.6, but would cause a bootloop on 2.3.5 US. So I looked at the logcat and used a modified version of this: http://forum.xda-developers.com/showthread.php?t=955847 for my deviceid hack.
I hate editing smali though...it's so difficult to understand.
klin1344 said:
I use apkmanager to modify my apks if I'm on windows, but if I just happen to be using Linux and I'm too lazy to reboot I use apktool (which requires more work though). For the device id hack, it was a method in framework.jar. Copying and pasting that method from Meticulus's worked for 2.3.6, but would cause a bootloop on 2.3.5 US. So I looked at the logcat and used a modified version of this: http://forum.xda-developers.com/showthread.php?t=955847 for my deviceid hack.
I hate editing smali though...it's so difficult to understand.
Click to expand...
Click to collapse
Thanks! I used apk manager, but it still did not work without fc....maybe i will try a different tool (for some reason it will not recognize adb or aapt in ubuntu even though I can run the commands from the terminal.
It seems we have competing roms now...may the best dev win.
Sent from my Galaxy Player Running my Stratusrom.
hanthesolo said:
Thanks! I used apk manager, but it still did not work without fc....maybe i will try a different tool (for some reason it will not recognize adb or aapt in ubuntu even though I can run the commands from the terminal.
It seems we have competing roms now...may the best dev win.
Sent from my Galaxy Player Running my Stratusrom.
Click to expand...
Click to collapse
Ummm...don't forget that your work is still based off of my work
Editing smali and the framework for new features (powermenu, toggles, etc) is the real ROM work...hehe
Besides, I'm not here to compete; I just want to share my work.
Point taken, I just wanted some friendly competition, it helps to make work go faster.
But, I would like to see you spend 3 hours fixing init.d scripts, and tweaking sysctl for best ram usage.
My point is, we are both skilled in completely different areas. I am better at some things, and You blow past me in others. It just comes down to the users preference.
klin1344 said:
I am trying to get INTL support for this ROM, but unfortunately I noticed that with XXKPQ if I use dsixda's kitchen I get this error when trying to use busybox:
Any busybox applet will result in the same...
It doesn't happen on 2.3.5 G1UEKI8 though.. I have tried unrooting and rerooting, using the install busybox option with kitchen, reinstalling busybox, but nothing seems to work.
So..for now I will only be supporting US devices until someone can either help me get rid of this error or at least help me find another INTL ROM that I can base my work off of.
Click to expand...
Click to collapse
Ugh..I just found out that it is the same with G1UEKI8 as well.
I flashed my factoryfs.rfs version and busybox worked, so I will upload the factoryfs in an Odin package tomorrow. From now on the roms will have to be flashed through Odin until I can find a fix.
Sent using Tapatalk
klin1344 said:
I am trying to get INTL support for this ROM, but unfortunately I noticed that with XXKPQ if I use dsixda's kitchen I get this error when trying to use busybox:
Any busybox applet will result in the same...
It doesn't happen on 2.3.5 G1UEKI8 though.. I have tried unrooting and rerooting, using the install busybox option with kitchen, reinstalling busybox, but nothing seems to work.
Click to expand...
Click to collapse
I have that same issue on my device (different rom). Busybox works fine; the issue is that somehow the symlinks got corrupted (hence the not found and weird characters). I fixed it (post-install) by deleting the broken files and recreating the symlinks in /system/xbin. You might want to check your updater-script or the 'install-busybox.sh' file the kitchen creates.
Sent from my 5.0 USA GenGin + ICS theme
Flash Tool for this ROM
Which flashing utility/method do you recommend for this ROM?
Thanks!
Mevordel said:
I have that same issue on my device (different rom). Busybox works fine; the issue is that somehow the symlinks got corrupted (hence the not found and weird characters). I fixed it (post-install) by deleting the broken files and recreating the symlinks in /system/xbin. You might want to check your updater-script or the 'install-busybox.sh' file the kitchen creates.
Sent from my 5.0 USA GenGin + ICS theme
Click to expand...
Click to collapse
Thank you. So all I have to do is just recreate the symlinks in /system/xbin? I didn't think it would be that easy
Sent using Tapatalk
If we did all that ext4 foo foo should we go back to stock before flashing?
rozelle25 said:
If we did all that ext4 foo foo should we go back to stock before flashing?
Click to expand...
Click to collapse
No need to. It will still work fine with ext4 partitions.
Sent using Tapatalk
What you need to do is make a list of all of the files in /system/xbin that are there after flashing but aren't in your working folder's system/xbin. Those are the (broken) symlinks created by the installbusybox.sh script at the root of your zip. You need to put a symlink command in your updater-script for each of those (referring to the lines already there), and then you can delete the installbusybox.sh script and the updater-script lines referring to it.
Sent from my 5.0 USA GenGin + ICS theme
Everytime I try to turn on Wifi it says error and bluetooth still doesnt work... besides that everything seems to be working fine is there a reason why my wifi wont start?
Like many of you, I like to keep my Android system rootless and true to stock as much as possible. However, I like to be able to enjoy the native support of layers for better look n feel. I wrote the script attached to help me with it however, it doesn't come easy without root access. There are some work cut out for you, read below.
Prerequisites:
Have extracted theme from layers theme app from Play Store. No, I'm not talking about the main theme app which is used by Layers Manager. Rather, it's the apks that go into the /vendor/overlay. I tried to extract respective apks out of the main one without using Layers Manager. However, my attempts yielded no success as I'm getting FCs all over, so I must be missing something. I current have a Nexus 9 which is rooted with Layers Manager, I use N9 for testing out and bring the /vendor/overlay/*.apk onto my N6P under /sdcard for my script to process. If you know of a better way, by all means share.
Of course, kernel which support INIT.D.
TWRP installed for root access via recovery, a MUST.
Busybox installed via flashable zip
Install:
- Download the script attached
- Rename .txt to .sh
- Have all extracted themed apks in one directory. For instance, I like fa and art layers, so my directory on sdcard as such /sdcard/0flash/layers/fa/fa_*.apk
- Change up the first few lines to match your environment
- Boot into twrp, mount /system if needed
- Drop the script into /system/etc/init.d
- chmod 755 /system/etc/init.d/01layersmanager.sh
- Create a file named ".current_theme" in /sdcard/
- In the above file (.current_theme), put the name of theme you want init.d to install. Example, if I want to install "fa" then I'll just have a line of text fa in it (same goes to art, coalesce,etc). IMPORTANT: no trailing new line.
- Reboot and test it out
- If theme successfully installed, you'll see it.
- Also, the /sdcard/.current_theme file will be updated with "current" to avoid theme installation on next reboot if you don't want to install new themes.
Troubleshoot:
See /sdcard/debug.txt for info. If you want additional information dumped, edit the init.d script to echo out more.
O bio hnki
vboyz103 said:
Like many of you, I like to keep my Android system rootless and true to stock as much as possible. However, I like to be able to enjoy the native support of layers for better look n feel. I wrote the script attached to help me with it however, it doesn't come easy without root access. There are some work cut out for you, read below.
Prerequisites:
Have extracted theme from layers theme app from Play Store. No, I'm not talking about the main theme app which is used by Layers Manager. Rather, it's the apks that go into the /vendor/overlay. I tried to extract respective apks out of the main one without using Layers Manager. However, my attempts yielded no success as I'm getting FCs all over, so I must be missing something. I current have a Nexus 9 which is rooted with Layers Manager, I use N9 for testing out and bring the /vendor/overlay/*.apk onto my N6P under /sdcard for my script to process. If you know of a better way, by all means share.
Of course, kernel which support INIT.D.
TWRP installed for root access via recovery, a MUST.
Busybox installed via flashable zip
Install:
- Download the script attached
- Rename .txt to .sh
- Have all extracted themed apks in one directory. For instance, I like fa and art layers, so my directory on sdcard as such /sdcard/0flash/layers/fa/fa_*.apk
- Change up the first few lines to match your environment
- Boot into twrp, mount /system if needed
- Drop the script into /system/etc/init.d
- chmod 755 /system/etc/init.d/01layersmanager.sh
- Create a file named ".current_theme" in /sdcard/
- In the above file (.current_theme), put the name of theme you want init.d to install. Example, if I want to install "fa" then I'll just have a line of text fa in it (same goes to art, coalesce,etc). IMPORTANT: no trailing new line.
- Reboot and test it out
- If theme successfully installed, you'll see it.
- Also, the /sdcard/.current_theme file will be updated with "current" to avoid theme installation on next reboot if you don't want to install new themes.
Troubleshoot:
See /sdcard/debug.txt for info. If you want additional information dumped, edit the init.d script to echo out more.
Click to expand...
Click to collapse
Yt? Bird :
Sent from my Nexus 6P using XDA-Developers mobile app
What is this?
This mod removes the persistent "Device is HD capable" Notification that appears on many custom roms
Applicability?
This mod is meant for Yu Yureka Plus running Resurrection Remix Rom 5.8.0 Official Build. For other devices, keep reading...
How does it do it?
The culprit package that causes this notification to appear in the status bar is ims.apk - located at /system/vendor/app/ims
This mod replaces that file with a modded one. More on that below...
Instruction of use
1) Download file - NR_yurekaRR580o.zip
2) Reboot phone into TRWP recovery
3) Mount > System partition
4) Install > NR_yurekaRR580o.zip file
5) Reboot
Downloads
1) Notification remover - NR_yurekaRR580o.zip
2) To re-enable this notification again, flash this file - NEN_yurekaRR580o.zip
-------------------
FOR OTHER DEVICES
This mod was made using the ims.apk file extracted out of Resurrection remix rom 5.8.0 official build meant for the yureka plus phone. So whether this mod will work on other phones cannot be answered. But if you want to create this mod for your phone, here are some quick lessons:
1) Find ims.apk file in your phone and extract it to PC
Try looking for it in /system/vendor/app/ims
2) Use apktool and do these edits in ims.apk
Decompile ims.apk
In ims.apk>res>values>bools.xml
Change value of config_update_service_status to True
In ims.apk>res>values>strings.xml
Delete value of device_is_hd_capable
In ims.apk>res>values-mcc** (inside dozen or so folders) > bools.xml
Change all values of config_update_service_status to False
Re-compile ims.apk and give necessary signs. And use it any flashable zip
Credits:
This mod is based on KabirKalsi's similar mod found here that he made for the redmi 3. All credits to him.
Will this works in RR Official March build??
Sent from my YU5510 using Tapatalk
Thanks for help. That notification was irritating me since I flashed voLTE firmware. Followed modification steps mentioned above.
PFA, apk file which worked for me on Yu Yureka RR v5.8.2.
Device Model: Yu Yureka AO5510
OS: RR-N-v5.8.2-20170307-tomato-unofficial
Flashed: voLTE firmware.
Android 7.1.1 (Resurrection Remix Nougat 7.1.1_r25 - NOF27B)
Steps to install:
make an adb connection to pc.
1. adb reboot recovery
2. adb push ims.apk /system/vendor/app/ims/
-- expected output -> [100%] /system/vendor/app/ims/ims.apk
3. adb reboot.
Done.
Download link. (remove the spaces)
http :// s000.tinyupload.com /index.php ? file_id = 37766304712524729237
Credits
@broadways
Worked perfectly fine on Moto G4 plus running Ressurection Remix.
If it remove hd sign...then is it add the volte icon??
Sent from my YU5510 using Tapatalk
Worked like a charm
Thanks man! It was really helpful and I used APK Editor to edit the values. Thanks a lot again. Cheers!
thanks for your help,I moved HD capable by this artcle.
Welcome to SuperR's Kitchen Donate version!
This thread is intended to organize release posts. All discussion regarding this kitchen can be found in the thread linked below.
[ Windows / Linux / Mac ][DONATE] SuperR's Kitchen (v3.2.2.2 - 10-13-2021)
Disclaimer: I am not responsible for anything bad that may occur from the use of this kitchen, but I will take all the credit you can give me if it works for you :D Please read the troubleshooting in post #4 of the standard kitchen thread...
forum.xda-developers.com
v3.0.0.1
Changes:
Download and extract Android Image Kitchen (Linux) directly from the XDA thread.
Fixed extracting tar.gz files.
Fixed crash if the main tools download/extract fails.
Fixed crash in Linux when updating the kitchen launcher.
Fixed crash when running the updater if there is no update available.
Added logging to img extract operations.
Fixed crash if Java 8 is not installed on Linux.
Added check for proper java installation on Windows.
Fixed language files other than English.
v3.0.0.2
Changes:
Fixed extracting Pixel firmware.
v3.0.0.3 (Donate version)
Changes:
Fixed custom zips on Pixel devices.
Removed attempts to pip install packages from within the kitchen.
Added logging to adb operations.
v3.0.0.4
Changes:
Require kitchen restart after updating.
Fixed duplicate unmount commands in updater-script when extracting extra img files.
Fixed some language file checks from crashing.
Added official Windows launcher (superr.exe).
The kitchen should install psutil (win/linux) and colorama (win) packages now if they are not already installed.
Thanks to @Xennet for the launcher idea. It makes running the kitchen in Windows a lot easier
NOTE: You should restart the kitchen manually after the update. This will be the last time you will have to remember on your own
v3.0.0.5
Changes:
Fixed Windows kitchen trying to update the Linux launcher.
Fixed cyfile errors.
Fixed system.img.ext4 not being renamed automatically if not in an archive.
Added dialog informing we are getting the plugin list when installing a plugin.
Check for and show error message when trying to run Bash plugins in Windows.
Remove all set_metadata lines with a context of "?".
Add all files in /system/bin to the updater-script.
edit: I forgot to reset the language file in this update, so if you update you will get an error when you try to install a plugin.
Easy fix after update (fresh installs do not need this):
Misc tools >> Reset language - After restart no more error
v3.0.0.6
Changes:
Hopefully fixed crash after signing zips when checking for update-binary script.
Updated Imgextract.exe to 1.3.7.
v3.0.0.7
Changes:
Ignore commented lines in build.prop.
Do not create set_metadata lines for files/directories that do not exist.
Do not use fstab with nodata in the name.
Removed duplicate /system/vendor/firmware set_metadata line.
Fixed tar creation for future use.
v3.0.0.8
Changes:
Minor improvement to set_metadata generation in Windows.
Fixed Android O rom not building due to lack of xbin.
v3.0.0.9
Changes:
zipalign - check to make sure files exist before renaming and record in main.log.
Fixed assert getting broken when building rom.
Fixed line endings in updater-script when running in Windows (thanks to @chevycam94 for pointing it out).
NOTE: You may need to change perm types to something else and back to whatever you want to get the line endings sorted out. Fresh extract will all be good now
NOTE2: If you go to ROM Tools >> Asserts Menu >> Reset asserts to default you will get your assert back to normal if it was broken.
v3.0.1.0
Changes:
Fixed crash when choosing main menu from root zip options menu.
Fixed crash when getting by-name through adb.
v3.0.1.1
Changes:
Fixed crash in Windows when checking for app_chimera at the start of deodexing N and O.
Fixed crash when finishing deodex on M and L.
Fixed crash and show error message when entering the wrong syntax for custom asserts.
Fixed boot/AIK still being part of the repo and causing Windows tools install failure after resetting tools and boot extraction failure on Linux.
Fixed crash removing knox in Windows.
Fixed crash deleting plugins if example does not exist.
Heapsize errors now return you to heapsize options instead of Misc Tools.
Added confirmation when deleting projects.
Tried to fix META-INF1 remaining after builing rom.
Thanks to @chevycam94 for testing like a mad man
v3.0.1.2
Changes:
Fixed logs crash when check for updates on start is enabled.
v3.0.1.3
Changes:
Change root status to rooted when adding Magisk using the plugin.
v3.0.1.4
Changes:
Display root type instead of Rooted.
Fix error during deodex cleanup on L and M.
Fix crash when removing knox.
v3.0.1.5
Changes:
Disable sepolicy-inject root method for Windows.
Fixed sepolicy-inject root method for Linux.
Fixed some debloat/knox checks.
Updated smali/baksmali to v2.2.1.
v3.0.1.6
Changes:
Fix crash when signing zips that use an update-binary script in Windows.
Log zip signing in sign.log.
Fixed update-binary conversion on roms that do not use by-name.
Make a copy of *_statfile.txt after extracting img files in Windows.
Add *_statfile.txt to support zip.
Add META-INF directory to support.zip.
Fixed Downloading/installing screen that disappeared.
v3.0.1.7
Changes:
Fixed manually signing zip when there are more than one to choose from.
Added ability to convert all flashable zips to update-binary script when building.
Added per-project option in Misc Tools for update-binary script - Always convert, Never convert, Ask every time.
Added check for delete_recursive when converting to update-binary script.
Fixed mount command not getting converted to update-binary script if rom does not use by-name.
NOTE: The default of the new update-binary conversion switch is "Ask every time". Remember, this is per project so you will need to change it for all projects if you want it changed globally.
v3.0.1.8
Changes:
Windows: Use 7-zip (included) to extract img files instead of Imgextractor.
Windows: Fixed missing symlinks in updater-script.
Windows: Fixed many file contexts not being set correctly.
Windows/Linux: Fixed system/SYSTEM on devices that use SYSTEM.
Linux: Do not create metadata lines for symlinks.
I think this will fix most of the flashing problems. Let me know how it goes
WINDOWS NOTE: It is important that the tools get updated. The updater should take care of it, but if you get errors that 7z is not found, go to Misc tools > Reset tools.
IMPORTANT: Start your rom fresh and extract from system.img again. Make sure you delete 00_project_files directory if you are reusing an existing project.
v3.0.1.9
Changes:
Windows: Fixed b key press not being recognized.
Added a Back option to the root method options.
Only allow key presses that correspond to menu options.
Fixed project name adding an extra superr_ when creating new project from the project selection menu.
Set permissions of configure.sh to 777 instead of /tmp to 755.