Database Users

[ROOT] <Generic topic about verified root exploit>

Sparkym3 released an automated tool for this, please see here http://forum.xda-developers.com/showpost.php?p=31730134&postcount=1
Please DO NOT donate to nor credit me me for this matter, this was not my find, we just tried an existing exploit on the device.
Dear bloggers, source this when copying:
http://www.androidpolice.com/2012/09/17/amazon-kindle-fire-hd-7-already-rooted-heres-how-to-do-it/
Amazon failed to fix the bug sparkym3 (http://forum.xda-developers.com/member.php?u=4411543) found in ICS, whoops.
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
unzip the zip, get su from /system/bin/ and Superuser.apk from /system/app/ and put them in your current directory
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk

SWEET!
jcase said:
Please DO NOT donate to nor credit me me for this matter, this was not my find, we just tried an existing exploit on the device.
Dear bloggers, source this when copying:
http://www.androidpolice.com/2012/09/17/amazon-kindle-fire-hd-7-already-rooted-heres-how-to-do-it/
Amazon failed to fix the bug sparkym3 (http://forum.xda-developers.com/member.php?u=4411543) found in ICS, whoops.
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
unzip the zip, get su from /system/bin/ and Superuser.apk from /system/app/ and put them in your current directory
adb shell
rm /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
Click to expand...
Click to collapse
This is really exciting news! Been hoping for some good news on this front! Just got my new Fire over the weekend. Looking forward to getting the play store working.
Was there a way with the old fires to block Amazon's automatic updates?

As always thanks for your work man!!

ThaPirato said:
As always thanks for your work man!!
Click to expand...
Click to collapse
Not my work, thank sparkym3. We just went testing older exploits before releasing a new one, and this worked.

Jcase , you love these kindles don't you. Thanks for helping us out
Sent from my Nexus 7 using Tapatalk 2

how do i get my kindle to be recognized when i type "adb shell" in the command line? I enabled adb in the security settings

stu5797 said:
how do i get my kindle to be recognized when i type "adb shell" in the command line? I enabled adb in the security settings
Click to expand...
Click to collapse
If you have the SDK installed and you get "error: device not found" you need to do the following steps. This worked for me.
Navigate to the [your user name]/.android folder. It is under C:\Users
Edit the adb_usb.ini file, adding the following line of code at the end:
0×1949
Close and save that file.
Now find the folder where your SDK is installed, and open the usb_driver folder. In that folder, find the file android_winusb.inf and add the following code to both the [Google.NTx86] and [Google.NTamd64] sections:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Reboot and then run adb shell again. It should recognize your device.

Jcase is the android locksmith. Just about every device I have seen he has atleast helped unlock. Now if a working recovery can get made, I can see my self getting one of these puppies down the road.
sent from my Nokia 5110 using t9

jcase said:
Please DO NOT donate to nor credit me me for this matter, this was not my find, we just tried an existing exploit on the device.
Dear bloggers, source this when copying:
http://www.androidpolice.com/2012/09/17/amazon-kindle-fire-hd-7-already-rooted-heres-how-to-do-it/
Amazon failed to fix the bug sparkym3 (http://forum.xda-developers.com/member.php?u=4411543) found in ICS, whoops.
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
unzip the zip, get su from /system/bin/ and Superuser.apk from /system/app/ and put them in your current directory
adb shell
rm /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
Click to expand...
Click to collapse
Thanks for your sharing!
Thanks Cameron Summerson!

Awesome work guys, especially for jcase and sparkym3...

Qemu automated root problem
Kindle Fire HD 7.2.1 using the Qemu auto - thing keeps stalling at step 3 "looking for access"
The filename, directory name, or volume label syntax is incorrect.
It's leaving me an unstable device that requires a factory reset to operate. Any insight would be appreciated.

BELASCO said:
Kindle Fire HD 7.2.1 using the Qemu auto - thing keeps stalling at step 3 "looking for access"
The filename, directory name, or volume label syntax is incorrect.
It's leaving me an unstable device that requires a factory reset to operate. Any insight would be appreciated.
Click to expand...
Click to collapse
Mine did the same, simply ignore it..
CTRL c
to stop
restart the script and start with step 4 --> it will stall again but will work..
Scsi

scs1man said:
Mine did the same, simply ignore it..
CTRL c
to stop
restart the script and start with step 4 --> it will stall again but will work..
Scsi
Click to expand...
Click to collapse
Happily rooted and hunting through Gplay.

Root works great with KFHD7 (firmware 7.2.1)

someonhe has sucessfuly rooted a 7.2.2 version?

7.2.2
So my system updated to 7.2.2 - darn!
So what's the current status...
- Google Chrome, Play store and frameworks still present - and working.
- ES Explorer is not able to enable Root Explorer, so root obviously shorted.
- The Superuser app remains, but is useless without the 'su' file.
- GoLauncher was completely removed.
- The Qemu exploit is not working. Gives error on cmd line: echo 'ro.kernel.qemu=1' > /data/local.prop
Hope everyone still on 7.2.1 puts up their firewalls. And :angel: praying that our developer legends work something out on what Amazon did to lock 7.2.2.

Also, an additional warning about the 7.2.2 update... I don't know if this happened to anyone else, but I had the Swype Beta installed on my rooted KFHD. The new update also came with Swype, and for some reason, instead of overwriting mine, there's this bizarre conflict with the two. When attempting to type, Swype tells me have an incorrect license, and refuses to work and tells me to redownload the beta. On top of that, attempts at removal or reinstallation are impossible since I no longer have root (Swype is in the system/apps directory).
Just about everything else works (minus apps needing root), including Nova Launcher Prime. I still can't type though. Yay Amazon.

I had Swype too, but I used nook tools to choose the Amazon keyboard and it works fine.
Sent from my KFTT using Tapatalk 2

VbSin said:
So my system updated to 7.2.2 - darn!
- GoLauncher was completely removed.
Click to expand...
Click to collapse
That's interesting. I had ADWLauncher before the update and it stayed. I've lost my desktop layout, I can't bind it to the home button and I can't add widgets but otherwise it works OK.

No root yet for 7.2.2
maxx1985 said:
someonhe has sucessfuly rooted a 7.2.2 version?
Click to expand...
Click to collapse
I tried and tried, but no success. With the automatic procedure I get always the same error ( screenshot attached) and it sends me to NOROOT-
Going to try the cmd one, let's hope!

Trouble with activation of voice service after root

Ok, I'm about at my wit's end on this. I'm trying to get Marshmallow with root access activated. I flash the firmware, activate it, verify everything works (i.e. voice calls), root it, then I'm unable to get voice calling back. LTE usually goes as well, but that's easy enough to fix. I've tried "Activate Phone" under Settings, and ##72786# with the dialer over 10 times on many installs without success. Doing a /data reset after root results in the initial setup going through, but no voice service. Importing build.prop from before rooting generally restores LTE but not voice.
Here's my general method:
Use Odin to flash a firmware, having tried with every firmware below. Some are rejected by the bootloader, I suppose attempting Nouget was ill-advised in retrospect, but most work fine:
Code:
07/09/2017 02:35 AM 2,339,073,264 G935PVPS4APK1_SPT4APK1_SPR_Sprint_USA_6.0
.1.zip
07/08/2017 05:23 PM 2,338,378,352 G935PVPU2APH7_G935PSPT2APH7_SPR.zip
07/08/2017 05:44 PM 2,415,317,465 G935PVPU4APL6_G935PSPT4APL6_SPR.zip
07/04/2017 06:02 AM 2,346,196,486 G935UUEU4API3_G935UOYM4API3_TMK.zip
06/29/2017 07:09 PM 2,393,582,382 SPR-G935UUES4AQC1-20170313090738.zip
07/04/2017 09:56 PM 2,333,204,698 SPR-G935UUEU2APEH-20160518091232.zip
07/05/2017 07:12 AM 2,332,915,504 SPR-G935UUEU2APG9-20160823142730.zip
07/05/2017 12:52 PM 2,346,196,486 SPR-G935UUEU4API3-20160909113048.zip
This activates on its own without any trouble. Sometimes I update the Profile/PRL, sometimes not.
Then I install Package Disabler and disable at minimum securitylogagent, but generally anything mentioned by any root guide and anything that looks squirrely to me.
Use Odin to flash g935a.tar
Use root.bat (I've modified it slightly over the various attempts. Mostly because someone put a reboot command in the middle of the script which introduced a race condition to finish the script before the system halted, with unpredictable results.)
Code:
adb wait-for-device
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount rootfs /
adb push SuperSU-v2.74-2.img /data/su.img
adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh
adb install -r SuperSU-v2.74-2.apk
adb shell pm hide com.LocalFota
adb shell pm hide com.samsung.android.intelligenceservice
adb shell pm hide com.samsung.android.securitylogagent
adb shell pm hide com.samsung.sdm
adb shell pm hide com.samsung.syncservice
adb shell pm hide com.sec.android.diagmonagent
adb shell pm hide com.sec.android.fotaclient
adb shell pm hide com.sec.android.fwupgrade
adb shell pm hide com.sec.fwservice
adb shell pm hide com.ws.dm
adb shell pm hide com.wssyncmldm
adb shell < supersu.cmds
Code:
touch /system/xbin/su
chmod 0755 /system/xbin/su
chcon u:object_r:system_file:s0 /system/xbin/su
chmod 0700 /system/etc/launch_daemonsu.sh
chcon u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh
if [ `cat /system/etc/init.sec.boot.sh | grep daemonsu >/dev/null 2>&1; echo $?` -ne 0 ]; then
echo '/system/etc/launch_daemonsu.sh' >> /system/etc/init.sec.boot.sh
fi
sync
reboot
Then root works, I switch the CPU governor and modify the three lines of build.prop (or reinstate the pre-root version), and disable securestorage in build.prop as well (wifi password persistence fix). Maybe install xposed if I feel like wasting my time, although it does work perfectly. Upon a reboot LTE generally works, if not I update the APN settings on the older firmwares. Then I try activation, which fixes it if APN settings are disabled. But no voice. After a few attempts I'll reenable everything and try again (+/- a reboot), but it doesn't make a difference.
Any ideas? I seem to be having an unusual amount of trouble with this and I'm not sure why...

Having this exact problem. Dont know what to do
Edit:
Got myself back to stock with help from this thread
https://forum.xda-developers.com/showpost.php?p=76029292&postcount=12
look for the binary 5 google docs links in there if you just want to get back to stock and get text and voice working again

Intel (Joying) Android 6.0.1 and Bluetooth

Hi,
I hope this is a thread that will soon be completely unnecessary.
Disclaimer: I have hardly any knowledge of bluetooth. I don't use it much either. I use WiFi tethering, I hardly ever call in my car (it is considered too dangerous and I agree), I have my music on SDcard.
So the reason for this post is not because I want "to tell" about bluetooth. The only reason is that multiple users sent me PMs asking questions about it.
To have it not too cluttered, and without the real bluetooth experts being able to give their valuable opinion in the forum, I created this post.
I downloaded a Cyanogenmod CM-13 6.0.1 (beta) ROM for the Asus Zenfone, and I downloaded the official 6.0.1 Asus ROM for the Zenfone.
The Asus Zenfone has an Intel(R) atom Z3560 CPU.
Our Joying has a Sofia x64 from the C3200 series, so there is a difference but programmaticaly they are the same. I can't find specifics on the used bluetooth chip set and of course the underlying MCU, in case of the Joying, is totally different.
So for those users who asked me and are brave enough to try for themselves I created two zips containing all necessary files AFAIK.
The CM13 file is of course the Cyanogenmod, the UL-Z00 is the official Asus one. The real system "stuff" in the Cyanogenmod is in general more a "fits all possible x86 architectures" build whereas brand specific ROMS are of course more tuned to the specific hardware.
I took these from the following links:
http://rootmygalaxy.net/install-cm13-on-zenfone-2/
http://rootmygalaxy.net/download-in...c550kl-android-6-0-1-marshmallow-beta-update/
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Knowledge/ (and likewise support pages for the variety of the models)
So again: If you are brave enough, try for yourself.
I hope some bluetooth expert can shine a light on this. Or better: That Joying or FYT fixes it.
I also downloaded another intel-MTCD (other MCU) head unit ROM, but it seems for 95% the same as the Joying 27 April first 6.0.1 ROM, so to me not worth the effort.

surfer63 said:
Hi,
I hope this is a thread that will soon be completely unnecessary.
Disclaimer: I have hardly any knowledge of bluetooth. I don't use it much either. I use WiFi tethering, I hardly ever call in my car (it is considered too dangerous and I agree), I have my music on SDcard.
So the reason for this post is not because I want "to tell" about bluetooth. The only reason is that multiple users sent me PMs asking questions about it.
To have it not too cluttered, and without the real bluetooth experts being able to give their valuable opinion in the forum, I created this post.
I downloaded a Cyanogenmod CM-13 6.0.1 (beta) ROM for the Asus Zenfone, and I downloaded the official 6.0.1 Asus ROM for the Zenfone.
The Asus Zenfone has an Intel(R) atom Z3560 CPU.
Our Joying has a Sofia x64 from the C3200 series, so there is a difference but programmaticaly they are the same. I can't find specifics on the used bluetooth chip set and of course the underlying MCU, in case of the Joying, is totally different.
So for those users who asked me and are brave enough to try for themselves I created two zips containing all necessary files AFAIK.
The CM13 file is of course the Cyanogenmod, the UL-Z00 is the official Asus one. The real system "stuff" in the Cyanogenmod is in general more a "fits all possible x86 architectures" build whereas brand specific ROMS are of course more tuned to the specific hardware.
I took these from the following links:
http://rootmygalaxy.net/install-cm13-on-zenfone-2/
http://rootmygalaxy.net/download-in...c550kl-android-6-0-1-marshmallow-beta-update/
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Knowledge/ (and likewise support pages for the variety of the models)
So again: If you are brave enough, try for yourself.
I hope some bluetooth expert can shine a light on this. Or better: That Joying or FYT fixes it.
I also downloaded another intel-MTCD (other MCU) head unit ROM, but it seems for 95% the same as the Joying 27 April first 6.0.1 ROM, so to me not worth the effort.
Click to expand...
Click to collapse
Will give this a try as soon as possible
Sent from my HUAWEI M2-802L using Tapatalk

I am going to have a try today and see what happens.
@surfer63
Is there anything in the joying server that is interacting with the Bluetooth core or the Joying BT app?
I have a funny feeling that something joying is turning the BT off if not using the Joying BT app, been doing this since android 6.0 after about 3mins.
sucks for people running apps that don't require the Joying BT app, eg Inet Truma Box for incar heating controlled with BT

So I started today putting together a batch ADB file to test the CM version of the BT for joying
I have completely run out of time to finish it and I wont be able to complete it till next week, there is quite a bit to go on it and i am not even sure it works, so if anyone want to continue with it, u can.
The ADB Files are not my work and i don't take credit for it, I only added the files and made the batch
This work is not complete and SHOULD NOT BE USED in its current state.
Attached is the half built BluetoothUpgrade Files
View attachment BluetoothUpdate.zip
Echo off
adb kill-server
adb connect %1
adb root
adb connect %1
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount /system /system
adb shell mount -o rw,remount /
adb shell mount -o rw,remount / /
# Push New Files To SDcard (Should Be Finished)
adb push Bluetooth.apk /sdcard/
adb push BluetoothExt.apk /sdcard/
adb push BluetoothMidiService.apk /sdcard/
adb push btnvtool /sdcard/
adb push btsnoop /sdcard/
adb push MTP_WCD9306_Bluetooth_cal.acdb /sdcard/
adb push MTP_Bluetooth_cal_ZD550KL.acdb /sdcard/
adb push MTP_Bluetooth_cal_ZE550KL.acdb /sdcard/
adb push MTP_Bluetooth_cal_ZE600KL.acdb /sdcard/
adb push QRD_Bluetooth_cal.acdb /sdcard/
adb push QRD_SKUL_Bluetooth_cal.acdb /sdcard/
adb push bt_did.conf /sdcard/
adb push bt_stack.conf /sdcard/
adb push android.hardware.bluetooth.xml /sdcard/
adb push android.hardware.bluetooth_le.xml /sdcard/
adb push init.qcom.bt.sh /sdcard/
adb push libbluetooth_jni.so /sdcard/
adb push bluetooth.default.so /sdcard/
adb push libbt-vendor.so /sdcard/
adb push libbtnv.so /sdcard/
# Move The Original Files To OLD Files (List Not Finsished)
adb shell "su -c cp /system/Bluetooth/Bluetooth.apk /system/Bluetooth/Bluetooth.apk.old"
adb shell "su -c cp /system/Bluetooth/oat/x86/Bluetooth.odex /system/Bluetooth/oat/x86/Bluetooth.odex.old"
adb shell "su -c cp /system/Bluetooth/lib/libbluetooth_jni.so /system/Bluetooth/lib/libbluetooth_jni.so.old"
adb shell "su -c cp /system/BluetoothMidiService/BluetoothMidiService.apk /system/BluetoothMidiService/BluetoothMidiService.apk.old"
adb shell "su -c cp /system/BluetoothMidiService/oat/x86/BluetoothMidiService.odex /system/BluetoothMidiService/oat/x86/BluetoothMidiService.odex.old"
# Make New Directories (List Not Finished)
adb shell "mkdir /system/app/BluetoothExt/"
adb shell "mkdir /system/etc/acdbdata/"
adb shell "mkdir /system/etc/acdbdata/MTP/"
adb shell "mkdir /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/"
adb shell "mkdir /system/etc/acdbdata/MTP/ZD550KL/"
adb shell "mkdir /system/etc/acdbdata/MTP/ZE550KL/"
adb shell "mkdir /system/etc/acdbdata/MTP/ZE600KL/"
adb shell "mkdir /system/etc/acdbdata/QRD/"
adb shell "mkdir /system/etc/acdbdata/QRD/msm8939-snd-card-skul/"
adb shell "mkdir /system/vendor/lib64"
# Set Permissions Of New Directories (List Not Finished)
adb shell "chmod 0755 /system/app/BluetoothExt/"
adb shell "chmod 0755 /system/etc/acdbdata/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/ZD550KL/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/ZE550KL/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/ZE600KL/"
adb shell "chmod 0755 /system/etc/acdbdata/QRD/"
adb shell "chmod 0755 /system/etc/acdbdata/QRD/msm8939-snd-card-skul/
adb shell "chmod 0755 /system/vendor/lib64"
# Copy The New Files To Locations (Should Be Finished, Not tested)
adb shell "su -c cp /sdcard/Bluetooth.apk /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c cp /sdcard/BluetoothExt.apk /system/app/BluetoothExt/BluetoothExt.apk"
adb shell "su -c cp /sdcard/BluetoothMidiService.apk /system/app/BluetoothMidiService/BluetoothMidiService.apk"
adb shell "su -c cp /sdcard/btnvtool /system/bin/btnvtool"
adb shell "su -c cp /sdcard/btsnoop /system/bin/btsnoop"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal.acdb /system/etc/acdbdata/MTP/MTP_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/MTP_WCD9306_Bluetooth_cal.acdb /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/MTP_WCD9306_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal_ZD550KL.acdb /system/etc/acdbdata/MTP/ZD550KL/MTP_Bluetooth_cal_ZD550KL.acdb"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal_ZE550KL.acdb /system/etc/acdbdata/MTP/ZE550KL/MTP_Bluetooth_cal_ZE550KL.acdb"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal_ZE600KL.acdb /system/etc/acdbdata/MTP/ZE600KL/MTP_Bluetooth_cal_ZE600KL.acdb"
adb shell "su -c cp /sdcard/QRD_Bluetooth_cal.acdb /system/etc/acdbdata/QRD/QRD_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/QRD_SKUL_Bluetooth_cal.acdb /system/etc/acdbdata/QRD/msm8939-snd-card-skul/QRD_SKUL_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/bt_did.conf /system/etc/bluetooth/bt_did.conf"
adb shell "su -c cp /sdcard/bt_stack.conf /system/etc/bluetooth/bt_stack.conf"
adb shell "su -c cp /sdcard/android.hardware.bluetooth.xml /system/etc/permissions/android.hardware.bluetooth.xml"
adb shell "su -c cp /sdcard/android.hardware.bluetooth_le.xml /system/etc/permissions/android.hardware.bluetooth_le.xml"
adb shell "su -c cp /sdcard/init.qcom.bt.sh /system/etc/init.qcom.bt.sh"
adb shell "su -c cp /sdcard/libbluetooth_jni.so /system/lib/libbluetooth_jni.so"
adb shell "su -c cp /sdcard/bluetooth.default.so /system/lib/hw/bluetooth.default.so"
adb shell "su -c cp /sdcard/libbt-vendor.so /system/vendor/lib/libbt-vendor.so"
adb shell "su -c cp /sdcard/libbtnv.so /system/vendor/lib64/libbtnv.so"
# Set Permission Of New Files (Should Be Finished, Not tested)
adb shell "su -c chmod 644 /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c chmod 644 /system/app/BluetoothExt/BluetoothExt.apk"
adb shell "su -c chmod 644 /system/app/BluetoothMidiService/BluetoothMidiService.apk"
adb shell "su -c chmod 644 /system/bin/btnvtool"
adb shell "su -c chmod 644 /system/bin/btsnoop"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/MTP_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/MTP_WCD9306_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/ZD550KL/MTP_Bluetooth_cal_ZD550KL.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/ZE550KL/MTP_Bluetooth_cal_ZE550KL.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/ZE600KL/MTP_Bluetooth_cal_ZE600KL.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/QRD/QRD_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/QRD/msm8939-snd-card-skul/QRD_SKUL_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/bluetooth/bt_did.conf"
adb shell "su -c chmod 644 /system/etc/bluetooth/bt_stack.conf"
adb shell "su -c chmod 644 /system/etc/permissions/android.hardware.bluetooth.xml"
adb shell "su -c chmod 644 /system/etc/permissions/android.hardware.bluetooth_le.xml"
adb shell "su -c chmod 644 /system/etc/init.qcom.bt.sh"
adb shell "su -c chmod 644 /system/lib/libbluetooth_jni.so"
adb shell "su -c chmod 644 /system/lib/hw/bluetooth.default.so"
adb shell "su -c chmod 644 /system/vendor/lib/libbt-vendor.so"
adb shell "su -c chmod 644 /system/vendor/lib64/libbtnv.so"

shanetrainST said:
So I started today putting together a batch ADB file to test the CM version of the BT for joying
I have completely run out of time to finish it and I wont be able to complete it till next week, there is quite a bit to go on it and i am not even sure it works, so if anyone want to continue with it, u can.
The ADB Files are not my work and i don't take credit for it, I only added the files and made the batch
This work is not complete and SHOULD NOT BE USED in its current state.
Click to expand...
Click to collapse
Nice work.
However, I would start with simply replacing the bluetooth.apk first.
And then the bluetooth.apk, the libbluetooth_jni.so and the bluetooth.default.so
Or did you already try that?
Note also that the "libbt-vendor.so" is seemingly a vendor library. Maybe you still need the original from Joying for the specific Intel vendor bluetooth stuff. On the other hand: the CM-13 is not hardware specific, so maybe it is more cross-compatible.

Going to try that soon thanks for tips, had a bit of time on my lunch break.
new batch file that replaces the three files u mentioned.
If anyone want to test it, file attached
I take zero responsibility if anything happens to your unit
To undo if it don't work just use root browser to delete the new files and rename the old files.
View attachment BluetoothUpdate2.zip
BluetoothHalfUpdate.bat
Echo off
adb kill-server
adb connect %1
adb root
adb connect %1
adb push Bluetooth.apk /sdcard/
adb push libbluetooth_jni.so /sdcard/
adb push bluetooth.default.so /sdcard/
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount /system /system
adb shell mount -o rw,remount /
adb shell mount -o rw,remount / /
adb shell "su -c mount -o remount,rw /system"
adb shell "su -c cp /system/Bluetooth/Bluetooth.apk /system/Bluetooth/Bluetooth.apk.old"
adb shell "su -c cp /system/Bluetooth/oat/x86/Bluetooth.odex /system/Bluetooth/oat/x86/Bluetooth.odex.old"
adb shell "su -c cp /system/Bluetooth/lib/libbluetooth_jni.so /system/Bluetooth/lib/libbluetooth_jni.so.old"
adb shell "su -c cp /system/lib/hw/bluetooth.default.so /system/lib/hw/bluetooth.default.so.old"
adb shell "su -c cp /sdcard/Bluetooth.apk /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c cp /sdcard/libbluetooth_jni.so /system/lib/libbluetooth_jni.so"
adb shell "su -c cp /sdcard/bluetooth.default.so /system/lib/hw/bluetooth.default.so"
adb shell "su -c chmod 644 /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c chmod 644 /system/lib/libbluetooth_jni.so"
adb shell "su -c chmod 644 /system/lib/hw/bluetooth.default.so"
adb reboot

Thanks guys for taking the time to fix it.
Have you tested just a little bit? It works?

Not having much luck with mine, also missed a line of command in the shell that I will add later that mounts it
Every time I get ADB shell root, it connects for about 2seconds then kick me off. I am on the latest July rom
Sent from my iPhone using Tapatalk

So I updated
Bluetooth.apk
(Strange that it didn't produce a Bluetooth.odex on reboot)
Libbluetooth-Jni.so
Bluetooth.default.so
When unit boot's up it shows that Bluetooth sharing has crashed, not sure how to fix it
Must need more files replaced, anyone know a android Bluetooth expert? Would help heaps
So far the BT is broken and won't power on and the Joying app cannot use it but...
Anyone remember was Bluetooth tethering in the menu? Pic attached
{
"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"
}
Sent from my iPhone using Tapatalk

That's difficult to understand this with my knowledge at the moment.:crying:

shanetrainST said:
So I updated
Bluetooth.apk
(Strange that it didn't produce a Bluetooth.odex on reboot)
Libbluetooth-Jni.so
Bluetooth.default.so
Click to expand...
Click to collapse
That is because the odex can't be written to the read-only /system on startup. So it will be written to /data/app like any downloaded app.
Most probably you will find it at /data/app/com.android.bluetooth/oat/x86/base.odex
For the rest I don't have an answer.

I might just put back the original Bluetooth.apk
Just swap the Bluetooth.default.so first
Sent from my iPhone using Tapatalk

This is probably a silly suggestion and already been tried but not seen anything on the joying threads... has anyone tried a Bluetooth tethering manager for the tethering side?
I use this for connecting my phone to a tablet in car.
Bluetooth tethering manager
https://play.google.com/store/apps/details?id=com.tomlocksapps.bluetoothtetheringmanager
Sent from my SM-G920F using Tapatalk

Merlous said:
This is probably a silly suggestion and already been tried but not seen anything on the joying threads... has anyone tried a Bluetooth tethering manager for the tethering side?
I use this for connecting my phone to a tablet in car.
Bluetooth tethering manager
https://play.google.com/store/apps/details?id=com.tomlocksapps.bluetoothtetheringmanager
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I've used that app and although it works fine I found it to be a bit slow.
I found the app the @doitright wrote a lot faster and it works fine and it's free
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
If you want to read more head to my Q&A : https://forum.xda-developers.com/an...ts/intel-sofia-to-micro-tutorials-qa-t3616074

instead of swapping out apk's
try firmware from another device. joying uses realtek rtl8723a/rtk8723
check out
~5009_60/system/vendor/etc/bluetooth
~5009_60/system/vendor/etc/firmware/bt
/nvm_fs_partition/bluetooth
/system/bin/bt_vendor_test
???

edit said:
I've used that app and although it works fine I found it to be a bit slow.
I found the app the @doitright wrote a lot faster and it works fine and it's free
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
If you want to read more head to my Q&A : https://forum.xda-developers.com/an...ts/intel-sofia-to-micro-tutorials-qa-t3616074
Click to expand...
Click to collapse
Thought you probably had but better safe than sorry! Thanks will check that one out.
Following your thread for when I get mine but just delayed it. Was ordering the single din 8" with 5.0.1 on but then they announced the newer cooler running one but it's on 6 and no 8" yet... was hoping this July 7th update might have solved more. Don't really need Bluetooth calling as I have side mounted exhausts and too loud really to talk and it's only a sheet of aluminium between the stereo and the outside so in the sun it will get rather hot...
Worse case will end up WiFi tethering.
Sent from my SM-G920F using Tapatalk

gtxaspec said:
instead of swapping out apk's
try firmware from another device. joying uses realtek rtl8723a/rtk8723
check out
~5009_60/system/vendor/etc/bluetooth
~5009_60/system/vendor/etc/firmware/bt
/nvm_fs_partition/bluetooth
/system/bin/bt_vendor_test
???
Click to expand...
Click to collapse
Thanks for the info
In the Joying 6.0 running OS I find there is this firmware file
vendor/etc/firmware/bt
-A11.Pbn
In the Joying 5.1 rom zip I found
vendor/etc/firmware/bt
-A00.pbn
-A10.pbn
-A11.pbn
Could anyone confirm what firmware file the 5.1 is running on
Could be as simple as swapping the A11.pbn for one of the other two.
A00.pbn seems to have the largest file size?? Not sure if it might be a fully featured firmware for the Realtek BT or it could be because they are using a few different variations of the RTL8723A
Will test tonight
Sent from my iPhone using Tapatalk

Getting very close to working out why Bluetooth disconnect and reconnect on apps that make their own Bluetooth connections without the Joying app.
This might be helpful for inet truma box aswell if it suffers the same issue.
The original problem was it would disconnect the apps Bluetooth after 3 and the the app would have to reconnect/disconnect/reconnect and then it would work fine.
I have started to rename some of the sys/app/ files as apk.old
I started renaming one at a time and got board and renamed a heap.
End result is my BT stays connected now and the app don't disconnect after 3mins of usages.
I think Joying turns the BT off if there is no device paired/connected via their Joying app, and one of the system apps takes care of it.
Tonight I will go back through and work out the culprit.
This has been a few month battle for me trying to figure out this issues, so happy it's not a driver or a Android core apk causing this
Sent from my iPhone using Tapatalk

shanetrainST said:
Getting very close to working out why Bluetooth disconnect and reconnect on apps that make their own Bluetooth connections without the Joying app.
This might be helpful for inet truma box aswell if it suffers the same issue.
The original problem was it would disconnect the apps Bluetooth after 3 and the the app would have to reconnect/disconnect/reconnect and then it would work fine.
I have started to rename some of the sys/app/ files as apk.old
I started renaming one at a time and got board and renamed a heap.
End result is my BT stays connected now and the app don't disconnect after 3mins of usages.
I think Joying turns the BT off if there is no device paired/connected via their Joying app, and one of the system apps takes care of it.
Tonight I will go back through and work out the culprit.
This has been a few month battle for me trying to figure out this issues, so happy it's not a driver or a Android core apk causing this
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Interesting and well done hopefully, I would have been the same as you with the impatience lol.
Sent from my SM-G920F using Tapatalk

[ROOT][GUIDE] Enable Google Voice Search for Kodi 18 on Fire TV

{
"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"
}
The following steps activate the Google Voice Search with Google Assistant so that it can be used in a current Kodi 18 Nightly Build on a Fire TV.
The tutorial assumes that an alternative launcher, e.g. AppStarter, is used because Amazon Alexa voice search is completely replaced by Google Assistant. Xposed edge and HDXPosed must also be installed and activated. Before installing it is recommended to make a backup of the system and data partition via TWRP if you have connected an external sdcard. Many thanks to @SimLynks for some tips from his PlayFire modification.
If you want to use the complete Leanback Launcher with integrated Chromecast, then have a look at my more comprehensive guide: Link
This manual is only possible with a rooted device!
Tested on a Fire TV 4k box
Firmware 5.2.6.2
Instructions:
Unpack all zip files and copy all apk in the appendix to C:\adb\
1. Disabling unnecessary and Google Voice Recognition blocking Amazon apps
Code:
adb shell su -c pm disable com.amazon.advertisingidsettings
adb shell su -c pm disable com.amazon.device.sale.service
adb shell su -c pm disable com.amazon.tv.legal.notices
adb shell su -c pm disable com.amazon.tv.nimh
adb shell su -c pm disable com.amazon.tv.settings/com.amazon.tv.settings.tv.AppDisableService
adb shell su -c pm uninstall -k --user 0 com.amazon.vizzini
(Notice: Disable com.amazon.vizzini works too, but I noticed that the app reactivates itself from time to time.)
2. Customize build.prop
View attachment mod-build.prop.zip
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\mod-build.prop.sh /sdcard/
adb shell su -c sh /sdcard/mod-build.prop.sh
adb shell su -c rm /sdcard/mod-build.prop.sh
adb shell su -c mount -o remount,ro /system
3. Adjust permissions for voice recognition
View attachment tv_core_hardware.zip
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\tv_core_hardware.xml /sdcard/
adb shell su -c cp /sdcard/tv_core_hardware.xml /system/etc/permissions/tv_core_hardware.xml
adb shell su -c chmod 644 /system/etc/permissions/tv_core_hardware.xml
adb shell su -c chown root:root /system/etc/permissions/tv_core_hardware.xml
adb shell su -c rm /sdcard/tv_core_hardware.xml
adb shell su -c mount -o remount,ro /system
4. Install Open Google apps for Android TV
(If you already have the Google Apps installed, you can skip this and the next section.)
Download the matching zip file and copy it to the sdcard.
Open GApps for ARM (Fire TV sticks)
Open GApps for ARM64 (Fire TV boxes)
Copy the customized gapps-config.txt to the same directory as the GApps on the sdcard.
View attachment gapps-config.txt
Then install the GApps zip via TWRP and restart the device. Please don't sign up for Google Play Store yet!
5. Allow Google registration (NoTouchAuthDelegate)
View attachment Tv-NoTouchGsf.apk
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\Tv-NoTouchGsf.apk /sdcard/
adb shell su -c chmod 755 /system/app/NoTouchAuthDelegate/
adb shell su -c rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c cp /sdcard/Tv-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c chmod 644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c rm /sdcard/Tv-NoTouchGsf.apk
adb shell su -c mount -o remount,ro /system
6. Install Google app to enable voice recognition (com.google.android.katniss)
Now restart the device and then sign in to Google Play Store. Attention, the Google Play Store is a system app and therefore only appears in the AppStarter if the display of system apps is activated. Alternatively you can use my modified conFIREator.
Then search for and install the "Google" app on the Play Store. It'll take a while.
(Notice: The search does not work with the search button on the remote!)
7. Adjust the Xposed edge key configuration for the search button of the Fire TV remote
Activate the "Keys" in the Xposed edge and add the new KEYCODE_SEARCH key (simply press the search key on the Fire Remote for recognition).
Use "Single Click" with the activity "com.google.android.katniss\.search.SearchActivity" and leave "Long press" empty. This is the standard function, you first have to click and release the microphone, wait until the input is ready ("Speak Now" appears), and then press and hold the microphone and speak again.
(Notice: Alternatively you also can only link the action "Long press" with the activity "com.google.android.katniss\.search.SearchActivity". Then you have everything at the touch of a button: activate and speak. You should try it the way you like it best.)
Reboot for the last time.
That's all and now you can start the voice search by pressing and holding the search button in Kodi.
Google Assistant also now finds hits in Kodi (movies, tv shows, music), along with other sources such as YouTube, if Kodi already is running.
Once you have installed the PlayFire TV settings, you can choose which apps the Google Assistant is allowed to search for hits.
(Notice: The activation of the detection can take up to 5 seconds in individual cases, but usually it is very fast. Just hold down the search button and wait. But this is also the case on an Android TV.)
.

Fire TV Stick 2/4K Launcher replacement ROOT

Store and Voice input will be lost.
1, Install Launcher of your choice. ( adb install 123launcher.apk )
2, adb shell su -c "pm disable-user --user 0 com.amazon.tv.launcher"
wait 5 seconds
3, adb shell su -c "pm disable-user --user 0 com.amazon.firehomestarter"
wait 5 seconds
5, adb shell reboot
6, adb install com.markus.firetools-1.2.apk (to access Settings "allow Root" )
#########
Disable OTA Updates:
adb shell "su -c pm disable com.amazon.tv.forcedotaupdater.v2"
adb shell "su -c pm disable com.amazon.device.software.ota"
adb shell "su -c pm disable com.amazon.device.software.ota.override"
adb shell "pm clear com.amazon.device.software.ota"
########
to restore the Amazon Launcher
adb shell su -c "pm enable com.amazon.firehomestarter"
wait 4 seconds
adb shell su -c "pm enable com.amazon.tv.launcher"

Update

New Settings APK in 1st Post

0815hoffi said:
After Tests i found out , you can replace amazon launcher without other Tools.
Please test if you want.
1 install launcher of your choice.
Boot twrp.
adb shell mount -o rw /system
Backup Apps
adb shell "cp /system/priv-app/com.amazon.firehomestarter/com.amazon.firehomestarter.apk /sdcard/"
adb shell "cp /system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk /sdcard/"
Delete amazon launcher.
adb shell "rm -r /data/app/com.amazon.tv.launcher-1/"
adb shell "rm -r /data/app/com.amazon.firehomestarter/"
adb shell "rm -r /data/data/com.amazon.tv.launcher/"
adb shell "rm -r /data/data/com.amazon.firehomestarter/"
adb shell "rm /system/priv-app/com.amazon.firehomestarter/com.amazon.firehomestarter.apk"
adb shell "rm /system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk"
adb push NewSettingsRoot.apk /sdcard/NewSettingsRoot.apk
adb shell "mkdir /system/priv-app/NewSettingsRoot/"
adb shell "chmod 0775 /system/priv-app/NewSettingsRoot/"
adb shell "chown root:root /system/priv-app/NewSettingsRoot/"
adb shell "cp /sdcard/NewSettingsRoot.apk /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell "chmod 644 /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell reboot
Workaround : The Settings app. Requires root
Click to expand...
Click to collapse
Works great! I'm really glad to see the last of the Amazon launcher screen. Thanks for your hard work.

TWRP Flashable Zip 1st Post.
Install launcher of your choice.
Then flash the zip.

Modified Leanbacklauncher with FireTvSettings.
Needs Root for Settings.

Will this work on the 2nd Gen sticks?

Yes it should.

Would it not be easier to just freeze pm disable com.amazon.firehomestarter and com.amazon.tv.launcher instead of deleting it? I'm using leanback launcher 1.18. I found it here on xda but I don't have the link anymore.

mrxtc89117 said:
Would it not be easier to just freeze pm disable com.amazon.firehomestarter and com.amazon.tv.launcher instead of deleting it? I'm using leanback launcher 1.18. I found it here on xda but I don't have the link anymore.
Click to expand...
Click to collapse
You can try it.
I haven't tested
Deleted some more on my Stick. See delete.txt
MarkusOnFire.apk is based on leanback launcher 1.19 .
Org. Leanback Launcher you can find here.
https://github.com/tsynik/LeanbackLauncher/releases/

Next step is to try using the stick without an amazon account and Initial Setup maybe

This is what worked for me on a fire stick 2nd gen
NewSettingsRoot.apk
adb push NewSettingsRoot.apk /sdcard/NewSettingsRoot.apk
adb shell su -c mount -o remount,rw /system
adb shell su -c mkdir /system/priv-app/NewSettingsRoot/
adb shell su -c chmod 0775 /system/priv-app/NewSettingsRoot/
adb shell su -c chown root:root /system/priv-app/NewSettingsRoot/
adb shell su -c cp /sdcard/NewSettingsRoot.apk /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk
adb shell su -c chmod 644 /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk
adb shell su -c mount -o remount,ro /system
adb shell su -c rm /sdcard/NewSettingsRoot.apk
adb shell pm grant com.markus.firetools android.permission.WRITE_SECURE_SETTINGS
adb shell pm grant com.amazon.tv.leanbacklauncher android.permission.WRITE_SECURE_SETTINGS

On a rooted FireTV2 (sloane) the Settings App doesn't work
If I select anything it goes back to the Home Screen!
I Flashed the zip with TWRP and also tried that Method which is discribed above, any Idea whats wrong?

Try this commands in adb shell.
su -c am start -a com.amazon.device.settings.action.APPLICATIONS -n com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity
su -c am start -a com.amazon.device.settings.action.APPS -n com.amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity
su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity
su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity
Is one of them working?
If yes, i Think that i must make a New settings apk for firetv2.
This one is for 4k.

0815hoffi said:
Try this commands in adb shell.
su -c am start -a com.amazon.device.settings.action.APPLICATIONS -n com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity
su -c am start -a com.amazon.device.settings.action.APPS -n com.amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity
su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity
su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity
Is one of them working?
If yes, i Think that i must make a New settings apk for firetv2.
This one is for 4k.
Click to expand...
Click to collapse
The first one works for me.
[[email protected] firestick]$ adb shell
-n com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity <
Starting: Intent { act=com.amazon.device.settings.action.APPLICATIONS cmp=com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity }
amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity <
Starting: Intent { act=com.amazon.device.settings.action.APPS cmp=com.amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity }
Error type 3
Error: Activity class {com.amazon.tv.settings/com.amazon.tv.settings.tv.BuellerApplicationsSettingsActivity} does not exist.
mantis:/ $
.settings/com.amazon.tv.settings.tv.applications.Application sActivity <
Starting: Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI pkg=ONS }
Error: Activity not started, unable to resolve Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI flg=0x10000000 pkg=ONS }
.settings/com.amazon.tv.settings.tv.applications.Application sActivity <
Starting: Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI pkg=ONS }
Error: Activity not started, unable to resolve Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI flg=0x10000000 pkg=ONS }
mantis:/ $
---------- Post added at 09:27 PM ---------- Previous post was at 09:20 PM ----------
0815hoffi said:
Try this commands in adb shell.
su -c am start -a com.amazon.device.settings.action.APPLICATIONS -n com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity
su -c am start -a com.amazon.device.settings.action.APPS -n com.amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity
su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity
su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity
Is one of them working?
If yes, i Think that i must make a New settings apk for firetv2.
This one is for 4k.
Click to expand...
Click to collapse
Just noticed a couple of extraneous spaces in #3 & #4. Removing the spaces results in a different error.
mantis:/ $
.settings/com.amazon.tv.settings.tv.applications.Application sActivity <
Starting: Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI pkg=ONS }
Error: Activity not started, unable to resolve Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI flg=0x10000000 pkg=ONS }
MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applic*
Starting: Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATIONS cmp=com.amazon.tv.settings/.tv.applications.ApplicationsActivity }
Error type 3
Error: Activity class {com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity} does not exist.
.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.s*
Starting: Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATIONS cmp=com.amazon.tv.settings/.tv.applications.ApplicationsActivity }
Error type 3
Error: Activity class {com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity} does not exist.
mantis:/ $

