Develop Bugs

How to enable dolby atmos or viper in j210f/j2 2016

Hi to everyone ,
At first I would like to show my frustation that even after trying 5 TIMES .I cant able to enable dolby atomes or viper in my STOCK ROM.
So ,someone please help me with this thing
I will be very greatfull to him
Thanks

Savitar99 said:
Hi to everyone ,
At first I would like to show my frustation that even after trying 5 TIMES .I cant able to enable dolby atomes or viper in my STOCK ROM.
So ,someone please help me with this thing
I will be very greatfull to him
Thanks
Click to expand...
Click to collapse
Okay so here's how you do it
1) Make sure you have root and TWRP/CWM recovery
2) Download and unzip the folder from the main viper page
3) Now for viper to work in Enforced SELinux, you'll have to flash this zip via the recovery that you have. (https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0)
4) After that, you will need to download this(http://forum.xda-developers.com/attachment.php?attachmentid=3244040&d=1428124059) You'll find a folder named audio_config. Go to your root browser /system/etc and scroll till you find a file named audio_effects.conf. Rename this file as audio_effects.conf.bak. This will be a backup just incase you mess something up or it doesn't work.
5) Move the audio_config file that you downloaded from the link above to /system/etc
6) Move viper app to /system/app folder and reboot. The app will disappear
7) Now go to /system/app and open the file. You'll see the apk there. Install it and reboot.
8) Open v4a and install drivers. Reboot again
9) Enjoy!

Thank you very much. It worked for me.

fredy97 said:
Thank you very much. It worked for me.
Click to expand...
Click to collapse
Good to know

darshan1504 said:
Okay so here's how you do it
1) Make sure you have root and TWRP/CWM recovery
2) Download and unzip the folder from the main viper page
3) Now for viper to work in Enforced SELinux, you'll have to flash this zip via the recovery that you have. (https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0)
4) After that, you will need to download this(http://forum.xda-developers.com/attachment.php?attachmentid=3244040&d=1428124059) You'll find a folder named audio_config. Go to your root browser /system/etc and scroll till you find a file named audio_effects.conf. Rename this file as audio_effects.conf.bak. This will be a backup just incase you mess something up or it doesn't work.
5) Move the audio_config file that you downloaded from the link above to /system/etc
6) Move viper app to /system/app folder and reboot. The app will disappear
7) Now go to /system/app and open the file. You'll see the apk there. Install it and reboot.
8) Open v4a and install drivers. Reboot again
9) Enjoy!
Click to expand...
Click to collapse
It works!

Hey, I Cant root my phone Samsung J200g and i cant install Dolby Atmos in my phone Please help me

Abhishek0555 said:
Hey, I Cant root my phone Samsung J200g and i cant install Dolby Atmos in my phone Please help me
Click to expand...
Click to collapse
How are you trying to root? Do you have a custom recovery? What super user?

Hey can someone help me ? I'm using glalxy j200g i was able to instal dolby atmos but even it turn on the sound still same no change

Can't root through SuperSU or Magisk on open beta 25 (android O)?

I've tried to root using Magisk to SuperSU but I'm into the same issue, The device get stuck on the boot screen until I re-flash the stock boot image, is there any solution for that's?

Not yet. Did this really require a thread of its own ?

skymera said:
Not yet. Did this really require a thread of its own ?
Click to expand...
Click to collapse
I just want to know how much will take so that it will be available.

rsm23 said:
I just want to know how much will take so that it will be available.
Click to expand...
Click to collapse
Nobody here can see in the future...

https://forum.xda-developers.com/showpost.php?p=74161852&postcount=3634
here try this Good Luck !

On my phone SuperSU 2.82 SR5 works fine. On other phones not, or SR3 woks....
Magisk 1.4 or 1.42 beta not working. I did not get boot loops, but not working.

rsm23 said:
I've tried to root using Magisk to SuperSU but I'm into the same issue, The device get stuck on the boot screen until I re-flash the stock boot image, is there any solution for that's?
Click to expand...
Click to collapse
Follow this guide brother

Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
How did you achieve this?

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
This is a good news. Cannot wait for more details!

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
Does this seems ok to you : https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901 ?

