I've been reading a lot over the web to find information about this issue I'm having, but by no means I could solve this issue.
I just got my S5. Here's a (very short) excerpt of the
Code:
adb shell dumpstate
command:
Code:
[ril.product_code]: [SM-G900MZWPZTO]
[ro.product.model]: [SM-G900M]
When I got the phone, the first thing I did, as it was used, was to factory-reset it, because I didn't want any data from the previous user. I did this through the phone UI, not from within recovery (wipe cache/wipe data).
Once reset was done, I put in my microSIM and turned it back on. I had no way to test wifi and bluetooth at that point, so I used the mobile network to update my personal info, etc.
By the end of the day, I got home and tried to turn on wireless. The normal behavior of the indicator when turning wifi on is GRAY->DARK GREEN->GREEN, but the phone goes GRAY->DARK GREEN and doesn't go further. It stays in DARK GREEN for a couple minutes, then it goes back to GRAY.
The same happens to bluetooth. The only difference is that bluetooth takes less time to go back to GRAY.
The Android version installed was 4.2.2.
There was an offer to update Android, so I thought that could solve the problem, so I updated Android to 5.0 over mobile network (no wifi, remember?).
After the update, wifi still didn't work. By dialing *#1234#, I noticed this:
Code:
AP: G900MUBU1BOC4
CP: G900MUBU1BOC3
CSC: G900MZTO1BOC4
AP and CP are different. Shouldn't they be equal?
Anyway, after seeing the update didn't solve the problem, I did a downgrade, again with no success. The *#1234# now shows this:
Code:
AP: G900MUBU1ANCE
CP: G900MUBU1ANCE
CSC: G900MZTO1ANCE
Wifi still don't go on.
I also tried to flash two Android 5.0 (Lollipop) versions available to my country (got them from sammobile dot com):
Code:
/firmwares/download/45787/G900MUBU1BOC4_G900MZTO1BOC4_ZTO/
Code:
/firmwares/download/44412/G900MUBU1BOC1_G900MZTO1BOC1_ZTO/
None worked.
I used ODIN for all updates. Some background on how to use ODIN can be found here:
www dot droidforums dot net threads guide-complete-samsung-odin-v3-xx-options-and-reference.278159
While inspecting the phone's dumpstate, I found this:
Code:
01-01 10:56:42.519 732 967 E WifiHW : ##################### set firmware type 0 #####################
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_fw_path(): fwpath = /system/etc/wifi/bcmdhd_sta.bin
01-01 10:56:42.519 252 914 E WifiHW : Cannot open "/data/.cid.info": No such file or directory
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_nvram_path() = /system/etc/wifi/nvram_net.txt
01-01 10:56:42.519 252 914 E WifiHW : TEMP_FAILURE_RETRY complete
.
.
.
01-01 10:56:42.529 732 967 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '16
01-01 10:56:42.529 732 967 E WifiHW : supplicant_name : p2p_supplicant
01-01 10:56:42.529 732 967 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
The following also appears from time to time along the log:
Code:
01-01 10:56:53.549 732 967 E WifiHW : Supplicant not running, cannot connect
I read a lot about wifi connections dropping, but none about not being able to turn on wifi on Samsung Galaxy S5. Got to some similar threads on S4 and previous versions, but none about S5, so I decided to post here.
Some questions arises:
1. Am I the only one having this issue?
2. Can it be hardware-related? And if yes, is there any way to check this?
3. Could the Factory Reset have done something nasty to wifi config files? I read some suggestions to erase wpa_supplicant config files.
4. When flashing a new rom, is any data kept inside the phone or everything is erased?
5. Is there a way to reset the wifi only or updating its firmware?
Thanks for helping!
There could be 3 causes for this...
1. Kernel WIFI modules doesn't match the kernel.
2. Hardware problem
3. Not sure about this since I'm just new to samsung but it could also be from a corrupt EFS partition.
But to further troubleshoot this problem can you do this for me?
1. Install terminal emulator from playstore.
2. execute this command from there
Code:
svc wifi enable
See if it shows some errors, warnings or whatever text it will print.
if not type logcat and paste here the last 100 to 150 lines of the output.
htimsxela said:
I've been reading a lot over the web to find information about this issue I'm having, but by no means I could solve this issue.
I just got my S5. Here's a (very short) excerpt of the
Code:
adb shell dumpstate
command:
Code:
[ril.product_code]: [SM-G900MZWPZTO]
[ro.product.model]: [SM-G900M]
When I got the phone, the first thing I did, as it was used, was to factory-reset it, because I didn't want any data from the previous user. I did this through the phone UI, not from within recovery (wipe cache/wipe data).
Once reset was done, I put in my microSIM and turned it back on. I had no way to test wifi and bluetooth at that point, so I used the mobile network to update my personal info, etc.
By the end of the day, I got home and tried to turn on wireless. The normal behavior of the indicator when turning wifi on is GRAY->DARK GREEN->GREEN, but the phone goes GRAY->DARK GREEN and doesn't go further. It stays in DARK GREEN for a couple minutes, then it goes back to GRAY.
The same happens to bluetooth. The only difference is that bluetooth takes less time to go back to GRAY.
The Android version installed was 4.2.2.
There was an offer to update Android, so I thought that could solve the problem, so I updated Android to 5.0 over mobile network (no wifi, remember?).
After the update, wifi still didn't work. By dialing *#1234#, I noticed this:
Code:
AP: G900MUBU1BOC4
CP: G900MUBU1BOC3
CSC: G900MZTO1BOC4
AP and CP are different. Shouldn't they be equal?
Anyway, after seeing the update didn't solve the problem, I did a downgrade, again with no success. The *#1234# now shows this:
Code:
AP: G900MUBU1ANCE
CP: G900MUBU1ANCE
CSC: G900MZTO1ANCE
Wifi still don't go on.
I also tried to flash two Android 5.0 (Lollipop) versions available to my country (got them from sammobile dot com):
Code:
/firmwares/download/45787/G900MUBU1BOC4_G900MZTO1BOC4_ZTO/
Code:
/firmwares/download/44412/G900MUBU1BOC1_G900MZTO1BOC1_ZTO/
None worked.
I used ODIN for all updates. Some background on how to use ODIN can be found here:
www dot droidforums dot net threads guide-complete-samsung-odin-v3-xx-options-and-reference.278159
While inspecting the phone's dumpstate, I found this:
Code:
01-01 10:56:42.519 732 967 E WifiHW : ##################### set firmware type 0 #####################
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_fw_path(): fwpath = /system/etc/wifi/bcmdhd_sta.bin
01-01 10:56:42.519 252 914 E WifiHW : Cannot open "/data/.cid.info": No such file or directory
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_nvram_path() = /system/etc/wifi/nvram_net.txt
01-01 10:56:42.519 252 914 E WifiHW : TEMP_FAILURE_RETRY complete
.
.
.
01-01 10:56:42.529 732 967 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '16
01-01 10:56:42.529 732 967 E WifiHW : supplicant_name : p2p_supplicant
01-01 10:56:42.529 732 967 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
The following also appears from time to time along the log:
Code:
01-01 10:56:53.549 732 967 E WifiHW : Supplicant not running, cannot connect
I read a lot about wifi connections dropping, but none about not being able to turn on wifi on Samsung Galaxy S5. Got to some similar threads on S4 and previous versions, but none about S5, so I decided to post here.
Some questions arises:
1. Am I the only one having this issue?
2. Can it be hardware-related? And if yes, is there any way to check this?
3. Could the Factory Reset have done something nasty to wifi config files? I read some suggestions to erase wpa_supplicant config files.
4. When flashing a new rom, is any data kept inside the phone or everything is erased?
5. Is there a way to reset the wifi only or updating its firmware?
Thanks for helping!
Click to expand...
Click to collapse
I believe, (Don't quote me on this), if the EFS partition was corrupted or lost, the phone would not have any radio functionality including voice and text etc
Also I 'think' the IMEI is also included on that partition, so *#06# should come up blank if it was the EFS partition causing the problem
But again, this is just what I've also picked up in the short time I've been with my S5 so could be missing something
[Solved], but the hard way
I took the device to Samsung and they said there was a problem on the main board (?), so they replaced it for a new one. I don't think I'm going to complain about it. Although I think that could be fixed somehow, replacing was probably easier. I said "the hard way" on the title, meaning it was a "brute force" fix. It is a pity I wasn't able to keep the old board for experimentation...
Thanks for your replies, guys. I didn't even expect replies and got yours and so complete! Thanks a lot!
Related
Hi,
I intensively searched for my problem, but found always other non-related stuff.
Recently (last 1, 2 days) my WiFi didn't connect to any APs any more. I was using CN nightlies and franco kernel, so today I did update CN without franco. Afterwards I downgraded CN and did a radio update and now I tried the stock 4.2.2 image with the flash-all script, which also seemed to reflash my radio.
The default wifi dialog always displayed the saved wifis only. And after installing stock, the initial wifi dialog displayed "searching" only for a very long time. Sometimes I see some networks and I even managed to connect to mine, but it dropped immediately.
I know, this is very undetailed, but do you have any recommendations / logs to look out / smth which could point me in the right direction? Or is my hardware just broken?
logcat outputs this when turning wi-fi on (on stock 4.2.2, unrooted):
D/WifiService( 499): setWifiEnabled: true pid=1942, uid=1000
D/BluetoothAdapter( 1942): 1110956336: getState() : mService = null. Returning STATE_OFF
W/Netd ( 156): No subsystem found in netlink event
D/NetlinkEvent( 156): Unexpected netlink message. type=0x11
W/Netd ( 156): No subsystem found in netlink event
D/NetlinkEvent( 156): Unexpected netlink message. type=0x11
D/Tethering( 499): sendTetherStateChangedBroadcast 1, 0, 0
D/Tethering( 499): InitialState.processMessage what=4
D/Tethering( 499): sendTetherStateChangedBroadcast 0, 0, 0
D/SoftapController( 156): Softap fwReload - Ok
D/CommandListener( 156): Setting iface cfg
D/CommandListener( 156): Trying to bring down wlan0
E/NetdConnector( 499): NDC Command {219 softap fwreload wlan0 STA} took too long (739ms)
I/wpa_supplicant( 9715): Successfully initialized wpa_supplicant
I/wpa_supplicant( 9715): rfkill: Cannot open RFKILL control device
I/wpa_supplicant( 9715): rfkill: Cannot open RFKILL control device
D/CommandListener( 156): Setting iface cfg
D/CommandListener( 156): Trying to bring up p2p0
D/BluetoothAdapter( 1942): 1110956336: getState() : mService = null. Returning STATE_OFF
Click to expand...
Click to collapse
when flashing stock (via the official google flash scripts), stock firmware files (qualcom, ..) are also flashed, right? or could I do something useful with the official google binaries?
Stupid post.... Ignore
I don't know what else to do.
Here's what i tried so far:
Flashed custom kernel
Flashed other rom (CM10.2)
Cleared Dalvik cache
Cleared cache partition
Flashed other modem
Reseted flash counter
Flashed back stock rom (4.2.2)
Upgraded to 4.3 (ota)
The problem remains.
Anything i forgot to try?
Any sugestions?
Thanks!
I think the only way to fix this would be to flash a complete official firmware package via Odin.
Sent from my GT-I9505 using Tapatalk
MegaMike604 said:
I think the only way to fix this would be to flash a complete official firmware package via Odin.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I did that, no luck.
Try multiple times, boot directly to download mode, not from the rom and make sure to use the firmware that the custom ROM is based on. If that fails you may have a hardware issue, not sure what else to try.
Sent from my GT-I9505 using Tapatalk
What do you mean by "can't activate wifi" ?
planetf1 said:
What do you mean by "can't activate wifi" ?
Click to expand...
Click to collapse
I mean that i activate and it deactivate.
arleybarros said:
I mean that i activate and it deactivate.
Click to expand...
Click to collapse
Try using custom kernel and then flash mga wifi lte fix. Take out the battery and then use Odin.
Sent from my GT-I9505 using Tapatalk
MemoryController said:
Try using custom kernel and then flash mga wifi lte fix. Take out the battery and then use Odin.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Ty, but no luck yet.
Logcat says:
Code:
E/WifiHW ( 2016): Cannot open "/data/.cid.info": No such file or directory
D/WifiService( 2016): setWifiEnabled: true pid=2237, uid=10040
E/WifiHW ( 2016): ==========[WIFI] Station firmware load ===========
E/WifiStateMachine( 2016): Failed to load driver!
E/WifiStateMachine( 2016): DriverFailedState
Have you tried flashing a fix for your current modem? worked for me with Odin 3.04
I9505XXUEMJ7 was my modem (nordic countries)
http://d-h.st/users/DjeMBeY/?fld_id=16262
tried to flash all the "wifi fixers" available in this forum, and keep getting this errors on adb:
Code:
I/WifiManager( 1421): setWifiEnabled : true
I/WifiService( 879): setWifiEnabled: true pid=1421, uid=10141
E/WifiHW ( 879): ##################### set firmware type 0 #####################
E/WifiHW ( 879): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 879): ==========[WIFI] Station firmware load ===========
D/SSRMv2:Monitor( 879): SIOP:: AP = 400 (read only)
E/WifiHW ( 879): return of insmod : ret = -1, No such device
E/WifiStateMachine( 879): Failed to load driver
D/WfdService( 879): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/STATUSBAR-NetworkController( 1421): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-NetworkController( 1421): Nothing, mRoamingIconId = 0
I/elm ( 2716): MainReceiver.onReceive() : android.net.wifi.WIFI_STATE_CHANGED
E/WifiStateMachine( 879): sendErrorBroadcast code:10
E/WifiController( 879): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
I/elm ( 2716): MainReceiver.onReceive() END - - - - - : android.net.wifi.WIFI_STATE_CHANGED
D/elm ( 2716): ELMEngine.getInstance().
I/DownloadNowBroadcastReceiver( 3770): onReceive
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.TMNetworkReceiver() Enter 1 main
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.StartTMHandler - enter
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.StartTMHandler - exit
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Enter
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Action android.net.wifi.WIFI_STATE_CHANGED
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() UnHandled
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Exit
D/MTPRx ( 4799): DRIVER_TIME_OUT 60s lapsed
current
Tried this?
http://www.alliance-rom.com/communi...-non-hlos-bin-temporary-flashing-method.8676/
After countless hours of frustration with all the steps you have tried, this finally solved my problem.
Geggan said:
Tried this?
http://www.alliance-rom.com/communi...-non-hlos-bin-temporary-flashing-method.8676/
After countless hours of frustration with all the steps you have tried, this finally solved my problem.
Click to expand...
Click to collapse
just tried, no luck.
Any luck on this? I've had a dead device for a while I would like to be able to connect to WiFi!
MegaMike604 said:
I think the only way to fix this would be to flash a complete official firmware package via Odin.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Where can I get the complete offical firmware package?
nalitox said:
Where can I get the complete offical firmware package?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/
arleybarros said:
just tried, no luck.
Click to expand...
Click to collapse
The WIFI "Trick" in .zip form. Just flash it via Recovery to make your 4.3 work: HERE
Hi,
Recently have rooted my S4 I9505, and have put this ROM (Google customized Edition build - using Ktoonsez kernel - http://forum.xda-developers.com/showthread.php?t=2557353)
WiFi and other stuff worked perfect.
In one moment have installed this app Pry-Fi (https://play.google.com/store/apps/details?id=eu.chainfire.pryfi), just to test the app & functionality.
This day WiFi have started not connecting to networks (have connect to some), and day after cannot turn on Wifi
Log shows this error:
08-13 15:18:13.305 823-1038/? E/WifiHW﹕ ##################### set firmware type 0 #####################
08-13 15:18:13.305 823-1038/? E/WifiHW﹕ Cannot open "/data/.cid.info": No such file or directory
08-13 15:18:13.305 823-1038/? E/WifiHW﹕ ==========[WIFI] Station firmware load ===========
08-13 15:18:14.106 823-1038/? E/WifiHW﹕ return of insmod : ret = -1, No such device
08-13 15:18:14.106 823-1038/? E/WifiStateMachine﹕ Failed to load driver
08-13 15:18:14.156 823-1038/? E/WifiStateMachine﹕ sendErrorBroadcast code:10
08-13 15:18:14.156 823-1055/? E/WifiController﹕ Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
Then i have tried to return to stock ROM, trying CM11, but all of them have same error.
(also tried to flash modem and NON-HLOS.bin - also nothing)
Full wipe with TWRP or CMW6 - nothing.
At last have made full wipe with TWRP, and put again same ROM (but this time Pure Nexus edition)
And now i have following in my log (attached)
but from log you can see:
08-14 12:27:58.609 780-1148/system_process E/WifiHW﹕ Supplicant not running, cannot connect
08-14 12:27:58.609 780-1148/system_process E/WifiMonitor﹕ startMonitoring(wlan0) failed!
08-14 12:27:58.609 780-1148/system_process E/WifiStateMachine﹕ Failed to setup control channel, restart supplicant
Have tried fixes with replacing wlan0 in /system/etc/wifi/wpa_supplicant.conf - nothing happens
Any help appreciate
EDIT: After last change (see my third post below, WiFi works without problem, have connected on several places, connection is persistent)
721
valic1986 said:
Hi,
Recently have rooted my S4 I9505, and have put this ROM (Google customized Edition build - using Ktoonsez kernel - http://forum.xda-developers.com/showthread.php?t=2557353)
WiFi and other stuff worked perfect.
In one moment have installed this app Pry-Fi (https://play.google.com/store/apps/details?id=eu.chainfire.pryfi), just to test the app & functionality.
This day WiFi have started not connecting to networks (have connect to some), and day after cannot turn on Wifi
Log shows this error:
08-13 15:18:13.305 823-1038/? E/WifiHW﹕ ##################### set firmware type 0 #####################
08-13 15:18:13.305 823-1038/? E/WifiHW﹕ Cannot open "/data/.cid.info": No such file or directory
08-13 15:18:13.305 823-1038/? E/WifiHW﹕ ==========[WIFI] Station firmware load ===========
08-13 15:18:14.106 823-1038/? E/WifiHW﹕ return of insmod : ret = -1, No such device
08-13 15:18:14.106 823-1038/? E/WifiStateMachine﹕ Failed to load driver
08-13 15:18:14.156 823-1038/? E/WifiStateMachine﹕ sendErrorBroadcast code:10
08-13 15:18:14.156 823-1055/? E/WifiController﹕ Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
Then i have tried to return to stock ROM, trying CM11, but all of them have same error.
(also tried to flash modem and NON-HLOS.bin - also nothing)
Full wipe with TWRP or CMW6 - nothing.
At last have made full wipe with TWRP, and put again same ROM (but this time Pure Nexus edition)
And now i have following in my log (attached)
but from log you can see:
08-14 12:27:58.609 780-1148/system_process E/WifiHW﹕ Supplicant not running, cannot connect
08-14 12:27:58.609 780-1148/system_process E/WifiMonitor﹕ startMonitoring(wlan0) failed!
08-14 12:27:58.609 780-1148/system_process E/WifiStateMachine﹕ Failed to setup control channel, restart supplicant
Have tried fixes with replacing wlan0 in /system/etc/wifi/wpa_supplicant.conf - nothing happens
Any help appreciate
Click to expand...
Click to collapse
well, that escalated quickly
Have checking build.prop and seen that ro.wifi.channels was empty.
I have add value 14, restart, and WiFi is finally back, at least temporary
Then is again disconnected, even WiFi signal of previoues connected network is great (but is not turned OFF)
valic1986 said:
well, that escalated quickly
Have checking build.prop and seen that ro.wifi.channels was empty.
I have add value 14, restart, and WiFi is finally back, at least temporary
Then is again disconnected, even WiFi signal of previoues connected network is great (but is not turned OFF)
Click to expand...
Click to collapse
valic1986 said:
well, that escalated quickly
Have checking build.prop and seen that ro.wifi.channels was empty.
I have add value 14, restart, and WiFi is finally back, at least temporary
Then is again disconnected, even WiFi signal of previoues connected network is great (but is not turned OFF)
Click to expand...
Click to collapse
when i have writing this answer, WiFi turned OFF (grey button, not possible to turn ON)
Again value was there after restart but not working, have switched to channel 11 (which is on my router)
Now works, but after several minutes just disconnect, some time stuck on turning ON and go back to position that is not working again
Entire log in attachment
valic1986 said:
when i have writing this answer, WiFi turned OFF (grey button, not possible to turn ON)Again value was there after restart but not working, have switched to channel 11 (which is on my routerNow works, but after several minutes just disconnect, some time stuck on turning ON and go back to position that is not working again
Click to expand...
Click to collapse
You should post your logs in the PryFi Thread, so that he can fix this, if it is serious.
give all permissions
valic1986 said:
when i have writing this answer, WiFi turned OFF (grey button, not possible to turn ON)
Again value was there after restart but not working, have switched to channel 11 (which is on my router)
Now works, but after several minutes just disconnect, some time stuck on turning ON and go back to position that is not working again
Entire log in attachment
Click to expand...
Click to collapse
give all permissions to
/system/etc/wifi/wpa_supplicant.conf and others wpa_supplicant.conf turn off/ turn on wifi. this work for me
nico_7t said:
give all permissions to
/system/etc/wifi/wpa_supplicant.conf and others wpa_supplicant.conf turn off/ turn on wifi. this work for me
Click to expand...
Click to collapse
Did you have this issue? I remember trying this and it not working, but I might try again and check
nico_7t said:
give all permissions to
/system/etc/wifi/wpa_supplicant.conf and others wpa_supplicant.conf turn off/ turn on wifi. this work for me
Click to expand...
Click to collapse
What do you mean by giving permissions?
How do your files look like?
My PH-1 reboots randomly, sometimes frequently, and it is accompanied with sudden surge of heat on the in almost the direct center of the phone, on both the front and back sides. This has happened on stock Oreo (from .010 to current stock builds), RR, Lineage OS, AOSiP, and Carbon ROM. I've had it occur while rooted/unrooted, with or without xposed, and have thoroughly wiped device in between new ROMs. And though the device does suddenly get quite hot it can happen when im in a dark cold place or outside in the sun. The only correlation is that it seems to only occur while talking on the phone but length of call is not a factor in that scenario. It could happen 5 times in an hour or in a week.
I'm new to modification, and although green I've made my way through it pretty well thanks to the great forums and tips offered here. Rooting/modding is now much simpler now but this problem has been persisting for almost two months. I've got a logcat from boot to crash taken via ADB (about 2-3 minutes real time) but don't know how to interpret it enough to discover the cause of the problem . Thanks in advance for any help provided. I will post the logcat but I'm not sure of how much to post or how for that matter haha.
Thanks again
That really sounds like a hardware problem if its persisting across ROMs.
Warranty for sure. Most definitely a hardware fault.
jhs39 said:
That really sounds like a hardware problem if its persisting across ROMs.
Click to expand...
Click to collapse
I've taken quite a few logs and there are two consistent segments that I can't get figured out. Any help would be great. The second one has way more variations on the theme and they're grouped. Also, my phone was brand new but NOT purchased from a retailer. I'm assuming I'm outta luck for warranty?
A) 05-17 20:58:36.979 1518 1877 E Diag_Lib: [IMS_FATAL]| 1877 |ims_qmi_register_client : Failed
B) 05-17 20:59:11.372 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getAuthFrequency []
05-17 20:59:11.373 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getUserHasFop []
05-17 20:59:11.374 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getFingerprintValid []
05-17 20:59:11.374 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getDesiredAuthMethod []
05-17 20:59:11.374 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getAuthFrequency []
05-17 20:59:11.375 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got
crixley said:
Warranty for sure. Most definitely a hardware fault.
Click to expand...
Click to collapse
Thank you for the response. Please look at my reply to user below your post. Is any information gathered just from those logs?
It looks like it's constantly polling to register you on the network and failing. What company are you with? Try two things just to satisfy my curiosity:
1) go into mobile network> advanced and change automatically select network to off. Click below and choose your provider yourself from the list.
2) double check the access point name (APN settings)
crixley said:
It looks like it's constantly polling to register you on the network and failing. What company are you with? Try two things just to satisfy my curiosity:
1) go into mobile network> advanced and change automatically select network to off. Click below and choose your provider yourself from the list.
2) double check the access point name (APN settings)
Click to expand...
Click to collapse
I'm on Verizon and step 1, done. It was active so I switched off. Step 2 it lists 2 APN... Verizon (VZWINTERNET) **checked** and Straight Talk Verizon (TRACKFONE.VZWENTP)**not checked**
Now im curious so I'll run logcat and see if similar codes persist. It seems like I'm on the phone nearly every time it happens, don't know if there is a correlation.
Thanks!
KingBeefy said:
I'm on Verizon and step 1, done. It was active so I switched off. Step 2 it lists 2 APN... Verizon (VZWINTERNET) **checked** and Straight Talk Verizon (TRACKFONE.VZWENTP)**not checked**
Now im curious so I'll run logcat and see if similar codes persist. It seems like I'm on the phone nearly every time it happens, don't know if there is a correlation.
Thanks!
Click to expand...
Click to collapse
Would be registering on the network when you make a call, it registers with the nearest tower to you. Let me know if that helps!
crixley said:
Would be registering on the network when you make a call, it registers with the nearest tower to you. Let me know if that helps!
Click to expand...
Click to collapse
So went a few hours with the changes you recommended and it was doing ok so far. The reboots are randomized. Might be 1 time in 36 hours and others its 6 times in an hour. Phone activity, battery life, etc seem to have a wide deviation too. BUT, so far so good. Much of the logcat did look like nothing was throwing a fail code, but this one still popped up enough to notice .
05-21 06:53:19.972 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:20.335 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:21.982 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:21.984 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:22.330 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:23.991 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:23.993 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:24.348 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:26.000 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:26.002 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
KingBeefy said:
So went a few hours with the changes you recommended and it was doing ok so far. The reboots are randomized. Might be 1 time in 36 hours and others its 6 times in an hour. Phone activity, battery life, etc seem to have a wide deviation too. BUT, so far so good. Much of the logcat did look like nothing was throwing a fail code, but this one still popped up enough to notice .
05-21 06:53:19.972 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:20.335 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:21.982 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:21.984 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:22.330 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:23.991 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:23.993 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:24.348 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:26.000 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:26.002 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
Click to expand...
Click to collapse
Hmmm. Have you flashed any other modems? Might be worth a shot.
crixley said:
Hmmm. Have you flashed any other modems? Might be worth a shot.
Click to expand...
Click to collapse
Teach me master!!!! What resource will you point me to?
KingBeefy said:
Teach me master!!!! What resource will you point me to?
Click to expand...
Click to collapse
Lol
What I would do is full wipe and fastboot flash the latest full file. Seems like OTAs haven't been updating the modem and ROMs wouldn't either I doubt.
You could probably just fastboot flash the modem.img from from the latest fastboot release if you really didn't want to full wipe.
The full wipe doesnt scare me off. I took my lumps teaching myself from scratch and the nuances of the way dual partition devices function has been an interesting learn. I prefer using ADB/fastboot/twrp instead of doing and OTA because of the learning opportunity so I have the latest modem.img from the current Firmware from essentials site. I also use @invisiblek builds. I sent Essential the log and they offered a suggestion as well, saying
I am sending you two troubleshooting steps that.... One of the reasons we need to do this is that when you factory reset your phone you restored backed up information and you signed back into you google account....
Click to expand...
Click to collapse
One of the first things I learned in forums like this one was that until you are ready to go, don't sign in to anything. So I will try and do that. Thanks again for suggestions @crixley
I was having this issue a while back. Every custom rom/kernel caused the processor to lock up at Max frequency randomly thus causing quick overheating no matter how small the load. Performance is amazing through this, but overheating is very annoying. I fixed mine by sticking to stock rooted and not touching the governors or thermal throttling. Maybe I would suggest monitoring your processor with a kernel manager and/or trying to play around with governors and thermal options for now, if you in fact have the same issue, to see if you get something thats stable and sticks. Good luck
I had an issue with mine where it was constantly locking up and rebooting, mostly during multimedia activities like watching YouTube, gaming and even browsing chrome. I never monitored the temperature and it never felt hot to the touch but it just kept happening constantly. I bought it as a refurbished on eBay and was crashing out of the box. It was completely stock Android 8.1.1. Most of the time it would just constantly non stop crash after 30seconds-10minutes of being turned on,. Would just freeze, sit for 30 seconds and then reboot itself. A couple times it lasted sitting idle for 14 hours before crashing and then constantly do it again.
Anyways even though it was a refurbished unit and the seller was not the original owner, it was still under warranty period and was able to be replaced. Just open warranty rma with essential is what I would do. If the serial/imei you provide them is still under warranty they will probably honor it.
Also they gave me that troubleshooting steps too,. Factory reset, start fresh and don't login to your, it's bogus. Still had the same issue on my phone and I actually had to send my phone back twice before they replaced it. The first time I sent it in they said they ran diagnostics that didn't detect any issue, but when I got the phone back it crashed within 10minutes and I never logged into Google. Just a bad hardware issue.
KingBeefy said:
The full wipe doesnt scare me off. I took my lumps teaching myself from scratch and the nuances of the way dual partition devices function has been an interesting learn. I prefer using ADB/fastboot/twrp instead of doing and OTA because of the learning opportunity so I have the latest modem.img from the current Firmware from essentials site. I also use @invisiblek builds. I sent Essential the log and they offered a suggestion as well, saying One of the first things I learned in forums like this one was that until you are ready to go, don't sign in to anything. So I will try and do that. Thanks again for suggestions @crixley
Click to expand...
Click to collapse
I am seeing the same errors. What did Essential say? Did it resolve the errors?
I flashed a custom built ROM to a TB-8504F and it didn't go well. I was able to restore the majority of the partitions, but the WIFI doesn't work now. Everything else seems to work.
Is there a particular petition that I need to flash?
Attached are screenshots of the partitions on a stock tablet.
I think these logs are related:
Code:
01-08 17:48:26.818 2890 2890 E Sensors : sns_main.c(447):Timeout waiting for SMGR service. Exit sensors daemon!
01-08 17:48:26.819 2890 2890 W Sensors : sns_main.c(355):sns_main_exit called unlock daemon to exit
01-08 17:48:26.819 2890 2890 E Sensors : sns_main.c(561):Exiting! Err 0
01-08 17:48:26.848 2909 2909 W sensors.qcom: type=1400 audit(0.0:74): avc: denied { read write } for name="diag" dev="tmpfs" ino=717 scontext=u:r:sensors:s0 tcontext=u:object_r:diag_device:s0 tclass=chr_file permissive=0
01-08 17:48:26.858 2909 2909 E Diag_Lib: Diag_LSM_Init: Failed to open handle to diag driver, error = 13
01-08 17:48:26.858 2909 2909 W Sensors : sns_debug_main.c(442):Diag_LSM_Init failed: log packets and messages will not be available
01-08 17:48:26.861 2909 2911 E Sensors : sns_fsa_la.c(84):realpath failed for directory name2
01-08 17:48:26.861 2909 2911 E Sensors : sns_reg_la.c(289):Error creating registry file
01-08 17:48:26.861 2909 2911 W Sensors : sns_reg_mr.c(367):File init failed 5
drizzle123 said:
I flashed a custom built ROM to a TB-8504F and it didn't go well. I was able to restore the majority of the partitions, but the WIFI doesn't work now. Everything else seems to work.
Is there a particular petition that I need to flash?
Attached are screenshots of the partitions on a stock tablet.
I think these logs are related:
Click to expand...
Click to collapse
Use lenovo moto smart assistant to flash the stock firmware
skoar said:
Use lenovo moto smart assistant to flash the stock firmware
Click to expand...
Click to collapse
Will try this when I get to a PC - thank you!