Database Info

AdBlocking on Rooted Z5

Hi,
A while back I rooted my phone because I had had enough of missing out on xposed modules and had had enough with all the Ads!! When did Android become so riddled with adverts. (i know its not android itself before you say anything)
Anyway I managed to root my phone using the methods highlighted in the forum. I've got xposed working perfectly but I am still seeing averts in apps and on web pages. Correct me if I'm wrong but I should be able to hide these now. I've come from Galaxy S4 which I had rooted from day 1 so I never saw a single advert (in app or webpage) but now on my rooted Z5 I am still seeing a lot. Many apps (baconreader for example) have had the ads in there hidden but many still persist.
I've tried all the options I can see to be available to me
In no particular order and never installed at the same time incase they conflict.
- Adaway (this errors when applying the host file saying the copy failed)
- Adblock plus (app not browser)
- Adfree (this is what I used on my S4)
- MinMinGuard (tried different modes on this one and still no luck and no errors to speak of)
None of them error apart from AdAway.
Have any of you guys got a totally adfree experience on the Z5? If so how have you managed this?

I am using Adguard, it costs 8$ a year. That's almost free I think.

I just installed AdAway, the host file applied fine as far as I can tell (haven't rebooted).
Did you make sure you have a kernel that disables RIC, or disable it your self in a terminal emulator?
Sent from my E6683 using Tapatalk

Funkmasterchilla said:
I am using Adguard, it costs 8$ a year. That's almost free I think.
Click to expand...
Click to collapse
Thanks. I am aware of that option as it's what I was using before I rooted. (free version)
Not that $8 is a lot I don't see the point in paying for something when I can get a permanent solution for $0 so I'd like to know why the host method isn't working on my current setup.
Is there anybody with a rooted Z5 that has blocked all adverts using the host modification method?

TimDawg said:
Thanks. I am aware of that option as it's what I was using before I rooted. (free version)
Not that $8 is a lot I don't see the point in paying for something when I can get a permanent solution for $0 so I'd like to know why the host method isn't working on my current setup.
Is there anybody with a rooted Z5 that has blocked all adverts using the host modification method?
Click to expand...
Click to collapse
AdAway is working for me.
Like I said ensure you can remount /system as r/w.
Sent from my E6683 using Tapatalk

_Dennis_ said:
I just installed AdAway, the host file applied fine as far as I can tell (haven't rebooted).
Did you make sure you have a kernel that disables RIC, or disable it your self in a terminal emulator?
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
I used the kernel that is on the dirty root guide. I was meaning to use the AndroPlus on but didn't in the end. Flashing a new kernel doesn't affect any of the data on it does it?
If I can disable RIC via terminal could you advise me how please. I've had a quick google and can't find anything.
Cheers

TimDawg said:
I used the kernel that is on the dirty root guide. I was meaning to use the AndroPlus on but didn't in the end. Flashing a new kernel doesn't affect any of the data on it does it?
If I can disable RIC via terminal could you advise me how please. I've had a quick google and can't find anything.
Cheers
Click to expand...
Click to collapse
Thanks to @tobias.waldvogel for this. Use the following in a terminal emulator to disable RIC, will need to be done on reboot (you can make it a boot script if you know how.)
Code:
su
echo 0 >/sys/kernel/security/sony_ric/enable
mount - o remount, rw /system
Sent from my E6683 using Tapatalk

See MOAAB (mother of all ad block) in Android Development and Hacking. Costs 0 bucks and blocks hosts. That's the best if you are rooted bro

_Dennis_ said:
Thanks to @tobias.waldvogel for this. Use the following in a terminal emulator to disable RIC, will need to be done on reboot (you can make it a boot script if you know how.)
Code:
su
echo 0 >/sys/kernel/security/sony_ric/enable
mount - o remount, rw /system
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
I get an error saying no such directory. if i try to create it manually it fails...

TimDawg said:
I get an error saying no such directory. if i try to create it manually it fails...
Click to expand...
Click to collapse
It worked for mine....
You did it one line at a time? And approved super user for the terminal emulator?
Sent from my SM-T710 using Tapatalk

_Dennis_ said:
It worked for mine....
You did it one line at a time? And approved super user for the terminal emulator?
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
yep one line at a time.
It's almost like my phone isn't totally rooted. I can do a lot of things that require root. If it try to create any folder inside /sys it fails.

TimDawg said:
yep one line at a time.
It's almost like my phone isn't totally rooted. I can do a lot of things that require root. If it try to create any folder inside /sys it fails.
Click to expand...
Click to collapse
What super user app do you use? How was it installed?

_Dennis_ said:
What super user app do you use? How was it installed?
Click to expand...
Click to collapse
SuperSU and it was installed via ADB
I think I must have messed up the kernel install somehow.
I'm busy tomorrow and not risking anything tonight so I'll give a fresh kernel a go on Monday. Already looking at AndroPlus kernels and there are a lot of options now. Enforcing and Permissive. I'm sure a Google will let me know what the difference is though.

TimDawg said:
SuperSU and it was installed via ADB
I think I must have messed up the kernel install somehow.
I'm busy tomorrow and not risking anything tonight so I'll give a fresh kernel a go on Monday. Already looking at AndroPlus kernels and there are a lot of options now. Enforcing and Permissive. I'm sure a Google will let me know what the difference is though.
Click to expand...
Click to collapse
Probably your best bet. Sorry I couldn't be of any help.
Sent from my E6683 using Tapatalk

How did you rooted your z5?

luisfillipe said:
How did you rooted your z5?
Click to expand...
Click to collapse
I used the method for Z5 dual SIM posted in the dirty root thread in development section. There are other simpler methods for the regular Z5, again in development section. It requires bootloader unlocks for all of them and that causes you to lose some Sony DRM keys.
Sent from my SM-T710 using Tapatalk

I tried Adblock since i'm not rooted, but it occasionally drain battery in sleep mode so I removed it..

I've always used Lucky Patcher for that. It has hosts blocking as well as disabling google ad modules inside apps, making everything clean and bull$hit free.

Gotta say I was starting it get a be pissed off with how much more complicated it is to do root this phone than any other android phone I've tried to do in the past...
so I came to the assumption that I'm supposed to be booting into recovery and installing the zip through there like I used to do to install ROMs on my older android phones.
I've flashed a few AndroPlus kernels and no luck. One of them left me stuck in bootloop which I let go around roughly 10 times until I decided it was getting nowhere. I did eventually manage to get one installed without a bootloop.
I wanted to know what Kernel I was running so I installed 'Kernel Adiutor' which required BusyBox to be installed alongside it. I found I was unable to install BusyBox which I guess was caused by the same thing causing all my other issues.
I've tried going through this whole over complicated process again and I hit a problem was trying to execute these two lines:
Code:
adb shell mount /dev/block/platform/soc.0/by-name/system /system
adb shell mount /dev/block/platform/soc.0/by-name/userdata /data
I read through everything I could find again to see if I could work out what was going on. While looking for this I can across this line of code:
Code:
fastboot flash boot boot.img
which is to be run if you want to flash the kernel via adb. (you need to extract the zip provided by AndroPlus)
Once this line had been executed I booted up again and was able to install BusyBox which let me see which kernel I had which showed AndroPlus (v3 incase you're interested) so I then tried AdAway again.
BINGO
Only thing is on some websites, particularly xda there is still a gap showing where the Advert would be displayed if not blocked. This I can live with.
I can't beleive how much more complicated this phone is to root compared to my HTC Desire, Galaxy S2 & S4. All of them were plug phone in. Click a few times and the jobs done. Is there a reason this hasn't been done for the Z5?
Just want to say thanks to all that have tried to help.
Thanks to AndroPlus for his kernel which has sorted me out.
Not so much thanks to Sony as this whole process has put me off ever getting another Sony phone. Mainly the fact I've lost some functionality what with having to unlock the bootloader. Overall I'm happy though.
Cheers

Pre-Installing APKs on Nexus Player Oreo stock rom

This really should be asked in the dev forum, But my post count is not high enough or worthy!
I have several Nexus Players I plan on selling with the oreo update pre installed, There are 2 addl non playstore apps I need to include as part of the package.
I'm trying to avoid "profiling" the devices to add the 2 extra apps. I have flashed the oreo upgrade to all 8 of them.
I cannot push the apks without profiling to enable adb nor can I seem to find a good zip template to make use the bootloader recovery adb function.
I have tested a few and they all fail with footer and signature failures? I'm only left with a few ideas. Please comment if you can help with any of the options below or suggest a better one..
1. Find a proper update.zip template that works with nexus player..Oreo 8.0 or can bypass the check..
2. Can apps installed in a profiled device be preserved thru a reset method that would allow the device to startup with the first run screens re-instated? Remote setup, WiFi, User account.. Out of the box experience?
3. Can an APK or ZIP be copied to a location on the Nexus Player that would allow it to be installed on first run? (I seem to think Youtube does this)
4. Least popular... Modify the Oreo upgrade img to have the 2 apps pre installed? <--This option looks messy..
Any suggestions appreciated!! Thanks

I suppose #2 is possible if you install as a system app.
Sent from my KFFOWI using Tapatalk

rufy93 said:
I suppose #2 is possible if you install as a system app.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
After careful examination, #2 and #4 are really the same thing. Without root, I would have to mount the oreo system.img file in linux and add the 2 apks to root/system/app then repack the img file to re-burn the rom. Not exactly sure if that would be enough, I assume there is some checksum or signing in the image file to prevent guys like me from modifying it. Also what would happen after google hits it with an update? would these apps survive? Finding the answer to why the stock Oreo bootloader recovery adb fails to accept the typical update zip format will end up being the right solution.

If you wish to flash using the stock recovery, the update zip must be properly signed. This usually means by the oem private keys.
I haven't been following the modding scene for a long time, but I'm sure these are still inaccessible.
Sent from my KFFOWI using Tapatalk

[How To] Native tethering on Rooted Pixel 4 XL

Disclamer: use at your own risk. I take no responsibility for bricked devices, bootloops, etc..)
Updated for Pixel 4 XL from my Pixel 3 XL Thread
Like my 3 XL, I unlocked and rooted out of the box but have a grandfathered At&t Unlimited Data Plan. At&t has somehow figured out how to block tethering on a Google purchased and unlocked device. Did a little research, and tethering can be achieved using methods already available for other devices. This can be done entirely on the device. Confirmed to work with At&t grandfathered unlimited, haven't tested others.
Prerequisites:
Unlocked Bootloader and Root with Magisk(See the How-Tos here: https://forum.xda-developers.com/pixel-4-xl/how-to/root-pixel-4-xl-unlocked-google-store-t3989033)
Magisk Module MagiskHide Props Config (available directly through Magisk)
BusyBox Module Installed
Terminal editor of your choice installed on your device
Step one: Make sure you're up to date on the Prerequisites above.
Step two: Open terminal editor and grant SU access by typing
Code:
su
Step three: Open up the props config by typing
Code:
props
Step four: Select add/edit custom props by typing
Code:
4
, Select new custom prop by typing
Code:
n
Step five: type
Code:
net.tethering.noprovisioning
it will ask what you want to set it to, type
Code:
true
make sure this is all lower case it will then ask you to confirm with y and ask if you want to reboot, select y again
Step six: Open the terminal again and grant SU access
Step seven: type
Code:
settings put global tether_dun_required 0
and exit the terminal
Step eight: reboot
Step nine: test the hotspot and crack a beverage of your choice to celebrate
On my Pixel 3 XL, If I sideloaded an OTA and was just re-enabling this mod, Steps 6-8 should were not required. Quick update(note from my Pixel 3XL thread 4/17/19), just sideloaded the April OTA via ADB. That retained my bypass settings, and tethering works even after re-rooting with no other changes (not even build.prop). it would seem that unless you flash the factory image, you should retain these modifications (but not root, go figure)

That works! Thank you.

Quick update to this. Re-rooting after sideloading the OTA still retains the tethering settings as it did in the April update to the 3XL

An easier way to do this is to add
net.tethering.noprovisioning=true
To the very end of the build prop using any note editor with root access.
You of course still have to follow The process to root your phone first.

Will this obscure Tmo from knowing how much I tether vs use as regular data?

bbender716 said:
Will this obscure Tmo from knowing how much I tether vs use as regular data?
Click to expand...
Click to collapse
Not sure, do you use native tethering with T-Mo, or is it their app?

emulater tells me inaccessible or not found after SU step when entering props

miahdog said:
emulater tells me inaccessible or not found after SU step when entering props
Click to expand...
Click to collapse
Are you rooted?

There is a magisk module that works as well (same commands in magisk module format essentially).
https://forum.xda-developers.com/apps/magisk/magisk-tethering-enabler-t3937427

loonix said:
There is a magisk module that works as well (same commands in magisk module format essentially).
https://forum.xda-developers.com/apps/magisk/magisk-tethering-enabler-t3937427
Click to expand...
Click to collapse
This one won't unlock the throttles that the carrier does, about 60kBps which you can't even see a YouTube video without buffering.
On t-mobile, you can see the hotspot usage., in other hand .. Pdanet+ USB hides it and you can use the phone download speed. Which goes about 7MBps... Hopefully this trick fixes it.. It did with the 2xl.. Eager to try it now.
---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------
fredgar75 said:
An easier way to do this is to add
net.tethering.noprovisioning=true
To the very end of the build prop using any note editor with root access.
You of course still have to follow The process to root your phone first.
Click to expand...
Click to collapse
Pixel 4 xl partitions A/B won't allow you to do so.... Build.prop can't be written for some reason.

@Gloff thanks! It worked on my 4xl on at&t 0120 security update.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
miahdog said:
emulater tells me inaccessible or not found after SU step when entering props
Click to expand...
Click to collapse
I was getting the same message untill I flashed the magisk hide prop module. After that I was able to follow the guide.

Who-Lep said:
@Gloff thanks! It worked on my 4xl on at&t 0120 security update.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
I was getting the same message untill I flashed the magisk hide prop module. After that I was able to follow the guide.
Click to expand...
Click to collapse
Glad I could help!
Ah yes, magisk hide prop is in the prerequisites, that's the tool that works through the emulator to edit the build.prop and global settings

eloko said:
This one won't unlock the throttles that the carrier does, about 60kBps which you can't even see a YouTube video without buffering.
On t-mobile, you can see the hotspot usage., in other hand .. Pdanet+ USB hides it and you can use the phone download speed. Which goes about 7MBps... Hopefully this trick fixes it.. It did with the 2xl.. Eager to try it now.
---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------
Pixel 4 xl partitions A/B won't allow you to do so.... Build.prop can't be written for some reason.
Click to expand...
Click to collapse
That's not true.. Look at the scripts inside the magisk module
In post-fs-data.sh
Code:
# This script will be executed in post-fs-data mode
settings put global tether_dun_required 0
and in system.prop
Code:
# This file will be read by resetprop
# Example: Change dpi
# ro.sf.lcd_density=320
net.tethering.noprovisioning=true
Exact same commands as what you have in your OP.

loonix said:
There is a magisk module that works as well (same commands in magisk module format essentially).
https://forum.xda-developers.com/apps/magisk/magisk-tethering-enabler-t3937427
Click to expand...
Click to collapse
Thanks

this thing wont unlocked the throttle, hotspot is enable but cant get more thatn 1mbps download. using vpn hotspot gets me 12mbps. FYI

The service/throttling etc are carrier dependent. I just wanted to mention that a magisk module that achieves the same commands is available for those who prefer to enable/disable it within the magisk manager. What you posted is all good, just the command line equivalent.

Hey all,
Its been a few years since I've messed around with the tethering on Nexus/Pixel devices.
I have a question...
Is this supposed to hide tethering usage from carrier? I'm on TMo native tethering and the usage is showing up when I check in the TMo app.
Sorry if this is something simple, I just need to make sure I'm not missing something.
Side Note:
I'm getting 100Mb+ through native tethering and only about 10Mb with PDANet.
Thanks.

Just an FYI - working perfectly on my Verizon 4xl

TriniMike215 said:
Hey all,
Its been a few years since I've messed around with the tethering on Nexus/Pixel devices.
I have a question...
Is this supposed to hide tethering usage from carrier? I'm on TMo native tethering and the usage is showing up when I check in the TMo app.
Sorry if this is something simple, I just need to make sure I'm not missing something.
Side Note:
I'm getting 100Mb+ through native tethering and only about 10Mb with PDANet.
Thanks.
Click to expand...
Click to collapse
I do not know if this will block that. I used about 20gb last month solely through tethering and didn't hear a peep from att, even though the plan i'm on is not native tether friendly. If they know, they don't care.

dtroup64 said:
Just an FYI - working perfectly on my Verizon 4xl
Click to expand...
Click to collapse
What sort of speeds are you getting? Did you do the opening post method or the magisk one?

[GUIDE] Enabling LTE on China Telecom (and others) on Pixel 3 XL (Android 10)

Being a huge fan of the Pixel series and living in China is not easy. Just upgraded my XL to 3 XL and naturally I had to enable the LTE to work in China. Regardless what you may see on the Chinese forums (gfan), all the files you need are already present on the phone.
Files you need:
1) The ADB bridge for Windows
2) The most recent factory image
3) Magisk Manager
4) Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (Magisk Manager module) - Github direct: https://github.com/wangdaning/Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (big thank you to wangdaning for allowing me to publish it.) Also attached as a zip file to this post.
If you don't understand what these files are for or where to find them, perhaps you should ask a friend to help you. Flashing anything wrong could result in an expensive brick. Always backup your data, never blindly trust a post, and do your research. This post is in good faith and I am not liable for your actions.
Now, I don't have any of the variants of 3 (Pixel 3, 3a, 3a XL) but I would assume it would work in a similar fashion; however, see above and do your research. Check file structures, read some posts, backup data, etc. If someone does try it, please report both success and failure to build the knowledge.
1) We need to ensure our phone has an unlocked bootloader. If your bootloader is locked, you WILL lose all your data. Ensure you backup everything you want to keep. There is no getting around this step. We need to be a developer first. Go to Setting->About Phone->Build number (tap it until it says you are a developer). Then go to System-> Developer options -> OEM unlocking: turn it on. Next we need to reboot to the bootloader by resetting the phone and hold the down volume key as it reboots. In the bootloader, first use the volume keys to find and select the unlock the bootloader command with the power key. Then, we need to send the following command:
Code:
fastboot flashing unlock
You will receive a wipe and security warning. Accept and reboot the phone. It will wipe and reset your phone to factory.
2) I started from a stock image (May update; QQ2A.200501.001.B2). I suggest you start from there.
3) While we have the May update in front of us, we need to extract the boot.img so it can be patched to root the phone. TWRP doesn't support us at the time of writing on Android 10. (Hope that new baby is healthy!) The boot image can be found in the zip image-crosshatch-*release code*.zip/boot.img. Transfer this boot.img to the phone to be modded to enable root.
4) Next the phone needs to be rooted. You need to download the most recent version of Magisk Manager. Once installed, open up Magisk Manager. It will report no Magisk and that's ok, we are installing it now.
5) Tap install on Magisk and it will ask if you want to install, so install. Then you need to select the method. We will choose "Select and patch a file." Tell it where you saved your boot.img and it will patch it to allow us to root the phone. The output file we need is called magisk_patched.img is on the phone. Move it back to your directory with your ADB bridge.
6) Next we need to flash this patched boot file to our phone to complete the rooting process. Reboot to the bootloader and send the two commands:
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Reboot the phone and congrats, you are rooted with an unlocked bootloader.
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
8) Download the LTE_enabler from Github or the zip file here. Open Magisk Manager and open the menu -> Modules -> "Yellow Plus" to add. Point it to the zip file.
9) Reboot and enjoy using your phone as intended.
I tried to be as detailed as I could but not be over verbose either. If any step is unclear, there are more detailed guides on this forum concerning bootloader unlocking and Magisk rooting on Android 10. As a bonus tip, does the "x" showing no data bother you and stop some services from working? If so, this can be fixed by re-pointing your captive portal to something inside the firewall. This can be accomplished with one line of code:
Code:
adb shell "settings put global captive_portal_https_url https://developers.google.cn/generate_204"
Enjoy and if you have questions about Pixel and China, feel free to post them. Support right to repair!

