Database Develop

my phone is not supporting any bluetooth

i have firm ware version 1.5 and every bluetooth i try on my phone doesnt work can someone help me

I got the same problem after rooting device. I use image RC29 and JACKHeroski ROM. But the bluetooth function is used by me rarely.

i really need my bluetooth im almost always in my car ... i need help
and i cant use my bluetooth!!!!!!!!!!!!!!!!!!

bluetoo has not work on jack yet
you guys need to know that , blutoo just has not work on jackhero.
bluetoo work on cyanengen, jf1.5.

first of all,
you need to explain more than your running 1.5
is your phone rooted.
have you tried rebooting your phone / wipe your phone
are you using any custom roms etc.

yes i did all of that rebooted anf=d everything but my bluetooth does not work
an my phone is rooted

excuse me sir.
ok, a suggestion. goto quicklinks and edit your sig. let us know what rom, radio and spl you are running. second, do you have adb? no? get adb installed so you can run logcat and we can get an idea what exactly is going on with your device. third: what is the history of your phone? what process did you follow to get where you are now? when is the last time you wiped? etc. etc. etc.
if you have questions about the aforementioned items, search. apply google-fu accordingly.
We can't help if we don't have something tangible to work with. internets are not magic, simply shouting "my stuff is b0rked" will not automagically repair your problem. harry potter is an iphone user. you are not harry potter, and that phone in your hand is no iphone.
i'd love to help you but simply cannot until you give me something firmer to work with.

Define doesn't work. Does it not connect? Does it seem to connect then you lose all audio? Does it stab you in the face? What does it do, exactly. Have you updated your radio?

This is a "my car doesn't work, how do I fix it?" kinda thread..
We need info in order to help you!
Did it work before?
what have you done in order to break it?
What are the errors?
What version af ROM are you running?
What radio version are you running?
etc etc etc..
BTW bumping the thread doesn't help either, it just will make a nice padlock appear on the thread, just like by magic..
And I moved the thread from DEVELOPMENT (!) to Q&A..

Try using a different ROM as suggested. The _Hero_ Roms don't support BT yet. If you need it you'll have to switch to JF, Cyanogen or Haykuro's etc. ROMs.

Just like everyone else said. And one more sugestion have you updated your radio.

how mean. thanks
look every one is being so mean. n e ways when i say it doesnt work i mean that it says its connected to bluetooth but u cant hear anything when u send or receive a call and for sure i know its not the bluetoth because i have 5 different ones and none work. i dont know if it have ever worked because i just started using the bluetooth . and well ill try finding our the rest of the info because i dont do the updates my self only sometimes and i dont know all them numbers u guys are asking for what i know are the numbers i put in the other messages. but its ok thanks to those who helped...

ok... seems like we got some info here.
It seems that someone else has been modding your phone for you. Installing custom ROMS is nothing to be taken lightly, you should really research things a bit to get a better understanding of how your phone actually works.
I wasn't trying to be mean, please understand that you posted a help request in a forum designated for development of new applications and customization of the system images that make up the operating system you see when your phone boots up. Posts like these have become a growing problem lately and many users here are getting frustrated, myself included.
First of all, goto settings, about phone.
Write down the following information:
Model Number
Firmware version
Baseband version
Kernel Version
Mod Version (if its there)
Build Number (if its there)
Post that info in a thread in Q&A, where this thread belonged to begin with and maybe we can actually get somewhere.

Model Number:x201
Android version : 4.2.2
Baseband version: moly.wr8.w1315.md.wg.mp v4.P1, 2013/11/09 14:19
Kernel version: 3.4.5 [email protected] #11
Custom build version: ensec 20140318
my bluetooth wont connect with my iphone 5? it says "connection unsuccessful, Truesmart is not supported
any suggestions??
thanks

[Q] At wits end!! Please Help.

OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!

You could try on another computer which doesn't run Vista

tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...

His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..

tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.

Can't find the right solution to Bluetooth not starting.

