[Q]Bluetooth dongle via OTG - General Questions and Answers

Hello,
I got a low cost tablet (MP MAN MP2000 (Model id : MP948 / Build ID : IML74K / Device : crane-MID9741-sc3052) running Android 4.0.3 (core : 3.0.8+)
This tablet don't have built-in Bluetooth, but I really want this feature.
I bought a USB Bluetooth dongle (Sitecom CN-523) which is natively compatible with Linux.
So I plug it on my tablet but unfortunately it's not working.
I installed "USB Host Diagnostics v1.3" and the result is :
Code:
[U]ANDROID API[/U]
Claims support > Yes
Classes found > Yes
Device detected > Yes
[U]ROOTED API[/U]
Claims support > Yes
Device detected > Yes
[U]KERNEL[/U]
Claims support > Yes
Device detected > Yes
[U]VERDICT[/U]
OS support > Yes
3rd party apps > Full
So it seem to be fully detected by my Android
I also saw many files and folder "Bluetooth" in /sys and /system (such "/system/etc/bluetooth", "/sys/module/bluetooth", etc...) I don't know if it's a hint ( )
I tried some apps to get acces to the Bluetooth settings screen (which is hidden of course), but the Settings "apps" crash.
Did you have any ideas about how to get it enable ? (maybe build.prop or another system files to edit ?)
Thank you for listening
(And sorry for my bad english ( ^_^ ) ... )

Belnadifia said:
Hello,
I got a low cost tablet (MP MAN MP2000 (Model id : MP948 / Build ID : IML74K / Device : crane-MID9741-sc3052) running Android 4.0.3 (core : 3.0.8+)
This tablet don't have built-in Bluetooth, but I really want this feature.
I bought a USB Bluetooth dongle (Sitecom CN-523) which is natively compatible with Linux.
So I plug it on my tablet but unfortunately it's not working.
I installed "USB Host Diagnostics v1.3" and the result is :
Code:
[U]ANDROID API[/U]
Claims support > Yes
Classes found > Yes
Device detected > Yes
[U]ROOTED API[/U]
Claims support > Yes
Device detected > Yes
[U]KERNEL[/U]
Claims support > Yes
Device detected > Yes
[U]VERDICT[/U]
OS support > Yes
3rd party apps > Full
So it seem to be fully detected by my Android
I also saw many files and folder "Bluetooth" in /sys and /system (such "/system/etc/bluetooth", "/sys/module/bluetooth", etc...) I don't know if it's a hint ( )
I tried some apps to get acces to the Bluetooth settings screen (which is hidden of course), but the Settings "apps" crash.
Did you have any ideas about how to get it enable ? (maybe build.prop or another system files to edit ?)
Thank you for listening
(And sorry for my bad english ( ^_^ ) ... )
Click to expand...
Click to collapse
m also on a similar quest..any luck??
Sent from my P275 using xda premium

Same question here. is it possible?

I'm also trying to achieve this.
I was able to cross-compile my bluetooth chip's module (BCM203x) and insmod it, although I can reach the "hidden" menu option in settings through a bluetooth shortcut app, there's no way to turn the bluetooth services on.
Is this just not built into the Android Kernel in my image (meaning that I would have to find a similar tablet with bluetooth and reflash with that image), or is there any settings file that can trigger the "turn bluetooth on" in settings, like /etc/bluetooth ?

OMG I have the same issue, has anybody figured anything out? I'm trying to get it to work on this http : // www . kingzer . com /product_view.asp?id=1214 , that way I can use my bluetooth snes controller with it and use it as an emulator on my T.V.
Belnadifia said:
Hello,
I got a low cost tablet (MP MAN MP2000 (Model id : MP948 / Build ID : IML74K / Device : crane-MID9741-sc3052) running Android 4.0.3 (core : 3.0.8+)
This tablet don't have built-in Bluetooth, but I really want this feature.
I bought a USB Bluetooth dongle (Sitecom CN-523) which is natively compatible with Linux.
So I plug it on my tablet but unfortunately it's not working.
I installed "USB Host Diagnostics v1.3" and the result is :
Code:
[U]ANDROID API[/U]
Claims support > Yes
Classes found > Yes
Device detected > Yes
[U]ROOTED API[/U]
Claims support > Yes
Device detected > Yes
[U]KERNEL[/U]
Claims support > Yes
Device detected > Yes
[U]VERDICT[/U]
OS support > Yes
3rd party apps > Full
So it seem to be fully detected by my Android
I also saw many files and folder "Bluetooth" in /sys and /system (such "/system/etc/bluetooth", "/sys/module/bluetooth", etc...) I don't know if it's a hint ( )
I tried some apps to get acces to the Bluetooth settings screen (which is hidden of course), but the Settings "apps" crash.
Did you have any ideas about how to get it enable ? (maybe build.prop or another system files to edit ?)
Thank you for listening
(And sorry for my bad english ( ^_^ ) ... )
Click to expand...
Click to collapse

I can get the bluetooth working in terminal, but the android user space GUI and thence every program is totally oblivious to its existence. I've copied over the files missing compared with tablets with integrated bluetooth (various hci tools, bluez, bluetoothd, some bt*.so libs, the .conf files...) to no avail. hw/bluetootha2dp would hang the system on boot, had to get in with adb and delete it. Also edited the permissions xml to include bluetooth, so now it show the option in the settings but still can't turn it on. I read somewhere that you don't need to hciattach and after setting bluetooth up with hciconfig and running scan it would let you turn it on in the settings. Not in my case, maybe I'm not linking it correctly with a /dev/ connection.
The bluetooth when connected and having the module properly loaded shows up in /sys/classes/bluetooth as hci0 but not in /dev/ as far as I can tell. I tried ln -s to /dev/hci0 didn't work, and to /dev/ttyS1 didn't let me link cuz it's already there, mknod /dev/ttyS1 c 216 didn't seem to work either.
Haven't tried enabling the startup script for bluetooth, my tablet has these commented out in init.sun4i.rc:
# -------- bluetooth related services ----------
#chmod 0666 /dev/ttyS1
#chmod 0777 /system/bin/hciattach
#change rfkill permissions for bluetooth power management
# chown system system /sys/class/rfkill/rfkill0/state
# chmod 0660 /sys/class/rfkill/rfkill0/state
# write /sys/class/rfkill/rfkill0/state 0
# setprop rw.bluetooth.status "0"
# --- used for usi bm01a 3in1 module's bluetooth attach
#service hciattach /system/bin/hciattach -n -s 115200 /dev/ttyS1 bcm4329 1500000
# user root
# group bluetooth net_bt_admin
# disabled
# oneshot
# --- used for huawei mw269v2 3in1 module's bluetooth attach
#service hciattach /system/bin/brcm_patchram_plus --enable_hci \
# --baudrate 1500000 \
# --patchram /system/vendor/modules/bcm4330.hcd \
# --enable_lpm /dev/ttyS1
# user root
# group bluetooth net_bt_admin
# disabled
# --- used for samsung swb-a31 2in1 module's bluetooth attach
#service bccmd /system/bin/bccmd -t bcsp -b 115200 -d /dev/ttyS1 psload -r /system/vendor/modules/ath6k/AR6003/A31_Script.psr
# user root
# group bluetooth net_bt_admin
# disabled
# oneshot
#
#service hciattach /system/bin/hciattach -s 1500000 /dev/ttyS1 bcsp 1500000 flow
# user root
# group bluetooth net_bt_admin
# disabled
# oneshot
#service abtfilt /system/bin/abtfilt -d -z -n -v -b -s
# disabled
# oneshot
# -------- bluetooth related services end ----------
I can call bluetooth services on but it seems to throw an error. Maybe it's missing the Java elements and it's impossible to just copy those and get them working.
I'm afraid that only from 4.2.2 android onwards bluetooth dongle support is standard. I don't want to mess with any unofficial version until they have hardware acceleration for videos.

Sorry to bump such old thread.
I have an Rk3026 based tablet which supports OTG but from user reports bluetooth dongles don't work.
Any way to bypass this limitation?
This is a tablet on a "promotion" in Portugal and Spain which can be get for 2eur, it would be nice to get bluetooth working. there are even custom rom for it.

To get bluetooth working with usb otg:
android needs to built with bluetooth support(unless you want to use it with console only)
the device's kernel needs to have the modules for usb bluetooth(each device has a diffrent kernel) but that is quite rare

Hi
I am running Android 4.4.2 an would also like to use a Bluetooth dongle.
I have a "old" dongle, that worked fine with Android 2.3.4, but I can't get it to Work with Android 4.4.2.
Do it have to be a bluetooth dongle with OTG support if it should work with Android 4.4.2 ?
Hope someone can help me .
Many regards
MrNisse

Hello.
I have the same wish: To use a dongle BT as extender on my S7 Edge.
Any idea?

I have the same needs. An android tv box without bluetooth. Any news on this guys? Actually for me is ok also a fake usb. One of my app is crashing because it tries to read the mac address of the bluetooth
Please advice

Me too. Waiting for an answer. My box can use I8 air mouse but I am not sure whether it can detect Bluetooth dongle

Sorry to relive the topic, but anyone knows if it is possible to use a bluetooth adptador on TV BOX?
Enviado de meu LG-D855 usando Tapatalk

Hi, also for me... to my MBOX DVB-S2

Khm... Two pages with questions only. Where are experts? Have the same problem

zaooooza said:
Khm... Two pages with questions only. Where are experts? Have the same problem
Click to expand...
Click to collapse
I set aside these cheap boxes and picked up the Raspberry PI, maybe there is a good BOX TV, but these are not the ones. If you have money, maybe an ODROID UX4 will do.
Enviado de meu LG-D855 usando Tapatalk

Hi guys,
I got TV box (MXQ model) it has not Bluetooth , so i bought USB BT 4.0 dongle, I connect to the port and nothing, but I connect this USB BT to the PC the device on a blue light and show it in the windows menu bar.
I have connected to the MXQ USB keyboard and mouse, both work fine , but there is an issue with the USB BT.
I don´t understand , how in the new releases for these devices there isn´t a software for activate dongle USB BT. if those previous devices have not been with BT inside.
Uptoday, Anybody can solved this issue ¿?
Sorry for my English.
-----------------------------------------------------------------------
Quiero activar mi USB BT en un TV BOX modelo MXQ, y por alguna razon no lo toma no prende la luz que trae el USB BT , como que no lo enciende, cosa que en la PC lo hace automatico, encima se baja los drivers y ya lo activa.
Tiene que haber una solucion para esto en los modelos de TV BOX o tablets que no tenga BT.
Porque se deberia poder activar el USB BT y poder utilizarlo, ya que los dispositivos estos no lo traen incorporado.
Parece que no hay una solucion a la fecha.
Saludos.

Related

[Q] WiFi TXpower + iwconfig + tether + Bumblebee on LG OP V

This post is actually part HOWTO and part Question / RFC
Hardware used:
LG Optimus V
Software used:
Bumblebee ROM 2.4
WiFi TXpower
Wireless Tether (for root users)
iwconfig
UAPick (to change the User Agent string in IE8 to avoid raising red flags with Virgin Mobile)
So I've been playing around with OP V and decided that it would be best for me to reduce my wifi TX power since I always us my wifi tether is close proximity to my laptop. Unfortunately, the ROM that I use does not come with the iwconfig tool necessary so I had to do a little fiddling around to get everything to work. So I figured I'd post here so you guys can review what I did and make any corrections if you think there is a better way to do this. And hopefully this info will help out some people that are newer at this than I am.
After I installed Bumblebee 2.4, I decided to play with the Tether APP that comes with it. I configured BB's tether and used UAPick to change IE8's UA string to the UA string from the Android Browser. It then occurred to me that my OPV was sitting ~2' away from my laptop and didn't to be transmitting at full power. So I started looking for APP to easily adjust the TX power. I happened upon WiFi TXpower in the android market and installed it. But it did not work because the Bumblebee ROM does not come with iwconfig.....hmmm....what to do what to do?
After many hours of Googling and reading forums I came to find out that I needed access to iwconfig to make WiFi TXpower work correctly. So I had to make a choice, 1) try downloading iwconfig and try to adb push iwconfig to /system/xbin and hope it works and that I can chmod the file correctly 2) install and APP that comes with iwconfig and symlink it into the /system/xbin dir.
Fortunately, I stumbled on a post in a forum that stated the APP Wireless Tether (for root users) comes with iwconfig and it allows for changing the TX power level in the APP (for hardware that supports TX adjustments). So I installed Wireless Tether (for root users) setup my Android for wi-fi tethering. I then proceeded to fire up my laptop and put it in my bedroom with the android phone on my kitchen table in order to test changing TX power levels and checking the change with my laptop.....SURE ENOUGH IT WORKS. Power level changes supported by the APP are as follows: disabled(no TX reduction)/3mW/5mW/10mW/15mW/20mW/25mW/30mW. The only problem is that the APP is rather large. 403KB for the .apk and ~.98MB when running on the Android. So onto the next step.
WiFi TXpower is pretty light weight @ 92KB supports the following power levels: 4/11/18/25/32 so all I need now is iwconfig to get it to work right. I decided to symlink iwconfig from the Wireless Tether (for root users) install dir instead of trying to adb push it. Here's what I did to symlink:
# adb shell
# echo $PATH
# mount -o remount,rw -t yaffs2 /system /system
# ln -s /data/data/android.tether/bin/iwconfig /system/xbin/iwconfig
After that I fired up WiFi TXpower and now it works because the symlink worked. . I was just happy because it's been a long time since I made a symlink.
So now I would like some input form you guys here.
1) Is it possible for me to just unzip the Wireless Tether.apk and pull out the iwconfig then use adb to push the file into /system/xbin so that I don't have to install the whole APP package then create a symlink. If I do go that route will I have to chmod the iwconfig?
2) Could I just copy the iwconfig to /system/xbin from the install directory then uninstall the APP it came with.
3) Can I package the iwconfig (and possibly other wireless tools) into a zip that I can flash to the system from the Xionia recovery? This is how I would prefer to do it so that I have a simple package to load if I ever switch ROMs.
I'd greatly appreciate any feedback you could provide as to the best method and if I may have done this the long hard way or the right way. Although I am new to Android, I have been playing with linux on & off for the last 12+ years. It's just been ~2 years since my last outing with a full blown install that I could play with.
-eric
P.S. Thx to obijon for Bumblebee. I've been loving this ROM for the last couple weeks and having the Terminal Emulator app installed by default was VERY helpful to me in getting this WiFi TXpower / iwconfig thing worked out.
so this will work on p500 also?
should i type these in terminal emulator?
# adb shell
# echo $PATH
# mount -o remount,rw -t yaffs2 /system /system
# ln -s /data/data/android.tether/bin/iwconfig /system/xbin/iwconfig
ccdreadcc said:
so this will work on p500 also?
should i type these in terminal emulator?
Click to expand...
Click to collapse
1/ Flash this
2/ Use /system/etc/setwifi.sh script or WiFi Tx Power (the iwmulticall method).
3/ Done
k i will try..
im using void froyo final
ccdreadcc said:
so this will work on p500 also?
should i type these in terminal emulator?
# adb shell
# echo $PATH
# mount -o remount,rw -t yaffs2 /system /system
# ln -s /data/data/android.tether/bin/iwconfig /system/xbin/iwconfig
Click to expand...
Click to collapse
To be 100% honest I don't know if it will work on other hardware, as I have only done this on my hardware. I guess you could always install the Wireless Tether for root users APP and conduct a similar experiment to mine, in order to verify that your platforms wifi radio can change TX levels. The thing I like about the WiFi TXpower app is that it can change TX levels on the fly and comes with a very simple widget that allows you to "single tap cycle" through the TX levels. Where as the Wireless Tether app shuts down the radio and tether to modify the power level.
So by using the WiFi TXpower app you can use your personal favorite wifi tether app and have the TXpower toggle/cycle seperate. And it even works when your using the WiFi radio for anything else since it runs as a service in the background and sets your specified power level whenever the radio comes on. Which is awesome when I'm at home or in a coffee shop with a good signal. No need to operate at full power.
You should definitely let us know if dr.notor's solution works for you. good luck man.
dr.notors method worked, thx anyway
no worries mate. that's why we post what we do. to help each other.
glad nortor's suggestion worked for you.
Talking about WiFi Tx power... what are recommended values for someone like me who use my home Wifi with a router on a small apartment?
LOL 1.4.2 Rom (which I use) has WiFi Tx set to 20 by default, but I've always wondered if that's already a "reduced value" or what. Does anyone knows what's the actual default value for The Optimus One?
ElGeorge said:
Talking about WiFi Tx power... Does anyone knows what's the actual default value for The Optimus One?
Click to expand...
Click to collapse
32 dBm......
dr.notor said:
32 dBm......
Click to expand...
Click to collapse
yep! 32/30 is the default.
I'm in a 750 sq/ft duplex and I go outside to smoke cigs (about 50+' away) and a setting of 4/11 dB works great for me. So you could drop it down a few levels and still maintain good connectivity. Judging by the the Windows Vista "WiFi power level meter", @ 4dB WiFi TxPower setting I still have 50% signal strength @ ~100' away on my HP Laptop's wifi card/antannae.
regarding dr.norto's setwifi.zip file: It's doesnt seem to like my Xionia/LG OPV. It gives me a "failed : no boot.img" error. So this .zip may not be for everyone. It may be an issue with the Bumblebee 2.4 rom or the Xionia recovery tool. Which is a bit of a bummer as I REALLY wanted to use iwmulticall instead of imconfig. But that is just how life goes.
I'm working on getting the Jave SDK & and Android SDK install and working so I can build a package for the LG OPV guys with either iwconfig or iwmulticall.
thx for all the help guys.
fatchick1o9 said:
regarding dr.norto's setwifi.zip file: It's doesnt seem to like my Xionia/LG OPV. It gives me a "failed : no boot.img" error. So this .zip may not be for everyone. It may be an issue with the Bumblebee 2.4 rom or the Xionia recovery tool. Which is a bit of a bummer as I REALLY wanted to use iwmulticall instead of imconfig. But that is just how life goes.
Click to expand...
Click to collapse
You can try to replace update-binary with one from some of the working ZIPs on your device. Other than that, no idea about your recovery. This works (tested) with CWM and AmonRa...
ccdreadcc said:
so this will work on p500 also?
should i type these in terminal emulator?
# adb shell
# echo $PATH
# mount -o remount,rw -t yaffs2 /system /system
# ln -s /data/data/android.tether/bin/iwconfig /system/xbin/iwconfig
Click to expand...
Click to collapse
" # mount -o remount,rw -t yaffs2 /system /system"
Thank you for the line of code!
dr.notor said:
1/ Flash this
2/ Use /system/etc/setwifi.sh script or WiFi Tx Power (the iwmulticall method).
3/ Done
Click to expand...
Click to collapse
I'm having a ***** of a time getting iwconfig on my Asus transformer tablet. I tried flashing this, but didn't work. I'm running Xenogenesis JB 4.2. is there any way to get this working?

