Related
Per App DPI, Per App Settings, Per App Color.. Time for something NEW!
PerAppFonts
(Apply custom fonts on a Per-App Basis)
This module allows you to use your own custom fonts not only without flashing a zip, but also have individual fonts for each individual app. However, due to Android's system permission, there is a catch. Changing fonts for apps will work WITHOUT a reboot, BUT a reboot is needed to LOAD the fonts.. (See important point below)
There are 8 options you can choose from even though you have no fonts. They are bundled in the app.
System Default (aka. Turn off changing fonts), default system Monospace, default system Serif, default system Sans, Roboto Condensed (from kitkat), Storopia (Gingerbread's lockscreen clock font), Rosemary (from Galaxy S3 flipfonts), and Roboto Slab (from Google Keep). More fonts can be added by placing it on your internal/external SDcard and choosing the folder in the preferences
Requirements:
1) Have Xposed Framework installed.
First Install Instructions:
1) Have Xposed Framework installed
2) Install & Enable PerAppFonts in Xposed Installer
3) Download Fonts on your internal/external SD card(if you haven't already)
4) Go to Preferences from the main screen of PerAppFonts
5) Choose the Font Folder
6) Reboot.
7) Start customizing!!
IMPORTANT:
• If you change an App Font, NO reboot is needed, just kill the app and launch,
• If you change your Font Folder, a reboot is required.,
• If you add fonts to your font folder, a reboot is required.
• If you eject your SD-card, the loaded fonts will continue to be usable and changeable until reboot.
• It's recommended you do not store more than 500 fonts on your font folder if you have a single core phone.
(Don't make the same mistake I did. Lag hurts) (**** you READ_EXTERNAL_STORAGE permission)
Screenshots in DevDB Tab right at the top
Great Thanks to:
• rovo89 for Xposed Framework
• Tungstwenty & rovo89 for their open source App Settings.
• Paranoid Android for the App List from HALO)))
• GriffinSauce for the icon
• Dzakus for code contribution
• and many more..
XDA:DevDB Information
PerAppFonts, a App for the No Device
Contributors
zst123
Version Information
Status: Beta
Current Beta Version: v0.3.2
Beta Release Date: 2014-01-04
Created 2013-11-23
Last Updated 2014-01-04
Download from Xposed Repo
If you want fonts, I can recommend you this thread.
Bugs:
ActionBar will not have your applied font unless you enable force fonts.
Changelog:
Version 0.3.2 (04 January 2013 / 1710 / GMT+8)
• Previous APK was corrupted. This should work.
Version 0.3 (04 January 2013 / 1345 / GMT+8)
• Add Russian Translation (By Teinharm from 4pda.ru)
• Hardcode the starting folder to be /sdcard/
(Prevents users from choosing /storage/emulated/0/ which is linked to
the sdcard but is not a symbolic link. Therefore, it will "not exist"
when booting up the system.)
• Show Warning if Emulated path is selected
Older Changelogs:
___________________________________________________________________
Version 0.2 (15 December 2013 / 0100 / GMT+8)
• New App Icon (by GriffinSauce)
• Reimplemented App List (by Dzakus)
• Reimplemented Font Loading (by Dzakus)
• Highlight Fonts that didn't load properly in Red (aka Incompatible Fonts)
• Optimizations for the Font Loader (May Fix External Fonts not loading)
• Optimizations for Settings Activity (May Fix Some FC's)
___________________________________________________________________
Version 0.1.2 (28 November 2013 / 0100 / GMT+8)
• Fix Font Folder Force Closing on ICS Devices.
• Fix Font not showing if it uses (caps) .TTF instead of (small) .ttf
Version 0.1.1 (23 November 2013 / 1700 / GMT+8)
• Fix Exception if font folder is non-existent.
Version 0.1 (23 November 2013 / 1240 / GMT+8)
• First Version Released
___________________________________________________________________
For Developers
PerAppFonts is open-source. The source is found on my GitHub.
If you would like to help in the development, you may leave bug reports and development tips in this thread or (better still) fork and send pull requests.
PerAppFonts might be compatible with Gingerbread in the future. All that is needed is to change the ActionBar related stuff to Menu and TitleBar. (If anyone wants to do this, Great! Less work for me.)
If you want to integrate anything in my module into your own ROM, no need to ask for permission, just mention me so I can keep track.
nice
Amazing Mod idea
But when I enabled it in xposed
i went to choose font family it force close !
vip57 said:
Amazing Mod idea
But when I enabled it in xposed
i went to choose font family it force close !
Click to expand...
Click to collapse
Oh.. Sorry.. A Minor Bug if the folder is non-existing.. Updated the app to v0.1.1 . Also, since the folder is not existing, I guess you forgot to select your font folder.
Another amazing work bud. Even if you say you're not amazing, you're indeed:laugh:
Thank you so much for your Xposed Mods, @zst123!
They are all so awesome! This one also works great on my Galaxy S3!
Great work
In my case , I created a folder for custom fonts . but the fonts were not applied any where.
Rest every thing is fine. Thanks for this unique app.
Request to add some more fonts as all the included fonts are almosts lookwise similar.
droidsman said:
In my case , I created a folder for custom fonts . but the fonts were not applied any where.
Rest every thing is fine. Thanks for this unique app.
Request to add some more fonts as all the included fonts are almosts lookwise similar.
Click to expand...
Click to collapse
Did you restart after putting the fonts? Also, remember to kill the app before launching.. It is easy to miss that out..
i was looking for this
great man
zst123 said:
Did you restart after putting the fonts? Also, remember to kill the app before launching.. It is easy to miss that out..
Click to expand...
Click to collapse
Before I got the concept of killing the apps I was rebooting the phone every time to apply the fonts.
BTW I am happy with current version. Thanks
thanks... very great module... :good:
thanks working flawlessly
thanks so much. its a very useful app
Custom fonts not applying...
I downloaded the fonts in fonts folder in internal sd card and all the fonts are showing in the app after rebooting but when I tried to apply the custom fonts on any app, it doesn't work.
Please, help..
vaibhav011286 said:
I downloaded the fonts in fonts folder in internal sd card and all the fonts are showing in the app after rebooting but when I tried to apply the custom fonts on any app, it doesn't work.
Please, help..
Click to expand...
Click to collapse
Did you click on the "X" button beside the launch button to kill the app? Also, some fonts are not compatible with Android but the system will not show an error, but just show the original font (Roboto).
asfandyarali2 said:
thanks so much. its a very useful app
Click to expand...
Click to collapse
1) Please do not quote the OP.
2) Please do not say "its a very useful app". Please post if you have suggestions, bug reports or tips for users. Click the Thanks button if you want to say thanks
What a beautiful Xposed module! I'm running MOAR 6.1 with Aviate launcher and have the launcher text and pulldown (system UI) using 2 different fonts and that is what I call kool! Thank you so much for this.
Sent from my SPH-L710 using Tapatalk
it force closes when i add custom fonts
eyesore123 said:
it force closes when i add custom fonts
Click to expand...
Click to collapse
May I have a logcat? Does it happen when there's a single font in the folder? or happens after a few fonts were added. What I can think of now is either the fonts are too large to handle (Very complex fonts) or you placed too many fonts (probably a few thousand to even force close like that).
zst123 said:
May I have a logcat? Does it happen when there's a single font in the folder? or happens after a few fonts were added. What I can think of now is either the fonts are too large to handle (Very complex fonts) or you placed too many fonts (probably a few thousand to even force close like that).
Click to expand...
Click to collapse
no, it force closes even with a single font, and so with few fonts..
how can i get a logcat for this? (sorrry im a noob :laugh: )
eyesore123 said:
no, it force closes even with a single font, and so with few fonts..
how can i get a logcat for this? (sorrry im a noob :laugh: )
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1726238
Hi, im currently developing a system for wifi-direct application testing.
To do so, i need to change some classes in the android framework, specially in android.net.wifi package.
I've downloaded the Android 6.0.0 source tree, made some changes and recompiled it to x86 to push the new framework into the emulator. (Running Nexus 6 image with Android 6.0.0)
After that i pushed the recompiled jars, boot.art and boot.oat, and the odex files.
When i restart the emulator the image don't work.
Is this possible to do? Change the framework or at least part of her implementation and manually push the files into the emulation?
If so, what can i be doing wrong?
Thanks for the help, Filipe Teixeira
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
I don't take responsibility for any damage may happen to your device because of using this tool, USE AT YOUR OWN RISKA new generation of Android ROMs development...The ClassyKitchen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About:
A new C++ Windows application that based on ASSAYYED KITCHEN to deal with the most of android ROMs (stock images, stock updates, running device ..... etc)
In addition to built-in apktool to easily decompile & recompile apk in the PROJECT
And with a friendly user interface with full mouse control just one click.
With static build feature and a new built-in windows tools feature (hex dump) that makes the whole working environment into one exe file only.
ROM editor features:
1 - Supported ROMs type for extract:
Any stock system[lz4] & boot[lz4] [cache | odm] images
All Samsung stock firmwares (TAR[.MD5]) with support for LZ4 compress
All Google stock firmwares (ZIP)
All Lineage stock ROMs (system.new.dat[br] & vendor - payload.bin)
Any other images dumped from other stock ROMs (Huawei - HTC.....etc)
Rooted device OR custom recovery (*With technology to dump boot & system & vendor images without need a space on device*)
2 - Supported ROM edits:
Pre-remove for Samsung RMM security
DeOdex for android [4.x.x] till [9.x.x]
ZipAlign for all APKs & JARs
Heavy DeBloat ROM with Re-Bloat
Full DeKnox ROM
Clean ROM from all CSC apks (in Samsung ROMs)
Support safe and powerful Build.prop tweaks
Support change Build Number text
Support add busybox into the ROM itself with all available symlinks in image
3 - Supported ROM build:
ZIP ROM contains sparse system [vendor & odm] dat
ZIP ROM for custom recovery flashing
ZIP images ROM for fastboot flashing
TAR images ROM for Samsung devices
Support compress Samsung images with original LZ4 format
4 - Supported boot image edits:
Support all boot images partitions names other than boot.img
Remove dm-verity with AVB & ForceEncryption
Enable ADB
Patch sepolicy (supports CIL) to supported deodexed Oreo
Add / Remove Magisk Root to boot image directly in windows
Support patch boot image to run scripts during boot that placed in /system/smart_scripts
5 - Supported Apktool:
Decompile single apk
Recompile single apk
Sign single apk
Support option to specify [New | Original] apk signature
Support use custom apktool.jar selected by user
Support Decompile - Recompile multi APKs in the same time
Support Decompile - Recompile JAR files (Support multi classes files)
6 - Supported On Device Features:
Support dump full device memory using (adb root) - supported (EMMC & UFS) Without need any space on device
Support dump specified partitions from device using (adb root) - (List to user and pick needed partitions)
General Features:
Quite simple user interface
Very safe when working with images ROM for files [modes, gid, uid, contexts, capabilities]
Read the exact EXT4 [symbolic links, full permissions] and re-apply them when building
Write full permissions for [fs_config, contexts, capabilities] when building an EXT4 image or in [updater-script]
Support fix the case sensitive problems with ROMs like (Samsung S8 / S8+)
Support save project and restore it when needing
Support [Added edits log] to allow the user to see all edits he made
Support add custom text during flash in recovery
Support save the system image and [odm] image sizes to rebuild them using the exact original size
Support allow user to change the build configs (size, sparse header, images ext)
Support custom debloat list
Support more that one connected ADB device and list them to user to pick one to pull ROM from
Pro Version:
The kitchen has two versions Free & Pro
And the Pro version requiring a small donation (20$) and it needs an authenticating code to run it on a specified PC,
If anyone need to use it just download and run then send to me the output code with a transaction ID to send the activation code that match the given code.
NOTE: The Pro version is to supporting my work only, and the Free version is enough to create a full modded flashable ROM
- The following features are only available in Pro version:
All On Device Features
Pull ROM from Rooted device or custom recovery
Change Build Number text
Build TAR images ROM for Samsung devices
Build ZIP images ROM for fastboot flashing
Add Magisk Root to boot image directly in Windows
Patch boot image to run script during boot
Decompile - Recompile multi APKs in the same time
Manual DeBloat as user wants
Download link:
- Latest Free Version: http://www.mediafire.com/file/7uch95enkpc7q2p/ClassyKitchen_Free_Beta_1.0.4.7z/file
- Latest Pro Version: http://www.mediafire.com/file/l62q85rj8d8lqu0/ClassyKitchen_Pro_Beta_1.0.4.7z/file
Changelog:
- Version: 1.0.4 - BETA:
Added support to build sparse dat images
Improved some props read in OnePlus devices
Added new tab On Device Features: Support dump Full device memory without need space on device & dump selected partitions without need space too (Pro Version)
Updated flash_kernel.sh script
Updated Magisk to version 18.0
- Version: 1.0.3 - BETA: Free Version - Pro Version
Added support to Decompile - Recompile multi apks in the same time (Pro Version)
Added support to manual DeBloat (list all ROM apks to user to pick one and remove) (Pro Version)
Updated DeKnox list
Improved dump ROM from device (skip search for ODM - VENDOR partitions if the device doesn't have them)
Added support to decompile & recompile JAR files
Added support to deal with boot images that have names other than boot.img
Added support to build ODM image in fastboot build option
ReCoded all Deodex codes to support ROMs that have symlinked 64 oat files like Huawei devices
Updated Magisk Root files and Magisk sources to v18
- Version: 1.0.2 - BETA: Free Version - Pro Version
Added support to ReCompress Samsung images to LZ4 during TAR building
Updated packing original APK signature during APK compiling
Updated Magisk to 17.3 (2018-11-22)
Added SmartScripts feature to easy run scripts as Root during system boot (Pro Version)
- Version: 1.0.1 - BETA: Free Version - Pro Version
Fixed bug happened when switch from system_root to system type ROM
Added support to vendor (build zip - build images - extract)
Updated building images codes (better size printing)
Added support to (vendor.new.dat[br])
Added support to pull vendor image from Rooted devices
- Version: 1.0.0 - BETA: Free Version - Pro Version
Initial release
Reports & Request features:
To report any issue Please provide a pic for the Error happened in the Kitchen and A link for the ROM used (Without them I can not provide any help) (Posting here not via PM please).
To request any features to add or any notes about exists features just post about them on this thread (Or via PM).
Credits:
- Cygwin Project: For base tools to deal with Linux symbolic links in Windows
- 7zip: For 7z binary to deal with EXT4 filesystem
- AOPS Platform Tools: For ADB tools
- And_pda: For ImgExtractor tool
- LZ4 Project: For sources to deal with lz4 compressed images
- AOSP Sources: For all android sources (sparse converting, simg2img, aapt, zipalign, brotli, cdex_convert_sources, readelf......etc)
- Cubinator: For his EXT4 images analyzing python sources
- testwhat: For oat2dex tool
- anestisb: For vdexExtractor tool
- Linus Yang: For compact_dex_converter tool
@topjohnwu: For Magiskboot tool sources
@JesusFreke: For his Smali & Baksmali
@xpirt: For sdat2img python tool
@iuss: For payload_dumper python tool
@iBotPeaches: For apktool tool
WoW , that was mind blowing . I Just got my Pro version, and i build my first tar rom and it was flashed successfully . Thank you sir.
Hello , Is this suitable to port roms , by repacking rom files , as i have a unpacked system folder need to repack to system.new.dat.br or system.new.dat
thank you
arvs47 said:
Hello , Is this suitable to port roms , by repacking rom files , as i have a unpacked system folder need to repack to system.new.dat.br or system.new.dat
thank you
Click to expand...
Click to collapse
Currently working with system folder is not supported due to hard get of correct permissions and image configs.
I will add support for that soon with creating system.dat*
AndroDef said:
Currently working with system folder is not supported due to hard get of correct permissions and image configs.
I will add support for that soon with creating system.dat*
Click to expand...
Click to collapse
ok i am trying to port asus zenfone 5 2018 zenui rom into Asus zenfone max pro m1
so does this app support manufacture rom port once you add system.dat support
arvs47 said:
ok i am trying to port asus zenfone 5 2018 zenui rom into Asus zenfone max pro m1
so does this app support manufacture rom port once you add system.dat support
Click to expand...
Click to collapse
No, Porting feature is not supported now
How do i create custom debloat lists?
Really great application! Made my first rom using it!
Sent from my dream2lte using XDA Labs
dr460nf1r3 said:
How do i create custom debloat lists?
Really great application! Made my first rom using it!
Sent from my dream2lte using XDA Labs
Click to expand...
Click to collapse
Create a (txt) file and write in it all items you want to remove (Names with extensions only without paths)
Then press on Debloat and select custom debloat list and select your txt file (File browser)
At samsung ruins, it would not be possible to include vendor.img.lz4 among the unpacked and repackaged
You also have to change things to get the better rom done
Thanks in advance
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
When downloading offical firmware there are lots of other images which are flashed via odin such as vendor etc. By using the kitchen only the system image is used.
Sent from my dreamlte using XDA Labs
dr460nf1r3 said:
When downloading offical firmware there are lots of other images which are flashed via odin such as vendor etc. By using the kitchen only the system image is used.
Sent from my dreamlte using XDA Labs
Click to expand...
Click to collapse
Thanks for the prompt answer. I didnt have a clue about that. Good to know.
Any idea why my SIM and radios got screwed up. No cellphone signal, didnt even ask for the SIM pin as if it didnt see it. The wifi didnt connect the usual network. Bluetooth kept asking me many times to confirm the connection code of my WearOs watch.
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
Before flashing any modded ROM with the kitchen flash the Full stock copy of the ROM first.
If this doesn't work try to flash a ROM by the kitchen but without any edits to know if the problem from edits or kitchen itself.
AndroDef said:
Before flashing any modded ROM with the kitchen flash the Full stock copy of the ROM first.
If this doesn't work try to flash a ROM by the kitchen but without any edits to know if the problem from edits or kitchen itself.
Click to expand...
Click to collapse
Do you mean flashing the full stock on Odin? That would make me lose TWRP. And the idea for me of using your very nice ROM creating tool was to remain official, rooted, without having to install custom recovery again.
It worked perfectly on my tablet.
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
rstwingo said:
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
Click to expand...
Click to collapse
Thank you for the explanation
Sent from my SM-N960F using Tapatalk
rstwingo said:
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
Click to expand...
Click to collapse
Sapiens said:
Thank you for the explanation
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
I finished add support for vendor partition and will release the update soon.
AndroDef said:
I finished add support for vendor partition and will release the update soon.
Click to expand...
Click to collapse
Looking forward to testing that update!
Sent from my SM-N960F using Tapatalk
---------- Post added at 10:58 AM ---------- Previous post was at 10:18 AM ----------
AndroDef said:
I finished add support for vendor partition and will release the update soon.
Click to expand...
Click to collapse
Also, is it possible to have for the debloating option, a list based on the default list that you provide where one can tick and untick apps to select what to remove and what to keep?
I know this requires more programming. If not possible then to provide the default list that you use to debloat, so we can customize it please.
Thanks
Sent from my SM-N960F using Tapatalk
vendor.new.dat missed
Sapiens said:
Looking forward to testing that update!
Sent from my SM-N960F using Tapatalk
---------- Post added at 10:58 AM ---------- Previous post was at 10:18 AM ----------
Also, is it possible to have for the debloating option, a list based on the default list that you provide where one can tick and untick apps to select what to remove and what to keep?
I know this requires more programming. If not possible then to provide the default list that you use to debloat, so we can customize it please.
Thanks
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
After debloat process you can navigate to (PROJECT_FILES/DEBLOAT) and delete what you want then restore the needed items by the kitchen, However I will add manual debloat feature and currently I attached the debloat list of the kitchen.
daxiaamu said:
vendor.new.dat missed
Click to expand...
Click to collapse
Send to me a link for a firmware contents that file.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WELCOME TO 420 ROM - MAGISK ROM FOR SAMSUNG GALAXY NOTE 20 ULTRA 5G N986B (EXYNOS)
Telegram-Group
Please bear in mind that things will be added as and when my learning and time permits (being a dad with a family and having ADHD myself means things get a lil gnarly) but i will aim to support this ROM as regularly as possible.
Ill usually release a test to one or two users before each release also - :cyclops:
CUSTOMIZABLE ONEUI EDITION MAGISK ROM FEATURES: - with Vol +/- keys
-Add YouTube Vanced - thanks to Vanced peeps github
-Add 3minit battery - thanks G Harrington - if online menus don't appear, install the apk that the module places on your internal storage in the 420rom folder. (PLEASE SEE KNOWN ISSUES FOR INSTALLATION)
-Add 3minit clock - thanks G Harrinton (PLEASE SEE KNOWN ISSUES FOR INSTALLATION)
-Add V4A
-Add custom 420rom bootanimation thanks to @chalmizzle
-Add SamsungSans fonts apk
-Add Goodlock
-Add SoundAssistant (for increased vol steps)
-Add Customized Secsettings (420 banner in every phone info screen) (coming soon)
-Add Custom wallpapers (coming soon)
-Remove Chrome
(further debloat options for stock rooted base)
-Remove Bixby
-Remove Netflix
-Remove kidshome
-Remove Facebook_stub
-Remove FBservices
-Remove Upday
-Remove Onedrive
CORE MAGISK ROM FEATURES
-installs custom secsettings
-Detects OMC code and ensures correct OMC folders and files installed (multi OMC support hopefully coming - thankfully OXM should be sufficient for now - please let me know if your N986B CSC isn't supported and ill see what i can do)
-detects base rom or rooted stock and presents relevant install features and aborts if attempted to be installed on anything else - should help keep non compatible setups intact
-Device detection as i'll will now be supporting several N20 variants
Enabled the following CSC fetures: (thanks @m8980
- Disable shutter sound menu
- AppLock Protection menu
- Support RealTime Network Speed in status bar - working
- Enable Camera during call
- Enabled call recording
- Data usage in quick panel - the feature displays but not the actual data used - if anyone knows a fix, let me know
- Block call number menu
GOOGLE EDITION FEATURES (FURTHER TO THOSE IN ONEUI EDITION MODULE ABOVE)
This Module is based on the main Main 420rom Rom Module but replaces some of the Samsung apps with Google ones. It is recommended to backup your Samsung apps 1st!!!
Installed with Module - Samsung App it replaces
--------------------------------------
Google Phone - Samsung Phone
Google Contacts - Samsung Contacts
Google Messages - Samsung Messenger
Google Chrome - Samsung Internet Browser
Google Calculator - Samsung Calculator
Google Calendar - Samsung Calendar
Google Clock - Samsung Clock
Google Drive - Samsung Cloud (stays installed)
Google Files - Samsung MyFiles
Google Fit - Samsung Health (can be reinstalled from Galaxy Apps)
Google Pay - Samsung Pay
Google Keep Notes - Samsung Notes
Google Photos - Samsung Gallery
Google Recorder - Samsung Recorder
Google TTS - Samsung TTS
Google Duo - n/a
Google News - n/a
Google Tasks - n/a
Google Sounds (Sound Picker) - n/a
Google Apo - n/a
Google Carrier Services (for RCS) - n/a
GBoard - Samsung Keyboard
GMail - Samsung Email
YouTube Music - Samsung Music
YouTube Vanced, Vanced Manager & Vanced MicroG - YouTube
Nova Launcher - OneUI Launcher
RECOVERY FLASHABLE BASE FEATURES
-Does away with warning on splash
-Debloated a fair whack but not too much
-rebased with each firmware update (when possible)
-rooted with magisk manager
-latest disabler from @ianmacd included (cheers for this and TWRP mate)
-flashes latest TWRP during Base flash
Changelog
v3.8 (3.7 unreleased)
- rebase to DUF8 - July patch
V3.6
- Main big change is that install options are now taken care of by the (now renamed) MASTER MODULE - you will be presented with your installation options on the first zip you install - these will then be picked up by the ROM MODULE that will automatically flash the relevant features selected in the MASTER MODULE flash.
- Rebased to DUDA - (next update will probably just be a rebase as new June firmware will be here v soon)
- Magisk v23 installed
- I have included the Audio Modification Library module for until they sort V4a out. The process to get v4a working is:
1 - Activate the AML module in magisk and reboot then when rebooted into system start v4a and install drivers (it will reboot)
2 - on reboot, disable the AML module and then reboot system once more
3 - when rebooted to system, start v4a and reinstall the drivers
4 - v4a should be functional after reboot
V3.5
This version brings a lot of automation to the install process. The mother module script will detect if the convertor has been flashed over that particular firmware and then make the convertor zip automatically if it is needed - in the case of reapplication of the rom or if i bring out an incremental update on the same firmware then this will mean that the convertor will be skipped by the mother module script and the rom module will be made only.
In short, the Mother module does my job by cooking the rom module and convertor mid flash
-Also rebased to DUD1 firmware
v3.4 Simple rebase to DUC8
- rebase to DUC8 firmware and most recent TWRP added
v3.3 no more disabler required after odin flash
- disabler files now added to odin files, no standalone disabler flash required anymore.
- rebased to DUC1 March patch
- workaround was required for wallpapers and will have this back to normal next time but end result is exactly the same. We're just using the DUB6 apk in this firmware no wallpapers were showing with DUC1 wallpaperres.apk
V3.2 another big update!!!! - in addition to the changes brought in recently, i have decided that patching system files instead of replacing them will be better going forward - the upshot for you guys is that the install process is even quicker now and the total package size has gone from 500mb to 240ish mb, yet the end result is exactly the same as any other release The convertor copies the relevant files from device and the rom module makes the amendments needed.
- fixes to backup and restore function
- tidied up script a bit
Now live in link in first post!!!
3.1- smallish update in comparison but still needed
- Home up added to goodlock package in rom - this incorporates task changer
- fixed Auto backup backing up previous rom options when new Rom Module selection option is selected (i.e no to restoring)
- Will now NOT install if any firmware version other than the one matching the rom is present
3.0- addition of Rom Module options backup/restore and rebase to OneUI 3.1:
- I have created a new Rom Module backup and restore function which will read the setup of the last rom module install (v2.6 onwards only) and ask you if you want to restore your previous install options. It will also backup any CSC features choices you make. This was not easy due to the complexity of my other function
-soundassistant updated
-some script optimisations and tidy ups
-completely rebased to DUB6 OneUI 3.1 - hence V3.0
-CTS fix working perfectly and is included as an install option
2.5 - big refinement on changes in 2.4
- module base convertor now installs the cts fix module automatically and systemlessly
- the Mother Module sends the convertor to internal/420rom which will then delete itself after flash and replace it with the rom module in internal/420. This is because it could be confusing with so many folders
- convertor now clears any old 420rom modules
- the convertor checks for old internal 420rom directory and clears it if detected then sets up a new one.
- more general automation and tidy ups in scripts applied
- advanced power mode app added for booting to recovery on the fly easier
2.4 - Big format change - see second post
2.3.2 - incremental update
- Added CTS safteynet fix by @kdrag0n - (huge thanks for your contribution to the community man!!!) - thread
2.2-2.3.1 (unreleased xmas testing)
Rom-module
- rebased files to CUA2 Jan firmware
- moved all install and extract code to functions which are each called when you select an install option for the magisk rom module features - main upshot is that it saves a **** load of time installing the module. The long boring extraction list before the install options is now a past nightmare
- tidying up the script big time - variables defined for mod extraction paths etc - makes debugging much easier haha
Module Base
- rebased to CUA2 Jan firmware
- Latest TWRP from Ianmacd included from now on - the base will automatically flash this.
- updated disabler included
- Magisk updated to V21.2
v2.1 (unreleased) & 2.1.1
- Full script rewrite for a big big change in cscfeatures implementation method
- csc features are now selectable should you not wish to install all of them
- updated source to CTL5
- CSC mod fixes
- bugs and performance fixes
v1.1/1.1.1
-changed default wallpaper
-compressed mods in module zip to save space
-added debloat to updater script - debloat is carried out after image flash (fixed issues in 1.1.1)
-general theme refresh
-fixed sound assistant not installing
v1-b6-b10
-added CTS fix
-added wallpapers
V1-b5
-implemented updated 3minit install procedure @starbucks2010 - cheers for the help and code for my flashable zip
-added updated YoutubeV manager etc - install youtubeV from manager is recommended
-tidied up install script
V1-b3&4
-unreleased, research mules for failed patch testing :laugh:
V1-b2
- initial xda release
what's next? & Known Bugs we can't do much about or will sort eventually
-N980F/N985F support
-Google edition of the module
-incorporation of further goodies into magisk rom and base
-if A SYSTEM APP hasn't been removed, try uninstalling it you should now be able to - any updates installed over an original system app remain as they are data apps following an update
CORE DEV TEAM
Myself - team owner and Rom Module chef
@abun880007 - team co-conspirator
Huge thanks to.................
@abun880007 for the legendary support and collab
@Zackptg5 for the brilliant MMT Extended zip
Rooted with Magisk - thanks @topjohnwu
@topjohnwu for magisk
@Winb33) for the samsungsans7.2 fonts
@superr for the kitchen
@starbucks2010 @ASHLEY117 & @ZonalRipper for showing me winrar was sh## and for all you help with getting around these invisible system.dat.br issues i was having! :good::laugh: link to Beyond Rom S20 Thread
@Team_DeWitt for the Awesome V4A 2.7 - a must have for audiophiles!!
G Harrington for the 3minit apps
Team Vanced for bringing us all youtube Vanced
@dr.ketan for the various pointers and sage advice
Finally, @m8980, thanks for letting me adapt your CSC features into my module. :good::good::good:
DOWNLOADS
MASTER MODULES
STOCK ROOTED ODIN FIRMWARE
XDA:DevDB Information
[MAGISK Rom & Base], ROM for the Samsung Galaxy Note 20 Ultra
Install procedure for V2.4 onwards has changed drastically as has the format of the module base itself
From now on N20U and soon on N10 and Tab, there will be no more 4gb zip files to flash (im sick of the time wasted waiting for copying and flashing lol) - the total size of files has gone from 4.5GB to 450mb but you will have exactly the same end result!!!!!!
I have created an "Mother Module" or "MM" which, when flashed in Magisk, places a (Magisk installed) Rom Module zip and a (TWRP flashable) Module Base Convertor zip into their own folder on internal/420.
The next thing to do is to go to TWRP and locate the Module Base Convertor zip and flash it. This will apply all debloat and This will also trigger a marker that will allow the rom module to be flashed.
Once the first zip is flashed, you can then go and install the rom module as normal in Magisk
I will be providing rooted stock firmware to start the whole thing off
BEFORE YOU START. DO NOT ATTEMPT TO FLASH THIS OVER A DIFFERENT DEVS ROM - IT WILL CAUSE ISSUES. BACKUP APPS AND DO A FRESH STOCK INSTALL FIRST - that's even if you get past the failsafe
Install process assuming you are on matching firmware to the released Rom and rooted
1, Flash the mother module in Magisk - reboot to TWRP
2, In TWRP, flash Module Base Convertor located in internal/420- this will apply all the modifications and debloat to your rom that i used to on the Old full size zips
3, reboot and install rom module in Magisk as normal- all done!!!
Install Process assuming you are coming from earlier 420rom:
1, Using the odin files i have provided, flash BL, Modded AP, CP and HOMECSC in Odin with AUTOREBOOT off
2, Keeping phone plugged in, hold vol down and power to exit download and immediately hold vol up and power to enter TWRP.
3, flash Multidisabler & reboot.
4, Flash the mother module in Magisk - reboot to TWRP
5, In TWRP, flash Module Base Convertor - this will install a few generic niceties seen on the module bases of old (No red text etc) and debloat a fair whack of crap out
6, reboot and install rom module in Magisk as normal- all done!!!
on a side note........................
How i patch and add TWRP to the Stock AP file - aka making stock rooted odin flashable files
Producing a stock rooted firmware is really easy and i would hope it would be part of people's standard updating process from now on & will take most people 10 mins if instructions on Xda are read through but I will make them nonetheless.
1, extract firmware zip so you have BL, AP, CP and HOMECSC visible (Put CSC aside)
2, copy AP to internal on phone and patch with Magisk (install -> select and patch file). Once done, copy the Modded AP file (also called magisk patched tar) that Magisk produced from /downloads on your phone's internal storage back to your firmware folder - call this one Modded AP or whatever.
3, get the latest TWRP and rename to recovery.img, drop the image into the magisk_patched.tar (delete recovery.img.lz4 if present)
4, extract the BL folder and delete vbmeta.img.lz4 in the extracted folder, pull out vbmeta.img from magisk_patched.tar and copy to the BL extracted folder - re-tar this BL folder using 7z. DO NOT REMOVE VBMETA.img from magisk_patched tar - call this one modded BL file or whatever.
5, you can now go ahead and flash Modded BL, Modded AP, CP and Homecsc in odin
Reserved
another
one more
Yes!!! Definitely rooting and flashing!
Sent from my [device_name] using XDA-Developers Legacy app
speedyjay said:
yes!!! Definitely rooting and flashing!
Sent from my [device_name] using xda-developers legacy app
Click to expand...
Click to collapse
hello maaaatttteeee!!!!
Hi, I just wanted to know, with this rom, can you edit and modify system apps? Because am unable to do it, when I try to remove a system app, it won't let me. With the s20 this is fixed installing the vbmeta_disabled file.
Looks nice
mcgomfer said:
Hi, I just wanted to know, with this rom, can you edit and modify system apps? Because am unable to do it, when I try to remove a system app, it won't let me. With the s20 this is fixed installing the vbmeta_disabled file.
Click to expand...
Click to collapse
Can you possibly point me to this? could find this very handy (if it's shareable)
Thanks for the work.
Need a detailed installation guide.
Hi, are there any instructions for flashing this rom, because am flashing, but when finished and rebooting, it goes into bootloop.
tuanduy7453 said:
Thanks for the work.
Need a detailed installation guide.
Click to expand...
Click to collapse
Yeah, a detailed installation guide would be great.
Install procedure in second post
Dex not working
Samsung DEX doesn't seem to be working, tried to connect it to Samsung tv, but won't work. Any idea how to fix this?
Play store crash... Goodlock navbar not supported
and i cant take screenshot everywere it says... U cant bcoz of security policy.....
Nice working rom waitin more updates
ok now i have gotten past a tonne of the quirks this new device is throwing out so will be releasing an updated base and module shortly.
- any users of 3minit wont have to install the apk manually - just flash a zip i will provide and then select the option in the module install steps - took me a while to get my head around the /system mounting lol
- add themed secsettings
- add wallpapers
- take a look at Dex issue - can anyone else confirm this issue?
exocetdj said:
ok now i have gotten past a tonne of the quirks this new device is throwing out so will be releasing an updated base and module shortly.
- any users of 3minit wont have to install the apk manually - just flash a zip i will provide and then select the option in the module install steps - took me a while to get my head around the /system mounting lol
- add themed secsettings
- add wallpapers
- take a look at Dex issue - can anyone else confirm this issue?
Click to expand...
Click to collapse
Dex working fine for me.
For me DEX isn't working won't connect with Samsung smart TV.