Hey guys, I finally made it with the rooting of the Galaxy S4 Mini Dual Sim variant (GT-I9192 model / SerranoDS)
Use the files attached and the procedure below to achieve root on your device.
Code:
This process and the files in this post will void your warranty.
You are responsible for your actions.
Using these modifications might render your device unusable.
Only proceed if you are comfortable with this fact.
WARNING: Do not use this procedure for any other device than the GT-I9192 (the dual sim model)!!!
This rooted kernel is for the XXUAMF7 stock ROM and it may or may not work correctly with other stock versions.
This root/recovery was only tested on EURO / AFRICA models of the I9192. Other regions may not be compatible.
Onto the procedure:
Download and extract the kernel, recovery & ODIN flashing utility "ROOT_I9192_CWM6_Kernel.zip" and save it to your computer from here. The recovery image was initially created by arco68 (thanks and credits go to him for the recovery!)
Download and copy the "GT-I9192-RootKit-v2.zip" to your device SD card, from here.
Turn off the phone.
Press and hold home, volume down and power. Download screen should appear.
Connect USB cable, and press volume up.
Start Odin, make sure "F. Reset Time" is not checked, and then click PDA button to select the recovery image.
Select "ROOT_I9192_CWM6_Kernel.tar" file, and press Start button. The phone will reboot when finished flashing a new kernel and recovery.
Reboot into recovery mode and select the option to install the ZIP file you have previously copied to your device and begin flashing it.
After flashing using CWM, reboot into system and enjoy your rooted device.
Root procedure functionality:
Code:
- Root access (obviously)
- Insecure boot process (early adb/logcat, QtAdb support, adb root support)
- Insecure kernel (disabled Samsung setuid prevention mechanisms - credits go to arco68!)
Note: After rooting you will get notifications about applications doing not permitted actions. This is a good thing, meaning that Samsung has properly implemented the security features of this device, features that we are trying to defeat. To get rid of this notification freeze/disable or remove the following three packages:
Code:
- KNOXAgent.apk
- KNOXStore.apk
- ContainerAgent.apk
That's it, you warranty is now void! Have fun with your device! And keep those thanks coming to show your support for the device development.
Cheers,
C.
Known Issues
The prompt for root access does not appear. This is a problem with the Superuser.apk and can be fixed by installing SuperSU by Chainfire instead. Install the updated binary and remove Superuser when requested.
Wi-Fi doesn't work after installation. Flash the XXUAMF7 stock ROM version before applying this root package or an equivalent ROM from your region.
great work I'll try it when I get at my office
UPDATE 2
Lost wifi! Im running this firmware version
Ap: i9192UBUAMF9
CP: i9192UBUAMF9
CSC i9192UUBAMF9
UPDATE! 1
What i had to do to get it working,
1.- Flash recovery through odin with "F. Reset Time and auto reboot unchecked,
2.- manually force reboot into recovery FROM odin mode
3.- profit!
edit: Didnt work for me :/ i still boot to normal recovery
Didn't work for me
Uploaded with ImageShack.us
{
"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"
}
fburgos said:
Didn't work for me
Click to expand...
Click to collapse
follow my instructions and it will , when the system boots before rooting it automatically removes the modified recovery so you have to jump directly from odin to recovery mode in order to be able to root
davioxx said:
follow my instructions and it will , when the system boots before rooting it automatically removes the modified recovery so you have to jump directly from odin to recovery mode in order to be able to root
Click to expand...
Click to collapse
now my recovery looks like this, does it mean my binary count has increased? Can I get official updates with kies
I posted another version of the recovery zip in the first post, with MD5 hash added to it so you don't flash any corrupt files. Let me know if it works fine with this version.
EDIT: you must enter recovery after the phone resets. If you don't, it might not work (though, it worked for me with full reboot).
@davioxx: thanks for feedback and info
Cheers,
C.
davioxx said:
follow my instructions and it will , when the system boots before rooting it automatically removes the modified recovery so you have to jump directly from odin to recovery mode in order to be able to root
Click to expand...
Click to collapse
cheatman said:
I posted another version of the recovery zip in the first post, with MD5 hash added to it so you don't flash any corrupt files. Let me know if it works fine with this version.
EDIT: you must enter recovery after the phone resets. If you don't, it might not work (though, it worked for me with full reboot).
@davioxx: thanks for feedback and info
Cheers,
C.
Click to expand...
Click to collapse
davioxx, solution works fine
cheatman said:
I posted another version of the recovery zip in the first post, with MD5 hash added to it so you don't flash any corrupt files. Let me know if it works fine with this version.
EDIT: you must enter recovery after the phone resets. If you don't, it might not work (though, it worked for me with full reboot).
@davioxx: thanks for feedback and info
Cheers,
C.
Click to expand...
Click to collapse
Still No wifi :/
I can test anything if you like I have had this device for a little bit more than a month and was waiting for root
davioxx said:
Still No wifi :/
I can test anything if you like I have had this device for a little bit more than a month and was waiting for root
Click to expand...
Click to collapse
same here, no wifi/wifihotspot,
i use a lot wifihotspot at home
can i remove all the bloatware and return and flash original kernel?
any one has the original kernel?
davioxx said:
Still No wifi :/
I can test anything if you like I have had this device for a little bit more than a month and was waiting for root
Click to expand...
Click to collapse
I don't really understand much when you say only "no wifi". Give me more details to work with. What you did, what the outcome was, what's your current stock ROM, region, variant etc.
@fburgos: I have attached the original stock kernel by Samsung to this post. You have to flash it with ODIN. Note that it is aslo from the XXUAMF7 stock ROM as the insecured one.
C.
davioxx said:
Still No wifi :/
I can test anything if you like I have had this device for a little bit more than a month and was waiting for root
Click to expand...
Click to collapse
cheatman said:
I don't really understand much when you say only "no wifi". Give me more details to work with. What you did, what the outcome was, what's your current stock ROM, region, variant etc.
@fburgos: I have attached the original stock kernel by Samsung to this post. You have to flash it with ODIN. Note that it is aslo from the XXUAMF7 stock ROM as the insecured one.
C.
Click to expand...
Click to collapse
im not shure how to logcat but heres the result
Code:
[ 07-18 16:29:42.772 767: 1155 E/WifiHW ]
##################### set firmware type 0 #####################
[ 07-18 16:29:42.772 767: 1155 D/WifiStateMachine ]
setWifiEnabled : WifiNative.setFwType(0)
[ 07-18 16:29:42.772 767: 813 D/WfdService ]
intent recieved android.net.wifi.WIFI_STATE_CHANGED
[ 07-18 16:29:42.802 767:12206 E/WifiHW ]
return of insmod : ret = -1, No such file or directory
[ 07-18 16:29:42.802 767:12206 E/WifiStateMachine ]
Failed to load driver!
[ 07-18 16:29:42.802 767: 767 I/LocationManagerService ]
remove 432f7680
[ 07-18 16:29:42.802 767: 767 D/LocationManagerService ]
provider request: gps ProviderRequest[OFF]
[ 07-18 16:29:42.822 767: 813 D/WfdService ]
intent recieved android.net.wifi.WIFI_STATE_CHANGED
[ 07-18 16:29:42.822 767: 968 E/WifiStateMachine ]
DriverFailedState
[ 07-18 16:29:42.822 767: 1110 D/GpsLocationProvider ]
setRequest ProviderRequest[OFF]
[ 07-18 16:29:42.832 2497: 2497 I/elm ]
MainReceiver.onReceive() : android.net.wifi.WIFI_STATE_CHANGED
[ 07-18 16:29:42.832 767: 1252 D/LocationManagerService ]
request 433d1828 passive Request[POWER_NONE passive fastest=0] from com.google.android.gms(10052)
[ 07-18 16:29:42.832 767: 1252 D/LocationManagerService ]
provider request: passive ProviderRequest[ON interval=0]
[ 07-18 16:29:42.842 2497: 2497 D/elm ]
MainReceiver.listeningToNetworkStateChanged( context, intent ).
[ 07-18 16:29:42.842 2497: 2497 D/elm ]
MDMBridge.getInstance()
[ 07-18 16:29:42.842 2497: 2497 D/elm ]
MDMBridge.getAllLicenseInfoFromSDK()
[ 07-18 16:29:42.842 2497: 2497 I/elm ]
MainReceiver.onReceive() END - - - - - : android.net.wifi.WIFI_STATE_CHANGED
[ 07-18 16:29:42.842 2497: 2497 D/elm ]
ElmAgentService : onStartCommand()
[ 07-18 16:29:42.842 2497: 2497 D/elm ]
ElmAgentService : onStartCommand() : intent is not null
[ 07-18 16:29:42.862 2497: 2497 I/elm ]
MainReceiver.onReceive() : android.net.wifi.WIFI_STATE_CHANGED
[ 07-18 16:29:42.862 2497: 2497 D/elm ]
MainReceiver.listeningToNetworkStateChanged( context, intent ).
[ 07-18 16:29:42.862 2497: 2497 D/elm ]
MDMBridge.getInstance()
[ 07-18 16:29:42.862 2497: 2497 D/elm ]
MDMBridge.getAllLicenseInfoFromSDK()
[ 07-18 16:29:42.862 2497: 2497 I/elm ]
MainReceiver.onReceive() END - - - - - : android.net.wifi.WIFI_STATE_CHANGED
[ 07-18 16:29:42.872 2497: 2497 D/elm ]
ElmAgentService : onStartCommand()
[ 07-18 16:29:42.872 2497: 2497 D/elm ]
ElmAgentService : onStartCommand() : intent is not null
[ 07-18 16:29:42.882 767: 1110 D/GpsLocationProvider ]
stopNavigating
[ 07-18 16:29:42.882 767: 1110 E/LocSvc_afw ]
I/Entering int loc_stop() line 499
[ 07-18 16:29:42.882 767: 1110 E/LocSvc_eng ]
I/===> int loc_eng_stop(loc_eng_data_s_type&) line 648
[ 07-18 16:29:42.882 767: 1290 E/LocSvc_eng ]
D/void loc_eng_deferred_action_thread(void*):1586] received msg_id = LOC_ENG_MSG_STOP_FIX context = 0x6f48a4e8
[ 07-18 16:29:42.882 767: 1290 E/LocSvc_eng ]
I/Entering int loc_eng_stop_handler(loc_eng_data_s_type&) line 675
[ 07-18 16:29:42.882 767: 1290 E/LocSvc_adapter ]
D/ virtual loc_api_adapter_err LocApiV02Adapter::stopFix():382]: stop called
[ 07-18 16:29:42.882 767: 1290 E/LocSvc_api_v02 ]
I/---> locClientSendReq line 2114 QMI_LOC_STOP_REQ_V02
[ 07-18 16:29:42.882 767: 1110 E/LocSvc_eng ]
D/gps_set_battery_flag, connect=0
[ 07-18 16:29:42.882 767: 1110 E/LocSvc_eng ]
E/gps_set_battery_flag() : file open error
[ 07-18 16:29:42.882 767: 1110 E/LocSvc_eng ]
I/Exiting int loc_eng_stop(loc_eng_data_s_type&) line 669 0
[ 07-18 16:29:42.882 767: 1110 E/LocSvc_afw ]
I/Exiting int loc_stop() line 520 0
[ 07-18 16:29:42.882 767: 1290 E/LocSvc_eng ]
I/Entering void loc_inform_gps_status(loc_eng_data_s_type&, GpsStatusValue) line 932
[ 07-18 16:29:42.882 767: 1290 E/LocSvc_eng ]
I/<=== status_cb line 941 GPS_STATUS_SESSION_END
i have this firmware:
cheatman said:
I don't really understand much when you say only "no wifi". Give me more details to work with. What you did, what the outcome was, what's your current stock ROM, region, variant etc.
@fburgos: I have attached the original stock kernel by Samsung to this post. You have to flash it with ODIN. Note that it is aslo from the XXUAMF7 stock ROM as the insecured one.
C.
Click to expand...
Click to collapse
Already posted it but no worries
Ap: i9192UBUAMF9
CP: i9192UBUAMF9
CSC i9192UUBAMF9
what i mean by no wifi is that after doing the whole procedure i lost my wifi it doesnt start, i push button and nothing happens,
Can you update the files for the version I have? Currently there are only like 3 different versions on ssmmobile I hope it's not a problem.
Thanks!
By the way do you know what would happen if I flash the stock boot image? Will I still be rooted as changes are done to system partition?
Ok, so judging by the screenshot I understand that:
1. You flashed the recovery image and the rebooted into the system.
2. Wireless stopped working.
In the screenshot it seems that you are not running the insecure kernel. So I'm ruling out any problem with the kernel. Also, judging by the error generated by wireless it seems it cannot load the kernel module for wireless functions. Can you also flash the insecure kernel (so you can gain root) and give me a listing of the following command:
Code:
ls -al /system/lib/modules
@davioxx: the system partition will still be rooted, but the kernel will prevent you from gaining root privileges (Error 13 preventing suid privileges). This is why an insecure kernel is required as well.
Cheers,
C.
Can I help you in any way to get this working for my version?
Yeah, provide me the output of the command I said in my previous post. It will help me understand if you have the wifi driver as a module or precompiled in your kernel.
Also, let me know if you have a I9192L (L stands for Latin America) variant or a EUR/Africa variant.
If you have a Latin America version, this kernel will most likely not work for you (separate sources must be built). I will look into it, but I can't test it on my phone and I can't promise anything.
PS: same principle applies to China and South West Asia (SWA) variants. You will need different kernels for everything to work fine.
Cheers,
C.
ima_debug_log.ko
wlan.ko
[email protected]:/system/lib/modules # ls -al
-rw-r--r-- root root 15344 2013-01-15 02:11 adsprpc.ko
-rw-r--r-- root root 8816 2013-01-15 02:11 ansi_cprng.ko
-rw-r--r-- root root 8640 2013-01-15 02:11 dma_test.ko
-rw-r--r-- root root 6172 2013-01-15 02:11 evbug.ko
-rw-r--r-- root root 77720 2013-01-15 02:11 exfat_core.ko
-rw-r--r-- root root 35756 2013-01-15 02:11 exfat_fs.ko
-rw-r--r-- root root 38196 2013-01-15 02:11 mcdrvmodule.ko
-rw-r--r-- root root 20704 2013-01-15 02:11 mckernelapi.ko
-rw-r--r-- root root 39584 2013-01-15 02:11 mmc_test.ko
-rw-r--r-- root root 9672 2013-01-15 02:11 msm-buspm-dev.ko
drwxr-xr-x root root 2013-01-15 02:11 prima
-rw-r--r-- root root 27944 2013-01-15 02:11 qce40.ko
-rw-r--r-- root root 27088 2013-01-15 02:11 qcedev.ko
-rw-r--r-- root root 48836 2013-01-15 02:11 qcrypto.ko
-rw-r--r-- root root 7568 2013-01-15 02:11 radio-iris-transport.ko
-rw-r--r-- root root 6188 2013-01-15 02:11 reset_modem.ko
-rw-r--r-- root root 3356 2013-01-15 02:11 scsi_wait_scan.ko
-rw-r--r-- root root 18096 2013-01-15 02:11 spidev.ko
-rw-r--r-- root root 23876 2013-01-15 02:11 test-iosched.ko
-rw-r--r-- root root 5632 2013-01-15 02:11 tima_debug_log.ko
lrwxrwxrwx root root 2012-12-31 22:53 wlan.ko -> /system/lib/modules/prima/prima_wlan.ko
---------- Post added at 03:27 AM ---------- Previous post was at 03:26 AM ----------
9192 version nothing special
Well, the output seems identical (specifically, the WIFI driver is there) so I have no idea why the driever is not properly loaded. Most probable cause is the base version (you have to flash XXUAMF7. Download and flash XXUAMF7 from samfirmware and then restart the rooting process.
Either that, or I can give you my system modules so you can try with them. There may be incompatibilities between the kernel build and the modules build and the module might not be loaded properly is the magic numbers are not correct.
So, if you have a standard I9192, flash XXUAMF7 stock on it and then root again. Let me know how it goes.
Cheers,
C.
Hello!
I have available device, vendor end kernel source for my device so I tried port Omnirom. I have never done this before or similar ports but I want to learn. I managed to do a working kernel and recovery but stuck with the ROM. It just stuck at the manufacturer logo not even the boot animation comes in. Of course no adb and no logcat. Managed to get the last kernel message from recovery: http://pastebin.com/wBshmx8J
Can someone help or give idea what did I done wrong?
Here is the device tree: https://github.com/Gaboros/android_device_vernee_thor_k506
I have managed to step forward, now I have adb on boot but I got this:
Code:
01-14 17:12:12.893 275 275 E libEGL : load_driver(/system/lib64/egl/libGLES_mali.so): dlopen failed: cannot locate symbol "__xlog_buf_printf" referenced by "/system/lib64/libdpframework.so"...
01-14 17:12:12.893 275 275 F libEGL : couldn't find an OpenGL ES implementation
--------- beginning of crash
01-14 17:12:12.893 275 275 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 275 (surfaceflinger)
The problem is "__xlog_buf_printf" in the "libmtk_symbols.so" which is compiled and installed in the ROM and also preloaded on boot. It's seems impossible to get this error after this but still can't get through it. Any idea please?
Gaboros said:
I have managed to step forward, now I have adb on boot but I got this:
Code:
01-14 17:12:12.893 275 275 E libEGL : load_driver(/system/lib64/egl/libGLES_mali.so): dlopen failed: cannot locate symbol "__xlog_buf_printf" referenced by "/system/lib64/libdpframework.so"...
01-14 17:12:12.893 275 275 F libEGL : couldn't find an OpenGL ES implementation
--------- beginning of crash
01-14 17:12:12.893 275 275 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 275 (surfaceflinger)
The problem is "__xlog_buf_printf" in the "libmtk_symbols.so" which is compiled and installed in the ROM and also preloaded on boot. It's seems impossible to get this error after this but still can't get through it. Any idea please?
Click to expand...
Click to collapse
Fixed it by patching liblog. If anyone interested in the fix: https://github.com/Gaboros/android_...mmit/44ac2f707c0a12af038f4a4911e8eca47f9a7aff
Hi guys
I am continuously experiencing libc errors in the logcat related to properties, e.g.
Code:
02-01 17:18:34.172 14601 14601 E libc : Access denied finding property "vendor.perf.gestureflingboost.enable"
02-01 17:18:34.182 14601 14601 E libc : Access denied finding property "vendor.perf.iop_v3.enable"
02-01 17:16:40.747 14601 14601 E libc : Access denied finding property "vendor.perf.iop_v3.enable.debug"
02-01 17:20:18.167 16326 16400 E libc : Access denied finding property "ro.serialno"
02-01 17:27:31.245 16816 16816 E libc : Access denied finding property "vendor.iop.enable_uxe"
These errors are continuously appearing in my logcat.
Could someone please check if you have this as well, do inside an adb shell:
Code:
> logcat | grep libc
thanks
libc errors also
I do have a libc errors but its not any that you have listed ->
libc: Access denied finding proptery "vendor.debug.egl.swapinterval"
Those logs are related to the perfd if I'm not mistaken, you can ignore it, it's not a problem.
PS: Don't touch the selinux.
I flashed a custom built ROM to a TB-8504F and it didn't go well. I was able to restore the majority of the partitions, but the WIFI doesn't work now. Everything else seems to work.
Is there a particular petition that I need to flash?
Attached are screenshots of the partitions on a stock tablet.
I think these logs are related:
Code:
01-08 17:48:26.818 2890 2890 E Sensors : sns_main.c(447):Timeout waiting for SMGR service. Exit sensors daemon!
01-08 17:48:26.819 2890 2890 W Sensors : sns_main.c(355):sns_main_exit called unlock daemon to exit
01-08 17:48:26.819 2890 2890 E Sensors : sns_main.c(561):Exiting! Err 0
01-08 17:48:26.848 2909 2909 W sensors.qcom: type=1400 audit(0.0:74): avc: denied { read write } for name="diag" dev="tmpfs" ino=717 scontext=u:r:sensors:s0 tcontext=u:object_r:diag_device:s0 tclass=chr_file permissive=0
01-08 17:48:26.858 2909 2909 E Diag_Lib: Diag_LSM_Init: Failed to open handle to diag driver, error = 13
01-08 17:48:26.858 2909 2909 W Sensors : sns_debug_main.c(442):Diag_LSM_Init failed: log packets and messages will not be available
01-08 17:48:26.861 2909 2911 E Sensors : sns_fsa_la.c(84):realpath failed for directory name2
01-08 17:48:26.861 2909 2911 E Sensors : sns_reg_la.c(289):Error creating registry file
01-08 17:48:26.861 2909 2911 W Sensors : sns_reg_mr.c(367):File init failed 5
drizzle123 said:
I flashed a custom built ROM to a TB-8504F and it didn't go well. I was able to restore the majority of the partitions, but the WIFI doesn't work now. Everything else seems to work.
Is there a particular petition that I need to flash?
Attached are screenshots of the partitions on a stock tablet.
I think these logs are related:
Click to expand...
Click to collapse
Use lenovo moto smart assistant to flash the stock firmware
skoar said:
Use lenovo moto smart assistant to flash the stock firmware
Click to expand...
Click to collapse
Will try this when I get to a PC - thank you!
Hi there,
I am looking to add PAN bluetooth service to my Fire 7", (9th). It is rooted. It is on FireOS 6.3.1.4 which is (afaik) based on Android 7.1.
The stock bluetooth process (packages/apps/Bluetooth) in FireOS seems to be missing the PAN service. I can see in the logs the following error:
BluetoothPan: Could not bind to Bluetooth Pan Service with Intent { act=android.bluetooth.IBluetoothPan }
Click to expand...
Click to collapse
I assume that the bluetooth stack and HAL are complete in FireOS and it is just a matter of replacing the bluetooth process with one that implements PAN service? Is there a way to verify that?
Has anyone attempted something like this? Where would I find sources for the Bluetooth process and info for it?
Thanks
gregd72002 said:
Hi there,
I am looking to add PAN bluetooth service to my Fire 7", (9th). It is rooted. It is on FireOS 6.3.1.4 which is (afaik) based on Android 7.1.
The stock bluetooth process (packages/apps/Bluetooth) in FireOS seems to be missing the PAN service. I can see in the logs the following error:
I assume that the bluetooth stack and HAL are complete in FireOS and it is just a matter of replacing the bluetooth process with one that implements PAN service? Is there a way to verify that?
Has anyone attempted something like this? Where would I find sources for the Bluetooth process and info for it?
Click to expand...
Click to collapse
I would not assume that. Amazon has a habit of leaving/stripping out core Android components that aren't used by FireOS. TTBOMK Amazon has not published source for the build of FireOS used on 9th gen devices.
Might reach out to @DragonFire1024. He's been through the framework a few times on older builds and may be able to share a few tips.
DB126 said:
I would not assume that. Amazon has a habit of leaving/stripping out core Android components that aren't used by FireOS. TTBOMK Amazon has not published source for the build of FireOS used on 9th gen devices.
Might reach out to @DragonFire1024. He's been through the framework a few times on older builds and may be able to share a few tips.
Click to expand...
Click to collapse
So I went ahead to just try it out. Compiled my new Bluetooth package but I'm struggling with permissions during install. I can get most of the permissions granted if I place the package in /system/priv-app/ but not these:
01-03 13:08:45.810 612 612 W PackageManager: Not granting permission android.permission.ACCESS_BLUETOOTH_SHARE to package com.android.bluetooth (protectionLevel=4098 flags=0x3048be45)
01-03 13:08:45.810 612 612 W PackageManager: Not granting permission android.permission.BLUETOOTH_MAP to package com.android.bluetooth (protectionLevel=2 flags=0x3048be45)
01-03 13:08:45.810 612 612 W PackageManager: Not granting permission android.permission.NET_ADMIN to package com.android.bluetooth (protectionLevel=2 flags=0x3048be45)
01-03 13:08:45.810 612 612 W PackageManager: Not granting permission android.permission.NET_TUNNELING to package com.android.bluetooth (protectionLevel=2 flags=0x3048be45)
01-03 13:08:45.810 612 612 W PackageManager: Not granting permission android.permission.INTERACT_ACROSS_USERS_FULL to package com.android.bluetooth (protectionLevel=4354 flags=0x3048be45)
01-03 13:08:45.811 612 612 W PackageManager: Not granting permission android.permission.BLUETOOTH_STACK to package com.android.bluetooth (protectionLevel=2 flags=0x3048be45)
Click to expand...
Click to collapse
Is there a way to bypass the checks?
gregd72002 said:
Is there a way to bypass the checks?
Click to expand...
Click to collapse
Well, it wouldn't be much of a permissions system if security checks could be easily bypassed. I'm sure there's a whacky hackaround but that's out of my wheelhouse.