[Q] Chi Tablet [MID] always returns to factory settings

I have done search after search, and I have found nothing.
Here is the problem, I bought a MID 097Q1 tablet, that runs ICS, and now when I shut it down, and reboot, it will basically reset to factory settings on it's own.
Has anyone any idea or even seen such behavior before?
Thanks All.
Is it an A13 tablet?
wcypierre said:
Is it an A13 tablet?
Click to expand...
Click to collapse
I am unsure on how to check for that. Under the settings -> About Tablet it just shows: Model = 097q1
If there was a way I could just flash and reset the thing, that might be good. But I have tried the hold volume and reboot trick, and it did not flash the thing back to factory. Basically my stuff was still there.
I found one set of posts that suggest that the install of busybox may be the reason to blame.
Also, the CPU is listed as BOXCHIP A10 - 1.5ghz (cortex A8).
Here are the specs from the site I got it from:
Specifications:
CPU
BOXCHIP A10 1.0-1.5GHz(cortex A8), GPU:Mali-400
Operation System
Google Android 4.03
Memory
1GB DDR3
NAND Flash
16GB
Display Screen
Capacitive touching screen (IPS), 1024*768 pixel
Touch Operation
Full-size touch operation, sliding menus, icons and drag
Network
WiFi 802.11 B/G
Bluetooth Support
Sensor G-sersor 360 degrees
Audio
Supports stereo speaker unit, built-in microphone
External Storage
Support to the 32 GB TF card
I/O Ports
Micro USB2.0
HDMI output
TF card slot
3.5mm stereo headphone jack
DC-in jack
Adobe Flash Flash11
Audio Player
MP3, WMA, APE, FLAC, OGG, WAV Frequency response: 20Hz to 20000H
Video Player
AVI,MKV(XVID/px/H.264),MOV,TS,M2TS,RM/RMVB,FLV,3GP,MPEG,DAT,MP4(support to 2160P:3480x2160)
Application soft ware
Google Search / Browser /Camcorder/camera/Email/Gmail
Video Player/Audio Player/Alarm Clock /Apk /Calculator
Calendar/ES file Explorer /ES Task Manager/Global Time
Google Maps /Google Talk/iReader/Market/NC Manager
PDF Reader/Photo Browser/Weather Forecast/QQ
PC camera
0.3M FF Front/2.0M AF Back
Accessories
Adapter, user manual, USB cable, OTG cable
Battery
Lithium-ion 8000mAh
Color
Silver
Net Weight 0.6kg
Product Size 240*185*9.8mm
ericm76903 said:
I am unsure on how to check for that. Under the settings -> About Tablet it just shows: Model = 097q1
If there was a way I could just flash and reset the thing, that might be good. But I have tried the hold volume and reboot trick, and it did not flash the thing back to factory. Basically my stuff was still there.
I found one set of posts that suggest that the install of busybox may be the reason to blame.
Also, the CPU is listed as BOXCHIP A10 - 1.5ghz (cortex A8).
Here are the specs from the site I got it from:
Specifications:
CPU
BOXCHIP A10 1.0-1.5GHz(cortex A8), GPU:Mali-400
Operation System
Google Android 4.03
Memory
1GB DDR3
NAND Flash
16GB
Display Screen
Capacitive touching screen (IPS), 1024*768 pixel
Touch Operation
Full-size touch operation, sliding menus, icons and drag
Network
WiFi 802.11 B/G
Bluetooth Support
Sensor G-sersor 360 degrees
Audio
Supports stereo speaker unit, built-in microphone
External Storage
Support to the 32 GB TF card
I/O Ports
Micro USB2.0
HDMI output
TF card slot
3.5mm stereo headphone jack
DC-in jack
Adobe Flash Flash11
Audio Player
MP3, WMA, APE, FLAC, OGG, WAV Frequency response: 20Hz to 20000H
Video Player
AVI,MKV(XVID/px/H.264),MOV,TS,M2TS,RM/RMVB,FLV,3GP,MPEG,DAT,MP4(support to 2160P:3480x2160)
Application soft ware
Google Search / Browser /Camcorder/camera/Email/Gmail
Video Player/Audio Player/Alarm Clock /Apk /Calculator
Calendar/ES file Explorer /ES Task Manager/Global Time
Google Maps /Google Talk/iReader/Market/NC Manager
PDF Reader/Photo Browser/Weather Forecast/QQ
PC camera
0.3M FF Front/2.0M AF Back
Accessories
Adapter, user manual, USB cable, OTG cable
Battery
Lithium-ion 8000mAh
Color
Silver
Net Weight 0.6kg
Product Size 240*185*9.8mm
Click to expand...
Click to collapse
Have you installed busybox before? If yes then you can follow the following steps:
Windows Only:
1. USB Driver: http://www.mediafire...q1oamnccjk82aq8 (Extracted from http://ployermomo9.w...cream-sandwich/)
2. Get yourself the fastboot files: http://wikisend.com/...id_fastboot.zip
3. Create a folder called fastboot at your root folder(C:/, D:/)
4. Open cmd(or also called command prompt)
4. Type "cd \fastboot" (without the quotes)
5. Type "adb shell" (without the quotes)
6. Type "su" (without the quotes)
7. Type "mount -o rw,remount /dev/block/mmcblk0p1 /system" (without the quotes)
8. Type "cp /system/xbin/busybox /system/bin/busybox" (without the quotes)
9. If there is an error(sh cp: not found), follow step 10. If there is no error, then skip step 10
10. Type "ln -s /system/xbin/busybox /system/xbin/cp" (without the quotes)
11. Type "cp /system/xbin/busybox /system/bin/busybox" (without the quotes)
12. Type "reboot" (without the quotes)
wcypierre said:
Have you installed busybox before? If yes then you can follow the following steps:
Windows Only:
5. Type "adb shell" (without the quotes)
6. Type "su" (without the quotes)
7. Type "mount -o rw,remount /dev/block/mmcblk0p1 /system" (without the quotes)
8. Type "cp /system/xbin/busybox /system/bin/busybox" (without the quotes)
9. If there is an error(sh cp: not found), follow step 10. If there is no error, then skip step 10
10. Type "ln -s /system/xbin/busybox /system/xbin/cp" (without the quotes)
11. Type "cp /system/xbin/busybox /system/bin/busybox" (without the quotes)
12. Type "reboot" (without the quotes)
Click to expand...
Click to collapse
You are the Man!!
Since I use a MAC, I had to load adb there. But once that was done, I was able to do steps 7 and 8 with out error, and it now works. Thanks for the information on that.
Here is the info for MAC and adb install:
1. Download the latest Android SDK from Google: Android SDK
2. Extract the ZIP file to your desired location
3. To get ADB, you need to install the SDK: Installing the SDK
If you are not a developer and not planning to develop, then just download the following zip file containing only the ADB tool and proceed with the tutorial: ADB
4.Create an environment variable (Optional)
5.Open Terminal
6.Type cd ~ this will take you to your home directory
7.Type touch .profile this will create a hidden file named profile
8.Type open -e .profile this will open the file you just created in TextEdit
9.In the file, type export PATH=${PATH}:/pathToTheAndroidSdkFolder/android-sdk-mac_86/platform-tools
10.Save file, close TextEdit, Quit Terminal, and Relaunch Terminal
NOTE: By creating an environment variable you won’t need to cd to the Android/tools folder every time you want to run ADB
NOTE: If you did not create an environment variable, then cd to the AndroidSDK/platform-tools folder, then type ./adb devices
NOTE: make sure you have your phone plugged in and have USB Debugging turned on (Settings > Applications > Development)
source: Just google: how-to-set-up-adb-android-debug-bridge-in-mac-osx
ericm76903 said:
You are the Man!!
Since I use a MAC, I had to load adb there. But once that was done, I was able to do steps 7 and 8 with out error, and it now works. Thanks for the information on that.
Here is the info for MAC and adb install:
1. Download the latest Android SDK from Google: Android SDK
2. Extract the ZIP file to your desired location
3. To get ADB, you need to install the SDK: Installing the SDK
If you are not a developer and not planning to develop, then just download the following zip file containing only the ADB tool and proceed with the tutorial: ADB
4.Create an environment variable (Optional)
5.Open Terminal
6.Type cd ~ this will take you to your home directory
7.Type touch .profile this will create a hidden file named profile
8.Type open -e .profile this will open the file you just created in TextEdit
9.In the file, type export PATH=${PATH}:/pathToTheAndroidSdkFolder/android-sdk-mac_86/platform-tools
10.Save file, close TextEdit, Quit Terminal, and Relaunch Terminal
NOTE: By creating an environment variable you won’t need to cd to the Android/tools folder every time you want to run ADB
NOTE: If you did not create an environment variable, then cd to the AndroidSDK/platform-tools folder, then type ./adb devices
NOTE: make sure you have your phone plugged in and have USB Debugging turned on (Settings > Applications > Development)
source: Just google: how-to-set-up-adb-android-debug-bridge-in-mac-osx
Click to expand...
Click to collapse
good to know that it works :good: The adb config depends on your OS and you'll usually have it set anyway btw, does the battery at your rom has the graph indicated(the percentage of battery used for each apps, ex. screen - 60%, whatsapp - 4% and so forth)?
wcypierre said:
good to know that it works :good: The adb config depends on your OS and you'll usually have it set anyway btw, does the battery at your rom has the graph indicated(the percentage of battery used for each apps, ex. screen - 60%, whatsapp - 4% and so forth)?
Click to expand...
Click to collapse
Nope. It is showing "no data available"
ericm76903 said:
Nope. It is showing "no data available"
Click to expand...
Click to collapse
I had the same problem as well......... I wonder how can we solve this problem
original firmware
hello, can somebody provide link for original firmware of this MID 097Q1 or costum rom that really works? Mine get bricked and i flash rom from some other similiar tablet from china (M907), everything works except the touchscreen (it use LG IPS screen). Thanks in advance.

