[Tutorial] Build Your Personal Magisk ROM - ZTE Axon 7 Guides, News, & Discussion

Figured some adventurous soul might have fun with this.....​
Anyone who follows our thread in the development section of this forum probably has figured out that I am a huge fan of @topjohnwu and Magisk.
Our team maintains a Magisk ROM there. So I decided that I would try to show anyone interested how to make their own personal Magisk ROM that they can flash over the stock ROM provided by ZTE.
I'm not big on disclaimers. You flashed a custom recovery, Right?
This may or may not work on LOS based ROMs. I am an audiophile from way back, and I'm not gonna flash and test any of it until someone says," sound is fixed 100% " Not, "I can kinda get by w/ this or that".
It's why I bought the phone.
Attached to this post you will find two templates. ROM.zip, and badboyz.zip (I'm feeling lazy, didn't feel like messing w/ the updater script). Download them both, and unzip onto your desktop. Most of the editing will be done in the badboyz.zip. We will deal with that first. Here is what the file structure should look like:
{
"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"
}
In the first folder, \common, there is a file named post-fs-data.sh. This is where you put your build.prop edits. I have left two examples to demonstrate proper syntax. Note that:
Code:
persist.adb.notify=0
As it would normally appear in build.prop becomes
Code:
persist.adb.notify 0
Feel free delete the demonstrative entries when you are finished with your edits.
You also will find a \system folder. If you have an app you would like to add to your ROM as a system app, or a system app that you have edited, i.e. SystemUI or Settings this is the place. Magisk will overlay the apk included in the stock ROM. You can also add edited files to /etc, /media, etc. just make sure to maintain the proper file stucture
Next we move on to the config file:
1) Call it what you want w/ no spaces (you'll need this later)
2) Call it what you want- This prints out on the twrp screen when flashing the module
3) This is where you debloat. I left two examples in the template (as seen in the ss). Anything you don't want to run, show up in the drawer,or on all applications, list it here keeping the proper folder structure.
Again, these entries can be deleted. They are there for demonstrative purposes.
The module.prop file is pretty self explanatory (tbd= to be determined)
Do notice that the module id matches the one from the config file........(where I said you'll need this later)
You can change both of these. Just make them match.
The rest- you can put your mom's facebook page, donation link for the red cross- whatever you want
So all that is left is to zip all those files up, and your ROM module is done.
Now let's make a flashable. That Rom.zip that you decompressed-
Inside there is a data folder. Leave the Magisk.apk and the PHH su apk there. You will need those. Anything else you have that you want to add throw it in there. Teeter.apk, Netflix whatever.
Then put your rom module (should be named badboyz.zip) into the magisk folder w/ the magisk.zip.
Now zip the whole shabang up and flash it over a bone stock ROM w/ a stock kernel.
Please follow THIS guy and donate what you can. Android will be a better place w/ him

Reserved

Mine

Super info, thank you. Can Masquerade be integrated to allow Substratum theming?
HERE is some detail I have found, but I don't understand exactly what to do.

Is there a working nougat kernel for a2017G knocking around which patches for Safety net? The ones i found only worked with A2017U, so WiFi and a few other things don't work

H0lmEd said:
Is there a working nougat kernel for a2017G knocking around which patches for Safety net? The ones i found only worked with A2017U, so WiFi and a few other things don't work
Click to expand...
Click to collapse
This should work for whatever ROM/kernel you are currently on.

Thank you for this amazing post

Themed stock ROM?
amphi66 said:
Super info, thank you. Can Masquerade be integrated to allow Substratum theming?
HERE is some detail I have found, but I don't understand exactly what to do.
Click to expand...
Click to collapse
Maybe a bit late: this https://xtremetricks.net/theme-stock-android/ seems to indicate stock ROM can be themed with substratum. If that is so, then you could include substratum in your personal magisk ROM.

Will this work on any android phone?
Sent from my ASUS_I01WD using Tapatalk

Related

How to...install CRT animation on rooted phone with OC kernel, NO ROM needed...

Hi everybody,
I think its best to address my question in a new topic since its the best way to get attention and maybe many others like me (noobs ) will go and read about this.
So as I said, I am a complete and utter newbie at all of this! so thats a warning so you know who you are dealing with here
The facts are: I got a Galaxy S2 i-9100 wich I already have rooted + I also have installed an overclock kernel (terminology is correct?).
The kernel I found on this page: http://www.androidng.com/how-to-overclock-samsung-galaxy-s2
Its the one from SetCPU and its a kernel you commonly find when doing a google search: "how to overclock Galaxy SII"
Prior to that I used the insecure.tar Kernel (KDD) that was posted in this topic:
http://forum.xda-developers.com/showthread.php?t=1056334
But I assume that information is irrelevant since I got the overcock kernel now.
And so this is how my system looks now:
{
"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"
}
All I want to do now is have that cool looking CRT Animation
Thats it! I don't want any custom ROM or anything else other than that!
Is it possible to install only the CRT animation without installing another custom ROM?
At first I thought it was possible from reading this topic:
http://forum.xda-developers.com/showthread.php?t=1117674
- dll the apk
- use Root Explorer app to place the apk file in the right place on your phone
- open animations in the display settings and voila!
But the starter replied me that it wouldnt be possible: "This mod is for i9000 with JVP (2.3.4) ROM, i doubt it will work on i9100"
And he suggested that I read the steps in this post: http://forum.xda-developers.com/showthread.php?p=14597949#post14597949
Download apk_manager 5.0 beta (somewhere in apk_manager thread).
Download apktool 1.4.1 (or newer), extract it, replace apktool.jar in apk_manager/other folder with downloaded version.
Pull framework-res.apk and twframework-res.apk from /system/framework/ and put them in apk_manager (modding folder).
Open apk_manager, choose framework-res.apk as project, decompile it with dependency, as dependency give twframework-res.apk.
After decompile go to projects/framework-res.apk/res/values/.
Open bools.xml in notepad, change value of bool name='config_animateScreenLights' from 'true' to 'false' and save it.
Go to apk_manager, compile, answer Yes for question about system file, answer Yes in next question, go to keep folder, remove resources.arsc, then hit enter in apk_manager.
After successful compile you can choose zipalign options.
You will find unsignedframework-res.apk in modding folder, rename it to framework-res.apk and put in /system/framework/.
BUT WOW, those steps are too complicated for a newbie like me.
Have to dll some tool apps or something, make adjustments etc. So I would really have to watch what I am doing and most of all, I must know what I am doing and be certain of it or otherwise I will certainly **** it up
Rooting is one thing, but this is much harder it seems...
So the main question, is there an easy way to get that nice CRT animation on a rooted Galaxy S2 phone without having to install a whole new ROM?
OK. You or someone else would need to edit the file to do this. It's actually very easy
RE overclocking, I strongly recommend you don't. I know of 3 people whose phones have died, likely due to OCing, as they were overheating even without OC... All had to be returned etc...
hm thank you for the heads up about the OC!
I actually made different profile in the SetCPU application so that I would avoid the phone to run at 1.5mhz constantly
For instance when the screen is off, the cpu range is set from 500-1000
When the temperature on the phone is above 55°C the range is set from 500-800
And when running the phone is running from stock 1.2 to 1.5, but only on demand, so when it has to, not forced
About the file, dunno, I might consider dll the Lite'ning ROM after all:
http://forum.xda-developers.com/showthread.php?t=1095274&page=256
I was convinced by the fact that I could still use all my applications + all my wallpapers and icons to make it look the same like before the installation of a custom ROM.
This is correct right? (just need a final confirmation before I dll and install that ROM)
topic can be closed as I am concerned, I have already upgraded my phone with a ROM that includes the cool CRT animation ;-)

