Database Users

[TIP] [Sabsa Prime 3.0~5.0] for having Apps Update Issue

Many users of Sabsa Prime posted they cannot update Facebook.
and.. maybe other apps also not available for update comes in. (Youtube, SuperSu, ... etc)
I have edited packages.xml on /data/local but some app still has problem.
(Problems with Google Apps might be solved with editing packages.xml and replacing apks. see EDIT 3 bottom)
You need uninstall those first and reinstall from market, will be fine :fingers-crossed:
How to Uninstall Apps on /system/app
1.
Install
Titanium Backup
com.keramidas.TitaniumBackup
OR
ROM Toolbox Lite
com.jrummy.liberty.toolbox
2.
Run it and GRANT it a Superuser access.
3.
Go for the Apps list.
on Titanium Backup
Tap Backup/Restore
OR
on ROM Toolbox Lite
Tap App Manager
then Tap All Apps
4.
App which its names written Red are on /system/app on apps list.
5.
Find app annoys you from being updated on market.
6.
Tap or long press its name then menu comes up.
7.
Press Uninstall
if you can't find, swipe left or right - it might be there.
8.
Wait until uninstall finishes...
9.
Reboot Your Phone NOW.
It's Done.
There's a one more step if you want to use them is:
Install them from market again.
Now, you can update apps.
The problem CANNOT be solved UNLESS the Developer puts correct apks(from market, UNTOUCHED) in their ROMs.
if not, and you install newer ROMs or somewhat from them, It'll annoy you again.
EDIT 1---------------------------------------------------------------------------------------------
for someone having poor(? disconnects too often) data reception,
please check this thread about build.prop Fast Dormancy:
t t p : / / forum.xda-developers.com/showthread.php?t=1684604
EDIT 2---------------------------------------------------------------------Sept. 21th, 2012
>> Oops, I forgot to tell reboot your phone. also, wrote about steps for titanium
EDIT 3------------------------------------------------------------------------Oct. 1st, 2012
>> Found something weired with Google apps by myself. so I edited again.
due to some reason you can't update or Install some Google apps like Google Play Service, etc.
1.
extract apks from gapps package 20120429
if you don't have it, Google it.
2.
go to recovery.
3.
mount /system/as writable.
4.
replace corresponding apks in system/app/
(Incldue MarketUpdater.apk: if you want to keep Play Store updated. and.. included Play Store App from gapps 20120429 IS OUTDATED.
DO NOT REPLACE GoogleBackupTransport.apk: this shares signature with the ROM's so do not replace it otherwise it will be NOT AVAILABLE on your phone.)
if you extracted the gapps package in folder gapps,
Shift-Click upper folder on tree view.
and open command window here
in command-prompt:
adb push /gapps /system/apps
Replacing apks done however you have more steps to do for replaced apks start working.
(optional)
you can unmount /system/ because you have finished replacing apks.
5.
mount /data/as writable.
6.
pull out packages.xml
in command-prompt:
adb pull /data/system/packages.xml
7.
open packages.xml in text editor
(IMPORTANT: DO NOT SAVE files on windows notepad or something else displays all of lines as single line because lack of UNIX support)
8.
Delete shared-user element has name=com.google.uid.shared.
then save.
you have to delete whole element this might look like:
<shared-user name="com.google.uid.shared" userId="10000">
<sigs count="1">
<cert index="1" />
</sigs>
<perms>
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.youtube" />
<item name="android.permission.INTERNET" />
<item name="com.google.android.providers.gmail.permission.WRITE_GMAIL" />
<item name="android.permission.WRITE_SYNC_SETTINGS" />
<item name="android.permission.BROADCAST_STICKY" />
<item name="com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH" />
<item name="android.permission.VIBRATE" />
<item name="android.permission.GET_ACCOUNTS" />
<item name="android.permission.MASTER_CLEAR" />
<item name="android.permission.SUBSCRIBED_FEEDS_WRITE" />
<item name="android.permission.ACCESS_DOWNLOAD_MANAGER" />
<item name="com.google.android.providers.gmail.permission.READ_GMAIL" />
<item name="android.permission.WRITE_CONTACTS" />
<item name="android.permission.READ_PHONE_STATE" />
<item name="com.android.providers.im.permission.WRITE_ONLY" />
<item name="android.permission.RECEIVE_BOOT_COMPLETED" />
<item name="com.google.android.gtalkservice.permission.SEND_GTALK_DATA_MESSAGE" />
<item name="android.permission.READ_CONTACTS" />
<item name="android.permission.READ_SYNC_SETTINGS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES" />
<item name="android.permission.WRITE_SETTINGS" />
<item name="android.permission.SUBSCRIBED_FEEDS_READ" />
<item name="android.permission.ACCESS_NETWORK_STATE" />
<item name="android.permission.WAKE_LOCK" />
<item name="com.android.providers.im.permission.READ_ONLY" />
<item name="android.permission.WRITE_SECURE_SETTINGS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser" />
<item name="android.permission.CALL_PHONE" />
<item name="com.google.android.gtalkservice.permission.GTALK_SERVICE" />
<item name="com.android.vending.INTENT_VENDING_ONLY" />
<item name="com.google.android.googleapps.permission.GOOGLE_MAIL_SWITCH" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.mail" />
</perms>
</shared-user>
Click to expand...
Click to collapse
9.
put packages.xml back to your phone.
in command-prompt:
adb push packages.xml /data/system/packages.xml
10.
set its permission rw-rw-r-- as it was.
in adb shell:
# chmod 664 /data/system/packages.xml
# chwon system.system /data/system/packages.xml
(optional)
to check permission has set:
# ls -e /data/system/packages.xml (if -rw-rw-r-- is okay first char is for a directory)
11.
Reboot Your Phone NOW.
It's Done.

Fails to install from Play store
AtomosVE said:
Many users of Sabsa Prime posted they cannot update Facebook.
and.. maybe other apps also not available for update comes in. (Youtube, SuperSu, ... etc)
I have edited packages.xml on /data/local but some app still has problem.
You need uninstall those first and reinstall from market, will be fine :fingers-crossed:
How to Uninstall Apps on /system/app
1.
Install ROM Toolbox Lite
com.jrummy.liberty.toolbox
2.
Run it and GRANT it a Superuser access.
3.
Tap App Manager
4.
Tap All Apps
Like Titanium, App which its names written Red are on /system/app on apps list.
5.
find app annoys you from being updated on market.
6.
Tap or long press its name then menu comes up.
7.
press Uninstall
8.
wait until uninstall finishes...
It's Done.
There's a one more step if you want to use them:
Install them from market again.
Now, you can update apps.
The problem CANNOT be solved UNLESS the Developer puts correct apks(from market, UNTOUCHED) in their ROMs.
if not, and you install newer ROMs or somewhat from them, It'll annoy you again.
Click to expand...
Click to collapse
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.

mani4all said:
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
Click to expand...
Click to collapse
I believe you need to re-start your phone after Step 8. Then re-install from Market.

Oops, I forgot something..
mani4all said:
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
Click to expand...
Click to collapse
Oh, Forgot to tell rebooting your phone after uninstalled app. Hope you enjoy Facebook
Yowhy said:
I believe you need to re-start your phone after Step 8. Then re-install from Market.
Click to expand...
Click to collapse
Thanks for telling them reboot is need. I was forgot but Now, Corrected

How to increase your Honor 7 maximum volume

If, like me, you find your Honor 7's maximum volume still too low, here are the steps to increase it, and finally be able to fully hear your music in public.
First, you need a ROOTED HONOR 7 PLK-L01.
Then you need a file browser like Root browser or so.
You will also need a xml file editor like QuickEdit.​
1. Go to system>emui>base>prop
Open local.prop with QuickEdit.
Go to: ro.config.hw.security_volume=14
Change it to #ro.config.hw.security_volume=14
OR
ro.config.hw.security_volume=20 (it increases the maximum, it doesnt change the volume itselfs but prevents it to be locked by the security from Emui)
2. Go to system>hw_oem>Plank-L01>prop
Open local.prop
Same as before, change the value or add a # before the line.
Note that i'm not fully sure if this steps are mandatory but it will prevent a non working volume tweak occured because of the Emui's volume security.
3. Now go to system>etc>audio>hi6402
Open mixer_volumes_PLK_L01_ce.xml with QuickEdit.
Go to:
<path name="dup-media-fm-headset">
<ctl name= "S1 IL PGA GAIN" value="250" />
<ctl name= "S1 IR PGA GAIN" value="250" />
(QuickEdit has a search option on the top right corner)
And change the values to what you think is enough for you.
For me its 265, like this:
ctl name= "S1 IL PGA GAIN" value="265" />
And it should be it ! Don't forget that security volume is set to prevent auditive damages so please be careful with the values you set.
That's only for a headset, you need the change the value manually for the speaker too, with the same method.
If you have any questions or need help i'll gladly help.
Also if the steps 1 and 2 arent mandatory, i'd be happy to know.
EDIT:
Seems that you also need to change these values now (can't tell from which update this came from) for the tutorial to work:
@ Path name="media-headphone"
ctl name= "s1 IL PGA GAIN"
ctl name= s1 IR PGA GAN"

Cant find step 1 and 2 in system

Thank you
Could You be so kind and give us step by step for speakers please?
Much obliged.

For me existing volume is sufficient

magnea said:
Cant find step 1 and 2 in system
Click to expand...
Click to collapse
What version of Emui do you have?

Demeth said:
What version of Emui do you have?
Click to expand...
Click to collapse
B330
---------- Post added at 12:26 AM ---------- Previous post was at 12:26 AM ----------
rspn69 said:
B330
Click to expand...
Click to collapse
What about u?

rspn69 said:
B330
---------- Post added at 12:26 AM ---------- Previous post was at 12:26 AM ----------
What about u?
Click to expand...
Click to collapse
Are you properly rooted? Check it with SuperSU.
What file browser do you have?

Raven78uk said:
Thank you
Could You be so kind and give us step by step for speakers please?
Much obliged.
Click to expand...
Click to collapse
That's the exact same method but you have to change <path name="dup-media-fm-speaker"> instead.
Tell me if you can't find it.

I have neither the EMUI or HWOEM folder under system on build B180. I do have the /etc. folder and relevant files. I'm using a root explorer and proper root.
Any suggestions?

Unillogical said:
I have neither the EMUI or HWOEM folder under system on build B180. I do have the /etc. folder and relevant files. I'm using a root explorer and proper root.
Any suggestions?
Click to expand...
Click to collapse
Neither do I

Raven78uk said:
Neither do I
Click to expand...
Click to collapse
Is changing the values working?

Raven78uk said:
Neither do I
Click to expand...
Click to collapse
I think you must have MM b320

magnea said:
I think you must have MM b320[/QUOT
Does this mean this problem is for b320
Click to expand...
Click to collapse

Demeth said:
Is changing the values working?
Click to expand...
Click to collapse
Didn't had the chance to do it yet. Also seems that values You recommending are massively to big.
EDIT: Just took a peek inside file : mixer_volumes_PLK_L01_ce.xml and there is line for headphones You was writing about. But for speakers i just dont know which one to change as there is 'hundreds' similar with word 'speaker'.
Can You tell me exact line to change for higher volume of speaker ?

magnea said:
I think you must have MM b320
Click to expand...
Click to collapse
I indeed run B320, don't know for the other versions yet.

Raven78uk said:
Didn't had the chance to do it yet. Also seems that values You recommending are massively to big.
EDIT: Just took a peek inside file : mixer_volumes_PLK_L01_ce.xml and there is line for headphones You was writing about. But for speakers i just dont know which one to change as there is 'hundreds' similar with word 'speaker'.
Can You tell me exact line to change for higher volume of speaker ?
Click to expand...
Click to collapse
I have a root issue, i'll tell you what exact line as soon as i can have access to my folder again.

Demeth said:
Is changing the values working?
Click to expand...
Click to collapse
Demeth said:
I have a root issue, i'll tell you what exact line as soon as i can have access to my folder again.
Click to expand...
Click to collapse
Thank You, please let me know when You can.

in the directory system, not exist folder "emui".

Demeth said:
That's the exact same method but you have to change <path name="dup-media-fm-speaker"> instead.
Tell me if you can't find it.
Click to expand...
Click to collapse
B330/Android 6.0
There is no simple value changing as in
Code:
<path name="dup-media-fm-headset" >
<ctl name="S1 IL PGA GAIN" value="265" />
<ctl name="S1 IR PGA GAIN" value="265" />
</path>
There is
Code:
<path name="dup-media-fm-speaker" >
<path name="media-speaker" />
</path>
So what or how to change?
And what does
Code:
<path name="dup-media-fm-headphone" >
<ctl name="S1 IL PGA GAIN" value="250" />
<ctl name="S1 IR PGA GAIN" value="250" />
</path>
do? I did not change those, just <path name="dup-media-fm-headset" > - do I need to edit those values too?
I really would like to push up the volume just a little bit for the main speakers.

Is this for bottom speaker? Since I cannot hear any difference on earpiece speaker at all.
Could someone save exampled mixer files to download? I think my files have some low values, because my earpiece is very low.

MM on Galaxy Tab 2 10" for dummies?

Hello!
This is actually my first post here.
I have been developing some android apps but I have never modded any roms.
My Galaxy Tab 2 10" is terribly slow with the stock rom and I would like to wipe it and install MM.
Is there anybody that could point me to some step by step guide?
Thanks in advance

mapkozaffo said:
Hello!
This is actually my first post here.
I have been developing some android apps but I have never modded any roms.
My Galaxy Tab 2 10" is terribly slow with the stock rom and I would like to wipe it and install MM.
Is there anybody that could point me to some step by step guide?
Thanks in advance
Click to expand...
Click to collapse
<b>HOW TO ROOT Galaxy Tab 2 10.1 Model GT-P5113, GT-P5110 or GT-P5100</b><br />
<br />
<font color="Red"> <b>This solution requires access to a PC running Windows.</b> </font> Linux & Apple install info: post #203. <br />
This process adds 1 to your Download Counter (indicates tablet is customized unless reset to zero). <br />
Like everyone else on xda-developers, I make no guarantees nor bear any responsibility for your Samsung Galaxy Tablet(s). <br />
<br />
<b><font color="Red">This procedure works on stock 4.03 ROM but may not work if your new tablet comes with 4.04 installed. <br />
For those who receive a new tablet running 4.0.3 : ROOT your tablet <font color="Blue">BEFORE </font>you install 4.0.4 update<br />
and if you update to a 4.0.4 ROM by installing a zip file via CWM5 your access to CWM5 should remain. <br />
<font color="Blue">If you used KIES to update to 4.04 BEFORE rooting OR received a new tablet that came loaded with 4.04, <br />
use</font> workaround at post 325. <br />
</font></b><br />
<br />
<b>What you need:</b><br />
1. Odin3-v1.85_3.zip<br />
2.ClockworkMod Recovery Version 5.5.0.4: <b> is no longer available for download so you can try using philz_touch_4.93.6-p5100.zip and his .tar</b> versions which should work as well or better than 5.5.0.4 did. Download BOTH the zip and tar versions.<br />
3. If you never installed Samsung KIES, you MUST install Samsung USB Drivers <b>BEFORE</b> any of the above (so your PC connects to tablet). <br />
<br />
<b>IMPORTANT:</b> Copy <b>philz_touch_4.93.6-p5100.zip</b> to the ROOT of your <b>external</b> sdcard ( /mnt/<b>ext</b>SdCard ). This is the micro sdcard you insert in tablet slot. Your <b>/mnt/sdcard</b> folder is internal memory (not recognized in CWM recovery).<br />
<br />
<b><i>To avoid confusion about using the Volume rocker switch, I'll refer to side closest to POWER button as LEFT/Volume DOWN and side away from power switch as RIGHT/VolumeUP. </i></b><br />
<br />
<b><font color="Red">STEP 1:</font></b><br />
Turn tablet OFF and restart in download mode by pushing and holding Power & <b><font color="Red">Volume UP/RIGHT</font></b> buttons at same time. When wording with yellow triangle appears, push <b>Volume down</b> to continue into download (ODIN) mode. Don't plug tablet into computer yet.<br />
<br />
<b><font color="Red">STEP 2:</font></b><br />
Make sure KIES (if installed) is closed and not running. <br />
Extract <b>Odin3 v1.85.exe</b> and run it.<br />
<br />
<b><font color="Red">STEP 3:</font></b><br />
Connect tablet to computer.<br />
In Odin, click <b>PDA</b> button. Select <b>philz_touch_4.93.6-p5100.tar</b> file you downloaded and click <b>START</b> button. <br />
Let Odin install files. When it's done installing CWM, box turns <b><font color="Lime">GREEN</font></b> and tablet will reboot.<br />
<br />
<b><font color="Red">STEP 4:</font></b><br />
Disconnect tablet from computer. Turn tablet OFF and restart in recovery (CWM) by pushing and holding <b><font color="red">Power & Volume DOWN/LEFT</font></b> buttons at same time. When Samsung Tab 2 10.1 logo appears, you can release power button but continue holding volume button for a few more seconds. Note: If you've done this on other Samsung devices, you will notice that it takes longer before blue CWM text appears ... just be patient. <br />
<br />
Once you are in recovery, use volume button (UP/DOWN/LEFT OR RIGHT) to move around and POWER button to select an option. <br />
Select <b>install zip from sdcard</b>. Choose <b>philz_touch_4.93.6-p5100.zip</b>) file you already copied to root of sdcard. <br />
<br />
When rooting is finished, choose <b>reboot system now</b> from CWM menu.<br />
<br />
<b><font color="Red">DONE !</font></b><br />
<br />
You should now be rooted. Depending on your Tab2 model, you may need to manually install SuperUser and disable <b>SuperSU</b> before you can install or use all root goodies.<br />
<br />
<i><font color="Green">Now that your Tab 2 10.1 is rooted, I strongly suggest going to Play Store and install a free app called <b>Quick Boot</b>. It lets you reboot into CWM the easiest & fastest way. Then reboot into Recovery (CWM) and make a Backup BEFORE you do ANYTHING else to your tablet. </font></i><br />
<br />
<b><font color="Purple">WARNING:</font> Do not install ROM Manager until developer says app will support Tab2 10.1 </b> < Posting this because someone bricked their Tab2. <br />
In addition, ROM Toolbox may not work properly (1 crash reported). <br />
<br />
<i>Thanks to nycbjr, xoomdev, Android Groupee, nitr8, Codeworkx snd trevd for help and pieces of the aforementioned process. </i><br />
<br />
<b>RE-ROOTING</b><br />
If you do a firmware update, simply re-root using same procedure and tablet will retain root status (until you do another firmware sometime in the future). <br />
<br />
<b>UNROOTING</b><br />
I have successfully unrooted my GT-P5113: <b>[How to] UN-ROOT Galaxy Tab 2 10.1 [GT-P5113 / 5100 / 5110]</b><br />
If you're curious about my complete analysis of this tablet, where to buy accessories at <b>LOW prices </b><br />
and my feedback after testing a few custom ROMs, read my <b>Galaxy Tab2 10.1 Review</b> on epinions.<br />
<br />
Enjoy,<br />
<br />
Glenn <br />
<br />
<font color="Gray"><br />
| Nexus 7 | Galaxy S II | ASUS TF700 | Jura J9 < Love my digital expresso machine<br />
(Sorry y'all ... sold my Tab2 10.1 many moons ago but I have updated the download links shown above). <br />
</font><br />
<font color="MediumTurquoise">Those who click <b>THANKS</b> are appreciated. </font><br />
<br />
<b><i>P.S. Samsung 4.0.4 was my NEW favorite ROM (until I sold my last T2). <br />
404 was faster & smoother than ANY other current custom ROMs!</i></b> and found more WiFi signals & faster tether to my Sprint E4GT Hotspot! Now my Asus TF700 is The Bolt.
Sent from my SM-N910V using Tapatalk

Thanks a lot, but what do I do after the device is rooted?
How do I wipe out the existing rom and install MM?
Thanks!

mapkozaffo said:
Thanks a lot, but what do I do after the device is rooted?
How do I wipe out the existing rom and install MM?
Thanks!
Click to expand...
Click to collapse
If you check out the development thread, you will find roms and all sorts of things for our aging tab.
Sent from my SM-N910V using Tapatalk

mapkozaffo said:
Thanks a lot, but what do I do after the device is rooted?
How do I wipe out the existing rom and install MM?
Thanks!
Click to expand...
Click to collapse
If your already rooted then :
This cm13 will do it fine for marshmallow : http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
And this twrp to flash it :http://forum.xda-developers.com/gal...overy-team-win-recovery-project-twrp-t3464050
Just follow the instruction and it will be fine :good:

Get yourself a custom recovery, like TWRP.

mapkozaffo said:
Thanks a lot, but what do I do after the device is rooted?
How do I wipe out the existing rom and install MM?
Thanks!
Click to expand...
Click to collapse
if you dont know what you are doing. you shouldnt flash anything.
first step for you. READ!! read all kind of threads here in tab2 forum.
it will help you a lot

Help get UI nav sounds.

Hi there!
I`m running an androidtv rom and i`d like to get the ui navigation sounds for Nexus player.
Thx so much.

well, I did some digging and found audio "ogg" files
"pano_blip_alt, pano_click, pano_error" under ui in media/audio folder under system...but when copied over to my rom nothing changes, so what file do I need to change to load them in my rom?
Thx!

Does anyone have any idea where to look?

You need to update audio_assets.xml in framework-res.apk to this:
Code:
<?xml version="1.0" encoding="utf-8"?>
<audio_assets version="1.0">
<group name="touch_sounds">
<asset id="FX_KEY_CLICK" file="pano_click.ogg" />
<asset id="FX_FOCUS_NAVIGATION_UP" file="pano_blip_alt.ogg" />
<asset id="FX_FOCUS_NAVIGATION_DOWN" file="pano_blip_alt.ogg" />
<asset id="FX_FOCUS_NAVIGATION_LEFT" file="pano_blip_alt.ogg" />
<asset id="FX_FOCUS_NAVIGATION_RIGHT" file="pano_blip_alt.ogg" />
<asset id="FX_KEYPRESS_STANDARD" file="KeypressStandard.ogg" />
<asset id="FX_KEYPRESS_SPACEBAR" file="KeypressSpacebar.ogg" />
<asset id="FX_KEYPRESS_DELETE" file="KeypressDelete.ogg" />
<asset id="FX_KEYPRESS_RETURN" file="KeypressReturn.ogg" />
<asset id="FX_KEYPRESS_INVALID" file="pano_error.ogg" />
</group>
</audio_assets>

Thx man....you are my savior.....love you!!!

update:
I used "Advanced_ApkTool_v4.2.0_By_BDFreak_2.2.1_2" to unpack...made the changes with notepad++, repacked and signed...flashed a zip file with twrp...but it get locked in bootloop...until i reflash the original file back in...glad i thought to make a backup...so now it`s back to normal...what gives?

When using apktool, you'll want to build with the -c option to carry over the signature from the original apk. Also, I'd use the -s option on decode so that it keeps the classes.dex intact. (No need to recompile those if you're just changing a resource.)

Thx so much...I don`t see where to enable those options....are they available on windows?
I just figured we`re talking about 2 different tools ...are you talking about this one?

{Guide} QXDM Port activation on Pixel 2 XL, (VoLTE,WoWIFI,CA)

Hi all.
First of all
I DO NOT PROVIDE ANY KIND OF SUPPORT. YOU ALONE RESPONSIBLE FOR ANY POSSIBLE ISSUES.
I wrote this post during my vacation. I know it could be quite handy, but unfortunately/thankfully my primary sources of money are completely aside from this findings.
I came to XDA from iOS jailbreak community and still believe that any findings have to be published if they allow to escape any kind of jail .
Sorry for any delays in my responses in PM and here, but i am really busy. In case somebody wants to share this info with other communities, feel free to do so.
Sorry for my EN
P.S.
all this small findings and adjustments would not be possible without @topjohnwu i have tried to rase a CR on github to enable a sub-function in Magisk for init.rc scripts injection through the existing magicg.rc but it was rejected. So any one who intrested in the same kind of projects please open an issue on Magis github page we really need *.rc injection as a part of Magisk module.
[/MENTION]
For the past couple of months I've been looking into finding the way to get an access to the Pixel 2 XL diag port.
As many of you know this feature is disabled by default on user builds. Thanks to @deeproot for his ROM. Because this is the only one userbuild ROM available right now with diag configuration. https://forum.xda-developers.com/pixel-2-xl/development/aosp-tamien-8-1-opengapps-t3727948
The only downside of this ROM is outdated version of the Android. To fix this unpleasant issue. I've took the init.taimen.diag.rc init script from the ROM and put it into the custom ROM. Later I have discovered couple of issues. First - dm-verity have to be disabled. Second - different ROMs dont play nice with instructions from init.taimen.diag.rc. (adb doesn't work properly).
With this being said I started to looking for a way to inject this instructions into Google Official ROM. Without touching the file system itself.
Unfortunately i haven't found the way make it via Magisk Modules. Because MagiskMount mount the module directory after init stage.
As many of you know Magisk injects init.magisk.rc into init.rc script. So ive decided to recompile the Magisk with the necessary init instructions. I simply updated init.magisk.rc with the following instructions. ( Thanks @topjohnwu for Magisk )
on property:sys.usb.config=diag,serial_cdev,rmnet_gsi,adb && property:sys.usb.configfs=1
start adbd
start port-bridge
on property:sys.usb.ffs.ready=1 && property:sys.usb.config=diag,serial_cdev,rmnet_gsi,adb && property:sys.usb.configfs=1
write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "Default composition"
rm /config/usb_gadget/g1/configs/b.1/f1
rm /config/usb_gadget/g1/configs/b.1/f2
rm /config/usb_gadget/g1/configs/b.1/f3
rm /config/usb_gadget/g1/configs/b.1/f4
rm /config/usb_gadget/g1/configs/b.1/f5
write /config/usb_gadget/g1/idVendor 0x05C6
write /config/usb_gadget/g1/idProduct 0x9091
write /config/usb_gadget/g1/os_desc/use 1
symlink /config/usb_gadget/g1/functions/diag.diag /config/usb_gadget/g1/configs/b.1/f1
symlink /config/usb_gadget/g1/functions/cser.dun.0 /config/usb_gadget/g1/configs/b.1/f2
symlink /config/usb_gadget/g1/functions/gsi.rmnet /config/usb_gadget/g1/configs/b.1/f3
symlink /config/usb_gadget/g1/functions/ffs.adb /config/usb_gadget/g1/configs/b.1/f4
write /config/usb_gadget/g1/UDC ${sys.usb.controller}
setprop sys.usb.state ${sys.usb.config}
as a result I was able to open diag port when the following properties are set.
setprop property:sys.usb.configfs 1
sys.usb.config diag,serial_cdev,rmnet_gsi,adb
There are two files attached.
1) Magisk-v18-Taimen-Diag.zip - Modified version of the Magisk. I strongly recommend to install the original version when you finish to play with QXDM. Because I am not a SW developer at all. From the Word "COMPLETELY"
2) Pixel 2 Diag Port.zip - Module for Magisk to properly enable the Diag port on boot via
PHP:
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
When you flash the Magisk via twrp and install the module you should be able to get an access to the diag port
{
"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"
}
To activate VoLTE on you phone you have to install VoEnabler module and upload proper mcfg_sw.mbn for your MNO.
ive tested Russian MNOs on my phone using Nokia 8 mbn. Works fine for me.
3)Open PDC tool -> Load -> Choose proper MBN -> SetSelectedConfig -> Sub0 -> Activate.
About VoEnabler and other OS methods.
There are actually two methods to get VoLTE\VoWiFI on the phone from OS point of view (VoLTE and VoWiFI provisioned) in *#*#4636#*#* Phone info -> IMS Status.
1) install VoEnabler it performs setprop for Vo*** related parameters.
2)modify /data/user_de/0/com.android.phone/files/carrierconfig-com.android.carrierconfig-XXXXXXXXXXX.xml .
Parameters for xml file you can get from https://developer.android.com/reference/android/telephony/CarrierConfigManager
for example
PHP:
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="carrier_wfc_supports_wifi_only_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
I use several SIM cards so for me it is more comfortable to use second method because this files configure phone module with different settings and it is easier to troubleshoot the issues
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<carrier_config>
<package_version>2</package_version>
<bundle_data>
<string name="_carrier_settings_version_string">25099-3000000346</string>
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="carrier_wfc_supports_wifi_only_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
<boolean name="display_hd_audio_property_bool" value="true" />
<boolean name="editable_enhanced_4g_lte_bool" value="true" />
<boolean name="hide_ims_apn_bool" value="false" />
<boolean name="remove_modify_call_capability" value="false" />
<boolean name="transmit_static_image" value="false" />
<boolean name="support_video_conference_call_bool" value="true" />
<boolean name="emergency_sms_support_bool" value="false" />
<boolean name="vowifi_call_quality" value="false" />
<boolean name="show_apn_setting_cdma_bool" value="true" />
<boolean name="carrier_rtt_downgrade_supported" value="false" />
<boolean name="allow_video_call_in_low_battery" value="true" />
<boolean name="world_phone_bool" value="true" />
<boolean name="carrier_rtt_upgrade_supported" value="false" />
<boolean name="hide_preferred_network_type_bool" value="false" />
<boolean name="show_static_image_ui" value="false" />
<boolean name="show_video_quality_ui" value="false" />
<boolean name="show_video_quality_toast" value="true" />
<string-array name="ratchet_rat_families" num="3">
<item value="1,2" />
<item value="7,8,12" />
<item value="3,11,9,10,15" />
</string-array>
<boolean name="apn_expand_bool" value="true" />
<boolean name="allow_adding_apns_bool" value="true" />
<boolean name="carrier_rtt_auto_upgrade" value="false" />
<boolean name="config_carrier_cs_retry_available" value="false" />
<boolean name="video_call_use_ext" value="true" />
<boolean name="show_cdma_choices_bool" value="true" />
<boolean name="carrier_rtt_supported_on_vtcalls" value="false" />
<boolean name="show_data_usage_toast" value="true" />
<boolean name="use_custom_video_ui" value="false" />
<boolean name="carrier_allow_deflect_ims_call_bool" value="false" />
<boolean name="config_hide_preview_in_vt_confcall" value="false" />
<boolean name="config_enable_display_14digit_imei" value="false" />
<boolean name="carrier_rtt_supported" value="false" />
<boolean name="show_call_session_event_toast" value="true" />
<string name="config_ims_package_override_string" value="com.google.android.ims" />
<string name="default_sim_call_manager_string" value="com.google.android.ims" />
</bundle_data>
</carrier_config>
Update 23/03/2019
Thanks to @topjohnwu work on Android Q i've updated the Magisk.zip with diag scripts enabled. Magisk-v18.2-f5f7fd91_Taimen_Diag.zip
The same approach the same steps.
That is true that Magisk module is not required, just disable enforcement and change the sys.usb.config settings.
Just be sure you are using correct drivers.
VoEnabler needs to be updated, not sure whether is works or not. VoLTE provisioning is disabled under "Phone Info"
I was able to open Phone Info app only through the "QuikShortcutMaker" app.
Because i modified /data/user_de/0/com.android.phone/files/carrierconfig-com.android.carrierconfig as well i am not sure what exactly activate the VoLTE. VoEnabler, or the file modification.
Also because TWRP was not able to decrypt the storage in my Phone i uploaded Magisk.zip to /tmp/ directory on my phone.
+ i installed the modified version of the Magisk on top of original canary build. Don;t know whether it important or not.
Update 14/04/2019
Android Q Beta 2 Magisk 19 attached.
Magisk-v19.0_Taimen_Diag
Magisk-uninstaller-20190413
Update 09/05/2019
I have forked Magisk repo. Now OTA updates should work for Taimen_Diag mod.
Testet on Android Q beta 3
App
https://github.com/AGagarin/magisk_files/blob/master/canary_builds/app-debug.apk
Zip
https://github.com/AGagarin/magisk_files/blob/master/canary_builds/magisk-debug.zip
For Drivers search for QUD.WIN.1.1 Installer-10037.3 Setup
For CA https://mt-tech.fi/en/modify-sony-xz-xzs-xz-premium-xz1-and-xz2-lte-a-band-combos/
For more information about PDC tool and mbn files https://forum.xda-developers.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542
Command line tool to read\write EFS settings https://github.com/JohnBel/EfsTools

Confirmed by @pokkaf for Swisscom network (Switzerland) - https://forum.xda-developers.com/showpost.php?p=78592698&postcount=9

Airpil said:
Reserved
Click to expand...
Click to collapse
so this basically enables VOLTE on any carrier, regardless if the carrier supports device or not?? i am currently on cricket, and VOLTE works only on cricket phones and iphones, but not on any other phone even if they are capable of it....

i42o said:
so this basically enables VOLTE on any carrier, regardless if the carrier supports device or not?? i am currently on cricket, and VOLTE works only on cricket phones and iphones, but not on any other phone even if they are capable of it....
Click to expand...
Click to collapse
It allows you to control Qualcomm Chipset. And yes basically you can enable VoLTE you can try different MBN files. Or modify NV items directly via QXDM or EFStool.
Cricket - it is an ATT so you can try to apply mbn file for ATT from the Noki8 folder. Or chose existing ATT profile form the phone. Also there is a profile for Cricket in Pixel3 ROM. Pixel 3 has a different CPU but it might work.

If this method works on Walleye or only on Taimen?

jwchen119 said:
If this method works on Walleye or only on Taimen?
Click to expand...
Click to collapse
Ive tested this method on my Pixel 2 XL. But the changes ive done is quite minor (important but minor) init commands are standard.
So i wouldn't be surprised if it works on Pixel 2 as well.

Hey, just a quick question. I am from India.Currently, volte on works on jio network for pixel devices in india.
Google has still not enabled volte for major providers like airtel/ vodafone even on the latest pixels.
All major phones in india including Oneplus support volte on airtel/vodafone. Will this method work to enable volte ? Also, what are the risk factors ?

coolsid8 said:
Hey, just a quick question. I am from India.Currently, volte on works on jio network for pixel devices in india.
Google has still not enabled volte for major providers like airtel/ vodafone even on the latest pixels.
All major phones in india including Oneplus support volte on airtel/vodafone. Will this method work to enable volte ? Also, what are the risk factors ?
Click to expand...
Click to collapse
there are several mbn for VDF India and Airtel in the Nokia zip attached. Usually MBN file has a vendor signature but Pixel 2 doesn't check the mbn signatures so you can try to apply MBN files from the archive or from any other phone with the same Snapdragon 835 CPU and Generation (MSM8998). Risks .. just notice the previous active MBN in PDC most probably it will be WildCard. If the MBN replacement will not work for you, you can select previous MBN at any time.

Thanks a lot. Helped me to get VoLTE and WiFi Calling working on my Pixel 2 XL on Swisscom network (Switzerland).
Though it was a bit tricky to get the diag mode enabled so that my computer would recognize the Qualcomm modem. After installation of patched Magisk and of the Magisk module zip (Diag port) I also had to execute the "setprop" commands via Terminal on the phone. Plus the Magisk VoEnabler module needs to be active constantly for it to work after adding the mbn via the PDC tool.

Anyone try this in pixel 3?

pokkaf said:
Thanks a lot. Helped me to get VoLTE and WiFi Calling working on my Pixel 2 XL on Swisscom network (Switzerland).
Though it was a bit tricky to get the diag mode enabled so that my computer would recognize the Qualcomm modem. After installation of patched Magisk and of the Magisk module zip (Diag port) I also had to execute the "setprop" commands via Terminal on the phone. Plus the Magisk VoEnabler module needs to be active constantly for it to work after adding the mbn via the PDC tool.
Click to expand...
Click to collapse
Hey , sorry to bug ya again. I have voLTE by default via my carrier. What did you have to do to get wifi calling? Just upload an mbn file?

WiFi calling was enabled when I installed the mbn file from the Nokia 8 (see other thread). I suppose if your carrier supports WiFi calling with the Nokia 8, then it should work with the Pixel if you install the the Nokia's mbn file.

Will it work on one plus one???

pokkaf said:
WiFi calling was enabled when I installed the mbn file from the Nokia 8 (see other thread). I suppose if your carrier supports WiFi calling with the Nokia 8, then it should work with the Pixel if you install the the Nokia's mbn file.
Click to expand...
Click to collapse
Thanks. And you used which program? I've messed with qxdm before but not the other one mentioned.
Also , why not flash a debugging vendor in the future ? Allows access to ports and is safer than the magisk method.

Honestly, I can write all of that here but you could just as well read everything in the other thread. The program was the PDC tool which comes with the whole Qualcomm package.
And for the vendor image.... I don't know. If it's safer to use that, why not try it this way.

Xdevillived666 said:
Thanks. And you used which program? I've messed with qxdm before but not the other one mentioned.
Also , why not flash a debugging vendor in the future ? Allows access to ports and is safer than the magisk method.
Click to expand...
Click to collapse
Advanced PDC Tool to swap the mbn file.
Debugging vendor image cause th dm-verity failure and bootloop. Also there are no PDC\QXDM settings in Debugging image. to support Diag mode we have to have an access to the rmnet usb function.
https://android.googlesource.com/de...eo-m2-release/init.hardware.diag.rc.userdebug
VS
https://android.googlesource.com/device/google/wahoo/+/master/init.hardware.diag.rc.userdebug

pankspoo said:
Will it work on one plus one???
Click to expand...
Click to collapse
For one +1 you can use this guide to get an access to the QXDM
https://forum.xda-developers.com/oneplus-one/general/guide-unlock-aditional-bands-qualcomm-t2877031
for PDC you need to activate rmnet usb function so you may want to try this one
https://forum.xda-developers.com/showpost.php?p=77783004&postcount=3
also OnePlus 5 has the hidden menu. It might work for One+One as well
*#800# --> oneplus Logkit --> Function Switch --> enable VoLTE + VoWifi switch
*#801# ->> Activate Serial & l Full-port switch

pokkaf said:
Thanks a lot. Helped me to get VoLTE and WiFi Calling working on my Pixel 2 XL on Swisscom network (Switzerland).
Though it was a bit tricky to get the diag mode enabled so that my computer would recognize the Qualcomm modem. After installation of patched Magisk and of the Magisk module zip (Diag port) I also had to execute the "setprop" commands via Terminal on the phone. Plus the Magisk VoEnabler module needs to be active constantly for it to work after adding the mbn via the PDC tool.
Click to expand...
Click to collapse
can u pm link for pdc tool? I have qpst and qxdm but I cannot find pdc

Windows start menu > QPST > PDC tool

I will try again tomorrow but using your magisk and module on pixel 3 running du unofficial allowed diagnostic but could not do anything. Will take a look using stock rom and try again