[Q] pppwidget on our tab??

Has anyone tested if it works on our tab or not....Plus does anyone know ho to find the power output of our tab's usb host mode????
I'll be geting my new usbotg cable soon so i'll also try n post the result....
For those who don't know about pppwidget, its a which allows you to use your 3G/2G stick(dongle) on your tab using the otg cable...
Market link
Read More about project here..
Hi thanks for this information, I tried this and it requires extra kernel modules (option, which is not included in cm10 kernel).
proudfoot said:
Hi thanks for this information, I tried this and it requires extra kernel modules (option, which is not included in cm10 kernel).
Click to expand...
Click to collapse
Can you please tell the steps you took and the result you got...This isn't supposed to need any modules except usb_modswitch which it already include....It works on CM10 nexus 7 too...Which dongle did you use???
Yup, it works it requires couple of modules not included in cm10 p5100 kernel, i already build the modules (see attachment) . Enjoy
I uses zte cdma modem, that modem requires 'option' module but most 3g/CDMA dongle uses this module.
You just need to copy those modules to /system/lib/modules.
edit: forgot to actually attaching the modules ~_~
Update: Vpn doesn't seem to work with pppwidget.
Update2: works, needs to manually set the gateway
cool...i'll get back to you in couple of days(waiting for my new otg cable)... can you please give the .c file for the modules also....still learning all this stuff so wlll be helpful....
kan_bleach said:
cool...i'll get back to you in couple of days(waiting for my new otg cable)... can you please give the .c file for the modules also....still learning all this stuff so wlll be helpful....
Click to expand...
Click to collapse
clone it from here -> https://github.com/cmenard/android_kernel_samsung_espresso10
as for compiling it follow/adapt from this tutorial -> http://stevechui.blogspot.com/2011/10/compiling-kernel-modules-tunko-for.html
Its giving 'port not found'....any solutions??
Did you directly connected the dongle to tab or used a powered hub???
kan_bleach said:
Its giving 'port not found'....any solutions??
Did you directly connected the dongle to tab or used a powered hub???
Click to expand...
Click to collapse
Directly, what the log (it should be in /sdcard/pppwidget/log/) say?
edit: actually with this -> http://www.amazon.com/Samsung-EPL-1PL0BEGXAR-USB-Connection-Kit/dp/B005518J6Q it's still count as directly right?
proudfoot said:
Directly, what the log (it should be in /sdcard/pppwidget/log/) say?
edit: actually with this -> http://www.amazon.com/Samsung-EPL-1PL0BEGXAR-USB-Connection-Kit/dp/B005518J6Q it's still count as directly right?
Click to expand...
Click to collapse
Yup that's direct
Checked the log...mod_switch successful, but loading option module fails...option.ko is in the correct folder..
I tried insmod but it says operation not permitted...
Tried su and then insmod but then it says failed (trying using terminal emulator)..
kan_bleach said:
Yup that's direct
Checked the log...mod_switch successful, but loading option module fails...option.ko is in the correct folder..
I tried insmod but it says operation not permitted...
Tried su and then insmod but then it says failed (trying using terminal emulator)..
Click to expand...
Click to collapse
Your option.ko probably not compatible with the kernel, try to do
Code:
strings option.ko | grep vermagic
uname -a
and compare both output, it should be similar.
also if you use insmod I think you'll need to insmod usb_wwan.ko first, because option.ko depends on that module, so it should be
Code:
insmod usb_wwan.ko
insmod option.ko
then, move the pppwidget to launcher and plug the dongle.
proudfoot said:
Your option.ko probably not compatible with the kernel, try to do
Code:
strings option.ko | grep vermagic
uname -a
and compare both output, it should be similar.
also if you use insmod I think you'll need to insmod usb_wwan.ko first, because option.ko depends on that module, so it should be
Code:
insmod usb_wwan.ko
insmod option.ko
then, move the pppwidget to launcher and plug the dongle.
Click to expand...
Click to collapse
Tried the command...output is the same...still not able to use insmod...
Log
Code:
USB_ModeSwitch log from Sat Oct 27 16:23:19 IST 2012
Raw args from udev: 1-1.4/1-1.4:1.0
Using top device dir /sys/bus/usb/devices/1-1.4
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product USB Storage
serial 000000000002
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.fff5
! matched. Reading config data
config: TargetVendor set to 19d2
config: TargetProductList set to fff1,fffe,ffff
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 14 -v 19d2 -p fff5 -f $configBuffer
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0xfff5
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="fff1,fffe,ffff"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/014 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:fff5
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x0a (out) and 0x89 (in)
USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x0a for message sending ...
Trying to send message 1 to endpoint 0x0a ...
OK, message successfully sent
Resetting response endpoint 0x89
Resetting message endpoint 0x0a
Could not reset endpoint (probably harmless): -34
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Reading attributes ...
All attributes matched
Mode switching was successful, found 19d2:fff1 (ZTE, Incorporated: ZTE CDMA Tech)
Now checking for bound driver ...
No driver has bound to interface 0
Module loader is /system/bin/insmod
Trying to find module "option"
Have you try to insert those modules manually first, before running pppwidget and plug-in the dongle? I think we use the same dongle, so it should works ~_~
anyway this is how i get this to work:
1. create directory /data/loca/modules/ on tab
2. move all those modules (option.ko, usb_wwan.ko, ppp_async.ko) to this directory.
3. su and insmod all those modules:
Code:
insmod /data/local/modules/usb_wwan.ko
insmod /data/local/modules/option.ko
insmod /data/local/modules/ppp_async.ko
5. move pppwidget to launcher and plug the dongle.
optional:
create this script and put it in /data/local/userinit.d/93loadmod directory
Code:
#!/system/bin/sh
/system/bin/insmod /data/local/modules/usb_wwan.ko
/system/bin/insmod /data/local/modules/option.ko
/system/bin/insmod /data/local/modules/ppp_async.ko
so it will load all those modules at boot time.
I am doing the same thing...but insmod is giving error
When i run the insmod command i get
insmod: init_module 'usb_wwan.ko' failed(Exec format error)
kan_bleach said:
insmod: init_module 'usb_wwan.ko' failed(Exec format error)
Click to expand...
Click to collapse
From a bit of googling it looks like your module is not build for your kernel (or even build for wrong architecture), what is your kernel? and where do you get the modules, do you compile it yourself or is it from somebody else?
try to do dmesg after you do insmod to see more information.
btw, the module that i have posted only works for p5100 and cm10 kernel (3.0.8-CM-g11fad65)
proudfoot said:
From a bit of googling it looks like your module is not build for your kernel (or even build for wrong architecture), what is your kernel? and where do you get the modules, do you compile it yourself or is it from somebody else?
try to do dmesg after you do insmod to see more information.
btw, the module that i have posted only works for p5100 and cm10 kernel (3.0.8-CM-g11fad65)
Click to expand...
Click to collapse
I used the modules you posted...I am using CMOC-10 kernel....Maybe that is the issue...But the kernels are supposed to be identical except for the OC and the governors feature...i am on 3.0.8-CM-gbd034d0
kan_bleach said:
gbd034d0
Click to expand...
Click to collapse
Yup that the problem, it needs to have the same extra version number even though it comes from same source. I guess I could compile it for you.
proudfoot said:
Yup that the problem, it needs to have the same extra version number even though it comes from same source. I guess I could compile it for you.
Click to expand...
Click to collapse
Please do...
kan_bleach said:
Please do...
Click to expand...
Click to collapse
Here, I hope it works because it comes from cm10 source, I only change the extra version to match yours.
proudfoot said:
Here, I hope it works because it comes from cm10 source, I only change the extra version to match yours.
Click to expand...
Click to collapse
Thanks i'll try and post the result...can you give me the github link for the cm10 kernal for our tab???

