Related
Anyone out there willing to help me out?
I just someone to run this command with their phone hooked up, USB Debugging ENABLED:
adb shell ls -l -R /sys/class > class_structure_DREAM.txt
This will output a text file in whichever directory you run the command from, that will list the hardware capabilities of the phone for me - this would help me IMMENSELY from a development standpoint!
Check out the text file - zero personal / private information will be in there!
Thanks!
This is off a T-Mobile G1. Don't know if it makes a difference but is unlocked, was rooted, then unrooted and stock SPL/radio and T-Mo 1.6 installed. Hope it helps.
Great! Thank you!
Do you mind if I get these ones, too?
adb shell ls -l -R /sys/devices/platform > platform_structure_DREAM.txt
and
adb shell ls -l -R /sys/devices/virtual > virtual_structure_DREAM.txt
Here you go.
Anyone out there willing to help me out?
I just someone to run this command with their phone hooked up, USB Debugging ENABLED:
adb shell ls -l -R /sys/class > class_structure_VIBRANT.txt
This will output a text file in whichever directory you run the command from, that will list the hardware capabilities of the phone for me - this would help me IMMENSELY from a development standpoint!
Check out the text file - zero personal / private information will be in there!
Thanks!
I have a samsung that is ROOT, has the gps-fix for ROOT users, the custom recovery image.
Is that good for you?
abcdavidefg said:
I have a samsung that is ROOT, has the gps-fix for ROOT users, the custom recovery image.
Is that good for you?
Click to expand...
Click to collapse
That would be a start - I'd like to find one that is non-root, though!
Doward said:
That would be a start - I'd like to find one that is non-root, though!
Click to expand...
Click to collapse
http://www.4shared.com/document/7F2UoKt-/class_structure_VIBRANT.html
This is from an un-rooted Vibrant bone stock Rom just after flashing it with ODIN!
mp2ning said:
http://www.4shared.com/document/7F2UoKt-/class_structure_VIBRANT.html
This is from an un-rooted Vibrant bone stock Rom just after flashing it with ODIN!
Click to expand...
Click to collapse
Great, thank you!
*edit*
Oh wow... oddball structure there!!
Can I get these as well?
adb shell ls -l -R /sys/devices/platform > platform_structure_VIBRANT.txt
and
adb shell ls -l -R /sys/devices/virtual > virtual_structure_VIBRANT.txt
adb shell ls -l -R /sys/devices/platform > platform_structure_VIBRANT.txt
http://www.4shared.com/document/ouZxt2TF/_2__platform_structure_VIBRANT.html
adb shell ls -l -R /sys/devices/virtual > virtual_structure_VIBRANT.txt
http://www.4shared.com/document/Vnvz-oEQ/virtual_structure_VIBRANT.html
I had already rooted after I posted the first file so I unrooted to get these last 2 files in case it matters!
mp2ning said:
adb shell ls -l -R /sys/devices/platform > platform_structure_VIBRANT.txt
http://www.4shared.com/document/ouZxt2TF/_2__platform_structure_VIBRANT.html
adb shell ls -l -R /sys/devices/virtual > virtual_structure_VIBRANT.txt
http://www.4shared.com/document/Vnvz-oEQ/virtual_structure_VIBRANT.html
I had already rooted after I posted the first file so I unrooted to get these last 2 files in case it matters!
Click to expand...
Click to collapse
LOL awesome, thanks!!
I connect my phone, open the cmd and then I type this
cd\
cd AndroidSDK\tools\
adb shell ls -l -R /sys/class > class_structure_VIBRANT.txt
I dont get error, but i dont get any text.
I am just trying to help
abcdavidefg said:
I connect my phone, open the cmd and then I type this
cd\
cd AndroidSDK\tools\
adb shell ls -l -R /sys/class > class_structure_VIBRANT.txt
I dont get error, but i dont get any text.
I am just trying to help
Click to expand...
Click to collapse
What do you get?
If the file completes, then you should be able to type in 'dir' and see class_structure_VIBRANT.txt in there
Doward said:
What do you get?
If the file completes, then you should be able to type in 'dir' and see class_structure_VIBRANT.txt in there
Click to expand...
Click to collapse
I attach the files that you asked for it
Hello everyone...
I have a Motorola RAZR 201M(XT902) in Japan and use Motofail2go to root it.But it doesn't work.
(follow http://forum.xda-developers.com/showthread.php?p=32889627)
I installed Sudoku.apk and push the motofail2go to the device(also su,Superuser.apk,busybox).
when
$ run-as com.motorola.bug2go /data/local/tmp/motofail2go prep2
Here is the error message:
"run-as: exec failed for /data/local/tmp/motofail2go Error: Operation not permitted"
and i try $ run-as com.motorola.bug2go
but error message : "run-as: exec failed"
Anyone help? Thanks...
Sorry buddy. Nothing works. We 201m users are SOL.
Have you tried this?
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
Thanks Paul!
No luck with that either. Appreciate the feedback, however.
I hope somebody will study the XT902 root.
goodayoo said:
I hope somebody will study the XT902 root.
Click to expand...
Click to collapse
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Almalieque said:
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Click to expand...
Click to collapse
There some Japanese guys doing some things to try and get root. They are active. The site has a lot of rather unpleasant (read offensive) advertisements. PM if you are interested (its in Japanese)
root
help!!!
Root and Unlocked bootloaders!
Proceed at yor own risk
hungln03 said:
help!!!
Click to expand...
Click to collapse
1)Prep
Android SDKと各種ドライバを導入する。
以下の必要ファイルをC:\***（何でも良い）に配置する。
・XT902_SBMの中身(http://www1.axfc.net/uploader/so/2991543 >>125氏)
・su（http://www1.axfc.net/uploader/so/2918729 password：f10d）
・Superuser.apk（in the above downloaded）
・busybox（in the above downnloaded）
201M Plug the phone into the comp
any port will do
2)adb pushで必要ファイルを/data/local/tmp転送
コマンドプロンプトを開く
C:\Users\（ユーザー名） >cd C:\***
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push busybox /data/local/tmp
adb push unlock_security_module /data/local/tmp
adb push break_setresuid /data/local/tmp/
adb push mole-plough-ccsecurity.so /data/local/tmp/
adb push mole-plough-lsm.so /data/local/tmp/
3)unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ chmod 777 *
[email protected]:/data/local/tmp $ ./unlock_security_module
[email protected]:/data/local/tmp $ ./break_setresuid
（unlock_security_moduleが動いてMIYABIとNANDロック解除）
（色々表示されるので↓が出る間で待つ）
Unlocked LSM.
Do setresuid...
OK.
[email protected]:/data/local/tmp #
（#if done correctly temp root should be achieved）
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
4)system putting together su，Superuser.apk，busybox
[email protected]:/data/local/tmp # mount -o rw,remount /system /system
[email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
[email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
[email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
[email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
[email protected]:/data/local/tmp # cd /system/xbin
[email protected]:/system/xbin # chown root.root su
[email protected]:/system/xbin # chown root.root busybox
[email protected]:/system/xbin # chmod 6755 su
[email protected]:/system/xbin # chmod 755 busybox
[email protected]:/system/xbin # mount -o ro,remount /system /system
After the opperation is done it is ok to remove the cable from the pc。
check and see if「SuperSU」was installed if it wasn't download chainfire (su) from the play store
⇒SU --> update
Fro the play store download busybox。
⇒busybox -->update
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
I don't own the 902, but it's good to see this. I know quite a few people have been looking for this. You should start your own thread with the procedures, so it will get more publicity.
Thank u!
thank u so much.!1
sbeaber4 said:
Proceed at yor own risk
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Can you tell me more about this step
Confirm?
Can confirm if the latest instructions have worked for your 201m?
That your rooted and bootloader unlock.
Thanks a bunch!
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
sbeaber4 said:
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
Click to expand...
Click to collapse
Thanks for the feedback.
Still awaiting more confirmation with others. It's a step forward though.
I've had my phone for almost a year now. If I cancel my softbank service or run the contract to the end I want an option to root and unlock the bootloader in the future.
could u provide more friendly filehost?
i can't find the download button there
Root! (temp root that is...)
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Quick Tip
zenstarlight said:
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Click to expand...
Click to collapse
Found that if I a did restart my phone root was lost but I found a quick fix without going through the whole process again.
Just do these steps
unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ ./unlock_security_module
Just enter those three steps then you're back to temp root
Also you can just to a quick reboot with link2sd or any other app that just reboots the android ui. You don't have to enter commands every time you reboot unless it's a full reboot.
Help for Gaigin rooting 201M
sbeaber4 said:
Proceed at yor own risk
...
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
kprower said:
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
Click to expand...
Click to collapse
Once CWM is online you might be able to flash a VZW or Aussie stock ROM. Actually, you could probably flash CM... That'll fix the Japanese popups. Of course, it also could very possibly brick it. Proper precautions must be made... On my tablet at the moment, does anyone know if sbf.droid-developers has 902 images?
Sent from my Nexus 7 using Tapatalk 4
Hello im trying to send MMS using ADB on phisical device, for SMS the code im using is simple
Code:
adb shell start -a android.action.SENDTO -d sms:xxxxxxxxx --es sms_body "SMS BODY"
adb shell input keyevent 22
adb shell input keyevent 66
The code im trying to write should work for two cases:
1. Take photo and attach it to my msg
2. Select photo from My Files and attach it.
Do You know how to do that? I will appreciate any help.
Redg
Iksior
Any one?
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