Database Develop

broken wifi- logcat included

1. did clean wipe out
2. installed kingorama 1.0
3. installed lastest pershoot's kernel
4. reboot
5. skip all the steps selected launcher pro, went to setting turn on wifi (scanning, but says unable to find any networks and turns off)
6.clear proxy setting, save , turn on wifi = same result
7.clear proxy setting, uncheck the "use proxy only on wifi" save, turn on wifi= same result
8. airplane mode on, turn on wifi = same result
Logcat
D/WifiSerivce( 134): ACTION_BATTERY_CHANGED PluggedType: 2
E/WifiHw ( 134): Unable to open connetion to supplicant on "eth0": No such file or directory
D/WifiStateTracker ( 134): Reset connections and stopping DHCP
D/WifiService ( 134): acquireWifiLocked: WifiLock{NetworkLocationProvider type =2 [email protected]
I/wpa_supplicant ( 1035): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
E/wpa_supplicant ( 1035): Failed to disable WPA in the driver
D/WifiStateTracker( 134) disabling interface
E/WifiHW ( 134): Supplicant not running, cannot connect
D/LocationMasfClient ( 134): getNetworkLocation(): Location not found in chace, making network request
D/ProtorequestListener (134): requestFailed()
E/WifiHW ( 134): Supplicant not running, cannot connect
V/WifiStateTracker( 134): Supplicant died unexpectedly
D/WifiStateTracker( 134):Reset connections and stopping DHCP
Right now what i have in System/lib/Module
2.6.34.7-cyanogenmod
2.6.35.9-cyanogenmod+
bcm4329.ko
i have Gateway 3800HGV router.
Router setting
Default: 2WIREXXX <-- x'ed it out just in case
SSID Broadcast : Enabled
Wirelesschannel is set to Auto
Current Channel is 11
Authentication Type : WPA-PSK (TKIP)
MAC filtering is OFF
Wireless Mode is set to 802.11 b/g
my mac address starts with 00
i posted it in Kang-o-rama thread but i wanted to see if i can get any more help from the Q&A
sorry for posting lots of question about broken wifi lately

Are you sure the correct wifi module is present that was built against the kernel?

evilkorn said:
Are you sure the correct wifi module is present that was built against the kernel?
Click to expand...
Click to collapse
yes. im 100% positive as i have relfahsed many roms many kernels.

Just to be clear, you did wipe after all those?
Also it never hurts to go back to stock as a test. If wifi fails under stock conditions it's a hardware problem and should be covered under the warranty.

evilkorn said:
Just to be clear, you did wipe after all those?
Click to expand...
Click to collapse
i wipe out everything b4 i flash anything. and yes i wiped out data, cache dalvik cache after i flashed to see if it makes any differences.
i am thinking about sending it for replacement idk..
i know mine is unlocked but..oh well..
did anyone expereinced this weird wifi issue?

eunkipark92 said:
i wipe out everything b4 i flash anything. and yes i wiped out data, cache dalvik cache after i flashed to see if it makes any differences.
i am thinking about sending it for replacement idk..
i know mine is unlocked but..oh well..
did anyone expereinced this weird wifi issue?
Click to expand...
Click to collapse
try going back to stock

andy2na said:
try going back to stock
Click to expand...
Click to collapse
yae im trying it again and having bit of a problem in a proper way .
is there a chat or anything ?

Wifi problem with 4.3 ROMs (CM,AOKP and PACrom)

Hello everyone,
I need your help because I have a problem with my wifi connection...
I previously installed version 10.1 of CyanogenMod and it works perfectly! Everything is functional and very stable.
But I would like to try some other Roms and change for Android 4.3 or 4.3.1 ...
The problem is that with the version 10.2 of CM, wifi does not connect ... It is active but after entering the password it says " connection" for a second then "Registred, secured with WPA " but it is not connected!
And it also does with other roms on android 4.3 ! AOKP and PAC-man ROM too! So I think the problem comes from the compatibility between my Xperia SP and android 4.3 ...
So I cannot use one ! Although Roms seem fully functional , I do not have wifi !
Do you have an idea to help me?
Thanks for your help
PS : I already tried to reinstall several times with wipe data , system , cache etc. flashing the kernel again ... and all that with CM10.2 , AOKP and PACROM ... nothing to do . The wifi does not connect unless I do a restore of my 10.1 CM ... then it works.

robbyus1111 said:
Hello everyone,
I need your help because I have a problem with my wifi connection...
I previously installed version 10.1 of CyanogenMod and it works perfectly! Everything is functional and very stable.
But I would like to try some other Roms and change for Android 4.3 or 4.3.1 ...
The problem is that with the version 10.2 of CM, wifi does not connect ... It is active but after entering the password it says " connection" for a second then "Registred, secured with WPA " but it is not connected!
And it also does with other roms on android 4.3 ! AOKP and PAC-man ROM too! So I think the problem comes from the compatibility between my Xperia SP and android 4.3 ...
So I cannot use one ! Although Roms seem fully functional , I do not have wifi !
Do you have an idea to help me?
Thanks for your help
PS : I already tried to reinstall several times with wipe data , system , cache etc. flashing the kernel again ... and all that with CM10.2 , AOKP and PACROM ... nothing to do . The wifi does not connect unless I do a restore of my 10.1 CM ... then it works.
Click to expand...
Click to collapse
Hy there .. i use 10.2 right now.. and i have no wifi problems at all .. I`m not sure what causes your wifi problem.. but i triyed PacMan rom for a few days and my wifi works perfectly fine.. don`t think it``s a ROM problem.. I use SP c5303 ..
Try to format all the system and then try again..

adryanodej said:
Hy there .. i use 10.2 right now.. and i have no wifi problems at all .. I`m not sure what causes your wifi problem.. but i triyed PacMan rom for a few days and my wifi works perfectly fine.. don`t think it``s a ROM problem.. I use SP c5303 ..
Try to format all the system and then try again..
Click to expand...
Click to collapse
Hi! Thanks for your answer!
I already did a format /system in the CWM so when you say "format ALL the system" you mean there is something else to do or only that?

robbyus1111 said:
Hi! Thanks for your answer!
I already did a format /system in the CWM so when you say "format ALL the system" you mean there is something else to do or only that?
Click to expand...
Click to collapse
I mean make a fully wipe (wipe data/factory reset, wipe dalvik cache) and in mounts and storage Format System.

adryanodej said:
I mean make a fully wipe (wipe data/factory reset, wipe dalvik cache) and in mounts and storage Format System.
Click to expand...
Click to collapse
I tried already... I always do that before installing a Rom and I even tried to format sdcard but it still doesn't work. :crying:
Any other idea?
Thanks anyway

robbyus1111 said:
I tried already... I always do that before installing a Rom and I even tried to format sdcard but it still doesn't work. :crying:
Any other idea?
Thanks anyway
Click to expand...
Click to collapse
i don`t know what to say.. for me it` works well .. i think something it`s not compatible with your phone..Try to ask about your problem in this thread: http://forum.xda-developers.com/showthread.php?t=2493994
Hope i helped you ..

OK I made it work changing the password of my internet box from a WPA security to a WEP security... Strange isn't it?
But it seems the connection is very bad, about half the speed, even on my PC...
So I have to put the WPA security back on... The problem is still there.

So I did a logcat and here is what I found concerning wifi (at least I think...) :
PHP:
11-12 11:02:19.364 D/WifiController(573): WifiController msg { what=155656 when=0 } deferred for 486ms
11-12 11:02:19.364 I/WifiService(573): WifiService starting up with Wi-Fi enabled
11-12 11:02:19.364 D/WifiService(573): setWifiEnabled: true pid=573, uid=1000
11-12 11:02:19.544 D/WifiHW (573): Unable to unload driver module "wlan": No such file or directory
11-12 11:02:19.754 D/CommandListener(205): Trying to bring down wlan0
11-12 11:02:19.845 D/WifiController(573): DEFERRED_TOGGLE handled
11-12 11:02:20.395 D/WifiHW (573): close sockets 1
11-12 11:02:22.097 I/wpa_supplicant(737): wlan0: Trying to associate with SSID 'Freebox_Glad_et_Pierre'
11-12 11:02:22.417 I/wpa_supplicant(737): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
11-12 11:02:25.090 W/WifiNormalizer(851): No specific device detected. Offset set to -7.
11-12 11:02:39.546 I/WifiService(573): WifiService trying to set country code to fr with persist set to true
11-12 11:02:48.705 I/NetworkMonitor(1934): Connectivity status changed to (CONNECTED) unmetered wifi: false mobileOrMetered: trueunmetered ethernet: false
11-12 11:02:54.081 I/wpa_supplicant(737): wlan0: Trying to associate with SSID 'Freebox_Glad_et_Pierre'
11-12 11:02:54.091 D/CommandListener(205): Clearing all IP addresses on wlan0
11-12 11:02:54.101 D/ConnectivityService(573): ConnectivityChange for WIFI: DISCONNECTED/DISCONNECTED
11-12 11:02:54.101 D/ConnectivityService(573): Attempting to switch to mobile
11-12 11:02:54.101 D/ConnectivityService(573): Attempting to switch to BLUETOOTH_TETHER
11-12 11:02:54.101 D/Nat464Xlat(573): requiresClat: netType=1, hasIPv4Address=false
11-12 11:02:54.391 I/wpa_supplicant(737): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
11-12 11:03:06.364 I/wpa_supplicant(737): wlan0: Trying to associate with SSID 'Freebox_Glad_et_Pierre'
11-12 11:03:06.705 I/wpa_supplicant(737): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
11-12 11:03:18.647 I/wpa_supplicant(737): wlan0: Trying to associate with SSID 'Freebox_Glad_et_Pierre'
11-12 11:03:18.888 D/ConnectivityService(573): [CheckMp] isMobileOk: not connected ni=NetworkInfo: type: mobile_hipri[DCHSPAP], state: DISCONNECTED/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
11-12 11:03:18.958 I/wpa_supplicant(737): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
11-12 11:03:28.104 D/SupplicantStateTracker(573): Association getting rejected, disabling network 2
Does anyone see something strange ?
Thx for helping
Here is the full logcat:

Did you fix this issue yet? I'm having trouble with my Note 2...

[Q] Is NC2 ODIN FIRMWARE AVAILABLE?

I am trying to go stock, and wasn't sure if there was an ODIN NC2 out there. I was searching and couldn't find anything.
Any hints to get back to stock on nc2?

matteosaeed said:
I am trying to go stock, and wasn't sure if there was an ODIN NC2 out there. I was searching and couldn't find anything.
Any hints to get back to stock on nc2?
Click to expand...
Click to collapse
There is no odin version of NC2 available at this time.
What you can do is download the UrDroid Stock NC2 from this post - http://forum.xda-developers.com/showthread.php?t=2786043
DOWNLOAD THE ODEXED VERSION
Odexed is Stock, Deodexed is not.
You will need to flash it using Safestrap.
Once you get it up and booting - install safestrap again, uninstall recovery, uninstall safestrap, and lastly unroot.
Sounds like a lot, but it will be quick and that will be full stock.

Thank you. I did that and got back to nc2 safely!

But is it the real OTA update? With the white battery? I'm trying to get back to nc2 myself
Sent from my SM-N900A using XDA Free mobile app

richgangsta41 said:
But is it the real OTA update? With the white battery? I'm trying to get back to nc2 myself
Sent from my SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
YEAH!!!!! Exactly HOW do we return this phone to the AT&T store??? I've had a couple failed attempts....
I think people need to clarify the difference between stock and stock that's even had one file modified. Very confusing.

richgangsta41 said:
But is it the real OTA update? With the white battery? I'm trying to get back to nc2 myself
Sent from my SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
jreed3786 said:
YEAH!!!!! Exactly HOW do we return this phone to the AT&T store??? I've had a couple failed attempts....
I think people need to clarify the difference between stock and stock that's even had one file modified. Very confusing.
Click to expand...
Click to collapse
EDIT :
To my knowledge that is the real NC2 version without any mods. You would have to ask Carl1961 if you want to confirm whether its full stock or not.
I don't think a DEV would call it a stock rom, if it wasn't fully stock.

147aaron said:
EDIT :
To my knowledge that is the real NC2 version without any mods. You would have to ask Carl1961 if you want to confirm whether its full stock or not.
I don't think a DEV would call it a stock rom, if it wasn't fully stock.
Click to expand...
Click to collapse
It's not completely stock. There are files changed if you would read the first post it says "
Stock NC2 KitKat ROM rooted that I made for myself, Sharing for others to Use​Thanks to bri315317 for Updater-script to get NC2 installed !!
Thanks to K-Alzwayed for Stock TWRP system backup
Ver_1 :
Replaced missing and different Bin files ( WiFi should work and remember password)
Files replaced:
adsprpcd
androidshmservice
apaservice
app_process.orig
at_distributor
ATFWD-daemon
auditd
bintvoutservice
bootanimation
bootchecker
bugreport
charger_monitor
charon
clatd
cnd
connfwexe
createsystemfile
cs
ddexe
ddexe_real
debuggerd
dhcpcd
diag_uart_log
dnsmasq
drmserver
drsd
dumpstate
dumpsys
e2fsck
e2fsck.bin
edmaudit
efsks
gsiff_daemon
hostapd
icd
immvibed
imsqmidaemon
installd
insthk
ipruleset
jackservice
keystore
ks
logwrapper
mcDriverDaemon
mdnsd
mediaserver
mm-pp-daemon
mm-qcamera-daemon
mpdecision
mtpd
netd
npsmobex
ping
pppd
prepare_param.sh
qcks
qmuxd
qosmgr
qrngd
qseecomd
racoon
rfs_access
rild
rmt_storage
samsungpowersoundplay
scranton_RD
sdcard
secure_storage_daemon
sensorhubservice
servicemanager
smdexe
ss_conn_daemon
ssr_diag
surfaceflinger
thermald
thermal-engine
tima_dump_log
time_daemon
vold
wcnss_service
wpa_supplicant

440bro said:
It's not completely stock. There are files changed if you would read the first post it says "
Stock NC2 KitKat ROM rooted that I made for myself, Sharing for others to Use​Thanks to bri315317 for Updater-script to get NC2 installed !!
Thanks to K-Alzwayed for Stock TWRP system backup
Ver_1 :
Replaced missing and different Bin files ( WiFi should work and remember password)
Files replaced:
adsprpcd
androidshmservice
apaservice
app_process.orig
at_distributor
ATFWD-daemon
auditd
bintvoutservice
bootanimation
bootchecker
bugreport
charger_monitor
charon
clatd
cnd
connfwexe
createsystemfile
cs
ddexe
ddexe_real
debuggerd
dhcpcd
diag_uart_log
dnsmasq
drmserver
drsd
dumpstate
dumpsys
e2fsck
e2fsck.bin
edmaudit
efsks
gsiff_daemon
hostapd
icd
immvibed
imsqmidaemon
installd
insthk
ipruleset
jackservice
keystore
ks
logwrapper
mcDriverDaemon
mdnsd
mediaserver
mm-pp-daemon
mm-qcamera-daemon
mpdecision
mtpd
netd
npsmobex
ping
pppd
prepare_param.sh
qcks
qmuxd
qosmgr
qrngd
qseecomd
racoon
rfs_access
rild
rmt_storage
samsungpowersoundplay
scranton_RD
sdcard
secure_storage_daemon
sensorhubservice
servicemanager
smdexe
ss_conn_daemon
ssr_diag
surfaceflinger
thermald
thermal-engine
tima_dump_log
time_daemon
vold
wcnss_service
wpa_supplicant
Click to expand...
Click to collapse
*facepalm* Oops! That is why its always good to read the whole post. Thank's for clearing that up 440bro :highfive:

So how exactly do you return to stock to bring the phone back to AT&T without them knowing, for warranty return?
440bro said:
It's not completely stock. There are files changed if you would read the first post it says "
Stock NC2 KitKat ROM rooted that I made for myself, Sharing for others to Use​Thanks to bri315317 for Updater-script to get NC2 installed !!
Thanks to K-Alzwayed for Stock TWRP system backup
Ver_1 :
Replaced missing and different Bin files ( WiFi should work and remember password)
Files replaced:
adsprpcd
androidshmservice
apaservice
app_process.orig
at_distributor
ATFWD-daemon
auditd
bintvoutservice
bootanimation
bootchecker
bugreport
charger_monitor
charon
clatd
cnd
connfwexe
createsystemfile
cs
ddexe
ddexe_real
debuggerd
dhcpcd
diag_uart_log
dnsmasq
drmserver
drsd
dumpstate
dumpsys
e2fsck
e2fsck.bin
edmaudit
efsks
gsiff_daemon
hostapd
icd
immvibed
imsqmidaemon
installd
insthk
ipruleset
jackservice
keystore
ks
logwrapper
mcDriverDaemon
mdnsd
mediaserver
mm-pp-daemon
mm-qcamera-daemon
mpdecision
mtpd
netd
npsmobex
ping
pppd
prepare_param.sh
qcks
qmuxd
qosmgr
qrngd
qseecomd
racoon
rfs_access
rild
rmt_storage
samsungpowersoundplay
scranton_RD
sdcard
secure_storage_daemon
sensorhubservice
servicemanager
smdexe
ss_conn_daemon
ssr_diag
surfaceflinger
thermald
thermal-engine
tima_dump_log
time_daemon
vold
wcnss_service
wpa_supplicant
Click to expand...
Click to collapse

jreed3786 said:
So how exactly do you return to stock to bring the phone back to AT&T without them knowing, for warranty return?
Click to expand...
Click to collapse
Returning to factory stock all depends on how heavily YOU modified the device.
Here's some scenarios.
1. You rooted. Installed superuser. Installed titanium backup (or favorite app for backup) and backed up entire system. Then you modified with xposed, froze apps, or whatever you wanted to do with root access.
Now to return to stock you remove xposed, unfreeze apps, and undo whatever you did with root. If you changed anything system wise use titanium (or favorite app) to restore system files. Then in superuser click "full un-root". You should be back to stock now. Perform a factory data reset if you don't think your getting your phone back.
2. You rooted, installed superuser, busy box, and safestrap. In safestrap you made a nandroid backup and saved it somewhere. Then you wiped and installed a rom to some slot and had fun!
Now to return to stock place your nandroid backup in stock slot. Reboot and it should be back to stock with root. Uninstall safestrap and busy box. Now use superuser to do a full un-root.
3. You rooted and had fun! You forgot to backup anything and are now scared. You can go to see a Samsung rep at bestbuy and have him re-flash kit Kat for ya.
4. You rooted and had fun! But didn't back anything up and don't have a bestbuy nearby. You can search for an at&t service center. They can re-flash kit Kat for you.
5. You rooted and had fun! But didn't backup and there's no bestbuy or at&t service nearby. You can send your device to www.mobiletechvideos.com and pay them to fix your fun. The process usually takes a week.
6. You rooted and had fun but no backups, no bestbuy, no at&t service, and can't afford mobile tech. You are now up the creek without a paddle. You have to wait for a restore nc2 thread, or Odin tar file gets released.

Help!
Got it thanks

MiiLLZz said:
I am currently soft bricked with no way back to being fine again. I tried to manually install with external storage with the stock recovery and it didnt work. Tried kies, didnt work. And i tried to find the odin file for nc2 and i couldnt find it. But i did find odin files for MLG leaked 4.4.2 kitkat and that also didnt work. I tried everything i know. If anyone can assist me in unbricking my phone i would be very grateful. Thank you
Click to expand...
Click to collapse
This will get you back up and running - http://forum.xda-developers.com/showthread.php?t=2703006

WiFi and Bluetooth won't turn on on any kernel and firmware (stock / custom)

Hello,
today I was working with my Xperia Z (C6603) and flashed a CM12 build. After having some problems with TWRP, I solved it in the end an TWRP and CM12 were working fine. But WiFi and Bluetooth won't turn on anymore. When I press "turn on" it takes some time and then the switch turns off again. A MAC address is not shown anymore. I tried to flash stock firmware with Flashtool, but didn't change anything.
Can someone help me to solve this? Is my phone partially bricked?
Thanks a lot!

Some update as I try to find the problem. I looked into logcat and only find this info when I try to turn on WiFi:
Code:
D/WifiService( 814): setWifiEnabled: true pid=1072, uid=10008
E/WifiStateMachine( 814): Failed to load driver
And when I try to execute wpa_suuplicant manually with "/system/bin/wpa_supplicant -Dnl80211 -iwlan0 -c/system/etc/wifi/wpa_supplicant.conf"
Code:
I/wpa_supplicant( 9440): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 9440): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 9440): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 9440): wlan0: Failed to initialize driver interface

Anyone? Just a hint to narrow down the problem?

Hi,
I have similar problem. My WiFi stopped working out of the blue.
I am quite sure I didn't changed anything. System crash occured when I was switching from Airplane mode to Normal mode (this usually turns WiFi on, if it was activated (and then deactivated) in Airplane mode). Then I got stucked in bootloop. Wiping dalvik-cache helped, but it was not the cause. At first, bluetooth was crashing too, but now it seems it works.
In *#*#INFO#*#* I can see
Code:
Supplicant state: UNINITALIZED
. LogCat issues are almost the same.
I've tried factory reset, but it didn't solved the problem. I've checked permissions, reflashed wifi-modules, tried WiFi Fixer app, reinstalled kernel, flashed another kernel, checked the wpa_supplicant.conf…but it still doesn't work.
EDIT: Oh, I forgot to mention my device: Xperi Mini St15i (Smultron), rooted, unlocked bootloader, Stock ICS ROM (only de-bloated, it worked until now) 4.0.4, build number 4.1.B.0.587. I've used kernel Kappa v1.6, but after the error occured, I tried switch to Rage kernel v2.32.
EDIT2: I've tried to restore original hosts, wpa_supplicant.conf, modules, wifi/*, etc....almost everything and nothing helped. I've flashed original stock ROM (you can find flashable stock ICS ROM for st15i here). I still don't know what happend and I'd like to know it. Hope I'll never see this problem again…

[KERNEL] SM-T713/T719 permissive kernel

Permissive stock kernel for the Samsung Galaxy Tab S2 SM-T713/T719/T813.
Rooting restrictions removed
Forced encryption and DM-verity disabled
SElinux permissive
Working ADB
Added F2FS support
Enabled standard CPU Governors - PERFORMANCE, POWERSAVE, CONSERVATIVE, INTERACTIVE, USERSPACE
For safety make a backup of your existing boot.img with TWRP.
This will trip the knox counter if you haven't already.
Flash with ODIN or extract the boot.img and flash with TWRP.
T713XXU1APD9_permissive_boot_5816
T719XXU1APD7_permissive_boot_9816
T813XXU1APD9_permissive_boot_16816
Source code: https://github.com/ashyx/kernel_gts28ve-gts210ve
.

Testing now. And I think you made a mistake - the only firmware for the T713 right now is PD9, not PD8
---------- Post added at 04:28 PM ---------- Previous post was at 03:59 PM ----------
Nope it doesn't boot. It just hangs at the "Samsung Galaxy Tab S2" (bootloader) screen. All that appears is
Code:
set warranty bit: kernel
There is no red "SELinux not enforcing" message.
The screen flashes (presumably rebooting?)
My bootloader is T713XXU1APD9. I'm running Lightning ROM (although I can't see that mattering...?)

Lightn1ng said:
Testing now. And I think you made a mistake - the only firmware for the T713 right now is PD9, not PD8
---------- Post added at 04:28 PM ---------- Previous post was at 03:59 PM ----------
Nope it doesn't boot. It just hangs at the "Samsung Galaxy Tab S2" (bootloader) screen. All that appears is
Code:
set warranty bit: kernel
There is no red "SELinux not enforcing" message.
The screen flashes (presumably rebooting?)
My bootloader is T713XXU1APD9. I'm running Lightning ROM (although I can't see that mattering...?)
Click to expand...
Click to collapse
Yep should be APD9.
Strange how the same kernel boots recovery just fine.
I take it you are still running unencrypted?
Can you pull:
cat /proc/last_kmsg >/sdcard/last_kmsg.txt

ashyx said:
Yep should be APD9.
Strange how the same kernel boots recovery just fine.
I take it you are still running unencrypted?
Click to expand...
Click to collapse
"Same kernel boots recovery fine" - aren't the kernel and recovery completely separate? Or are you talking about TWRP being built from that kernel.
Yes, I am unencrypted. Thanks for all the help here.
---------- Post added at 04:45 PM ---------- Previous post was at 04:44 PM ----------
ashyx said:
Can you pull:
cat /proc/last_kmsg >/sdcard/last_kmsg.txt
Click to expand...
Click to collapse
Do this where? In TWRP after booting the faulty kernel?

Lightn1ng said:
"Same kernel boots recovery fine" - aren't the kernel and recovery completely separate? Or are you talking about TWRP being built from that kernel.
Yes, I am unencrypted. Thanks for all the help here.
Click to expand...
Click to collapse
Yes they are separate, but I am using this kernel in the latest build of TWRP.

I think you missed my previous post (maybe I posted it right before you posted and you didn't see it?) Where should I get the last_kmesg from? In TWRP after booting the broken kernel?

Lightn1ng said:
I think you missed my previous post (maybe I posted it right before you posted and you didn't see it?) Where should I get the last_kmesg from? In TWRP after booting the broken kernel?
Click to expand...
Click to collapse
Boot to twrp straight after boot failure.
Sent from my SM-T280 using XDA-Developers mobile app

ashyx said:
Boot to twrp straight after boot failure.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
On it.

Last_kmsg is attached.
Look, I'm no expert, but based on that log, it doesn't look like the boot made it very far.
Also, if its worth noting, plugging in the charger while its off does pull up the charging animation, which I know is handled by the kernel.
EDIT: this kmsg might actually be the kernel booting to show the battery charging animation. I'll get a new one now.

Here's a new last_kmsg from an Android boot (the failed one) attached.

Lightn1ng said:
Here's a new last_kmsg from an Android boot (the failed one) attached.
Click to expand...
Click to collapse
Is that directly after the failed boot?
I haven't got time to pick through it now as I'm turning in. Will try and get a look tomorrow.
Sent from my SM-T280 using XDA-Developers mobile app

ashyx said:
Is that directly after the failed boot?
I haven't got time to pick through it now as I'm turning in. Will try and get a look tomorrow.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes this is right after the failed boot. Take your time

Lightn1ng said:
Yes this is right after the failed boot. Take your time
Click to expand...
Click to collapse
Corrected a couple of errors in the kmsg. Hopefully this one boots: T713XXU1APD9_permissive_boot_26716
.

ashyx said:
Corrected a couple of errors in the kmsg. Hopefully this one boots: T713XXU1APD8_permissive_boot.tar
Click to expand...
Click to collapse
Wait theres no link there. What do I flash?

ashyx said:
Corrected a couple of errors in the kmsg. Hopefully this one boots: T713XXU1APD9_permissive_boot_26716
.
Click to expand...
Click to collapse
Flashed the new kernel. This time it boots. Wi-Fi doesn't turn on. WiFi works fine on the kernel included in lightning rom.
In case it matters, I'm extracting the boot.img from the tar and flashing it in twrp via
Code:
dd if=/sdcard/Download/pd9_ashyx_0726_kernel/boot.img of=/dev/block/bootdevice/by-name/boot

Lightn1ng said:
Flashed the new kernel. This time it boots. Wi-Fi doesn't turn on. WiFi works fine on the kernel included in lightning rom.
In case it matters, I'm extracting the boot.img from the tar and flashing it in twrp via
Code:
dd if=/sdcard/Download/pd9_ashyx_0726_kernel/boot.img of=/dev/block/bootdevice/by-name/boot
Click to expand...
Click to collapse
Is the kernel permissive?
DD is fine, but unnecessary. Just use the image flashing options in TWRP.
The kernel is built from APD9 source, so should work.
Can you install the syslog app and pull the logs with it after trying to turn on wifi?

ashyx said:
Is the kernel permissive?
DD is fine, but unnecessary. Just use the image flashing options in TWRP.
The kernel is built from APD9 source, so should work.
Can you install the syslog app and pull the logs with it after trying to turn on wifi?
Click to expand...
Click to collapse
OK I sent you the logs via PM. I think they may have personal info in them so that's why I didn't post them here. Sorry I sent 2 messages as my Internet sucks right now.
Getenforce on this kernel does respond with "Permissive."

Lightn1ng said:
OK I sent you the logs via PM. I think they may have personal info in them so that's why I didn't post them here. Sorry I sent 2 messages as my Internet sucks right now.
Getenforce on this kernel does respond with "Permissive."
Click to expand...
Click to collapse
Thanks, syslog removes any personal info before creating the logs.

Ok, I've had a look at the logs and think these are the lines of interest, this is from LOGCAT:
07-27 09:32:28.091 D/WifiService( 1149): setWifiEnabled: true pid=6012, uid=1000
07-27 09:32:28.091 D/SettingsProvider( 1149): isChangeAllowed() : name = wifi_on
07-27 09:32:28.091 D/WifiController( 1149): [FCC]setFccChannel() is called !!!
07-27 09:32:28.091 D/WifiController( 1149): [FCC]WifiOnly model, setFccChannel(0)!!!
07-27 09:32:28.101 E/WifiHW ( 1149): ##################### set firmware type 0 #####################
07-27 09:32:28.111 E/WifiHW ( 1149): return of insmod : ret = -1, Required key not available
07-27 09:32:28.111 E/WifiStateMachine( 1149): Failed to load driver
07-27 09:32:28.111 E/WifiStateMachine( 1149): sendErrorBroadcast code:10
07-27 09:32:28.111 D/HS20StateMachine( 1149): Broadcast Received: android.net.wifi.WIFI_STATE_CHANGED
07-27 09:32:28.111 I/WifiHs20Service( 1149): Broadcast received:android.net.wifi.WIFI_STATE_CHANGED
07-27 09:32:28.111 I/WifiHs20Service( 1149): Message received 5011
07-27 09:32:28.121 D/NetworkController( 1595): onReceive: intent=Intent { act=android.net.wifi.WIFI_STATE_CHANGED flg=0x4000010 bqHint=4 VirtualScreenParam=Params{mDisplayId=-1, null, mFlags=0x00000000)} (has extras) }
07-27 09:32:28.121 E/WifiController( 1149): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
The error of interest is in red and seems to be caused by this error from DMSG:
[ 263.154359] [2:WifiStateMachin: 1521] Request for unknown module key 'Magrathea: Glacier signing key: e86c91eb461b23b3c218698b09a60a0cd5a2b96b' err -11
I'm assuming this means some sort of module version mismatch with the kernel. The thing is I don't see a specific wifi module built with the kernel?
I'm going to upload the kernel modules, could you make a backup up of the current ones and replace them with the ones I upload then reboot?
Modules: https://www.androidfilehost.com/?fid=24591000424950422
These need to go in system/lib/modules/
Probably need to set permissions to the same as the other modules.
If you don't have time for this at the moment as you are on holiday that's fine it can wait.
Cheers.

@ashyx
Thanks for all the time. I'll try these modules in a moment. One question: are the modules replaced whenever I reflash boot.img or are they on the system partition?