No wifi and bluetooth

Hi all,
I have a problem with wifi and bluetooth with my pf75aa3a xtrons radio unit. After try to install the upgrade to px5, when I go back to my px3 because compatibility issues, I am not able to enable wifi. It when I change wifi status from off to on, it changes to off automatically. I have seen that in advanced options I can't see my wifi mac address (I that this is the main problem).
Bluetooth is always enabled but undescoverable and the unit doesn't discovers any bluetooth enabled device.
Somebody had experienced this issue? (I have not seen it in forum)
Thanks in advance.
Ernest.
Enviado desde mi ONE A2003 mediante Tapatalk
Same issue at Erisin MTCD KGL RK3188 after flashing Malaysk ROM!
I have the same problem with MTCD KGL RK3188!
After flashing the appropriate Malaysk ROM, Bluetooth and Wlan not working ...
The field "Device Name" and "Password" in the Bluetooth settings are empty ...
If i go back to the stock Rom, the problem is still there...
Unfortunately, I also have not found a solution to the problem.
But there must be a solution :wütend:
Greetings from Germany!
Thanks for your Help guys!
No one has this problem?
you probably set bluetooth version to bc6 or bc8 in factory settings. set it to md725 which is the realtek chip used for BT and WiFi
zapedge said:
you probably set bluetooth version to bc6 or bc8 in factory settings. set it to md725 which is the realtek chip used for BT and WiFi
Click to expand...
Click to collapse
I have already selected md725. I have only 3 options, no/md725/parrot. No one works.
Enviado desde mi ONE A2003 mediante Tapatalk
internest said:
No one has this problem?
Click to expand...
Click to collapse
Hi
I discover that problem once with my XTRONS TB706APL unit when I was trying the Bluetooth telephone echo fix, changing the two files in system\bin folder (gocsdk and sdsdk) after reboot there was no Wi-Fi and Bluetooth as you described no password and car kit name. Strange part was that I have done this chang of files a lot of time without any problems. My solution was to try different files and suddenly on the original files there was Wi-Fi and Bluetooth again.
You could try to download these two files from https://forum.xda-developers.com/an...elopment/px5-solution-bluetooth-echo-t3638779 as a test
Basmand
basmand said:
Hi
I discover that problem once with my XTRONS TB706APL unit when I was trying the Bluetooth telephone echo fix, changing the two files in system\bin folder (gocsdk and sdsdk) after reboot there was no Wi-Fi and Bluetooth as you described no password and car kit name. Strange part was that I have done this chang of files a lot of time without any problems. My solution was to try different files and suddenly on the original files there was Wi-Fi and Bluetooth again.
You could try to download these two files from https://forum.xda-developers.com/an...elopment/px5-solution-bluetooth-echo-t3638779 as a test
Basmand
Click to expand...
Click to collapse
It doesn't works. I have tested from a to d :crying:
Is there any procedure to repartition de device? In mobile phones is usual, but I have not seen with head units.
Thanks for all!
With me the same, unfortunately does not work. Maybe you should try to flash the firmware via the RockChip BatchTool. I have unfortunately also found no other solution. I do not know where the error is.
any news? i have the same problem
Ozi021 said:
any news? i have the same problem
Click to expand...
Click to collapse
No, my wifi and bluetooth still death... I'll try to flash with the rockchip tool when I have a litle bit of time.
Enviado desde mi ONE A2003 mediante Tapatalk
The seller sent me an update , I will try in this week , if it works I will tell it
Do we have any solution to solve this problem? I have the HA2100-V600 Universal and just updated the MCU to V2.59. Suddenly bluetooth stopped working. Wifi is working. I checked the factory setting. BT is set to WQ_BC8.
EDIT: After hours of troubleshooting. Turns out the unit I have isn't BC8 as described in the store. SD-968 is what BT module is inside my headunit.
I'm having similar problems, no BT or WLAN after px5 uppgrade for Joying 10.1" HU. The unit with px5 is now really fast (with px3 it was almost unusable slow) but without BT or WLAN PX5 is no go. I have updated the latest sdsdk968 android firmware and tried every bluetooth option from factory menu (MD725 was as original setup when I started the HU with px5)...
okvp said:
I'm having similar problems, no BT or WLAN after px5 uppgrade for Joying 10.1" HU. The unit with px5 is now really fast (with px3 it was almost unusable slow) but without BT or WLAN PX5 is no go. I have updated the latest sdsdk968 android firmware and tried every bluetooth option from factory menu (MD725 was as original setup when I started the HU with px5)...
Click to expand...
Click to collapse
I opened the HU and found out that the BT and WLAN in the Joying 10.1" PX3 unit is Realtek RTL8723BU which is compined WLAN and Bluetooth chip. There is no option for this chip in factory menu just: MD725, WQ_BC5-6-8, Parrot_FC6000T and SD-968. Adroid drivers for this chip can be found from internet, but I have no idea how to install them in HU, could somebody help me please?
okvp said:
I opened the HU and found out that the BT and WLAN in the Joying 10.1" PX3 unit is Realtek RTL8723BU which is compined WLAN and Bluetooth chip. There is no option for this chip in factory menu just: MD725, WQ_BC5-6-8, Parrot_FC6000T and SD-968. Adroid drivers for this chip can be found from internet, but I have no idea how to install them in HU, could somebody help me please?
Click to expand...
Click to collapse
MD725 is an option for RTL8723BU.
There are two variants of MD725 handling on these head units. First is handling via sdsdk process, second is handling via gocsdk process. Both are loading /system/lib/wb.ko module (driver) to handle MD725.
My MD725 can be controller either by gocsdk or sdsdk. The best way would be to check whether same binary is executed to handle your MD725 module on PX3 SoC and PX5 SoC.
If you do not want to go back to PX3 try to do:
Root your device
Install Termux from play store
Run commands ps | grep sdsdk and ps | grep gocsdk
If 1st command gave you more lines of output it means that MD725 is handling via sdsdk:
rename sdsdk located at /system/bin to sdsdk_backup
rename gocsdk located at /system/bin to sdsdk
If 2nd command gave you more lines of output it means that MD725 is handling via gocsdk:
rename gocsdk located at /system/bin to gocsdk_backup
rename sdsdk located at /system/bin to gocsdk
f1x said:
If 1st command gave you more lines of output it means that MD725 is handling via sdsdk:
rename sdsdk located at /system/bin to sdsdk_backup
rename gocsdk located at /system/bin to sdsdk
If 2nd command gave you more lines of output it means that MD725 is handling via gocsdk:
rename gocsdk located at /system/bin to gocsdk_backup
rename sdsdk located at /system/bin to gocsdk
Click to expand...
Click to collapse
But what about difference between gocsdk and sdsdk ?
f1x said:
MD725 is an option for RTL8723BU.
There are two variants of MD725 handling on these head units. First is handling via sdsdk process, second is handling via gocsdk process. Both are loading /system/lib/wb.ko module (driver) to handle MD725.
My MD725 can be controller either by gocsdk or sdsdk. The best way would be to check whether same binary is executed to handle your MD725 module on PX3 SoC and PX5 SoC.
If you do not want to go back to PX3 try to do:
Root your device
Install Termux from play store
Run commands ps | grep sdsdk and ps | grep gocsdk
If 1st command gave you more lines of output it means that MD725 is handling via sdsdk:
rename sdsdk located at /system/bin to sdsdk_backup
rename gocsdk located at /system/bin to sdsdk
If 2nd command gave you more lines of output it means that MD725 is handling via gocsdk:
rename gocsdk located at /system/bin to gocsdk_backup
rename sdsdk located at /system/bin to gocsdk
Click to expand...
Click to collapse
Thank you for an answer!
Finally I got time to try your guide. I tried to assemble the apps but Termux requires internet connection to be fully assemled, I could not find packages to assemble it fully from usb stick. Kingo root can be assembled from PC but I cant get usb debugger mode on, 7 taps to build code is not working.
For the internet connection I also tried couple of old 3g/4g dongles but no success.
Any Ideas?
Hello
someone could test update from px3 5.1 to px3 7.1 2gb ram 16 gb rom?
would i have same problem for BT and WiFi as px5?
thank you
f1x said:
MD725 is an option for RTL8723BU.
There are two variants of MD725 handling on these head units. First is handling via sdsdk process, second is handling via gocsdk process. Both are loading /system/lib/wb.ko module (driver) to handle MD725.
My MD725 can be controller either by gocsdk or sdsdk. The best way would be to check whether same binary is executed to handle your MD725 module on PX3 SoC and PX5 SoC.
If you do not want to go back to PX3 try to do:
Root your device
Install Termux from play store
Run commands ps | grep sdsdk and ps | grep gocsdk
If 1st command gave you more lines of output it means that MD725 is handling via sdsdk:
rename sdsdk located at /system/bin to sdsdk_backup
rename gocsdk located at /system/bin to sdsdk
If 2nd command gave you more lines of output it means that MD725 is handling via gocsdk:
rename gocsdk located at /system/bin to gocsdk_backup
rename sdsdk located at /system/bin to gocsdk
Click to expand...
Click to collapse
I installed to my Joying 10,1" unit Malaysk rom with the help of system recovery menu. With Malaysk rom I could use pre installed Root Explorer and I renamed sdsdk to gocsdk and then when it didn't work, gocsdk to sdsdk (also with restart) couple of times but I still cant get wlan or bluetooth working. What should i do to fix the problem, could i use drivers from px3 rom?
okvp said:
I installed to my Joying 10,1" unit Malaysk rom with the help of system recovery menu. With Malaysk rom I could use pre installed Root Explorer and I renamed sdsdk to gocsdk and then when it didn't work, gocsdk to sdsdk (also with restart) couple of times but I still cant get wlan or bluetooth working. What should i do to fix the problem, could i use drivers from px3 rom?
Click to expand...
Click to collapse
Here you have WLAN module files from JY PX3.
first rename (if exist) /system/lib/rtl8723bu_wlan.ko to rtl8723bu_wlan_backup.ko and /system/lib/wlan.ko to wlan_backup.ko then copy files from zip archive to /system/lib