I downloaded the zip file but it tells me it's not a module.

jifengSherry said:
I downloaded the zip file but it tells me it's not a module.
Click to expand...
Click to collapse
Could use more details, otherwise it is hard to help. It definitely is a module and installs fine. Something else is going on.

is this for china only? I have a Canadian 3 XL and moved to Bucharest, need to enable VOLTE on Orange Romania. I'm also on Android 11

It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?

wangdaning said:
It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?
Click to expand...
Click to collapse
I contacted Orange and they say VOLTE should be working, that the issue is my device not being compatible with their network. I also bought a Samsung watch 3 with LTE and can't activate LTE through my phone, i assume it's due to the same issue.
I'll follow your guide and report back.
Should be no issue if i am using Android 11 instead of 10 right?

Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
Click to expand...
Click to collapse
If that does not work then you need to modify the module to include the romania mbn.

wangdaning said:
Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
If that does not work then you need to modify the module to include the romania mbn.
Click to expand...
Click to collapse
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!

angeluszero said:
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!
Click to expand...
Click to collapse
ok i spoke too fast, while VOLTE is enabled now in the settings, when i make a call, it switches to H+ which means its not using VOLTE. any idea? I modified the .txt file to include the location of the romania .mbn file, i modified the file directly on the phone though, after installing the module with magisk manager

Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.