[THEME][FROYO] ClassicTheme v1 ||9 lockmod + EPM + ICS transitions||

Hi all, this is my second theme. I hope you all like it!
Credits :-
Thanks to Google for the awesome Android OS
Thanks to Samsung for galaxy 3
Thanks to dhirend_6d for the theming guide
Thanks to vivekchamoli for the theme remix
Thanks to aarrun for the theme remix
ClassicTheme v1 //Download//
{
"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"
}
Frequently Asked Questions (For Noobs)
1) How to install this theme?
First of all, it requires a "deodexed" stock/custom rom and CWM recovery
Download the theme and put the .zip in your sdcard
Boot in CWM recovery and select "Wipe Cache" and "Wipe Dalvik Cache"
Reboot recovery
Select "Install .zip from sdcard" and wait till its done
Reboot & Enjoy
2) Can this theme work in JPU?
Yes, but I haven't really test it yet
3) Is there icon bug?
No, the .zip already contain some .jars and .so for fixing icon bug
4) Can this theme work in other firmwares?
I don't think so.........
Got more questions? Post Reply or PM me!
reserved for later
reserved for lateer
will it run on XXJPU?
-> cause JPU is a little different in framework files
qaysedcftgb said:
will it run on XXJPU?
-> cause JPU is a little different in framework files
Click to expand...
Click to collapse
Yes ofcourse it will run. But there s a point,
"If you're using a rom that already has 9lockmod (such as kyrillos, kyorarom, vivek's rom and etc), delete ALL the .jars and lib in the .zip before installing!!"
So if you already have 9 lockscreenmod enabled JPU in your phone, just delete the lib folder and all the jar files from /system/framework/ from the zip.
so all in one word:
it is enough to install the *framework*.apk files. Settings.apk is not really necessary.
The question comes up, because I am using a stock deodexed XXJPU and halcos 9lock package with extended power menue.
In this package there were only a few lib and jar files.
The package in this thread contains a lot of lib files. So I am a bit unsettled if it is enought to install the two framework apk files.
The aim of the game or better the root cause why this question comes up:
I have seen some strange pattern while moving the slider for unlocking the fone (4lock default). So I have decided to use invisible sliders and gre smybols.
But moving the slider very slow to the side... what do I see?
Looks like the slider description -> "freigeben" means "to release"/"unlock".
Have a look to the attachment for illustrating the words.
It´s just a cosmetic thing. So I would like to try the framework file out of this package and use my own icons for battery and so on...
If its not implemented in the apk files I assume that the *framework*.jar files may also be necessary to get exchanged.
decompiling and recompiling the *frame*.apk ends up in a mess of *.9.png errors, even unmodified, so this way is not usable for me
Thats why I want to try another theme in order to get rid of this small thing.
It runs very good on vivek's 6.0 rom
What if I'm on stock JPQ but have only 5ls and extended power menu? Do I get 9ls with theme or I have to install 9ls alone first?
Because when I first flashed JPQ and tried to install themes with 5 or 9 ls mods I had lots of crashes and new flashes...
hello all, like i said..this will work in ALL froyo base roms! so don't worry about it, just read instruction carefully

