I'm Rooted and using Androids FX file Explorer, to try to add a ring tone to the ringtones system folder.
/system/media/audio/ringtones
Would someone explain how to make the file write accessable or direct me to a link to how to do this?
{
"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"
}
I searched but all I could find were links how to do it through a command promt, which is not what I'm looking for.
Android 13
galaxy A22 plus
Rooted with Majiks systemless-ly activated
20GT said:
I'm using Androids FX file Explorer, to try to add a ring tone to the ringtones system folder.
/system/media/audio/ringtones
Would someone explain how to make the file write accessable or direct me to a link to how to do this?
View attachment 5836745
I searched but all I could find were links how to do it through a command promt, which is not what I'm looking for.
Android 13
galaxy A22 plus
Click to expand...
Click to collapse
after android 8 (in preparation for project Treble), system partition is mounted during boot as read-only by default (as you can find out through the partition's mount flags). so there's 2 ways to achieve what you want:
you remove the shared_block feature from Super.img and mount system as R/W. There are tools to do this, but they're not tested on Samsung devices. Like this Tool.
you root your phone with Magisk and make a Magisk module to add your files systemless-ly. Here is the Developer Guide.
Of course, You would need an unlocked Bootloader. Here is the guide for Unlocking and Rooting. I also advise you to flash TWRP before experimenting with the Module you create. Good luck.
Slim K said:
after android 8 (in preparation for project Treble), system partition is mounted during boot as read-only by default (as you can find out through the partition's mount flags). so there's 2 ways to achieve what you want:
you remove the shared_block feature from Super.img and mount system as R/W. There are tools to do this, but they're not tested on Samsung devices. Like this Tool.
you root your phone with Magisk and make a Magisk module to add your files systemless-ly. Here is the Developer Guide.
Of course, You would need an unlocked Bootloader. Here is the guide for Unlocking and Rooting. I also advise you to flash TWRP before experimenting with the Module you create. Good luck.
Click to expand...
Click to collapse
Sorry I forgot to mention that I'm already Rooted with systemless-ly already activated.
Just tested Fx file explorer on my privious phone and it works correctly after mounting the folder.
I passed the root check. is there a diffent option/checkmark to allow Fx access to root or give Fx pemisions in majiks on android 13?
Related
Hi!
I picked up a Mate 8 from a local service provider and would love to flash a new ROM to get rid of the ugly stock one, but I am stuck when trying to flash anything from TWRP.
The phone boots fine, I unlocked the bootloader, and has TWRP Mate 8 version...I can't locate any files from the internal storage though. I understand this is due to the system being encrypted. I cant seem to get around that though. I tried the format data option, hit yes, then go back but that obviously has deleted what I had stored (the SU zip). I can't mount the SD either afterwards, to load it in recovery.
I tried using the Italian knife tool, and used the Root option, and option 3, but get an error: error: cannot load '.\rec\boot.img
I am not a pro on this so it might be something farely stupid. I would love if anyone could help me with this...
{
"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"
}
--------------------------------
Edit:
I was able to solve myself. It was a rookie mistake. Perhaps the internal storage is encrypted, however I was able to flash SU using TWRP by inserting an external SD, which I had not done before. I was able to view contents from that location and did not need to use the Italian knife tool.
Hi there I am using iBall KitKat mobile is rooted but i am unable delete system apps and can't use link2sd showing error mount structure needs cleaning can anyone help
aceslivelong said:
Hi there I am using iBall KitKat mobile is rooted but i am unable delete system apps and can't use link2sd showing error mount structure needs cleaning can anyone help
Click to expand...
Click to collapse
Are you using SuperSU ??
To delete system apps, download system app uninstaller from play store and grand it superuser permission.
{
"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"
}
good afternoon
I root my Samsung tablet t285m
someone knows how i try and root with vroot and kingorot and nothing
I need root please help
I come to this forum because they are the master of the android
[IMG="TABLET SM T-285 TABLET A"]
[/IMG]
please see my PM (private message) maybe set you in some direction maybe not...also need help from you if possible advice/guidance
thanks
needed root file
gencom said:
needed root file
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/help/looking-to-direction-root-galaxy-tab-a6-t3390941
(T285M,....modified system image for debloat etc-tar.md5 fails on flash in odin-not sure if some signing is needed-have the system folder if anyone interested...took out some apps, added csc folder with some xmls for control on data on off auto for mms, added two fonts...nothing more than that)
also see page 14 here
http://forum.xda-developers.com/and...ng-tab-e-sm-sm-smnu-smp-t3302935/post66585078
I just got my T285 yesterday. Noticed that in Setting, App manager I can move some app to sdcard but after restart, the moved app disappear.
Sorry if I have mislead anyone.
Now I am also facing memory shortage with this 8G device.
I have lost all hope for root on the SM-T285. Why such a low profile device gets a locked down bootloader annoys me.
However I'm trying to customize its system.img, I'm stuck though as Heimdall fails at 3% upload everytime I try to use a repacked system.img file. Flashing the original image works fine though so it could just be in the way that I repackage the image. tune2fs shows some difference which I am still trying to sort out.
I'm willing to help if there are things that I can try.
jaritico said:
i found this on web, seems fake but, uses a beta root file of cf auto root webpage:
HOW TO ROOT GALAXY TAB A 7.0 (2016)
Note: This is a developing story. As far, we have found only one way to root your phone. But if someone invent more tricks of rooting in future, we will try to share with you.
You can install Chainfire’s SuperSU manually using a custom recovery such as TWRP (In this method we are showing how to install SuperSU.zip file with TWRP). If you are interested, check details below but take a backup of your device’s data first. This method should work with any variant of tab including SM-T280 (Wi-Fi only) and SM-T285 (4G/Wi-Fi)
Step One: Download Chainfire’s SuperSu.zip file.
Step Two: Copy the downloaded zip file to your device.
Step Three: Turn off your Samsung device and boot into recovery mode (boot device by pressing and holding down volume up, home, and power keys at the same time to enter in recovery mode).
Step Four: Take a backup, it is optional but important because if something happen bad in rooting, backup file will help you to restore previous state easily. So press ‘backup’ button, check all the boxes for backing up everything and then swipe to start the game.
Step Five: Once you have taken the backup file, press ‘install’ button, locate the SuperSu.zip file and confirm you want to install it.
Step Six: Reboot the device and your device is rooted.
Credits: http://lifeatsamsung.com/root-galaxy-tab-7-0-2016/
Click to expand...
Click to collapse
Yeah it's fake. To even be able to follow that, you need a custom recovery, but there is no way to install custom recovery right now with a locked bootloader.
Hey everyone, in this guide I will show you how you can get 24bit audio processing on your beloved rosy.
Keep in mind that I WILL NOT provide a bunch of files for you to change within your root, because audio xml's changes a lot and its hard to keep track for me as to which files will work and which won't. So rather, I will provide a way for you to edit those files on your own.
Requirements:-
1. Rooted with Magisk
2. A File manager (ex. MiX) with root permission granted
3. Note Editor (You can use MiX note editor)
4. Terminal Emulator like Termux to test if the method worked or not
5. Some Common Sense
ROMs I tested this on:-
1. LOS by Pulkit
2.RevengeOS by Pratyakshm
3.PixelExperience
4.AOSP11 by Pulkit
This method should also work on:-
1. Any Android 10 based ROM
I cannot say about android 9 or the version's before that because i never tested them, however if someone is willing to do that, let me know in the post replies and make sure you follow the guide.
Before we start, MAKE SURE TO BACKUP YOUR OLD FILES IN CASE ANY PROBLEMS ARISES LIKE BOOTLOOP'S.
So the steps are as Follow:-
1. Open up MiX or any of the file manager that you have then head over to /vendor/etc .
2. In there, find "audio_policy_configuration.xml" .
3. Take backup of this file and then open "audio_policy_configuration.xml" .
4. Under <mixPort="primary output"> profile name would be written as "AUDIO_FORMAT_PCM_16_BIT" change this string to "AUDIO_FORMAT_PCM_24_BIT_PACKED" .
5. Follow the same process as given in Step 4 for <mixPort = "raw"> , <mixPort = "deepbuffer"> and <mixPort = "direct pcm"> .
6. Scroll down the section of <device_port> and replace the string shown above for <Wired_Headset>, <Wired_Headphones>,<BT_SCO>,<BT_SCO_Headset>,<Line>.
- - Refer to the Screenshot Attached below, That will be enough for you to understand it properly.
{
"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"
}
6.This step is only for people who also have the file audio_policy.conf in vendor/etc directory.
>> under primary > outputs , change format to "AUDIO_FORMAT_PCM_24_BIT_PACKED" for primary, raw & deep_buffer. [Screenshot attached below]
6. Save the file and put it back in /vendor/etc and give chmod 0644 [-rw-r--r--] .
7. Reboot your device.
- - At this point if your Phone doesn't boot, use TWRP to replace the new file [edited] with the Old one [unedited] file and message me on telegram @bancelhub so that I could look into the matter.
PROFIT!
How to check if it's working.
1. Open up termux with su.
2. Type "dumpsys media.audio_flinger"
3. AudioOut_D and AudioOut_1D should show "AUDIO_FORMAT_PCM_24_BIT_PACKED" as HAL Format. [Refer to Screenshots Attached]
Hope this guide was good enough, this was the first guide I wrote on xda. You might have noticed that I only explained how to do this on one device tree, Pulkit one's, since his dt is public I used it to show this experiment. You can try it on other ROM's based on other DT's but your procedure may vary, mildly. let me know your experience on telegram!
Happy Editing!
Awesome !!
Thanks for detailed guide :good:
Nice Guide ,Working
Hi what is secret to using file manager on phone Android 10+ with su access to read and write in system - remove bloat apps? I have su access, but I read in 10+ file system not allow from file manager, only need use adb. How to use file manager with su to remove manually on Android 10+? I get error when deleting app from any file manager with su access "cannot delete". Danke.
Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect（,avb_keys=/product/etc/security/avb/oem.avbpubkey）code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
{
"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"
}
SirisRui said:
Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect（,avb_keys=/product/etc/security/avb/oem.avbpubkey）code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
View attachment 5577955
Click to expand...
Click to collapse
Wow very complex but thank you for explain!
Hi everybody !
I've root my S22 Ultra with Magisk and when I want to removed bloated apps, nothing happen. It's not possible.
/System stay in RO mode.
I try with Root Explorer and MiXplorer.
Any idea ?
Thank you
You have to install mixeplorer with Foxcom app. Reboot after System you can Mount in RW and RO
I don't know Foxcomm. I will search what it is. Thank you
I have installed Mixplorer with Fox. Doesn't work
{
"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"
}
Root folder as RO and RW
I don't understand...
This doesn't make a difference since /system cannot mounted as r/w in android versions >= 12.
You need to install the magisk module "debloater" and uninstall your system apps with this.
matze19999 said:
This doesn't make a difference since /system cannot mounted as r/w in android versions >= 12.
You need to install the magisk module "debloater" and uninstall your system apps with this.
Click to expand...
Click to collapse
I already try this.
Debloater module just hide apps, not delete
Johncaffee said:
I already try this.
Debloater module just hide apps, not delete
Click to expand...
Click to collapse
Mate debloat with adb the whole Android 12 root Story is bad. Google ****ed it up...
Goku1992 said:
Mate debloat with adb the whole Android 12 root Story is bad. Google ****ed it up...
Click to expand...
Click to collapse
Even with ADB you can't remove the apps, only disable them.
matze19999 said:
Even with ADB you can't remove the apps, only disable them.
Click to expand...
Click to collapse
You can uninstall them. They remain on the Partition but cant Start so if you wipe your data they are back again. You can also Re-install them with adb.
When you disable some Apps will reenable themselves and force Start.