wangdaning said:
Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.
Click to expand...
Click to collapse
I did that, both VOLTE and Wifi calling say provisioned. I guess it might be something on Orange's end.
I saw a reddit post for a Pixel 3 having the same issue and the carrier ended up doing something on their side.

Confirmed working on Pixel 3 w/ Android 11!

Can this patch work on Pixel 4 as well? Thank you

duffercn said:
Can this patch work on Pixel 4 as well? Thank you
Click to expand...
Click to collapse
You would have to find the location of the files on the Pixel 4 as I am not sure where they are. Then modify the module to point to the correct location.

[Video][Tutorial] How to enable 5G for Unlisted Countries on Pixel 4a(5G) and Pixel 5 using QPST.

EDIT: I have moved on to the Pixel 7 and don't have the energy to push into this any more. If this doesn't work for you for any reason, I don't know how to help you, sorry.
--------------------------------------------------------------
This is a step by step video tutorial for those who find written guides difficult to follow.
Download links and CMD commands:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
QPST Tool v2.7.496 - QPST Tool
Download the official QPST Tool v2.7.496 which allows you to flash the stock firmware on your Qualcomm Smartphone and Tablets.
qpsttool.com
Downloads | Notepad++
notepad-plus-plus.org
adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog

@nsiti @elong7681