Question Z-Flip3 dead?! Data Recovery possible?

Hello,
I opened this thread yesterday => https://forum.xda-developers.com/t/unable-to-pair-to-smart-watch-after-root.4541453/
So I tried to patch the Bluetooth libary today by entering the following 4 lines in a terminal window.....
$ su
$ mount -o remount,rw /vendor
$ for i in `grep -lr 'security.wsm' /vendor/etc/vintf`; do [ ! -z $i ] && sed -i "$((`awk '/security.wsm/ {print FNR}' $i`-1)),/<\/hal>/d" $i; done
$ mount -o remount,ro /vendor
Then I wanted to reboot the phone. But I just saw the Samsung Logo on black ground. Ok... Sometimes it takes a bit longer so I waited over 2 hours. Nothing happened.
Since the taken photos are very important to my girl I flashed the newest firmware (I used the home file instead if CSC to keep the user data) hoping it would boot up normally and she could rescue her photos. But It doesn't wanna boot. Android recovery menu still work but I can't "mount /system" => "E:[libfs_mgr]Error updating for slotselect"
Is there a way to rescue the data (photos) before I do a factory reset?
Best regards
Manuel
Oh no!
you've broken rule number one.. always do a backup first (google/samsung/swiftbackup/pc etc) especially when doing something a little bit risque like flashing scripts.
I'm guessing you don't have TWRP recovery installed or able to use ADB?
There's loads of data recovery tools online, most (if not all) say they're free but they're not. You'll get to the last part of the recovery process then ask you to pay big bucks to use their service (I've seen $900 per year subscription fees!)
Your best bet now is to take it to your local phone shop and ask them to do it (probably cost about £20)
When you are all up and running again I saw this tip that might fix your bluetooth connection prob (it's from the Fold 3 forum so it should work on our Flip 3)
android 13 bluetooth issues fix
Hey all, I have had issues with my smartwatch since updating to android 13, and I have seen others having simmer issues. I have found a fix! Go to Settings > Apps> turn on Show system apps Scroll to Bluetooth Tap Battery Set it to Unrestricted...
forum.xda-developers.com
You can try reflashing the same firmware version without root to see if your phone boots up, make sure you flash home_csc to retain data with Odin
Posso tentar te ajudar! Eu tenho a ferramenta Chimera que posso te emprestar. E tentar trazê-lo de volta

Categories

Resources