[UTILITY][10-18-2011] APK Manager for Mac OS X, Intel only, v1.2.1

[UTILITY][10-18-2011] APK Manager for Mac OS X, Intel only, v1.2.1
This is from the more general Android Development section of XDA. I thought that some of you here may like it to work on mods for our NOTE's apps.
Original Thread: http://forum.xda-developers.com/showthread.php?t=1285130
s0niqu3 said:
{
"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"
}
So almost everyone here should be pretty familiar with android, and that means you've probably heard of (and maybe even used yourself) the windows tool APK Manager by fellow XDA member Daneshm90.
Earlier this year I started to port the current windows 4.9 version to mac using the outdated linux script for a base. And I had some early success at the time with simply using macports to install sox, optipng, etc. And then my computer crashed (double drive failure back in July) and I gave up for the time being. Recently though I was excited to find that someone else tried to do the same thing, XDA member MAD Industries released a very basic port for mac.
Sadly though, a quick diff of his script and the outdated linux version shows that its not much of a port at all. In fact there were only 9 changes, purely for MAD Industries to add his credit lines, and disable the options to optimize png images, and ogg files.
And so a couple of weeks ago I started working (once again) on my own port of APK Manager for Mac OS X.
Since I used the MAD Industries version originally for my base, I have kept his credit in the readme.txt, though to be honest, I've undone every single change he made, and changed virtually every line in the original linux script. And on top of that, I've written over 1700 new lines of code to not only bring this current to the windows feature set, but exceed it in many ways.
I've built in 32/64-bit architecture checking, and compiled and include the required missing binaries to re-enable optimizing png images and ogg files. I'm also including a .terminal file for easily configuring the default display, and a copy of my NEW favorite fixed-width font, Bitstream Vera Sans Mono.
And now some notes, and requests:
PLEASE note: this is currently INTEL only, but it supports both 32-bit and 64-bit all-in-one with architecture checking built-in to the script.
PLEASE note: if your computer is running OS X 10.7.X, "Lion" then it does not include a java runtime by default, please download it here first: http://support.apple.com/kb/DL1421
PLEASE note: due to the length of some of the strings used in the menus, etc., in order to not need to scroll your terminal window, you must adjust your default columns and rows settings. You can set this automatically by using the include "JocelynCustom.terminal" file, and you can also find simple instructions to set this yourself in the README.txt
PLEASE read the included readme for installation and very basic (for right now) usage instructions. I welcome any and all feedback on improvements for the readme file.
PLEASE report any and all bugs or generally wonky behavior, preferrably by posting here in this thread, or by posting a comment back on my blog.
LASTLY, please if you re-post this anywhere else, including blogs, other forums, etc. I would greatly appreciate if you would at least give me credit, and link back to my blog (http://girlintroverted.wordpress.com/) or at the very least, link back here to this post.
IMPORTANT: Starting with v0.9.7/RC1 I'm including an applescript setup applet. I've also changed some directory names, removed some old files, added new files and changed location of some files. Please backup your existing APKManager directory, then unzip and setup the new version. Once you verify that it works, then you can copy the CONTENTS of the following old directories, to the new ones.
place-apk-here-for-modding -> place-here-for-modding
place-apk-here-for-signing -> place-here-for-signing
place-here-to-batch-optimize -> place-here-to-batch-optimize
place-ogg-here -> place-ogg-here
projects -> projects
DO NOT COPY OVER THE CONTENTS OF THE "other" directory or the root directory unless you absolutely know what you're doing.
Download current version v1.2.1 here: http://www.mediafire.com/?29bosvufiiv66vl
Click to expand...
Click to collapse

[MOD] Emoji for EVO 4G LTE

All Credits to Iridaki(Original Post)
I Just changed the fallback_fonts.xml file
Confirmed to work in the Stock Messaging app so far. I sent a text full of them to an Verizon iPhone and they received them.
Proof in Attached Thumbnail
Original Post:
iridaki said:
:victory: :silly: :laugh: :highfive: :good: :fingers-crossed: :cyclops: :crying: :angel:
Admit it, you secretly like emoji icons that iOS users seem to (ab)use in their messages.
OK maybe you don't, but you do hate the "blocks" or blank spaces appearing in their place on Twitter, Instagram, Foursquare, Email, SMS, etc.
Google knows. And has worked out a way to implement their own version in Android, starting from Jelly Bean 4.1.
Now, ICS users seem to be out of luck and that made me think and finally figure out a way to implement them in ICS.
Here is a little sneak-peek on how they look:
{
"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"
}
Note that they are black and white. This is because they are font symbols and not drawables (as they are in iPhones).
HOW?
First of all, Android uses a set of so-called "fallback fonts" for displaying characters that are not included in the primary fonts (DroidSans, Roboto, etc).
In the older days, to get emoji support, we used a modified DroidSansFallback ttf file, placed in /system/fonts. Well, if I wanted to merge AndroidEmoji font and DroidSansFallback, I'd probably lose a great part of my patience sanity and eye-vision... (there are 471 emoji icons)
So, I modified the fallback_fonts.xml in /system/etc/ and added the AndroidEmoji.ttf, as well as changing the priority with which the fallback fonts are called.
And TADA, I could view Google B/W emojis everywhere!
HOW DO I INSTALL IT?
I made a flashable zip that will work on all the Xperia 2011 models, on stock and stock-based ICS ROMs and probably to all Sony models that run ICS also (do not have access to those devices to check and be 100%).
DOWNLOAD ANDROID JB EMOJI FONT ENABLER
Flash with CMW.
(If you are rooted and on stock kernel, check how to get CMW here)
Preferably make a backup prior to installing.
I am not responsible for your device, YOU are!
Nandroid backups take 5-10 minutes to complete and can save lives.
Enjoy!
WHAT IF YOU DON'T HAVE AN XPERIA DEVICE OR RUN A CUSTOM ROM?
The tinkering needed for it to work on all devices is minimal.
Depending on the company, there may be different fallback fonts included.
For those you feel confident enough to edit system files, all you have to do is
add this line in the fallback_fonts.xml, save it, replace it in the CMW zip and flash:
Code:
<family>
<fileset>
<file>AndroidEmoji.ttf</file>
</fileset>
</family>
Just make sure it is before all the other entries, so that the Emoji font gets called first upon an unknown character.
HOW CAN I PUT EMOJIS IN MY MESSAGES/STATUSES/TWEETS/etc?
If you also want to be able to insert them anywhere, you have some choices:
1. A brilliant choice is Multiling Keyboard, which uses the newer encoding system.
2. There is also Emoji Keyboard.
However, it uses and older encoding system, so you will also need to flash this package. This mod is totally independent, you can flash it whether you flash the main mod or not. They will not interfere with each other at all. Having both mods means you can view emojis of both older and newer encoding.
___________________
NOTES
- If you like this, just press Thanks.
Do not post just to say how awesome I am. I know.
- If you are having questions/problems, post here, do not PM me.
Other people might also benefit from our conversation.
- If you are a ROM cooker/developer, PLEASE, ask for my permission before including this mod in your ROMs.
And I shall elaborate on this:
What I did here is no rocket science. Yes, I am sure anybody who would set their mind on it, could pull it through eventually. And maybe someone already has. However, I do enjoy being appreciated, because I took some time off my life to create this thread rather than just parading with my cool emoji-enabled phone, unwilling to spread the joy. I do wish for all the members of this community to benefit from this small tweak, but if I see something like this:
without my name mentioned anywhere and a link to this thread, I am going to be hurt. And probably mad.
That's all folks!
Click to expand...
Click to collapse
first! Yay! Thanks for sharing this
:good::good: thanks i need this
Thank you! Can't believe it took Google till JB to implement emojis.
Sent from my EVO using Xparent SkyBlue Tapatalk 2
I'm running CM10, and Emoji's still don't show up in text messages..why?
This doesn't appear to be working for me as well.... Running Stock with Goodies ROM
jkt97401 said:
This doesn't appear to be working for me as well.... Running Stock with Goodies ROM
Click to expand...
Click to collapse
Ditto here. I can get them to show up when I type them using either keyboards linked in OP but when I send them or receive them I still get the weird "question mark in diamond symbol".
http://forum.xda-developers.com/showthread.php?p=29281110
This works and has been up for while now too. So to those have problems give it a try very simple.
Sent from my EVO using Tapatalk 2
klbjr said:
Ditto here. I can get them to show up when I type them using either keyboards linked in OP but when I send them or receive them I still get the weird "question mark in diamond symbol".
Click to expand...
Click to collapse
It seams that the fallback_fonts.xml file is different for each rom. Im on mean rom. If someone can send me their fallback_fonts.xml from the /system/etc directory i can edit it and upload a new zip.

NoStorageRestrict (A11+)

{
"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"
}
This module removes the restriction when selecting folders (Downloads/Android) through the file manager on Android 11 and higher (also available as a Magisk module through Fox Module Manager)
2.0 Update
* Enabled Managed Mode on the DocumentsUI (make sure to apply the module to the Files/Documents app)
* This change allows selecting /data and /obb folders on the Android folder (where as before they were hidden)
### Note
The signature has changed on this version so you'll have to uninstall the previous version before updating
- [GitHub](https://github.com/Xposed-Modules-Repo/com.github.dan.nostoragerestrict)
- [Telegram](https://t.me/dnmgsk)
This works brilliantly - better than the Magisk module! Thank you!
Hey, thanks for this, first time poster here, tried installing this on my Xperia xz2c (lineage-19.1-20221111) but couldn't get it to work, folders remain inaccessible when trying to move files... Any way you could share a .zip of this to install via Magisk?
Gabieler said:
Hey, thanks for this, first time poster here, tried installing this on my Xperia xz2c (lineage-19.1-20221111) but couldn't get it to work, folders remain inaccessible when trying to move files... Any way you could share a .zip of this to install via Magisk?
Click to expand...
Click to collapse
Could you show a screenshot of that?
Thanks for getting back to me. Sure thing, here goes:
As you can see, the "data" folder and the "obb" folder are missing. By the way, the first time I tried to move stuff, immediately after installing the app, those folders were actually visible as intended, but once I quit the moving process and tried a second time (and from that moment on) this is what I get
Gabieler said:
Thanks for getting back to me. Sure thing, here goes:
View attachment 5759967
View attachment 5759971
As you can see, the "data" folder and the "obb" folder are missing. By the way, the first time I tried to move stuff, immediately after installing the app, those folders were actually visible as intended, but once I quit the moving process and tried a second time (and from that moment on) this is what I get
Click to expand...
Click to collapse
Oh, that's a different restriction (imposed by a different app)
My module is mainly to allow granting access to folders (downloads/Android) where it would normally tell you to create a new folder and not allow you to select that folder
The data/obb folders being hidden is a different thing
You could try this zip, tho it's a bit sloppily made, so i can't guarantee it'll work
DanGLES3 said:
Oh, that's a different restriction (imposed by a different app)
My module is mainly to allow granting access to folders (downloads/Android) where it would normally tell you to create a new folder and not allow you to select that folder
The data/obb folders being hidden is a different thing
You could try this zip, tho it's a bit sloppily made, so i can't guarantee it'll work
Click to expand...
Click to collapse
Ah I see. Makes sense. Thanks for the .zip, I'll test it out later!
The apk, in my redmi note 7 with cr droid android 12, doesn't work.
In my Samsung galaxy note 9 usino noble rom 2.8 oneui 4.1 Android 12 it work Great i have Access to media stored by all the app i have using xplore
DOOGEE S80 Android 11 LiR .... I have always used CX File explorer and it worked once I uninstalled\reinstalled it.....worked great, thanks for this.
2.0 Update released
* Enabled Managed Mode on the DocumentsUI (make sure to apply the module to the Files/Documents app)
This change allows selecting /data and /obb folders on the Android folder (where as before they were hidden)
Note
The signature has changed on this version so you'll have to uninstall the previous version before updating

Categories

Resources