swangjang said:
@nsiti @elong7681
Click to expand...
Click to collapse
@swangjang you've done it once again! Lol thank you!

Thank you! Finally get to enjoy the full capabilities of my phone!

Thanks swanjang, very straightforward
I assume the phone does not have to be rooted for this?
Can similar approach be used to enable VoLTE & VoWIFI for un-supported carriers?

damkov said:
Thanks swanjang, very straightforward
I assume the phone does not have to be rooted for this?
Can similar approach be used to enable VoLTE & VoWIFI for un-supported carriers?
Click to expand...
Click to collapse
Your device must be rooted because abd shell calls for su (superuser).

swangjang said:
Your device must be rooted because abd shell calls for su (superuser).
Click to expand...
Click to collapse
thanks @swangjang for the youtube video, but is there anyway to do the same but without root?

xh4ni said:
thanks @swangjang for the youtube video, but is there anyway to do the same but without root?
Click to expand...
Click to collapse
It's not possible to do this without root. You need root to change some device settings to open a Diag Port, which is the bridge to the EFS Partition. This can only be done if you have root.

@swangjang I will attach all files from the policyman folder that I have from the March update, it includes carrierpolicy.xml

elong7681 said:
@swangjang I will attach all files from the policyman folder that I have from the March update, it includes carrierpolicy.xml
Click to expand...
Click to collapse
I think the March update changed how 'unlisted countries' sim cards load mbn. Your carrier is Verizon, right? therefore it will load the Verizon specific mbn which is why you have the carrier policy xml. But my carrier is not 'officially supported' therefore from March update, it loads the mbn without a carrier policy file maybe. Not too sure.

