So I got a re-certified att note 3 about a year ago, I rooted it and have been running on dynamic kat ever since. About a month ago I randomly lost the ability to turn on wifi, it was just completely grayed out. I tried a bunch of things and nothing worked until I wiped cache, dalvik, system and data then re-installed the latest version of dynamic kat. I eventually got wifi back but ever since then my bluetooth range has been HORRIBLE, I have no issues pairing with devices but I literally have keep my phone within 2.5 of what ever speakers/headphones I'm paired with. I can't even put the phone into my pocket while I have BT headphones on, if I do it for a few seconds the music will stop and restart if I pull the phone back out, if I leave the phone in my pocket for more than say 20 or 30 seconds the connection just disconnects. Just last night I decided that I would try to go all the way back and went to install the stock rom, in the process I soft bricked it while wiping everything again cache, dalvik, system and data. I'm now finally back all the way to stock and I'm still having the same BT issues. I'm starting to think my hardware is bad?
1) anyone have an ideas?
2) if there's a consensus that it is a hardware issue, any one ever replace the radio hardware before?
3) if #2 is too complicated any thoughts on where to get it repaired? do i have to be without a phone for a while?
thanks in advance
What process did you use to return to stock? If you used Odin and the home file that might be your problem. It doesn't wipe before installing. If that's what you did try flashing all 4 files in their respective slots for a full wipe and restore.
440bro said:
What process did you use to return to stock? If you used Odin and the home file that might be your problem. It doesn't wipe before installing. If that's what you did try flashing all 4 files in their respective slots for a full wipe and restore.
Click to expand...
Click to collapse
I used Odin with the 4 individual files and also use the pit file with the repartition box checked, it did a wipe but I just wiped everything again and tried again still no dice. Also just did another full wipe again including system & data and went to DK6.1.3 again. still no good
Thanks for the idea though!
Anyone have any clue if the internal BT antenna is soldered right to the board or if it's a clip on wire? I'm tempted to open it up and see if there's maybe a bad connection.
Related
Hello everybody.
I am having serious trouble with my phone and I was hoping some of you might be able to help me out.
I just bought my SGS 3 days ago. It came with android 2.1.1 eclair installed.
I had read that that version was not the best ( the first thing I saw when I opened the phone actually was an error screen, and the lag was horrible) so when I got home I decided to try and upgrade it using the official software for it (Kies).
Unfortunately Kies would simply disconnect my phone when I told it to upgrade, after which it would ask me to upgrade again >.>
So I decided to use Odin to flash one of the newer 2.2.1 versions.
I flashed a 'JS3' version with a repartition to 803 pit , but it crashed after rebooting with the dbdata error (which as I learned later was caused by not flashing a full firmware).
I flashed JPU after which worked great. It was fast and responsive.
However my phone kept crashing. Whether on standby, using apps, or just trying to dial a number, it would freeze, start vibrating, and sometime reset, other times just stay frozen until I force shut down it from the power button.
I flashed JS5 afterwards, with full cache clearing, factory reset etc. Still crashed.
Then I tried flashing Darky's 9.2 Ressurection. Loved it but I couldn't even set up my google account because it crashed constantly.
Then I went back to what I believe is the current official version for my location and carrier (Vodafone Romania), JP9 .
After flashing it didn't crash, but after a while (one night), it started crashing like crazy, even wound up with weird gray lines and a freeze in the morning.
I was hoping someone here might know what is wrong with it. I already sent it back to be serviced but I am thinking maybe I broke it somehow and would like to know how so I don't do it again.
The phone is network locked, which I later learned is usually a bad thing for flashing, unfortunately I didn't know about that when I started.
well first of you want to remove the network lock so try these:
http://forum.xda-developers.com/showthread.php?t=761045
http://forum.xda-developers.com/showthread.php?t=913681
next step is to register on www.samfirmware.com (its free) and here is where you will get all the latest official firmwares from samsung..
what you want to do is download (XWJS5) with all 3 files and PIT and flash that through odin with RE-PARTITION..
Before you do that, put your phone into recovery mode (volume up + Home button + Power button ) and do a factory reset / wipe cache ect...
so when you have done that and flashed the new firmware. let me know what the outcome is..
another thing.. ALWAYS MAKE SURE KIES IS CLOSED.... EVEN IN THE ICON TRAY... AND MAKE SURE DRIVERS ARE UP TO DATE.
other than that you shouldn't have any problems
hi, thanks for the advice.
I already did most of that however. I did a factory reset numerous times, and I also did a full repartition flash more than once, to no avail.
I am waiting to get it back from warranty service now but I am wondering what went wrong.
Was it broken when I bought it or did I damage it somehow by trying to flash it while network locked ?
flashing with network lock wouldnt make everything force close. the worst thing that could happen when flashing with network lock is not picking up a signal and possible IMEI corruption.
i think you may have just flashed the wrong ROM, it happens to us all, but the more you do it the more experienced you become and you soon learn methods to restore things..
dont worry too much it will be fine when it comes back from samsung, just be sure to read up properly if you have any doubts.. or ask a question first you will get a reply quicker than you can Unbrick your phone..
My phone seems to hate the 803 pit file. Lots of force closes when I used it. Try using 512, see if that works any better.
Hello all,
please forgive me first of all because I've had very little sleep due to this issue. And its a long thread, but more detail is better generally I believe.
First, some background, and unfortunately, it starts with my wifes phone.
My wife has a Galaxy S GT-i9000 on Orange in the UK. She has had it, probably about a year maybe at most. She has a few apps that she has downloaded but nothing major and on first looks when I got it nothing I expect would cause this issue, just facebook etc.
My wife came home and said, my phone keeps coming up with a message saying force close. Ahh, I thought, some apps gone nuts, but alas, it appeared to be many apps including Maps, Google Upload (I assume this is a system process), Facebook Katana and many more, probably about 20 Force Close messages pop up one after the other and it lags whilst trying.
Odd, I thought, I also noticed the icon for one of the apps on her homescreen had changed to the default White and Green one with the android on it.
I suspected something had gone wrong (obviously), I asked if she had rebooted it and she said she had. So, I rebooted it again, just incase. Same problem.
I then thought it might need an update, it was running official Kies 2.3.3 (or was it 2.3.4, I forget) so I plugged it into my netbook and ran Kies, had to update that as it didn't have the latest application update. I then started the firmware update, after backing up the phone using Kies.
Halfway through the update, Kies popped up a message saying something went wrong and that I had to unplug the phone, take out the battery and reboot. Odd, I thought as the phone was telling me to not doing anything. I waited a minute, nothing further happened, so I did this. Then I got the Black Screen of Death with the phone, the dots and the computer screen.
Crap!!! I thought, I managed to get into Download mode, and reflash it using what I believe was an official ROM using Odin. I then rebooted, and found that it STILL had the data on it and it STILL was doing the force close. At least I had it back to "working" though so I was mildly happy.
I then did a factory reset using the menu system, erased the USB storage (there is no external SD card in her phone) and rebooted, still force closing but prompting me to setup again. Weird. I went through the setup slowly, as every second or so a force close would popup, then when I completed the setup (which still had the wifi settings, account settings etc in it) the System Setup crashed with Force Close. I then rebooted and got to the Home Screen, but still crashing.
I rebooted and used the recovery screen to clear the cache and factory reset, despite the warnings I will lose everything, nothing was wiped.
I tried to update using Kies again but it tells me that the firmware/device is not supported. I am now trying to see if I can use Odin to install a Kies supported firmware. So that I can then try an update using that again.
Anyone got any suggestions, at present, my thoughts are, I was going well within the realms of warranty up until I reflashed it using Odin to try and get back in as I'd only used Kies to update and the issue "just started happening" without my missus doing anything.
There are no signs of damage on the phone and she tells me it was just sat on her desk all day.
So, my question is, what now? I'm of the opinion based on the above that if I can't reflash a warranty supported Kies update, then maybe a custom ROM will be worth a shot to see if its a hardware failure or if its software. I just have never had an issue like this with my HTC Desire and I've ran many custom ROMs and standard ROMs on it.
I do have the .tmp file of the update Kies downloaded, and I also have a Binary folder which has some file inside a couple more folders but its not a .tar or a .zip because when I try renaming it (after a copy) it won't open.
So, suggestions on a postcard, thanks if you got this far through this nightmare. All help massively appreciated.
Edit: it appears to be the same issue as this: http://forum.xda-developers.com/showthread.php?t=822238
I'll try some of their suggestions. Today I also did the *2767*3855# today which I found after a bit more searching. Same problem after a reboot. Force close and data still there.
I've tried and tried again to do various solutions for this, I've even ran a logcat using adb to see if I can see the problem. I suspect its a Dalvik Cache issue in that its unable to write to it for some weird reason.
I've downgraded it to Froyo following this guide: http://forum.xda-developers.com/showthread.php?t=1100906
It now detects in Kies and offers me a firmware upgrade. I suspect it will die again though if I try due to this Dalvik problem.
Wiping cache does not wipe the cache. Everything still appears to be there on reboot as mentioned above.
Here is a copy of the LogCat with Java errors all over it: http://leenukes.co.uk/downloads/logcat1.txt (its quite long)
I guess nobody knows. Today I will speak to Orange to try and get it fixed or replaced.
Sent from my HTC Desire using Tapatalk
We've been told it is beyond repair. We will see what they say when we go back into the shop. Its still in warranty so I don't see why they won't replace it.
Sent from my Galaxy Nexus using Tapatalk
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
ZiDanRO said:
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
Click to expand...
Click to collapse
Sound advice there mate, other thing I would have done is in recovery mode before the ODIN flash I would have format sdcard, making sure you have removed BOTH the external sd and the sim card, as it can wipe them as well.Then flash through ODIN as per instructions above.
Using JVT I would flash either speedmod or semaphore 2.1.1 which I personally use.
Happy flashing!!
turns out it was water damage and some parts corroded.
Its going to be claimed for on insurance.
Sent from my Galaxy Nexus using Tapatalk
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Its going back to the insurance company. Especially as Orange were suggesting that we pay £70 for a new handset.
Absolute fool I had on support today, yesterday I at least had someone sensible.
Sent from my Galaxy Nexus using Tapatalk
SGS force close problem
Hey guys i m facing a similar solution in my samsung galaxy s. After deleting all the contents and uninstalling the applications, I m getting them back after rebooting and all applications has to be force closed after rebooting.
Please help me to solve this problem
Signal issues
leenukes said:
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Click to expand...
Click to collapse
Sounds like a modem issue, where the techs at Orange put in the wrong modem for your firmware. I did the same thing when I upgraded from Froyo to Gingerbread.
Alternately, it could be a broken external antenna connection as a result of the corrosion from the water damage. Google "no signal fix" and look for a site that ends in .uk
Just a thought for others who come across this problem.
I
Hi,
with the newest builds of LineageOS for the OnePlus 3T im facing similar problems like in this post here ...
https://forum.xda-developers.com/oneplus-3t/help/lineage-os-bluetooth-crashing-op3t-t3561225
This applies both for the 20/03 and the 24/03 build. When I enter the settings and go to the Bluetooth section and there enable BT, the phone becomes unresponsive for some time and then reboots. What I found out is that if I enable BT via the status bar shortcut, everything is fine and my previously connected device (gear s2) reconnects stable. But if I then enter the settings and just click on the BT section entry, same story again, phone becomes unresponsive and then reboots. I flashed the ROM and then the OOS Firmware 4.1.0. Phone is rooted with SuperSU.
Have you tried a clean flash?
not yet. just dirty flashing with wipe cache and dalvik so far. i guess I'll give it a try then.
greg1977 said:
not yet. just dirty flashing with wipe cache and dalvik so far. i guess I'll give it a try then.
Click to expand...
Click to collapse
Report back with results plz
sakumaxp said:
Report back with results plz
Click to expand...
Click to collapse
I don't know what did the trick now but this is what I was trying...
I cleaned the cache + data of the Bluetooth system app and reinstalled BusyBox, then rebooted. The problem seems to be gone, no more crashes and freezing OS. Will leave it like this for me now. Just wanted to let you know as I don't seem to be the only one with this issue.
greg1977 said:
I don't know what did the trick now but this is what I was trying...
I cleaned the cache + data of the Bluetooth system app and reinstalled BusyBox, then rebooted. The problem seems to be gone, no more crashes and freezing OS. Will leave it like this for me now. Just wanted to let you know as I don't seem to be the only one with this issue.
Click to expand...
Click to collapse
All,
just wanted to give an update on this topic and hope for a solution
As the problem was coming back I decided to go for a full wipe and clean flash of the latest LineageOS version for the OnePlus 3T from this thread here: https://forum.xda-developers.com/oneplus-3t/development/rom-lineageos-14-1-t3547024
After I restored my apps I activated Bluetooth on the device and flawlessly connected my Smartwatch, a Gear S2. All good, all fine, all working.
AFTER that, when entering Settings => Bluetooth on the OP3T, there are 2 possible scenarios:
1) No other Bluetooth devices are around and emitting, the search stops after a few seconds saying that "no other BT devices are detected" ... makes sense.
2) There are other Bluetooth devices around and emitting, and based on my experience only one device is sufficient. The search goes on and on and on, after a while the screen freezes, and then the phone warm resets.
I was able to reproduce this inside my car when I tried to connect to the car audio system and also with my Bluetooth headset. Devices turned off => scenario 1, devices turned on and ready to connect => scenario 2.
Any idea here?
Hi guys I really need some help. It's been quite a few days now since my Bluetooth isn't turning on. I've tried clearing cache n data for Bluetooth apps and services in application manager but still no luck. This is what happens when I try to turn on Bluetooth... (Check screenshot)
The switch just fades and Bluetooth doesn't really turn on at all. And after a while the switch turns off by itself. Please help.
I also tried flashing another kernel (from stock) but still no luck. I'm on OOS 4.1.7 with Blu spark r174.
It had stopped working since I was on stock OOS (non rooted) and then I rooted and installed Blu spark but still no luck.
I have tried clearing app cache and data of Bluetooth share app, reset network settings even tried factory reset, still no luck. OOS 4.1.7.
Someone please help.
King_root said:
Hi guys I really need some help. It's been quite a few days now since my Bluetooth isn't turning on. I've tried clearing cache n data for Bluetooth apps and services in application manager but still no luck. This is what happens when I try to turn on Bluetooth... (Check screenshot)
The switch just fades and Bluetooth doesn't really turn on at all. And after a while the switch turns off by itself. Please help.
I also tried flashing another kernel (from stock) but still no luck. I'm on OOS 4.1.7 with Blu spark r174.
Click to expand...
Click to collapse
If it isn't working after factory reset, most probably it is a hardware problem..
Another issue that I've heard off is related to the encryption of the storage, but i don't think this is the case now
neinfricatu said:
If it isn't working after factory reset, most probably it is a hardware problem..
Another issue that I've heard off is related to the encryption of the storage, but i don't think this is the case now
Click to expand...
Click to collapse
But then the system acts weird about Bluetooth. When I try to turn it on (notice I do get an option to turn it on), the switch flips on the other side (switching ON) but fades n does nothing. And if I move out of settings and come back to Bluetooth section, it goes back to off. I kind of have a feeling it's a software problem n just needs some system modifications. But I really don't know, really need some expert opinions, please help guys.
Full wipe and try to downgrade to earlier OOS version..
( 4.1.5 ) or try another custom kernel ..EX or Dorimanx....
King_root said:
But then the system acts weird about Bluetooth. When I try to turn it on (notice I do get an option to turn it on), the switch flips on the other side (switching ON) but fades n does nothing. And if I move out of settings and come back to Bluetooth section, it goes back to off. I kind of have a feeling it's a software problem n just needs some system modifications. But I really don't know, really need some expert opinions, please help guys.
Click to expand...
Click to collapse
This happened to my dad on another phone and after a while the wifi died as well. It's a hardware issue.
I had the same issue 2 months ago. tried to switch back to stock and everything, it did not work. So I sent mine back to Oneplus, it was a hardware problem and the motherboard had to be changed. It sounds like you are unlucky as I was.
Just dirty flash your Rom and check if it works.
Unleashed by ONEPLUS 3T rooted
neinfricatu said:
If it isn't working after factory reset, most probably it is a hardware problem..
Click to expand...
Click to collapse
When folks say "factory reset" they most usually means just using the option "factory reset" in stock/custom recovery, or in phone Settings. All those do, is wipe user data. SO the problem will only be solved if some problem/incompatibility with user data was the culprit (does not actually "restore" any software/firmware).
I would suggest flashing the full 4.1.7 (or even early version) zip to restore to full stock, which I think is more what you meant.
This has happened to me before after updating magisk and not re-flashing a kernel. Wi-Fi and Bluetooth weren't toggleable (if that's a word) and the phones battery was draining pretty aggressively. I'd follow the advice from others and do a reset, or flash a custom kernel over what you have.
So I have a Galaxy S10 verizon that was working fine, was up to date with all updates and etc and all of a sudden it decided to keep on freezing then reboot. Figuring it was a software issue I already have done the following with no luck
-Wiped cache
-Ran in safe mode
-Full wipe restore of the system
None of them have worked so I then proceeded to obtain the combination files and have reloaded the phone fresh using Odin new figuring it was a corruption in the software.
After it successfully finished loading the problem is still present after about 30 seconds after rebooting the phone. I don't know what else I can do next besides playing around with a custom rom maybe to see if the reboot loop is still present.
Any Ideas what else I can do or try?
Phone is in perfect condition, never dropped, no water damage, never flashed anything to the phone and was running just the stock verizon firmware. Phone doesn't even has a scratch in it...
Any ideas would be greatly appreciated!
If a data factory reset in recovery didn't work nor flashing stock firmware with ODIN, then it's probably hardware related and thus you will need to claim insurance if you have it with your carrier or warranty thru Samsung if it's still in warranty.