[Q] Bluetooth doesn't turn on and Camera Fail issues - Galaxy Tab S Q&A, Help & Troubleshooting

Hi guys,
Bought a 2nd hand T705Y, after factory reset and getting accounts and apps running after 2 days I noticed I couldn't turn on BT. A day after I get Camera Fail msg with camera app.
Stock 4.4.2 rom rooted with cf. Following online instructions I tried clearing cache, wiping cache and factory reset. Nothing helped. Finally I restored original phone firmware with Kies and everything was working again.
Now 2 days later again… both BT and Camera are giving me grief again with same symptoms.
Anyone hear of this?
Surely not HW problem as both worked fine immediately after reflashing firmware.
Any suggestions? I was thinking trying a ROM to see if that avoids any software problem presented by stock rom.

If the EFS partition has become corrupt it could cause problems. It contains important data for wifi, Bluetooth and network.
I had a problem with my radio, couldn't connect to the network. Restored the EFS partition and all was well.
See if someone can make a backup of it in recovery and you can flash it back.
Back yours up first though as it contains your IMEI too.

Wouldn't the reflashing of stock firmware by Kies include refreshing the data in that partition? Or if I installed custom roms?

Roms don't contain that data. Stock or otherwise.
Sent from my SM-T805 using XDA Free mobile app

Finally figured out what was causing this. It seems camera fail pop up appears whenever I have the kitkat sd write hack to platform.xml you know the adding of <group gid=”media_rw” />.
Once the line is added, reboot. Camera fail pop up appears. Line removed, reboot and the pop up is gone.
So instead of adding the line I replaced the entire section with just above line and both functions work now.

Hi
Kind of same problem
After about a week i get camera failed warning. How can I resolve it.
I'm a newbee!!!
I have a T-805

Related

[Q] (Telus) Can't make or receive phone calls, "Call ended"

For some reason, my phone randomly has lost the ability to make or receive phone calls. Any time i try to place a call, it simply says "call ended" before even attempting to dial. I have not made any major changes to the phone recently. This seems to have happened out of nowhere. Data and text messaging work just fine, but phone calls won't.
My phone is rooted and I have the leaked Touch Wiz Jelly Bean rom installed. Also using CWM recovery.
I have tried pulling the battery for 10 minutes, and I also wiped cache/dalvik then did a system reboot through recovery, to no avail. Is there anything else I can try? Would prefer not to have to do a full data wipe if possible. Unfortunately I can't even call Telus (my carrier) to ask them for advice, due to this problem.
Is your IMEI# intact? Maybe try a new SIM card? Go back to stock to see if that fixes it. (I know you said you'd prefer not to wipe.)
Just to rule out any ROM related issues you could always make a full backup from recovery, then full wipe and flash back to stock and see if the problem persists. This way although you did wipe you can revert back to you current setup in a matter of minutes like nothing ever happened, if the problem is not fixed by going back to stock.
saj222 said:
Is your IMEI# intact? Maybe try a new IMEI card? Go back to stock to see if that fixes it. (I know you said you'd prefer not to wipe.)
Click to expand...
Click to collapse
Yep IMEI is still there. Anyone have any other suggestions before I wipe and flash back to stock? I'll try a new SIM card if wiping and re-flashing doesn't work.
dntesinfrno said:
Just to rule out any ROM related issues you could always make a full backup from recovery, then full wipe and flash back to stock and see if the problem persists. This way although you did wipe you can revert back to you current setup in a matter of minutes like nothing ever happened, if the problem is not fixed by going back to stock.
Click to expand...
Click to collapse
This seems like a good idea, I think I'll have to go this route... thanks.
Okay so I did a full backup using CWM, then wiped everything. Attempted to re flash the stock rom but ran into an issue and decided to try a different rom instead just to try it out.
Dialler worked fine on the new rom, so that was great news. Then I attempted to sync my contacts and everything with my Gmail.... But nothing was there. Apparently I somehow lost all my contacts!
So, freaked out, I immediately reverted to my Cwm backup, which thankfully restored everything. Just for the hell of it I tried the dialler... And it worked! So.... Yeah I have no idea what exactly fixed my problem in the end, but I'm just happy its working.
Thanks for the suggestions everyone!
Sent from my SGH-I747M using xda app-developers app
Sounds like the dialer app was borked somehow, might want to look into those sync settings though. I had an issue one time where the contacts i added to my phone were saving to the phone and not as gmail contacts. To check you can just log into gmail in a broswer and look at your contacts, make sure they are all there. If not you can go to your contacts on your phone, press menu and export to a .csv file. This will move all contact info into this file and you contacts will be blank, at this point simply find where you saved the .csv and import the contacts which will give you the option to make them gmail contacts. Then all you need to do is go into gmail on the browser again and delete and/or merge the duplicates.
Okay so I left my phone as-is for the past couple weeks until earlier tonight. I made a backup with CWM, then I attempted to flash a couple new roms. Did a cache/dalvik/system format/factory reset before each rom installation, then made sure to format cache/dalvik and fix permissions after each installation attempt. The roms installed fine and everything was working, except I lost use of my dialler again! So I reverted to my backup, but the dialler problem has persisted, just like I described in the OP. The way I "fixed" it last time, was to restore my backup....but that isn't helping this time...
Anyone know what else I can try? IMEI still intact, getting mobile data, wifi, MMS, etc... just can't make or receive calls again.
I should also mention that I a while back, before I tried rooting/installing any custom ROMs, I made a backup of my EFS folder on my phone... should I attempt to restore this?
Dial
*#2263#
Check to make sure automatic it's selected.
I had a similar problem messing around with lte, and found the above fixed the issue.
Also on Telus.
Sent from my SGH-I747M using Tapatalk 2
Wow thanks so much! That totally fixed the problem. I seem to pick up lte signals less often now but at least I can use my phone!
Sent from my SGH-I747M using xda app-developers app
Yeah, the lye on my phone only picks up when I'm out of my house. Has to do with the signal from telus I believe
Sent from my SGH-I747M using Tapatalk 2