Yes the 1st one is for mantis an Stick2 an should work in this devices.
This command style is used for my app.
I not have a FireTV2 to test what is the correct am start command for this device
So i need any one Who can test it.

Edit:
Sry hatte das eben nur überflogen!
Also bei jedem der Befehle kommt der gleiche Fehler raus, Nr 3 und 4 sind gleich, hab dann nochmal einen Versuch gemacht ohne die 2 Leerzeichen aus 3/4, aber wieder der selbe Fehler
Code:
[email protected]:~/Downloads$ adb connect 192.168.2.51
already connected to 192.168.2.51:5555
[email protected]:~/Downloads$ adb shell su -c am start -a com.amazon.device.settings.action.APPLICATIONS -n com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.onRun(Am.java:299)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:97)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256)
[email protected]:~/Downloads$ adb shell su -c am start -a com.amazon.device.settings.action.APPS -n com.amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.onRun(Am.java:299)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:97)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256)
[email protected]:~/Downloads$ adb shell su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATI ONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.Application sActivity
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.onRun(Am.java:299)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:97)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256)
[email protected]:~/Downloads$ adb shell su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.onRun(Am.java:299)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:97)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256)
So with each of the commands the same error comes out, No. 3 and 4 are the same, then I tried again without the 2 spaces from 3/4, but again the same error

0815hoffi said:
You can try it.
I haven't tested
Deleted some more on my Stick. See delete.txt
MarkusOnFire.apk is based on leanback launcher 1.19 .
Click to expand...
Click to collapse
@0815hoffi
I would be interested in how and from where you execute start the delete.txt file,
thank you

Akki67 said:
@0815hoffi
I would be interested in how and from where you execute start the delete.txt file,
thank you
Click to expand...
Click to collapse
On your Windows PC folder where the adb.exe is located.
Download cleanup.cmd.txt, rename to cleanup.cmd and run.

Hi
thank you first. Unfortunately, nothing is deleted for me, see log.
Code:
C:\adbLink>adb devices
List of devices attached
G070VM1600230K52 device
C:\adbLink>cleanup.cmd
Wait for TWRP
Drücken Sie eine beliebige Taste . . .
Debloating Amazon Apps...
rm: can't remove '/system/priv-app/android.amazon.perm': No such file or directory
rm: can't remove '/system/priv-app/com.amazon.android.marketplace': No such file or directory
rm: can't remove '/system/priv-app/com.amazon.awvflingreceiver': No such file or directory
USB cable from the PC goes directly to the FireTV4K, without a USB hub.
Or do I have to enter or install something in TWRP?