I am having an a chronic bluetooth issue, which i failed to resolve. A help in this matter will be deeply appreciated.
The issue started after the February security update (at least thats what i observed). I was trying to pair my device to an external speaker (Beats Pill) and i had a hard time doing so; and i deleted previously paired devices (mainly my car bluetooth). The attempt was not successful. Then, i tried to pair the device to my car again, and i only see a code (instead of the car name) in the bluetooth search. When trying to connect, i got the message (Can't communicate with XXX device).
After multiple failed attempt, i decide to dive into Unlocking, rooting, and trying different ROMs hoping it would solve the problem. I literally flashed all available ROMs for the device with no use. I suspected it was a hardware issue, but my phone can connect to my Moto 360 with no problems.
I am puzzled with this issue to the extent of considering changing the phone. I use car bluetooth extensively as i spent much time commuting to work. If someone can help with the issue i would be gratefully. From reading around the forum, i think the system app "Bluetooth Share" is responsible for such function; could it be possible that i need a modified version of it, or maybe flash a radio of some sort??
Have you tried a factory reset or a custom ROM? BT pair works fine on my 1575. I highly recommend the TrueMM ROM.
Before unlocking the bootloader and flashing different ROMs, i did a factory reset with no use. Currently, i am running TrueMM ROM, great ROM....but still no bluetooth connection.
Have you tried the latest CM13. Thought I saw something about a Bluetooth fix in the thread there.
MdSaif said:
I am having an a chronic bluetooth issue, which i failed to resolve. A help in this matter will be deeply appreciated.
The issue started after the February security update (at least thats what i observed). I was trying to pair my device to an external speaker (Beats Pill) and i had a hard time doing so; and i deleted previously paired devices (mainly my car bluetooth). The attempt was not successful. Then, i tried to pair the device to my car again, and i only see a code (instead of the car name) in the bluetooth search. When trying to connect, i got the message (Can't communicate with XXX device).
After multiple failed attempt, i decide to dive into Unlocking, rooting, and trying different ROMs hoping it would solve the problem. I literally flashed all available ROMs for the device with no use. I suspected it was a hardware issue, but my phone can connect to my Moto 360 with no problems.
I am puzzled with this issue to the extent of considering changing the phone. I use car bluetooth extensively as i spent much time commuting to work. If someone can help with the issue i would be gratefully. From reading around the forum, i think the system app "Bluetooth Share" is responsible for such function; could it be possible that i need a modified version of it, or maybe flash a radio of some sort??
Click to expand...
Click to collapse
I'm assuming it's an XT1575? Download the appropriate firmware file from HERE. The firmware number that matches "settings> about phone> build number". Extract the BTFM.bin file and the flash it via fastboot:
Code:
fastboot flash bluetooth BTFM.bin
Then reboot. That is the only idea I have, reflash the bluetooth firmware/drivers.
Related
My Trinity device is not recognized by any of my 3 pc's using any of USB ports. The problem started when I wanted to try a different ROM. I currently have 20070418_RUU_Trinity_LVSW_WWE_1.25.0.8 installed. I wanted to install img-32424-mUn_1_25_AKU3_5 but during the reboot after the ROM transfer the connection failed for the USB connection, after which I gave up and thought well let's try again and soft resetted the device. However I was never able to get a Active Sync session going again. The OS is still booting fine so I feel I am trying to fix something which is not entirely broken. I also tried the suggestion for flashing from SD card, but that did load the TRINIMG.nbh file as I hoped (and read) it would be loading. So I have a IR connection and possibly a bluetooth connection (I left my bluetooth module at work so I cant test this) Will this be my free ticket out of jail? Thanks for your input
You might want to ask this on the upgrading subforum, where all the people who flash their trinity are. This isnt the place for this discussion.
Though personally I'd say no, IR is slow and unreliable, given the length of time it would take to flash a 50mb ROM file, the chances of it breaking halfway through are pretty high, which would brick your device totally.
Try finding a mate's PC that works and doing it from that?
You can't flash using IR or BT because the drivers for those are removed during the flash process.
Post a query in the Upgrading section for info on how to set the device into Bootloader mode, to avoid the need for activesync.
OK will post it in the correct group. Thanks I wont flash it with IR. I already had a suspicion it would not be a happy ending.
Hello.
I'm sorry if it has been already discussed before, but i couldn't actually find a solution for this in here.
I got a brand new U8800 (2.2). The WIFI was working properly.
So i installed the official 2.3.5 version required to get Aurora installed. At this time i couldn't enable WIFI anymore. I did try to wipe everything more than once before and after upgrading, same story.
I saw people saying that it might be a missed IMEI problem, but i didn't lose it, but the MAC addresses for WIFI and BT are "Unknown".
After root the phone i tried to set the MAC manually using terminal emulator, and it didn't work either.
Upgrading to Aurora also didn't solve the problem, still can't get either Wifi or BT enabled.
Is there anyone who could actually solve it?
Thank you
If the MAC address for wifi and bluetooth shows 'unknown' that indicates a configuration problem because of a somehow faulty update. I do not know how to solve this problem, but in case there is no quick solution I suggest that you install the official Huawei-Gingerbread-ROM and have the unit returned then.
It is not likely that this problem occurs on the next device too - as long as the file you downloaded (the huawei update) is not corrupt. As long as you can unzip it without any error message the file should be alright and the update process should not break anything. If you know that your harddrive is very old and you believe that this could be the problem, get this checked out.
XphX
search in the forum i think there is a way to put again mac adress again with some tools... but 4 that you need to have a backup of them...
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.
Hi,
I open this thread because I detected this issue after doing a downgrade of the STOCK ROM.
- After apply the OTA for NPNS25-137-33-11 (RETEU) and return to NPNS25-137-33-5 I start to see very annoying troubles. Sometimes, when the WIFI state changes (mainly when stating it, or enable hotspot mode, or chaging from one to other network) in this case the phone hangs. The only solution is a hard power-off. Also I noticed that the WIFI range is very small.
I listen before that some users have troubles with WIFI. I haven't detected any problem before, only now. My assumption is that the OTA has updated some partition with RADIO data. Then, now the driver is unstable.
Perhaps some others have a similar problem because an upgrade using a flash backup and not upgrading their RADIO partitions.
Please, share your experiences to see if the problem is widespread?
Thank you!
My device was fine before Rooting importantly the Bluetooth stack was was also fine. However, after rooting all BT Pairings are lost across reboots etc. Just turning BT off then on again causes the issue making it necessary to delete and re-pair every time the device starts. over the last week i've ran various tests, and concluded the issue lies with either the hardware or the stock image i got from Sammobile.com. Being a noob, during my experimentation i have had to flashback to the stock image on several occasions. Only discovering the Bluetooth issue when putting my work to good use and using the device.
Yesterday i tested the theory. Flashed it to stock, booted to OS and skipped all the config disabled WI-FI and DATA so it couldn't pull updates. Tested Bluetooth and the issue is present. The Bluetooth did work correctly before i started rooting it. This is unlikely a hardware issue so can only assume its an issue in the build i have from Sammobile. If any of you have access to a stock pre-installed rom that works that they could give me access to, so i can do some testing or indeed any advice it would be very much appreciated.
Device = Samsung Galaxy Tab S4 (SM-T835 on EE)
PDA = T835XXU2ARJ3
CSC = T835OXM2ARJ3
Many thanks
Colin