Develop Bugs

Es File Explorer issue

I'm having a problem with es file explorer and root explorer. Last night my fire tv kept booting to home screen and rebooting, so I had to re-install 5.0.5.1 prerooted rom thru recovery. I reinstalled all my apps, and when trying to enable root explorer, I get the superuser request as usual, I grant and get the notification that it's been granted. Root explorer access is enabled for about 6 seconds before disabling with the message "Sorry, test failed. This feature cannot run on your device". Adaway works fine when asking for su permission. Only thing I did differently this time around with installation of the rom is I installed Es file explorer and tried to enable root explorer before doing the SU command from adb shell. I've since uninstalled and reinstalled ES file explorer and reacquiring SU permission but it does the same thing. I went and installed a much older version and it does the exact same thing. Anyone else come across this problem?

The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.

deanr1977 said:
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
Click to expand...
Click to collapse
Thanks for your reply. I'll do what another user suggested and use Total Commander instead as I have it installed and granted root access for it, and it does the same functions. I haven't had any issues with es file explorer on my ftv 2 at all, but another user reported the exact same problem in a different thread on this forum so I'm not alone.

Ok mate no worries, just a note I have both manager apps working on 2 sticks (1 rooted & 1 not, both updates blocked but on different firmware) & also on my prerooted AFTV2 so dunno what happened with yours & the other forum member?
Sent from my SM-G900F using Tapatalk

i have this same issue on 2 firebox's after a full conversion from os3, running rbox latest 5.2.x
both give the identical error, yet other apps are getting su control just fine?
any idea's? @rbox

I am having this problem on my first FTV1 I upgraded from PreRooted FireOS 3 to latest PreRooted FireOS 5. It is a fully rooted with fully unlocked bootloader FTV1. ES File Explorer is giving me this error when trying to turn on its Root Explorer option and all though Total Commander & Root Explorer are not giving me this error. They are not letting me copy files from a Root folder into regular storage. I can view them & choose them but it errors out when trying to copy over. I had to copy them thru TWRP.
I plan to do a Factory Reset thru TWRP & reinstall the latest PreRooted Rom again. But this time after doing the TWRP special build number update blocking tweak. I plan to run the SU command before installing any apps. Will see if that helps at all or not. If not I will post more detail info in case someone can help. This is the last bug I've encounter since doing the move from FireOS 3 to FireOS 5.

@d3adpool , @deanr1977 , @LittleBill21
Where you guys ever able to come up with an answer or fix for this issue ??

Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.

Y314K said:
I am having this problem on my first FTV1
Click to expand...
Click to collapse
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?

d3adpool said:
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
Click to expand...
Click to collapse
Sorry to hear that, thanks for responding. I had already done a few reinstalling of the latest PreRooted Rom via TWRP without that fixing it. Will keep at it, though.
phresch said:
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
Click to expand...
Click to collapse
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
---------- Post added at 01:07 AM ---------- Previous post was at 12:17 AM ----------
@RBox ; @AFTVnews.com
Decided to upgrade my first TowlRoot Rooted Bueller FTV1 on the last FireOS 3 PreRooted Rom (v51.1.6.3) to the latest FireOS 5 PreRooted Rom (v5.2.1.1_r1). I verified that I meet all the requirements. My bootloader was FULLY unlocked & I was on the latest CWM (v6.0.5.1.4a) with BootMenu (v1.0). I decided I wanted from the start the upgrade on as a clean as possible FTV1. So I uninstalled all programs except for SuperSU. Then I went into CWM & did a Factory Reset (Wipe Dalvik, Cache, Factory Reset) from within CWM & Reinstalled the last FireOS 3 PreRooted Rom (v51.1.6.3). All that was left after the Factory Reset was SuperSU.
Then I pushed over the TWRP bueller-twrp_3.0.0-7.img to the /SDCard & verified it's hash to make sure it was not a corrupt upload. Then I ran the command to switch to the TWRP recovery & everything installed perfectly.
I had ready a USB stick (Fat32) so I could install & md5 verify the FireOS 5 PreRooted Rom (v5.2.1.1_r1) on installation. Booted into TWRP & first did a wipe from within TWRP of Dalvik, Cache, Data & Internal Storage. Then installed the FireOS 5 PreRooted Rom (v5.2.1.1_r1) without any errors. Then I rebooted into system & it went thru it's paces. I did hit a road block when it came to check updates. This was because I was blocking the HTTPS update address from both my router & thru OpenDNS. I did a few re-flashes of the FireOS 5 PreRooted Rom (v5.2.1.1_r1) until I figure out that since this was the latest Rom version I should just let it talk to the update servers or do the PropBuild mod. So finally I got past the update nag. I first turned on ADB Debuging & I first did the SU command & chose to GRANT SuperUser rights. Then I did the update block command from SU. I installed my apps & the only bug I found after that was that ES File Explorer, even after it has been granted SuperUSer rights. It will error out "Sorry, test failed. This feature cannot run on your device". I thought this problem was just with ES file Explorer. But it seems to happen to a lesser degree on Total Commander & Root Explorer too. On those I can see the Root directories. But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
I tried flashing the bueller-fixsusdcard.zip thru TWRP on that install but nothing changed on the test response. Then I tried to do a full reinstall of the PreRooted Rom with the bueller-fixsusdcard.zip as a secondary .zip to flash during the installation. And same... Then I re-verified that I do have a unlocked bootloader. And that I am rooted. Passed on both. I was able to verified I am rooted by using an SDCard app while trying to see what size my MBCache.db file was. I was able to find it in /Data/Data/ without any problem.
So this is where I am at. I wonder if the bueller-fixsusdcard.zip file needs an update for FireOS 5 PreRooted Rom (v5.2.1.1_r1). Or should we try to install SuperSU as a secondary .zip file in TWRP or what can possibly be the answer to getting SU & Root working properly.
I would appreciate any ideas to try.