swangjang said:
I think the March update changed how 'unlisted countries' sim cards load mbn. Your carrier is Verizon, right? therefore it will load the Verizon specific mbn which is why you have the carrier policy xml. But my carrier is not 'officially supported' therefore from March update, it loads the mbn without a carrier policy file maybe. Not too sure.
Click to expand...
Click to collapse
Yes it is Verizon. That's bull**** if Google changed this so that people can't use their phones to it's fullest capabilities.

elong7681 said:
Yes it is Verizon. That's bull**** if Google changed this so that people can't use their phones to it's fullest capabilities.
Click to expand...
Click to collapse
Google is already limiting phone capabilities to US only. E.g "Call screening" and "Hold for me" is also US only feature. I can spoof my location with Market Unlocker to force enable it but this makes my phone think I have a Verizon sim card inserted which occasionally causes me to lose data connection (easy fix is to just make a phone call and hang up). Also, the March feature drop "Smart Compose" is also US only and I have no ****ing idea why. I understand it being English only and that's totally fair but limiting that to just the US is total bull****.
I was a long time samsung fan and switched over to Pixel 5 after hearing about all these advertised features, only to realise after I got it that these features are US only. Pixel 5 may be my first and last google phone, depending on how Google comes around and stop with all their bullshits.

Hi,
What are the commands to turn off diag mode off? or does this automatically disable when removing the USB, thank you.