ashokmor007 said:
Follow this guide brother
Click to expand...
Click to collapse
Thanks, but I don't like SuperSU
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
mr.charlie said:
Does this seems ok to you : https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901 ?
Click to expand...
Click to collapse
Thanks, but too much of a hassle for me right now.
I think I'll just wait for an official Magisk update to be released, at this point

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
! We are looking forward to your description: how to take the steps? !

papzi57 said:
! We are looking forward to your description: how to take the steps? !
Click to expand...
Click to collapse
Be carefully, you can lose you data!!! For me all work fine)))
1.Flash Oreo via trwp
2.Downgarde bootloader for DM-Verity
3. Flash Magisk via twrp
4. Turn off the phone manualy
5.Turn on & boot in twrp
6.Do the backup of boot
7.And edit boot.win in hex editor on pc
Code:
androidboot.selinux=permissive
screen in attachment
8.And flash boot back, reboot.
P.S When you set selinux permissive via fastboot you'll have freeze (braking) in system - i don't know how it say

baskaflyfer said:
edit boot.win in hex editor
Click to expand...
Click to collapse
This worked for me too, but maybe some other users need more information on the boot partition
Oreo compatible TWRP: Download (Credits: @akhilnarang)
OOS Open Beta 25: Download (Official OnePlus Website)
Magisk 14.3 (Beta): Download (stolen from this thread)
Magisk Manager 5.4.0: Download (GitHub)
You are responsible, if it kills your device, but this was my way:
1. Full Backup in TWRP
2. Reboot into Fastboot Mode
3. Flash Oreo compatible TWRP
4. Use Volume Keys to select and boot into recovery
5. Install OOS Open Beta 25
Then i did a reboot and Steps 1&2 again but i don't think this is required.
6. Install Magisk 14.3 Beta
7. Create an image of the boot partition
Code:
adb shell
dd if=/dev/block/sde18 of=/sdcard/boot.img
exit
8. Copy the boot.img file to your computer
9. Open this file in a hex exitor, add the following text after "buildvariant=user" (image in baskaflyfer's answer) and save the file:
Code:
androidboot.selinux=permissive
10. Reboot into fastboot mode
11. Flash modified boot image
12. Reboot to OOS
13. Install the Magisk Manager APK

Is it safe?
Do you dirty flash open beta 25?
Why need I modifyed the boot. img? Why don't modifyeed it the Magisk for me?
Sent from my Pixel 2XL using XDA-Developers Legacy app

papzi57 said:
Is it safe?
Do you dirty flash open beta 25?
Why need I modifyed the boot. img? Why don't modifyeed it the Magisk for me?
Click to expand...
Click to collapse
I am not able to tell you how safe this method is.
Yes, i did a dirty flash of OOS Open Beta 25, but some apps lost their data (Jodel, photoTAN, ...) but not Google Authenticator :fingers-crossed:
I think the modification of the boot.img is device-specific. I can not tell you details about this because i don't know that either.
There might be another way to set selinux=permissive as recently described in this thread, but your bootloader need to allow the following command:
Code:
fastboot oem selinux permissive
If you are able to perform this command in fastboot mode, maybe you don't need to modify the boot.img manually. Just reboot to fastboot mode after the installation of Magisk in TWRP and type that command.

davidlueder said:
This worked for me too, but maybe some other users need more information on the boot partition
Oreo compatible TWRP: Download (Credits: @akhilnarang)
OOS Open Beta 25: Download (Official OnePlus Website)
Magisk 14.3 (Beta): Download (stolen from this thread)
Magisk Manager 5.4.0: Download (GitHub)
You are responsible, if it kills your device, but this was my way:
1. Full Backup in TWRP
2. Reboot into Fastboot Mode
3. Flash Oreo compatible TWRP
4. Use Volume Keys to select and boot into recovery
5. Install OOS Open Beta 25
Then i did a reboot and Steps 1&2 again but i don't think this is required.
6. Install Magisk 14.3 Beta
7. Create an image of the boot partition
Code:
adb shell
dd if=/dev/block/sde18 of=/sdcard/boot.img
exit
8. Copy the boot.img file to your computer
9. Open this file in a hex exitor, add the following text after "buildvariant=user" (image in baskaflyfer's answer) and save the file:
Code:
androidboot.selinux=permissive
10. Reboot into fastboot mode
11. Flash modified boot image
12. Reboot to OOS
13. Install the Magisk Manager APK
Click to expand...
Click to collapse
Is Magisk stable? Did you try any modules and which ones? Are they working fine?

ishanp said:
Is Magisk stable? Did you try any modules and which ones? Are they working fine?
Click to expand...
Click to collapse
I did not try any modules but multiple apps that require root: AirDroid, AFWall+, Amaze (Root enabled). They're working fine.
Additionally, this magically fixed my ctsProfile. Magisk's SafetyNet-Test is successful on my device now.
Edit: I was able to install ViPER4Android FX for Magisk v14+ (v2.5.0.5) by ShadySquirrel without any errors, but driver status tells me that it is not enabled. Maybe because they officially just support ROMs up to Android Lollipop.

davidlueder said:
Edit: I was able to install ViPER4Android FX for Magisk v14+ (v2.5.0.5) by ShadySquirrel without any errors, but driver status tells me that it is not enabled. Maybe because they officially just support ROMs up to Android Lollipop.
Click to expand...
Click to collapse
Try in terminal after boot:
Code:
su
setenforce 0
Restart ViperFX app. Please report, I am on SuperSU but will jump the moment my fav modules start working
Also I'm using Viper4Arise (bundled with Magnum Opus) right now. If that didn't work you can use that.

[Guide]Magisk Modules Disabler for Modules gone wrong

Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2239421
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3xl.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3xlRemove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291

Looking forward to this, Tulsa. Will be a real lifesaver and game changer.

sliding_billy said:
Looking forward to this, Tulsa. Will be a real lifesaver and game changer.
Click to expand...
Click to collapse
It's official. It works.

Tulsadiver said:
It's official. It works.
Click to expand...
Click to collapse
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.

sliding_billy said:
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.
Click to expand...
Click to collapse
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time

Tulsadiver said:
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time
Click to expand...
Click to collapse
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.

sliding_billy said:
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.
Click to expand...
Click to collapse
I pasted it again. Hopefully it works now.

Tulsadiver said:
I pasted it again. Hopefully it works now.
Click to expand...
Click to collapse
It works!

Thank you!!!!

Latest magisk canary added an adb command to remove modules if bootlopps happens ?

DvLAx3l said:
Latest magisk canary added an adb command to remove modules if bootlopps happens
Click to expand...
Click to collapse
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?

Tulsadiver said:
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?
Click to expand...
Click to collapse
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know ?

DvLAx3l said:
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know
Click to expand...
Click to collapse
Well, if it's an ADB fix, a person is going to have to, at the very least, flash boot.img (though probably system images depending on what you flashed), reboot without root. Enable the ADB mode, flash ADB commands, and reboot. Remove bad modules. Then, go back and root again.
Seems simpler to just flash the modded image-new.img, reboot with root, remove modules (with ADB if you like) and reboot.
Edit: what would be cool is an option to patch a boot.img in core-only mode, right from Magisk manager, where the other option is to patch the boot.img. All that would be needed on John's part is an edited init file in that option. That's the only difference.

Thanks for this! I could've really used this image a few times in the past...

Face_Plant said:
Thanks for this! I could've really used this image a few times in the past...
Click to expand...
Click to collapse
You and me both, buddy!

Got in to a bootloop situation with Bromite systemless webview module. I restored stock boot image and patched it with the latest canary build (the one with 'recovery mode' checked under advanced settings) and bootlooped again. I flashed this file, got in with magisk working, disabled the offending module, patched the boot image without recovery mode, then flashed the patched boot image and everything is up and running! Thanks for the help!

Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?

Jiggs82 said:
Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?
Click to expand...
Click to collapse
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.

Tulsadiver said:
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.
Click to expand...
Click to collapse
Yes I was able to open magisk but even if I uninstalled it I still had this weird bootlloop so before I saw this message I ended up just flashing factory 10 image clean this time just to be sure everything would flash/install successfully and luckily they did lol but thanks anyways and I will hold onto to these files for future references:good:

would the modded boot img that disables modules work for the pixel 3 as well?

[ROOT]Stock and Magisk patched boot images

Until TWRP is available for this device, root must be done by flashing patched boot image via fastboot. I'm still in the waiting period for the bootloader unlocking, but I prepared files in the meantime. Maybe someone will find them useful. Attached are stock boot and patched image with Magisk 21.1, EEA ROM version. Just unzip them and flash from fastboot.
Full version: V12.0.6.0.QJSEUXM_20201117
Edit: patched boot image reuploaded, the previous one didn't work (at least on my phone). This one has been tested and is working fine.

hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?

carabot said:
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
Click to expand...
Click to collapse
You can flash patched boot image directly, or just hotboot it (fastboot boot patched_image.img) and install Magisk from Magisk manager.

hello,
I did and at the moment everything is ok.
thanks
but there is a strange thing, Mixplorer, it does not change the permissions of the files, yet it has root permissions

I think the root is not perfect, I can't change the permissions of the files

carabot said:
I think the root is not perfect, I can't change the permissions of the files
Click to expand...
Click to collapse
Which files on which partition with what kind of permissions? RO partitions must be remounted as RW, but it's not always possible and using Magisk is usually a better and safer approach.

hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed

carabot said:
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
Click to expand...
Click to collapse
I keep my system partition RO so I can apply OTA updates, so I haven't tried it. You could try another app (for example Total commander), but you will be probably out of luck because of Android 10 limitation. Read more detailed explanation here https://android.stackexchange.com/q...m-partition-locked-to-read-only-in-android-10
I would suggest using Magisk module for system modifications.

hi
i tried other app manager like root explorer and es explorer, but the result is the same. i also installed magiskhideprops module, but my phone is not supported as fingerprint yet

What are you trying to achieve?

the terminal command to try to mount as RO would you know?

_mysiak_ said:
What are you trying to achieve?
Click to expand...
Click to collapse
full root to modify root files

carabot said:
full root to modify root files
Click to expand...
Click to collapse
I meant which files do you want to modify and why..
carabot said:
the terminal command to try to mount as RO would you know?
Click to expand...
Click to collapse
It's in the link above, along with explanation why it might be impossible to do.

I wanted to change the audio files regarding the volume, I wanted it a little higher

carabot said:
I wanted to change the audio files regarding the volume, I wanted it a little higher
Click to expand...
Click to collapse
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.

i read android 10 problem, would you recommend me to mount with termux, installing vim?

_mysiak_ said:
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
Click to expand...
Click to collapse
i don't know about magisk modules that can affect volume controls

carabot said:
i don't know about magisk modules that can affect volume controls
Click to expand...
Click to collapse
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.

_mysiak_ said:
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
Click to expand...
Click to collapse
unfortunately no, I edit the audio value of the system files, but I don't know how to build a module

Hello
the twrp for gauguin is online, to mount it i have to go back to the stock boot?

My experience - CAOS R 300l+ (Android 11) Stable so far.

Hi all.
I wanted to share my experiences with you all.
I have the last couple of days run this rom as my daily driver - and I must say, that this is by far the best I have tried yet.
The rom is very fast and so far all features that I have used have worked perfect right out of the box.
I will link you to the rom and write a short guide to how I made it stable and usefull.
Hope more of you will enjoy running Android 11 (R) on your P20 Lite - Mine is ANE-LX1 hw/eu but this should run on all versions.
First som screenshots from my phone:

Links to files:
set-bl-key_TishSerg4pda - https://drivemere.com/drive/ne
TWRP-oreo-smart.img - https://drivemere.com/drive/nf
CAOS R 300I+ ROM - https://drivemere.com/drive/ng
Ekstra:
Netflix apk (this one will work on android 11) - https://drivemere.com/drive/nd
NB: None of these files are created by me so please help support the creators by donating to maintain their work.

Guide:
Requirements: Unlocked phone - Guess you alle have this by now.
I started off from EMUI 9.1.0.370.
First off i installed the TWRP from bootloader to ramdisk_recovery.
fastboot flash ramdisk_recovery TWRP-oreo-smart.img
Then boot phone to recovery
(Star phone - in eRecovery choose to reset to factory default - type in "yes" and the phone will boot to TWRP.
In TWRP go to "wipe" -> advanced -> Select Dalwik Cache, Cache, Data and System. Swipe to wipe.
Now go to install -> select img -> choose CAOS image and flash to "system image" - DO NOT REBOOT SYSTEM!
Select wipe -> slide to factory reset.
Now you can boot the phone to the startup-screen.
Set up the phone and go to Play Store. Install the app named Treble Info (just search it)
Look in the app to what kind of "Treble and VNDK" used by your phone - Mine was using VNDK version 28.
This next part is a bit tricky!!
Boot to the recovery (as described above -> eRecovery -> factory default -> TWRP recovery.
Now go to mount - make sure that "system" is selected.
Go to advanced -> File Manager.
Now go to folder system -> system -> system_eks -> apex
You will most likely find som folders named (xxx=something):
xxxx.vndk.27
xxxx.vndk.28
xxxx.vndk.29
xxxx.vndk.current
Since my was using 28 I could chose to enter folder .27 and mark the blue folder in the down right corner
Choose to delete folder.
This will free up approx. 1GB system memory to install apps on the phone.
I hope you will like this rom as much as I have during the last week.
Please leave any feedback..

It has been many years, I haven't uploaded rom. I hope I succeed without any problems. thanks

whitetigerdk said:
Please leave any feedback
Click to expand...
Click to collapse
Tried afternoon "caos-v300l-210117-arm64-bvZ.img.xz" ROM, I installed it like any other GSI Treble ROM - flashing extracted .img file from fastboot & factory reset.
Maybe it's an easier way...

tried this myself.. wouldn't boot.. but through TWRP there was no problem
Might be working for some to flash it directly from fastboot:
fastboot flash system "caos-image-file".img
Anyway -still need the TWRP to delete the files from system folder - som might as well use it when it's available

whitetigerdk said:
Anyway -still need the TWRP to delete the files from system folder - som might as well use it when it's available
Click to expand...
Click to collapse
You can simply use root explorer (Solid Explorer etc.)

-Alf- said:
You can simply use root explorer (Solid Explorer etc.)
Click to expand...
Click to collapse
Well.. only if you root the ROM first. This one is not rooted by default. (I prefer it like this) so if you follow my guide - TWRP is the way to do it.
Yes there might be more ways to go there but I wanted to do a simple step-by-step guide easy to follow for beginners.

whitetigerdk said:
Well.. only if you root the ROM first. This one is not rooted by default.
Click to expand...
Click to collapse
Is that supposed to be a joke?
caos-v300l-210110-arm64-bgZ - "Z" means that the ROM is pre-rooted with SuperUser and there's is an option turn on/off root in phone settings.
No comment...

No comment...

It's such a waste of time. Have a nice day!

Where in settings should this be? Looked all over.. can't seem to find it..
Nevermind - found it.
Forgive me - it's been 10 years since I last worked with Android ROMs.. a lot has happened since then..

This might be a weird beginner question. But in description of rom image i find the AOSP sounds were replaced with Q Google ones. But I can not find any one of them. No notification, ringtone, alarm sounds present on the phone. Why is that? Where can I find them?
I used caos-v300l-210117-arm64-bgZ-lite.img using fastboot install over stock 9.1.0.374.
Sure, I could use 3rd party apps for that, but I hate to use them.

luka_bubi said:
This might be a weird beginner question. But in description of rom image i find the AOSP sounds were replaced with Q Google ones. But I can not find any one of them. No notification, ringtone, alarm sounds present on the phone. Why is that? Where can I find them?
Sure, I could use 3rd party apps for that, but I hate to use them.
Click to expand...
Click to collapse
I actually had the same.. no alarm sound or ringtones.. I just uploaded some mp3's to the phone and use those.. (ringtone is CTU phone from the serie "24"..)

luka_bubi said:
No notification, ringtone, alarm sounds present on the phone.
Click to expand...
Click to collapse
Everything can be found in "audio"folder. Go root/system/product/media/audio , you can copy sounds to the int.storage using root explorer (e.g. Solid explorer) .

-Alf- said:
Everything can be found in "audio"folder. Go root/system/product/media/audio , you can copy sounds to the int.storage using root explorer (e.g. Solid explorer) .
Click to expand...
Click to collapse
Thank you, that worked!

rom link is no longer working help plz!

[OFFICIAL] AOSP Q Mod // CAOS <= official tread by author
CAOS TrebleGSI <= latest version on SourceForge

luka_bubi said:
[OFFICIAL] AOSP Q Mod // CAOS <= official tread by author
CAOS TrebleGSI <= latest version on SourceForge
Click to expand...
Click to collapse
Whats agz bgz bzg lite bvz lite avz on the download section

stunteur said:
Whats agz bgz bzg lite bvz lite avz on the download section
Click to expand...
Click to collapse
an explanation can be found here
luka_bubi said:
] AOSP Q Mod // CAOS <= official tread by author
Click to expand...
Click to collapse