Y314K said:
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
Click to expand...
Click to collapse
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
Click to expand...
Click to collapse
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps

phresch said:
...
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
I searched for a download of v2.05 and could only fine sources that I did not trust. Do you have a link to that version?

phresch said:
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
Click to expand...
Click to collapse
I haven't tried to change or flash to a different SuperSU then the one that comes stock with the PreRooted Roms. Which is v2.46. Trying my best not to loose having a Fully unlocked bootloader. Are you flashing/testing the different versions of SuperSU thru TWRP or are you just flashing APK's just to try to see which one's GUI might still work ?
I notice the SU /SDCard bug only after trying out Total Commander & Root Explorer. Others said those where working fine for them. But for me it looked like they where gonna work fine. But as soon as any of those went to Root mode. I started to see bugs in those programs too. Although in those programs I can at least view Root files. And this last time Root Explorer is letting me copy files over from Root to /SDCard. Total Commander is still hanging when trying to copy files from Root to /SDCard. Like I said this last time I installed the /SDCard SU .zip fix right after I flashed the PreRooted Rom. So it did changed something. But from ADB I still get the same response from the SU List command.
phresch said:
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
Click to expand...
Click to collapse
I have not swapped SuperSU from what comes with the PreRooted Rom. Trying other SuperSU versions might be something I do after getting some feedback from @rbox since I really do not want to accidentally loose my Fully unlocked bootloader.
phresch said:
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Click to expand...
Click to collapse
Are you doing the SuperSU changing thru APK flashing or thru TWRP zip flashing ? Do you know a link to where we can find most versions of SuperSU from v2.16 (used when we towelrooted) to v2.78 ? I see v2.79 is the latest version. Have you tried v2.79 on your FTV1 ? Is there a version of SuperSU we shouldn't go beyond ?
phresch said:
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
Please post v2.05. I wonder if we can go down to v2.05 for that option. And then when things are working right go back to v2.46.
Either way ES File Explorer / Root Setting will not work for your right. Not matter what?
Hope I can get past this bug before updating my other 3 FTV1's.

Just ran into something else that is very odd. I've been using Amazon FireTV Utility App v0.66 to access ADB non-Root & Root Shell. Decided to switch to the stand-alone "adb-setup-1.4.3" to see if that would help with the SU commands. But I found that as soon as I give it the "adb shell su" command. Even if SuperSU has been granted full access on a fresh install of the PreRooted Rom on the FTV1. The "[email protected]:/ # _" line gives me a blinking _ & it won't let me input anything else. On the FTV1's screen it says "ADB Shell (2000)" was granted root access each time. But I can't get past that. Is like ADB never receives the granted access response. Then I have to CTRL+C to be able to input anything & exit. This happens whether I opened the CMD with & without Admin rights on my Windows 8.1 PC.
Gonna try downgrading to adb-setup-1.4.2 but I doubt it will make a difference. So the bugs are bunching up. Seems SuperSU is not being installed or allowed to work properly. Any help would be appreciated.
Forgot that on FireOS 5 you have to break the command.
First "adb shell" to get "[email protected]:/ $" & then just "su" to get to "[email protected]:/ #" without it freezing.
The /SDCard list still had the same response though.
"lrwxrwxrwx root root 1970-01-07 19:45 sdcard -> /storage/emulated/legacy"

