Basically, vivo has restricted some of its bloatware from being disabled/uninstalled via the adb method. The link mentioned above mentions an alternate way to uninstall bloatware via adb.
The function is:
adb shell service call package 134 s16 com.vivo.hiboard i32 0 i32 0
The author mentions he gets "134" by decompiling the /system/framework/framework.jar file:
To get the command number for your phone, you need to decompile the
/system/framework/framework.jar
JAR file and open the IPackageManager.java file
On the phone, I was able to do this by installing the Termux console emulator, installed and updated Archlinux in it, then installed java there (
pacman -S jdk-openjdk
). I downloaded the dex2jar archive , put it in the Termux folder along with framework.jar, and then I got an intermediate fw file
sh d2j-dex2jar.sh -f -o fw framework.jar*
I threw it on the site http://www.javadecompilers.com/ and there I already got the necessary code. (The phone does not have enough memory).
Since, I'm not a technical android person, and this JAR file varies with brand and android version, and thus the number is different for such variations, can someone explain step by step how can one arrive at a number from his unrooted framwork.jar file in /system/framework/framework.jar