{
"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"
}
*** Disclaimer ***
These modifications use root access privileges to modify the system files, you must use it at your
own risk you are the only responsible.
Requirements:
- Root Access
- Android 10
- Stock Firmware and Kernel
- compilation required 17.0240.2007.27
- a file manager with root access (Root Explorer)
- Terminal Android
Installation process:
- You need to download this file and you need to unzip it
step 1
- you will see the following folders
- inside the folder 01 ViPER4Android System-app another folder comes that you must move to the path /system/app
- the folder must be given permission 0755 and the application permission 0644
step 2
warning: installing these settings permanently disable the DTS equalizer
- inside the folder 02 Mod Audio System Asus There are several files including a custom installer so you can do it quickly, these files should be
moved to the path /data/local/tmp
- now change the permissions of the installer_audio.sh file to 0755
- open your terminal and grant root permissions and type the following command
Code:
sh /data/local/tmp/installer_audio.sh
- just enter to run the script
- select option 1 for installation
- Once the installation is finished, you must close the terminal and turn off and on your device
step 3
- Now open your application it will ask you to install the driver click on accept
-then it asks for root permissions, gives it to accept and automatically the phone reboots
- After the restart open the application again and it is activated now, it only remains to install a module
step 3
- go to magisk manager in settings and select the modules option
- in the folder 03 Module magisk Audio library this is the module oh although they prefer it they can
download it from the repository
- they just need to flash it
- to finish they must give you restart and wait for your device to start
step 4
to enable the equalizer you must activate the master limit and with that it would be activated and enjoy your new audio
system that I made for you.
- in magisk modules it should look like this if you have any problem with the audio just delete the Audio Modification Library file
- and you just have to restart and go
Faqs:
Does it work on a different compilation than Android 10?
R= I would need to test yourself since I don't have that compilation on my device
/17.0235.2004.1/17.0230.2004.60/17.0230.2002.32/17.0225.2001.13'
Works on tencent and republic variants
R= Yes
support telegram support [ES]
support telegram support [IN]
so, let's say if we wanna restore the original dts audio wizard, is there any way to revert the process?
dvijetrecine said:
so, let's say if we wanna restore the original dts audio wizard, is there any way to revert the process?
Click to expand...
Click to collapse
Of course, you only need to make a backup of the files that are going to be replaced, you can see within the installer files which files are the ones you need to backup
kaiiori said:
Of course, you only need to make a backup of the files that are going to be replaced, you can see within the installer files which files are the ones you need to backup
Click to expand...
Click to collapse
there are a few dozen files that need to be backed up.
it would be easier for everyone if you made the backup option in the installer.
also, it doesn't install. says that files are not found.
this seems like a great mod but i would like to know if this will work on kirisakura kernel , i don't want to revert to stock kernel just to ejoy this mod while losing out better functionality of the kernel than stock.
applets not found and no such file or directory...
how fix it?
After installation, I get update notification in Magisk. Can I make update
Related
Firstly: I'm new here, but I'm sure this is a fresh thread. I doubt anyone else will have asked this yet.
So basically, CommBank Kachinghttps://play.google.com/store/apps/details?id=au.com.commbank.kaching is an online banking app, but the developers have decided that it can't be downloaded to or run from a rooted device. I think.
Basically, is there a filter that will allow Play to disallow rooted device from downloading, or is it the Device Status flag that does this? Also, if downloaded to a stock device which is later rooted, the app will fail to run, with a message saying "This device cannot be supported." I suppose this is the nice way of letting us down.
Is there anyway for me to check whether a particular "status" is preventing this from running?
There are a limited number of devices that are currently supported, but the I9300 is one of them. It requires 2.3 (GB) or above, which I'm running, technically. The app actually worked during the root process, right up until the device rebooted to complete the root process - I'm guessing that that's when the "Device Status" is updated? Would this be it?
tl;dr
Is there anyway to find out what is 'triggering' this app? (And how would I do this?)
If it is the Device Status = 'Modified', is there a way to change this?
Is there anyway to find out what is 'triggering' this app? (And how would I do this?)
Some apps refuse to run due to security risk of root . Fix font know but i would look in APPS section .
If it is the Device Status = 'Modified', is there a way to change this?
Unroot and flash a stock rom is all so far .
jje
hxxps://dl.dropbox.com/u/32917310/modded.commbank.kaching-p1xel8ted.rar (if you cant be bothered do the steps below.)
First off, you need to get "framework-res.apk" off your Rom, it can be found in /system/framework. Put it somewhere safe for now.
1. Get APKMultiTool from hxxp://apkmultitool.c0m/, when your run it for the first time, before selecting any options, copy your "framework-res.apk" into {apkmultifolder}/platform-tools.
After its copied, select option 2, then option 1. It may exit afterwards, if it does, re-run "setup.bat", found in the apkmulti install folder, and select option 3.
After that, run Apk Multi-Tool from the desktop.
2. On your phone, using a file explorer (Romtoolbox, esfile explorer etc) make a backup of CommBank and Kaching
3. Copy those backups as APKs to your computer
4. Place the apks in the "place-apk-here-for-modding" folder within the APKMultitool directory.
5. Run apkmultitool
6. Use option 23 (set project) and select commbank
7. Use option 9 (decompile)
8. Repeat step 6 and 7 for kaching
9. Open {apkmultifolder}\projects\au.com.commbank.kaching.apk\smali\au\com\vivant\util\deviceutils.smali
10. At line 32, replace and save
const-string v1, "test-keys"
with
const-string v1, "test-keysss"
11. at line 61, replace and save
const-string v2, "/system/app/Superuser.apk"
with
const-string v2, "/system/app/Superuser11.apk"
** Repeat steps 10 and 11, but with {apkmultifolder}\projects\CommBank_2.2.2.apk\smali\au\com\vivant\util\deviceutils.smali
12. Back into apkmultitool, again using option 23 (set project) select commbank
13. Use option 11 (compile), answer No to system app, and answer No to use other files
14. Use 12 (sign).
15. Repeat steps 12 to 14 but selecting kaching instead.
16. Go back into "place-apk-here-for-modding" and there will be two new files with "signed" in front of the names, copy those to your phone and install.
What we've done is basically "cracked" the check for your phone being rooted or custom rom'd/modified.
Why dont you just get an app that hides root? i did that and it works great!
although the app does suck. its a shoddy iClone
I am also rooted and use siyah kernal, which has the 'remove root' function. I leave the option 'restore root on reboot' ticked and once I've finished I just reboot the phone.
Edit: Just found a quicker way which doesn't require a reboot, as per Milz123's recommendations. And it wasn't that hard or messy.
I downloaded 'hide my root' from the play store. Then I selected 'hide su binary' then 'hide su app'. Logged on Kaching and worked perfect.
Logged out then restored su binary then su app and tested some apps which require root. They worked prefect. Then tried logging into Kaching again but couldn't.
Fyi, I use supersu, not superuser. When I selected to hide the su app it said it didn't exist, but in reality it still hid then restored the correct app. So worked 100% and took seconds.
Edit 2: Tested with just 'hide su app' and it worked. Phone is still rooted and app works.
{
"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"
}
Sent from my GT-I9300 using xda premium
First of All I'm Just Sharing this App to you guys
Click to expand...
Click to collapse
#SUPERUSER APP BY Koush#
#Description#
Grant and manage Superuser rights for your phone.
Troubleshooting
Issues installing or upgrading from another Superuser or SuperSU? Try the recovery zip installation linked below.
Apps being denied? Disable the "Declared Permission" setting, and delete the "Deny" policies.
This app requires that you already have root, or a custom recovery image to work.
Features
* Multiuser support
* OPEN SOURCE (https://github.com/koush/Superuser)
* Pin protection
* Manifest permission support
* Per app configuration
* FREE
* Request timeout
* Logging
* Notifications
* Proper Tablet UX
Why another Superuser?
* Superuser should be open source. It's the gateway to root on your device. It must be open for independent security analysis. Obscurity (closed source) is not security.
* Superuser should be NDK buildable. No internal Android references.
* Superuser should also be AOSP buildable for those that want to embed it in their ROM.
* Superuser should also be AOSP embeddable, meaning a ROM can easily embed it into their Settings app.
* Maintenance and updates on both the market and source repositories should be timely.
* If something goes wrong, I can fix it.
* Handle multiuser (4.2+) properly
* Handle concurrent su requests properly
Manual installation with the recovery zip:
Recommended if you are having installation issues or are not rooted
http://download.clockworkmod.com/superuser/superuser.zip
APK download:
http://download.clockworkmod.com/apks/Superuser.apk or Playstore Link
#Screenshot#
{
"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"
}
great.thanks.
Superuser came preinstalled with android revolution hd version 31.
It asks to update the binary file, but the only option it gives is via recovery. However this seems impossible with twrp, only possible with clockwork mod recovery maybe?
Normally I wouldn't care, I would just uninstall and install one of the other superuser or supersu apps, but in this case you can only uninstall the "update" not the actual superuser app which is impossible to uninstall and doesn't appear in the program list.
I don't want any conflicts with other superuser apps so would appreciate any info how to either update or completely uninstall this app.
I'm thinking, something that's "open source" shouldn't have limited functionality with all but a specific recovery rom
thank very much
pontypool said:
Superuser came preinstalled with android revolution hd version 31.
It asks to update the binary file, but the only option it gives is via recovery. However this seems impossible with twrp, only possible with clockwork mod recovery maybe?
Normally I wouldn't care, I would just uninstall and install one of the other superuser or supersu apps, but in this case you can only uninstall the "update" not the actual superuser app which is impossible to uninstall and doesn't appear in the program list.
I don't want any conflicts with other superuser apps so would appreciate any info how to either update or completely uninstall this app.
I'm thinking, something that's "open source" shouldn't have limited functionality with all but a specific recovery rom
Click to expand...
Click to collapse
This is a somewhat old post but I will respond to it like this... The reason it will not let you uninstall it is cause it is installed as a System APP if you download an APK called RootAppDelete which you can find in the Google Play Store you can uninstall it. I'm not sure what dependencies in your system you have but I think as long as you install another Superuser app it should be ok..
Hope this helps you and clears up why you cannot remove it.
EDIT: This is also the reason you can only uninstall updates and not the APP it self. (ALSO) This is an old post as I mentioned but maybe it will help others who read it..
- orbit
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
Step 1-If your phone is rooted download build prop editor and add these lines from screenshot in the build prop editor
Step 2 - sav and exit the changes made in build prop editor then restart your device
Step 3 in your account setting in phone setting a new setting will be there named as users create and setup a new user after completing it switch back to original user
Step 4 now try to Create a secure folder it will say user Already exist so delete the user and again try to create secure folder this te you will succeed
Works on my smasung a51 and samsung s20 should work on all samsung android device with android 10+
{
"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"
}
Ironmanmark42 said:
Step 1-If your phone is rooted download build prop editor and add these lines from screenshot in the build prop editor
Step 2 - sav and exit the changes made in build prop editor then restart your device
Step 3 in your account setting in phone setting a new setting will be there named as users create and setup a new user after completing it switch back to original user
Step 4 now try to Create a secure folder it will say user Already exist so delete the user and again try to create secure folder this te you will succeed
Works on my smasung a51 and samsung s20 should work on all samsung android device with android 10+View attachment 5360953
Click to expand...
Click to collapse
which firmware version are you using?
Samsung a51 Android 11 official rooted and magisk v23 installed
bixbylmlulu said:
which firmware version are you using?
Click to expand...
Click to collapse
Samsung a51 Android 11 official rooted with magisk v 23
Ironmanmark42 said:
Step 1-If your phone is rooted download build prop editor and add these lines from screenshot in the build prop editor
Step 2 - sav and exit the changes made in build prop editor then restart your device
Step 3 in your account setting in phone setting a new setting will be there named as users create and setup a new user after completing it switch back to original user
Step 4 now try to Create a secure folder it will say user Already exist so delete the user and again try to create secure folder this te you will succeed
Works on my smasung a51 and samsung s20 should work on all samsung android device with android 10+View attachment 5360953
Click to expand...
Click to collapse
My Tab S7 is still saying Couldn't create Secure Folder
Did you had tried to use Secure Folders at least once before root? I haven't and this method is not working. Every time I click on 'Secure Folders' I have to log in, and it says "Can't create Secure Folders" right after login, same with this method.
bladez said:
Did you had tried to use Secure Folders at least once before root? I haven't and this method is not working. Every time I click on 'Secure Folders' I have to log in, and it says "Can't create Secure Folders" right after login, same with this method.
Click to expand...
Click to collapse
same ****
Any of you got it working? i have a magisk module that works in android 12
{
"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