Solution:
First let me start by Thanking @rbox , @AFTVnews.com , @zroice , @phresch for all their work & feedback.
Was finally able to test multiple options & found a reproducible solution to this problem. The key was in @zroice post about Holo Themer.
https://forum.xda-developers.com/fi...w-to-supersu-xposed-app-t3552590#post71703744
Basically you got to make sure you install or have installed the latest version of BusyBox & XPosed & HDXPosed Module. And to have activated Holo Themer from within XPosed so you can run the SuperSU APK that comes with the PreRooted Rom. SuperSU should ask you to update. Once you have done a "Normal" update like we did when we first rooted our FTV1's then that should fix the Root Option fail that ES File Explorer & other apps have had. I am guessing the problem comes when we uninstall or wipe our FTV1's during our FireOS 3 to FireOS 5 update. Some of us thought BusyBox & Xposed would not be as important to functionality on FireOS 5 as it was on FireOS 3.
Make sure you only activate Holo Themer on a per needed basis. Since it will make your FTV reboot randomly if you leave it on all the time.
And like always. As long as you installed TWRP correctly. You can always start anew with a wipe (NEVER WIPE SYSTEM) & install of the latest PreRooted ROM. I would also recommend having all the files you know you will need in a USB drive or SDCard in FTV2's case ready to go & in separate folders before you start flashing away. Makes things much easier.
If you forgot how to install BusyBox or XPosed you can always find how in the many guides over @ AFTVNews.com . For me even the old FireOS 3 guides & FTV2 guides help as a good refresher or visual confirmation.

[How-To]N930T - Root, Mods, Everything Working - 9/29/16 - Updated to PI4 System.img