I have followed some threads regarding Bluetooth problems, but could not fix it.
I tried:
1. Flashing a new kernel (TheAceKernel-beta4) using the overclocked option when prompted.
2. Copying the files from Bluetooth.zip in Nooblar's post (http://forum.xda-developers.com/showthread.php?t=1657310&highlight=bluetooth)
to /system/etc/bluetooth folder in the root directory.
3. Tried but could not understand how to use the information and files for "CyanogenMod / android_device_samsung_cooper" on the following link (https://github.com/CyanogenMod/android_device_samsung_cooper) which seam to be related to the problem I have and are provided in the process I followed when flashing a new ROM to be able to get more internal space (http://forum.xda-developers.com/showthread.php?t=1543521)
I'm ok with how the phone works in general. My only problems are I cannot connect to Kies and BT will not start. The first I don't mind, but I use the BT to connect to the handsfree while driving the car and I use it a lot. Without it I'm bound to be one of those one-hand drivers out there who is going to crash into your car, so you better help me fix this... jajaja
I have a Samsung Ace GT-S5830LUBKPA with Android 2.3.7, Build Gingerbread
Installed:
- recovery-clockwork-5.0.2.6-galaxyace-fix
- AceGingerRoot
- CronMod-INT2EXT+_signed
- cm-7-20120930-NIGHTLY-cooper
- gapps-gb-20120317-237-signed
- cm-blackhawk-kernel and then TheAceKernel-beta4
Hope someone knows where I can find the solution if there is any. I am trying not to go through the hole process of reinstalling a different ROM since I barely made it last time and I don't want to mess up my phone again. But if that is the only solution, I'll do it.
Thanks!!

Solved! thanks anyway.
mushatrusha said:
I have followed some threads regarding Bluetooth problems, but could not fix it.
I tried:
1. Flashing a new kernel (TheAceKernel-beta4) using the overclocked option when prompted.
2. Copying the files from Bluetooth.zip in Nooblar's post (http://forum.xda-developers.com/showthread.php?t=1657310&highlight=bluetooth)
to /system/etc/bluetooth folder in the root directory.
3. Tried but could not understand how to use the information and files for "CyanogenMod / android_device_samsung_cooper" on the following link (https://github.com/CyanogenMod/android_device_samsung_cooper) which seam to be related to the problem I have and are provided in the process I followed when flashing a new ROM to be able to get more internal space (http://forum.xda-developers.com/showthread.php?t=1543521)
I'm ok with how the phone works in general. My only problems are I cannot connect to Kies and BT will not start. The first I don't mind, but I use the BT to connect to the handsfree while driving the car and I use it a lot. Without it I'm bound to be one of those one-hand drivers out there who is going to crash into your car, so you better help me fix this... jajaja
I have a Samsung Ace GT-S5830LUBKPA with Android 2.3.7, Build Gingerbread
Installed:
- recovery-clockwork-5.0.2.6-galaxyace-fix
- AceGingerRoot
- CronMod-INT2EXT+_signed
- cm-7-20120930-NIGHTLY-cooper
- gapps-gb-20120317-237-signed
- cm-blackhawk-kernel and then TheAceKernel-beta4
Hope someone knows where I can find the solution if there is any. I am trying not to go through the hole process of reinstalling a different ROM since I barely made it last time and I don't want to mess up my phone again. But if that is the only solution, I'll do it.
Thanks!!
Click to expand...
Click to collapse
Solved! thanks anyway.

[support] OP3T will not turn on at all after flashing OOS Beta 9 after a soft-brick

Hello everyone. I updated my rooted OP3T (with TWRP installed for recovery) to OOS 4.0.1(I think? I know for sure it was 4.0.x) a week or so ago using a VPN as I live in the US and today I got the new update for whatever version that was about 30 mb, and after I rebooted I got stuck booting into TWRP so I followed the guide linked underneath here and got up to step 12 (flashing beta 9) and after swiping to restart my phone will not turn on in any way, shape, or form. Whenever I plug it in/unplug it from my computer I'll still get the Win10 device connected/disconnected sound and if I hold the power button for long enough while it's plugged in I'll get another device connected sound or disconnected, usually followed by the opposite sound. There doesn't seem to be a pattern to the sounds, but if anyone knows what's happening I really need help with this as it's the only phone I was able to afford and if it's bricked I don't know if I have the money for another one. Thanks
https://forum.xda-developers.com/showpost.php?p=70102813&postcount=5

Lol no wonder your phone doesn't work anymore. You flashed the beta to the OP 3 onto your 3T. Use this to fix your phone.
Edit: Sorry if this was of use to some people when it was deleted.

Just Passing By said:
Lol no wonder your phone doesn't work anymore. You flashed the beta to the OP 3 onto your 3T. Use this to fix your phone.
Click to expand...
Click to collapse
I tried to use that thread, but my phone wouldn't show up underneath Unknown Devices, in fact unknown devices would never come up at all. my pc is still in test mode from this :/

Don't worry if it doesn't appear under unknown devices. Just use the tool. A lot of what the instructions say is unnecessary. Just make sure that when you plug in your phone that one of the ports becomes "active" (I haven't had to use this tool in months, so I'm not sure exactly what it's supposed to say exactly) and press the start button.
Edit: Sorry if this was of use to some people when it was deleted.

ok. I 'll download the tool and get back to you after trying it.
edit:that worked! you are my new favorite person.
thank you so much )))))))))