[Q] Stuck on bootloader after changing screen density with Rom Toolbox

Hey guys. As the title suggests, I can't boot my Note 2 (sgh-i317). It is stuck on the AT&T logo and while it's stuck there it vibrates slightly every 5-6 seconds. I tried changing my screen density to 240 and it worked for a bit but annoed me. then I went to change it back and got this problem. I accidentally set it to 360 I think though, instead of 320. I have wiped the cache. I have wiped the data. I have installed roms countless times already with Odin. I'd imagine my reset counter is at over 10 just from today.
I've been searching on google and these forums for hours and have seen many suggestions, but none of them have worked. The farthest I have gotten was to get the phone to boot, but once I start going through all the setup stuff I begin getting error popups saying that Touchwiz home has stopped responding. As soon as I push OK the error immediately pops up again. I seriously can not do anything with my phone.
Is there any way to get a stock build.prop file somewhere for this phone, and if so, how would I install it if I can't even boot into the device?
Any help would greatly be appreciated. I have no idea where else to turn here. Thanks!
-Mark
Do you have a backup to restore from recovery ??
If not....then power down the device and remove the SD card and place it into a PC card adapter...
Then download or copy over a suitable rom...
Then place the SD into the phone and boot into recovery...
Fully wipe the device and flash the rom of choice...
Reboot....set....profit....g
Edit:
Are you certain that your power button is not stuck ?
If the method I suggested fails... and rebooting occurs with vibration...then your power button is suspect....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks. Well I got it to boot finally, however there's been a couple issues since. It's on 4.1.2 right now...
1. Whenever I try to officially update to 4.3 through the settings, it downloads, then when installing it ALWAYS fails at 25%.
2. This is a big issue. My data connectivity is gone. I have no 4g access period. If I'm not using a wifi network, I can't do anything online, period. I've reflashed numerous times, and can't get it to recognize the network. I can make calls just fine, just no data.
I've tried wiping data and going to factory reset, but this doesn't help in any way whatsoever. I've popped out the battery and sim card and reinserted after a few minutes, still to no avail.
The funny thing also, last night my friend, who has the same phone, updated to 4.3 and got the EXACT issues I've been dealing with. The ONLY thing in common is that we have both rooted our phones in the past. When I first got 4.3 it worked fine. It wasn't until I rooted that these issues began. My friend's phone was not rooted, however it had been in the past. I'm thinking that this 4.3 update has an issue with phones that are rooted or have been at some time. I don't know how it can tell, but that's all I can think of. his phone now is also a doorstop, like mine.
K, fixed data connectivity from another thread here. For some reason, even if I wipe my system, it seems to still keep settings intact. In this case, nothing set in APN. Seems the more I try to fix my phone, the more problems show up.
If you updated to official 4.3...then yes ...a whole new host of problems are yours until the devs figure out the locked bootloader and it's knox flag...
Backups won't restore....and so forth...
Read around ....you'll see...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

[Q] Updated to 4.3, now GApps continuously force closes

I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.

[Q] Can't turn wifi on. Tried with 5.1 and 4.4.4

I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
stevenx37 said:
I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
Click to expand...
Click to collapse
Hope you had read the posts, it should had said the Rom is not "stable"
If your friend are going use their phone for daily driver, then I recommend you not have the 5.1 Roms for now because it's not really suitable for that right now.....
I'm not sure the CM11 you have flashed is unoffical or is offical. Offical onces are still work in progress and have most of the things broke (I think)
Here is a Kitkat Rom for SGH-T989
If your friend really wanted to have a Lollipop running on his/her phone, then I will recommend this one. Make sure you read the instruction CAREFULLY if you do wanted to install this one since it's a bit complicated with it's "virtual partition"
Or, if you wanted it to be just stock. Odin it back to normal, here is a instruction (with video too).
This is all the possible way to fix your friend's phone that I can think of, if you have encounter any error or have anymore question, feel free to reply :fingers-crossed::good::highfive:
P.S: yes, wiping dalvik & cache is a way to prevent any error caused by another old Rom if you decided to flash a new one. It's a good way to prevent error during Rom flash process
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
stevenx37 said:
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
Click to expand...
Click to collapse
For the virtual partition, it's best for you to have it on the External SD card. Since TWRP transporting file to Internal Storage after that seems bugged (not working)

Galaxy Note 10.1 SM-P600 Reboot Loop

Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!

Categories

Resources