rasseru16 said:
Hi,
What are the commands to turn off diag mode off? or does this automatically disable when removing the USB, thank you.
Click to expand...
Click to collapse
If I'm not mistaken it reverts back after a reboot and the phone is no longer recognized by QPST

elong7681 said:
If I'm not mistaken it reverts back after a reboot and the phone is no longer recognized by QPST
Click to expand...
Click to collapse
Ok thank you.

Thanks a lot for the video and instructions, however, I tried your method for CMHK (China Mobile Hong Kong) and it doesn't work.

galenfung said:
Thanks a lot for the video and instructions, however, I tried your method for CMHK (China Mobile Hong Kong) and it doesn't work.
Click to expand...
Click to collapse
China uses a different type of network technology than the global standard. This may be why it doesn't work for China.

Thank you so much , that was great & i have a pixel 5 with a 5G work because if this great thread

Hi, is the method works also to rooted CalyxOS or any other custom ROM? I'm thinking to move to CalyxOS, but want to keep VoLTE & VoWifi unlocked capablities and Gcam.

mxtuu222 said:
Hi, is the method works also to rooted CalyxOS or any other custom ROM? I'm thinking to move to CalyxOS, but want to keep VoLTE & VoWifi unlocked capablities and Gcam.
Click to expand...
Click to collapse
Hi, unfortunately I'm not sure if it will work on custom roms.