Here it is. Full T-mobile With root, wifi calling, bluetooth and volte all working - since this is t-mobile based all bands should work as well
Updated to use API4 System Image and API4 Modem - MyMods has also been updated for the API4 System - Whatever you do DO NOT FLASH the API4 BL file. you will be Stuck on the new firmware without root if you do this as you cannot go back
To Avoid Repeat Questons. READ! READ IT AGAIN! and then READ it once more! if you do not Understand any part of this. Do Not Continue!!!
This Guide assumes you have some basic knowledge and is for advanced users!!!!!!!!
This Guide also Assumes you have an sdcard inserted in your phone(however some of you may not and this will not work.)
i will post an update to this guide when we have a method working for those of you with no extsdcard
Read this entire post before doing anything to avoid issues and FOLLOW Directions - if you don't things will not work right.
Note! if at anytime during the following steps you see the samsung boot animation before step 11. start over cause you screwed up!
Step 1. download the following files
https://www.androidfilehost.com/?fid=24651430732237653 bbx.rar
https://www.androidfilehost.com/?fid=457084094631641263 API4 system.rar
https://www.androidfilehost.com/?fid=24686680535467223 T-mobile APGC Bootloader
https://www.androidfilehost.com/?fid=529152257862665245 T-mobile API4 Modem
Step 2. extract system.rar and bbx.rar and then copy system.img and bbx to your extsdcard(the sdcard you inserted into your phone)
Step 3. odin sprint userdebug firmware available here. http://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202
Step 4. Directly after odin is done with the sprint file you will immidiatly be presented with an update screen
Step 4a when this process of erasing your phone is finished it will reboot(this is the point you want to do the next step)
Step 4b. press and hold power, home and vol up to enter recovery
Step 4c If you see the samsung boot animation. you did NOT do this right and i would suggest you start over
Step 5. open a command prompt in your adb folder and do the following steps 1 at a time(these are case sensative)
Step 5a. adb shell
Step 5b. su
Step 5c. setenforce 0
Step 5d. export PATH=$PATH:/sbin
Step 5e. mount -o remount,rw /
Step 5f. on your phone, go to apply update from sdcard(this will mount your extsdcard as /sdcard and you should see the system.img file and the bbx file) do not select anything, go back to adb and continue(it is not a big deal if those files don't show. we just needed the extsdcard mounted as sdcard - the files exist, just continue to the next step)
Step 5g. cp /sdcard/bbx /sbin/bbx
Step 5h. chmod 777 /sbin/bbx
Step 5i. cd /sbin
Step 5j. ./bbx --install /sbin
Step 5k. umount -l /system
Step 5l. /sbin/dd if=/sdcard/system.img of=/dev/block/platform/soc/624000.ufshc/by-name/system
Note. you will see a blinking cursor. just be patient
Step 7. when it is done you will see something similar to this
11161600+0 records in
11161600+0 records out
5714739200 bytes (5.3GB) copied, 268.668086 seconds, 20.3MB/s
Step 8. if all went well you should be at your prompt and not in adb anymore
Step 9. from your command prompt simply type
Step 9a. adb reboot bootloader
Note! - if you still have odin open and the sprint file in the ap box make sure you uncheck it so it doesn't reodin the sprint firmware
Step 10. open odin and click the bl button and select this file - BL_N930TUVU1APGC_CL8706614_QB10376889_REV00_user_low_ship_MULTI_CERT.tar.md5
Step 10b. now click the cp button and select this file - CP_N930TUVU2API4_CL9115549_QB10937257_REV00_user_low_ship_MULTI_CERT.tar.md5
Step 10c. now click start. it will reboot when done let it fully boot this time.
Step 11. once booted and you have setup your phone, we need to add the root files or supersu as most of you know it
Note! pertaining to Step 12. these instructions were taken Explicitly from @freeza thread which is listed in step 3
Step 12. Now we need to add supersu and the needed files for it to work
Step 12a. download this file - https://www.androidfilehost.com/?fid=24651430732236679
Step 12b. Extract the sun7 file to your adb folder making sure the files are in a folder called sun7(mine looks like this - c:/adb/sun7 and contains 4 files)
Step 12c. Open a command prompt where your ADB executable and sun7 folder are.
Step 12d. adb shell
Step 12e. su - Note! if your adb prompot changes from a $ to #(you are good and have root access)
Step 12f. type exit twice to get back to the command prompt. - Your Phone should be fully booted when you do this
Step 12g. adb push sun7 /data/local/tmp/su
Step 12h. adb shell chmod 0777 /data/local/tmp/su/*
Step 12i. adb shell
Step 12j. cd data/local/tmp/su
Step 12k. su
Step 12l. ./root.sh - Note. this command begins with a . do not leave it out
Step 12m. Your Phone will now reboot
Step 13. when booted back up go to playstore and install busybox on rails or a similar app and install busybox to /system/xbin(if your given an option of where to install it)
Step 14. Thats Pretty Much it. install any additions i have included if you like. most of all enjoy it
Additional Notes!
If for any reason you do a factory reset. you will break root and need to redo this method to get it back
If you use shealth do not update it or allow playstore or galaxy appstore to auto update it or it will break it
If you plan on running the debloat/deknox file you will need to disable auto updates in google playstore as soon as you finish the setup wizard or you will be uninstalling the apps that managed to update
Note! Keep in mind that i remove alot of things(ie. allshare, knox, gear manager, game manager, tmo apps, google apps, facebook and alot of other things) if you need any of what i remove, you can simply open the zip and go to META-INF/com/google/android and open the following file "updater-script" in notepad++(do not open it with windows notepad as it will screw up the formatting on the entrys) you will see a whole bunch of lines that begin with delete_recursive, remove the lines with names of the apps you do not want removed. most of this stuff is self explanatory by it's name as to what it is and should be very easy to figure out. when done editing the file, save it. and flash the updated zip in flashfire. it's as simple as that.
Additional Files for those that want them(these are all flashed via flashfire)
https://www.androidfilehost.com/?fid=385035244224381428 my modifications zip API4 Version(very minor mods to statusbar and a few other added features)
https://www.androidfilehost.com/?fid=24686680535467932 debloat/deknox zip - Updated with remaining t-mo apps i missed initially
https://www.androidfilehost.com/?fid=24651430732237106 beats audio installer(this is a blue themed version done by me)
https://www.androidfilehost.com/?fid=24651430732237109 Dolby Atmos Installer
https://www.androidfilehost.com/?fid=24651430732237107 Viper4Android Installer
https://www.androidfilehost.com/?fid=24651430732237108 selinuxmodechanger.apk so you can set kernel to permissive for viper(this is an apk. just install it from your sdcard)
My Mods Contains the Following Modifications
3minit battery
battery bar - option is in rom control
potato clock
loud volume warning - toggle to disable or enable this via rom control
network speed on statusbar - option in rom control
aokp rambar in recents
added some additional toggles
ability to move the wifi and signal bar indicator to the left or right side via a toggle in rom control
a few csc tweaks
Applock Added - Thanks @TEKHD
FOLLOW Directions - if you don't things will not work right.
thank you to the following:
@freeza - for posting the original userdebug file
@ted77usa - for testing
@bajasur - for the initial idea which ultimately led to this
@Surge1223 - for the busybox installer and the adb help and android commands that make this work
@galaxyuser88 - for testing this and pointing out some flaws
@Hashcode - for inspiration
and anyone i missed
this was a complete collaboration and is only available because of those mentioned so be sure to give them thanks
Big Thanks to @galaxyuser88 for testing the mods for me as i can't

for those that don't like PI4 update. heres the original PGC files
https://www.androidfilehost.com/?fid=24686680535467933 - PGC mods
https://www.androidfilehost.com/?fid=24651430732237809 - PGC system.img
https://www.androidfilehost.com/?fid=24686680535467224 - PGC CP File(modem)
method is the same, just use these files instead of the updated pi4 files

reserved 2

reserved 3

Ok here it is: Xposed still works with this new root method, Only one catch, you have to install this before you install any of @OvrDriVE Mods.
If you plan on using Xposed then do not install @OvrDriVE my modifications zip as this will crash your systemui.apk.
As with any custom rom's, root, add-on's, you assume all risks with modding your phone. You have been warned.
Make sure you read all of my directions below, before you start posting errors with the install. Worst case you just have to start over with @OvrDriVE s installation.
Here is the way you can install xposed on your phone after you have root. I in no way have made any files or apks, I am just posting ways you get this loaded on your phone.
Please Thank the devolopers and others that have made all these files and apks possible..
The way to install Xposed framework via FlashFire:
1. Download FlashFire, You can get it from the app store: https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
2. Download the Xposed Installer Apk: Xposed installer Apk
3. Download the Xposed Framework zip.<<< this is the file that you will be flashing via FlashFire: Xposed Framework.zip
4. Once you have all the files downloaded onto you computer/phone: you are ready to start. If you have'nt all ready copied all the files to your phone storage, do so now. If you did then you can move on to the #5.
5. Open FlashFire on your phone. Once it is loaded and open, click on circle with + button on the bottom right of the screen.
Then Click on Flash ZIP or OTA button.
Now select the xposed framework zip that you downloaded from #3.
Next you click the check mark on the top right of
the screen( do not change any of boxes on the left of the screen.<<< You Have Been Warned!!!!! .
Next scroll to the bottom of the screen and click the left button (flash button w the lighting bolt)
Sit back and watch FlashFire do its magic..
6. After #5 completes, you can now install the xposed installer apk from #2. Once installed open and check framework in the app and you should have this : Xposed framework version 86.1 (custom build by wanam / 2016709 is active.
7. Now go to Download in the xposed installer and download: XTouchWiz 1.1.2 or Wanam Xposed 1.3.0 Made for Samsung Android 5 and 6 Roms by Wanam. You can also download Firefds kit 1.0.5.1 by firefds <<<<< this is just a modified version of XTouchWiz with more stuff added to it.. This works as well on samsung note 7 root method.
8. Once you downloaded it, installed it, then go into the Xposed installer app- modules- you select the the app in #7 by placing a checkmark in the box on the right to activiate the modules.
9. Reboot your phone to activate the module.
10. Enjoy your efforts and customizing your phone:
If you some reason you want to uninstall xposed : flash this:xposed-uninstaller-20160211.zip

Awesome.....finally[emoji106]
Video tutorial could be found in here http://forum.xda-developers.com/showthread.php?p=68831392..... make sure to download correct modified system.rar for your specific carrier.
https://youtu.be/Oi-tuA_EIxA
*TwisT3DroiD_N930T*

Thank you!!!!
Sent from my SM-N930T using Tapatalk

OvrDriVE said:
Ok all here it is. root, with wifi calling and volte along with a few modifications
1. Follow the guide here skipping the root method for now- http://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202
2. go through setup. add your google account but do not setup samsung account(you'll do this later)
3. once at the homescreen, open google playstore and go to settings and set it to not auto update apps(you can change this back later)(this is to prevent apps from auto updateing as i will be removing most of them)
4. now do the supersu install as instructed in the sprint post
5. once booted back up, open playstore and install flashfire
6. once flashfire is installed flash this zip
7. https://www.androidfilehost.com/?fid=24651430732237438 - note7update.zip
8. once booted back up. open themes and add your samsung account info.
9. exit themes and open galaxy apps and update all available apps(they should install without errors)
10. you can skip this if you want - install supersu2.77 apk
11. https://www.androidfilehost.com/?fid=24686680535467222 - superuser 2.77
12. when done. open shealth. and go through it's setup. when done flash this file - if you don't setup shealth it will not work once we remove knox.
13. https://www.androidfilehost.com/?fid=24686680535467219 - knox remover
14. when booted back up. go to your apn settings and reset it to default and then select the t-mo apn
15. boot download mode
16. and odin t-mo cp file only - This will flash the t-mo Modem
17. https://www.androidfilehost.com/?fid=24686680535467224 - t-mo cp odin file
18. once booted up, enable airplane mode, then enable wifi and wifi calling should turn itself on.
19. everything should work fine
20. if by chance you get a wifi calling error 0082 just enable airplane mode then enable wifi and it will fix itself
heres a few Extra Files for those that may want them
here is a beats audio installer
https://www.androidfilehost.com/?fid=24651430732237106 - beats
here is dolby atmos installer
https://www.androidfilehost.com/?fid=24651430732237109 - dolby atmos
and here is viper4android installer
https://www.androidfilehost.com/?fid=24651430732237107 - viper4android
and here is selinuxmodechanger to set kernel to permissive
https://www.androidfilehost.com/?fid=24651430732237108 - selinux mode changer
all 3 audio mods fully work together. make sure you have permissive set or they won't work
enjoy
the mods included are battery bar, 3minit battery, potato clock, network speed statusbar mod, 5 way reboot, ability to toggle wifi/data on the left or right, and a few other mods. it debloats the rom as well.
FOLLOW Directions - if you don't things will not work right.
thank you to @jovy23 for the wifi calling files. and a great big thanks to all those who tested this. and a great big ty to @freeza for posting the original userdebug file
also ty to anyone i missed
i know this isn't a proper post and i will fix it later
View attachment 3865172View attachment 3865173
Click to expand...
Click to collapse
Wow nice job man!

FTW
Sent from my SM-N930T using XDA-Developers mobile app

Nice job man! :good:

Thanks!

Samsung Pay
Does this still make Samsung pay not work or any other NFC payment types?

freeza said:
Wow nice job man!
Click to expand...
Click to collapse
nah. thats all you guys man. you guys deserve the credit. i just did a few mods and wrote out the install instructions.

batsup606 said:
Does this still make Samsung pay not work or any other NFC payment types?
Click to expand...
Click to collapse
keep in mind that once you root no payment method will work. however as this does not trip the knox counter. you can odin stock t-mo firmware and samsung pay and android pay will work just fine. you can't have it both ways unfortunately. it's either or

!!!!!!!!

If you guys want Samsung pay....u need to stay stock and use disabler package pro to debloat and like @OvrDriVE said we can't have it all ....either or we gotta give up something. .... but with this breakthrough with root from @freeza.... now WiFi calling and volte work.... we are moving in good direction .... until we all get new note 7 replacement phone in couple week..... happy Labor days guys for people in US.
Sent from my SM-N920T using Tapatalk

OvrDriVE said:
keep in mind that once you root no payment method will work. however as this does not trip the knox counter. you can odin stock t-mo firmware and samsung pay and android pay will work just fine. you can't have it both ways unfortunately. it's either or
Click to expand...
Click to collapse
Ah okay thanks! and do you know if the Bluetooth issues still occur?

I am going to watxh this topic. I know alot of work is going on however i want to see how stable it is before i do anything. I can wait no problem. i know we have been hitting roadblocks and until we have an official root method I am perfectly fine without for now... To all the Devs great job now we wait and see if penetration testing and users can do this method of root. Thank you all for your time and hard work!
Ice.
Sent from my SM-N930T using XDA-Developers mobile app

OvrDriVE said:
keep in mind that once you root no payment method will work. however as this does not trip the knox counter. you can odin stock t-mo firmware and samsung pay and android pay will work just fine. you can't have it both ways unfortunately. it's either or
Click to expand...
Click to collapse
Great job on this and all the other developers who finally got android development this far for us!
Also has anyone tried chainfire's suhide app to see if samsung pay or android pay will work even while being rooted?

batsup606 said:
Ah okay thanks! and do you know if the Bluetooth issues still occur?
Click to expand...
Click to collapse
i do believe the issue still exist. i havn't tryed replacing the etc folder yet to see if it fixs it or not
you can connect but once disconnected you have to unpair the device and repair it for it to work.

[ROOT] [MAGISK] Global ROM on CN Device - WORKING ROOT

THIS IS NOT FOR FAINT OF HEART. DON'T BLAME ME IF YOU BREAK SOMETHING.
Mount system as RW in TWRP. (this took mounting, unmounting, then remounting for me)
Use the following commands CAREFULLY from a computer.
cat /system/build.prop > /sdcard/build.prop
Open the build.prop from the sdcard and edit the following line numbers: 25, 26
You are changing:
ro.product.name=perseus
ro.product.device=perseus
To this:
ro.product.name=perseus_global
ro.product.device=perseus_global
save the file on the sdcard
Go back to ADB session and do this:
cat /sdcard/build.prop > /system/build.prop
IF THIS FAILS YOUR SYSTEM IS NOT RW, UNMOUNT AND REMOUNT IN THE MOUNTS MENU.
Go back to the mounts menu and unmount /system
Flash Magisk 17.3 (18.0 seems to be having intermittent issues with passing checks)
Reboot, and enjoy your CN device running Global with ROOT.

out-file : Could not find a part of the path 'C:\sdcard\build.prop'.
I got that error above. How do i know twrp mounted system correctly?
nvm... i went into advance and did via terminal

Great find, works!!
Thanks!!

You're welcome. I may try to make a flashable zip to do this automatically, but I haven't had a chance to look at it.

Work so well, Thanks @PWn3R!

xterminater07 said:
out-file : Could not find a part of the path 'C:\sdcard\build.prop'.
I got that error above. How do i know twrp mounted system correctly?
nvm... i went into advance and did via terminal
Click to expand...
Click to collapse
Here is the clue. " 'C:\sdcard\build.prop'."
What is a Windows drive letter doing on an Android? Adb session?

@PWn3R YOU ARE THE MAN

Has anyone tried a custom kernel on the latest global? I tried androplus v 0.6 and it didnt really work. It allows me to replace files in system but not rename because when I overwrite it still says there is an existing file with same name.
Any kernel that works please let me know. I am working with defcomg to get gcam modded more than the current ones.

I would like to try, i already had install last global, and this rtemove my twrp instead the official recovery.... Can you give me all the steps to do from this position? Thank you

I have a problem with camera, force close no matter what I've done. may be build.prop change?

kbello said:
I have a problem with camera, force close no matter what I've done. may be build.prop change?
Click to expand...
Click to collapse
i got this as well... oh well going back to xiaomi eu rom

Hi the change to the build.prop did not break the camera. Mine is working fine. Maybe clear app data for that app?

I do many times, didn't work,
---------- Post added at 11:45 PM ---------- Previous post was at 11:23 PM ----------
This is the error:
java.lang.RuntimeException: unSupported Saturation
at com.android.camera2.compat.MiCameraCompatBaseImpl.applySaturation(MiCameraCompatBaseImpl.java:248)
at com.android.camera2.compat.MiCameraCompat.applySaturation(MiCameraCompat.java:49)
at com.android.camera2.MiCamera2.applySaturation(MiCamera2.java:2486)
at com.android.camera2.MiCamera2.applyCommonSettings(MiCamera2.java:2858)
at com.android.camera2.MiCamera2.applySettingsForCapture(MiCamera2.java:2971)
at com.android.camera2.MiCamera2ShotNormal.generateRequestBuilder(MiCamera2ShotNormal.java:141)
at com.android.camera2.MiCamera2ShotNormal.startShot(MiCamera2ShotNormal.java:59)
at com.android.camera2.MiCamera2.captureStillPicture(MiCamera2.java:2042)
at com.android.camera2.MiCamera2.triggerCapture(MiCamera2.java:1892)
at com.android.camera2.MiCamera2.takePicture(MiCamera2.java:991)
at com.android.camera.module.Camera2Module.startNormalCapture(Camera2Module.java:1130)
at com.android.camera.module.Camera2Module.onWaitingFocusFinished(Camera2Module.java:406)
at com.android.camera.module.loader.camera2.FocusManager2.capture(FocusManager2.java:767)
at com.android.camera.module.loader.camera2.FocusManager2.doSnap(FocusManager2.java:326)
at com.android.camera.module.Camera2Module.onShutterButtonClick(Camera2Module.java:1057)
at com.android.camera.fragment.bottom.FragmentBottomAction.onSnapClick(FragmentBottomAction.java:1653)
at com.android.camera.ui.CameraSnapView$1.handleMessage(CameraSnapView.java:67)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6806)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)

@PWn3R, the root is working but there are some functionalities that disappeared in the setting menu such as slider settings, screen color.
For those who wants to revert to CN rom, revert the changes you have done and DO NOT forget to remove Magisk by flashing the uninstaller zip otherwise the device will bootloop.

I restore the original build.prop and boot.img, the camera came back to work. Any workaround?

kbello said:
I have a problem with camera, force close no matter what I've done. may be build.prop change?
Click to expand...
Click to collapse
I didn't notice if the slider settings were there before changing the build.prop. The problem here is that when you flash magisk it's enabling secure boot, which is triggering a check that normally runs when the device is locked. I think we can probably fix that by modifying the file that causes it and then this will work without build.prop changes. I have not had a chance to look into that, but will try to do so.

No Mobile Data on Treble Roms

I've tried over 5+ different treble ROMs and the mobile data will not work. My friend @Spaceminer had helped me try to solve it by finding an apns-conf.xml as well as a flashable zip but no luck.
I'm using the Moto G6 Play XT1922-7 Boost Mobile Variant.
I'm sorry I haven't provided much detail to the issue but this basically sums it up.
Thank you for any help.

Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie

Alphita said:
Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie
Click to expand...
Click to collapse
Did you try to flash the vendor.img on TWRP?

sinkoo1979 said:
Did you try to flash the vendor.img on TWRP?
Click to expand...
Click to collapse
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks

Alphita said:
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks
Click to expand...
Click to collapse
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.

Spaceminer said:
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.
Click to expand...
Click to collapse
How do i set those permissions? Thanks in advance

Alphita said:
How do i set those permissions? Thanks in advance
Click to expand...
Click to collapse
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot

Spaceminer said:
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot
Click to expand...
Click to collapse
Thanks! I will try this the next time i flash a rom

Would someone be so kind enough to share their BOOST apn.config.xml that the replaced the one on with that does NOT work on these GSI's?? If you do I'll follow you and hit thanks all day. ??

Here's (see screenshot) the closest I've ever gotten far as having data on a gsi. I must have the wrong xml file. I am fully aware of the process described above and have even done it multiple ways after I knew the way described and how I was adding the apn xml was correct and I have zero data.
If someone will attach their apn.config.xml, the one that they acquired data from using the boost Mobile network I'll be extremely thrilled and forever greatful to add it to the thread I made over in guides section so that in the future people can solve this issue fast and get her running and have a jolly day. ? I made that thread (I'll change the name later today) initially to consolidate as much info as I could and put it all in the op so we can be a bit more organized. I just haven't figured out anything else so I can't add to it just yet. ? This would be a great addition if someone would be so cool enough to kick me down some knowledge far as what's the correct apn.config.xml to replace the og one in gsi to get data working. I've deleted the current apn xml and replaced it with the one I have, I've overwritten it, I've tried countless times messing with the telephony.db and I obviously can't do it. Please pleeeaasee post the proper apn xml so I can get this phone going and add to op over there. @Starkiller2
I hope everyone is having a good day. It hot as **** where I'm at today. ??

I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight

Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.

Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Vague and unhelpful. Need better directions on that I messed with sqlite editor for days on end swapping out telephony.db things and never did get it going.
Did you swap both of them??
Did you swap other files in telephony.db too?
Details...?
What files exactly did you extract in telephony.db?
Vague comments never help anyone. Better to not post at all then post some two word comment with a link.

I apologise, I'm driving across country and was making an effort to help in the little time I had, but you're right, better to not try at all. Which may be why you aren't getting any answers to your questions. Some info is usually better than none and can sometimes lead you in the right direction, but you won't even get that much snapping at everyone who doesn't immediately solve the problem you have and then rage quitting when you can't do it yourself. It makes people not want to put in any effort. You have 4000 posts I assumed you could figure out how to edit apns with an app from the play store. You're right. I should absolutely stop offering any input at all, but rather I should just start *****ing and whining when I'm not spoon fed like I see so much here.
And as I have posted directions in multiple other threads, I assumed you had done at least a cursory search for your answer(as per forum rules) which would've found those posts but I was apparently wrong there as well.
---------- Post added at 07:00 PM ---------- Previous post was at 06:45 PM ----------
Spaceminer said:
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.
Click to expand...
Click to collapse
Thank you. That's good to know

hi, there is in the web a file apns-conf.xml to download? or sombody take us a backup? Thanks

Hey gang, I too am having issues trying to simply get mobile data working on GSI's. I have a Pixel 3a, and have tried multiple Android 10 GSI's, all of them don't allow me to use mobile data. I have not tried the apns-conf.xml trick yet, as I am unsure if that's the answer if it hasn't worked for others. Android 11 does not use an apns-conf.xml in system/etc/ so I couldn't extract it from my current setup unfortunately. Wish you all luck, post back if you get something working.

not working, moist do you have rooted phone? because only on rooted phones you can do this trick

doid1 said:
not working, moist do you have rooted phone? because only on rooted phones you can do this trick
Click to expand...
Click to collapse
I'll probably flash a ROM this weekend and pull my xml to test this. I have Telus so I unfortunately can't help with the Boost users, but can at least help confirm whether this method works or not.

ok thanks i wait, my phone seems to be dead on 4g.. says: no registration..
I tried everything imaginable and perhaps even the unimaginable .. heheheh .. but the result is always the same: no recording on the 4g, so I'm more and more inclined that it is a hardware failure or even a damage to the eeprom memory because 'I have formatted everything and the mobile phone has recharged everything correctly but it was useless ..
I tried to see that maybe it has a sim locked, but I didn't manage to enter meta mode and try to force it also because only with miracle box there is a guide ... umh ... and I do not stop until I succeed in the objective, and then the next step will be to take a complete image of another mobile phone identical to mine and copy it over it (but it is almost impractical because I cannot find anyone who gives me a full backup of this phone) and then I will brutally try to put another image of another working smartphone on it, leaving only the crucial sectors intact (system, boot, vendor, recovery, preloader, everything else I format it hehehehh) I will know..

Well I have a ROM flashed and found the apns-conf.xml, which is not included on my stock ROMs (10 or 11). Now going to flash a GSI or two and do some tests to see if I can get any data working.
Edit: Couldn't get the apns-conf.xml to work. However, I did find out the some GSI's work right out of the box for my Pixel 3A, those included AOSP 10 / 11 by Phh, and the CAOS R build. Bless, qidroid, havoc booted fine but did not have mobile data working.

[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?