Deleted

WAIT
Just Passing By said:
Deleted
Click to expand...
Click to collapse
WHY IS THIS DELETED? IM having the same problem what did you do please save me as well

Sounds like you flashed the wrong version of Oneplus 3 firmware to your phone. Do you have a 3 or a 3t? If you flash the incorrect one you will get exactly the unbootable state you describe. In that case you will have to use Qualcomm MSM Downloader tool to flash back the correct ROM and firmware partitions to get it running again. Just download the correct MSM recovery package for your phone and follow the instructions in the thread.

Question SM-G998B Bricked

Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?

Seems different?
Well I would try Odin and an official ROM anyway, no pain no gain right?

What exactly were you doing before this occured?

You try the old delete usb driver, restart computer, install usb driver then restart computer and restart phone and try again.

SirDigbyCC said:
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Click to expand...
Click to collapse
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something

flairepathos.info said:
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
Click to expand...
Click to collapse
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.

To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.

SapphireEX said:
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
Click to expand...
Click to collapse
Oh I see the issue now you need to wipe all and re-flash full firmware when flashing the device using Odin
if that doesn't work flash the partitions with the kernel drivers and system partition
I had a similar issue with my current mtk phone and it was because the boot/preloader partition bilieved i had flashed the wrong firmware for my device(it was just a different firmware release for my phone
Just to be safe some ota updates break wehn the bootloader is not unlocked (when updationg from say android 8(oreo) -9(pie)...)
especially because of code errors in the update, cache/vendor partition being too full after downloading update

SirDigbyCC said:
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
Click to expand...
Click to collapse
If you're telling the truth, and it wasn't a bad module / firmware / etc, it is possible your eMMC got too hot and melted some solder. I've seen it happen before.
You'll want to diagnose everything you can. If you're on Windows, does it recognize a USB device or a COM device? If linux, does lsusb return anything useful about it?
If it's not being detected, and multiple wires doesn't change anything, are you able to access sahara mode / download / DFU? If so, go to those and try again.
If you are lying, and this is a bad firmware flash / OTA brick, you'll need to tell us otherwise we'll be going in circles.

So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?

SirDigbyCC said:
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
Click to expand...
Click to collapse
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.

SapphireEX said:
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
Click to expand...
Click to collapse
I appreciate the vote of confidence, I don't think it was an OTA update that did it this time, it usually requests to do updates which I highly doubt I would have pocket approved through a flip case only short after pressing play on Spotify.

So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!

SirDigbyCC said:
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
Click to expand...
Click to collapse
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!

shriom_manerker said:
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
Click to expand...
Click to collapse
It was free, turned out to be a hardware issue internally so I think covered by warranty as I have Care+ which has an excess of £40 which they didn't make me pay. They also replaced the screen due to some dead pixels, and the battery! Happy days!
Thanks all for your suggestions!