Related
Hello There
I have run into a strange problem: when I copy video files into kindle I get this error:
An unexpected error is preventing the operation. Make a note of this error code, which might be useful if you get additional help to resolve this problem
Error 0x80070057: the parameter is incorrect,
What could be the problem?
So tonight I was bored and wanted to try a new rom, I backed up my current Pacman rom, and went to install rootbox, installation finished succesfully, but when the rom was booting, the bootanimation froze, and suddendly I got this Blue Screen saying the following:
Subsystem Crash!
-----------------------------------------------------------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)
Press key to choose Dload Mode/Reboot/Fastboot
1)Volume Up: Dload Mode.
2) Volume Down: Reboot.
3) Power: Fastboot.
If you choose Dload Mode,
Please do following action.
1)Dload Mode. Please connect USB
2) Get the ram dump image using QCT's Memory Debug App
3) Send em-mail to contact point or [email protected].
-------------------------------------------------------------------------------------------------------
and just below this there are like 8 lines of pure random letters and symbols like "\Zp0ieKjmKxp {(<--51m<rZ--mZi.p0.mKp0x" etc etcetc
So I wiped everything(including format system) and tried reinstalling the rom, got the same result.
Wiped everything again and restored my nandroid backup of PacMan ROM, SAME THING HAPPENED, SAME ERROR ON BOOTANIMATION OF MY PREVIOUS ROM.
So I went ahead and wiped everything again! but now I restored the Stock LG 4.1.2 rom nandroid backup I had from last week, it booted just fine, but the phone didnt reognize my sim card, and after like 3 minutes botted The screen turned off and THE SAME ERROR APPEARED, but this time saying "Kernel Crash!"
Rebooted and the phone booted again just fine, and after like 5 minutes AGAIN SUBSYSTEM CRASH! it ends up happening every time.
The phone boots into recovery, fastboot, download mode, just fine.
I just have no idea on what to do now, I've googled everything but I have found no solutions or helpful information whatsoever, I don''t know what I did wrong, please guys I hope you can help me with this one, I cannot afford a new phone right know, thanks!
EDIT1: After different attempts with wiping and flashing roms and restoring backups with no luck, I was able to boot in my pacmanrom by flashing a different kernel, specifically, Kite Kernel 30, with this kernel the rom boots and it works just fine, although I got a couple of random reboots without the error previously pointed, but the problem is that MY PHONE DOESN'T RECOGNIZE MY SIM CARD ANYMORE, No matter what I do, pull it out pull it in, the phone doesnt even do anything, is like nothing is happening, I have wifi signal but no sim recognition.
Im trying to understand what this problem is all about, how flashing a different kernel made the rom boot? With Kite kernel it boots, but when i flash the old f93 kernel I used for weeks the phone wont boot, i get the same error in the bootanimation.
Please I need some feedback on this, this forum is so dead :S
Can you try kdz back to stock? If it happens after that then send it on repair, as long as you kdz back they can't see what you have done.
Man I live in freakin Venezuela, If I send my phone to LG, best case scenario im gonna get it back(or replaced) in like 3 months -_- I need to fix this on my own
So I used the KDZ to go back to stock firmware, and the phone boots, but in reboots all the time and my sim card is not recognized! Man did I screw up my device so hard?
LRC1710 said:
So tonight I was bored and wanted to try a new rom, I backed up my current Pacman rom, and went to install rootbox, installation finished succesfully, but when the rom was booting, the bootanimation froze, and suddendly I got this Blue Screen saying the following:
Subsystem Crash!
-----------------------------------------------------------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)
Press key to choose Dload Mode/Reboot/Fastboot
1)Volume Up: Dload Mode.
2) Volume Down: Reboot.
3) Power: Fastboot.
If you choose Dload Mode,
Please do following action.
1)Dload Mode. Please connect USB
2) Get the ram dump image using QCT's Memory Debug App
3) Send em-mail to contact point or [email protected].
-------------------------------------------------------------------------------------------------------
and just below this there are like 8 lines of pure random letters and symbols like "\Zp0ieKjmKxp {(<--51m<rZ--mZi.p0.mKp0x" etc etcetc
So I wiped everything(including format system) and tried reinstalling the rom, got the same result.
Wiped everything again and restored my nandroid backup of PacMan ROM, SAME THING HAPPENED, SAME ERROR ON BOOTANIMATION OF MY PREVIOUS ROM.
So I went ahead and wiped everything again! but now I restored the Stock LG 4.1.2 rom nandroid backup I had from last week, it booted just fine, but the phone didnt reognize my sim card, and after like 3 minutes botted The screen turned off and THE SAME ERROR APPEARED, but this time saying "Kernel Crash!"
Rebooted and the phone booted again just fine, and after like 5 minutes AGAIN SUBSYSTEM CRASH! it ends up happening every time.
The phone boots into recovery, fastboot, download mode, just fine.
I just have no idea on what to do now, I've googled everything but I have found no solutions or helpful information whatsoever, I don''t know what I did wrong, please guys I hope you can help me with this one, I cannot afford a new phone right know, thanks!
EDIT1: After different attempts with wiping and flashing roms and restoring backups with no luck, I was able to boot in my pacmanrom by flashing a different kernel, specifically, Kite Kernel 30, with this kernel the rom boots and it works just fine, although I got a couple of random reboots without the error previously pointed, but the problem is that MY PHONE DOESN'T RECOGNIZE MY SIM CARD ANYMORE, No matter what I do, pull it out pull it in, the phone doesnt even do anything, is like nothing is happening, I have wifi signal but no sim recognition.
Im trying to understand what this problem is all about, how flashing a different kernel made the rom boot? With Kite kernel it boots, but when i flash the old f93 kernel I used for weeks the phone wont boot, i get the same error in the bootanimation.
Please I need some feedback on this, this forum is so dead :S
Click to expand...
Click to collapse
what is phone model? E975 or 973?
geoworld_200 said:
what is phone model? E975 or 973?
Click to expand...
Click to collapse
E977
Just stating a probability here. But not sure. Maybe its not that ur phone isn't recognising the sim. Maybe u just have the wrong radios. Try flashing a radio for ur model.
Sent from my LG-E975 using xda app-developers app
I'm getting this:
-----------------------------------------------------------------------------------------------------------------
DemiGod Crash Handler : Kernel Crash! :
Press key to choose Dload Mode/Reboot/Fastboot
1)Volume Up: Dload Mode.
2) Volume Down: Reboot.
3) Power: Fastboot.
If you choose Dload Mode,
Please do following action.
1)Dload Mode. Please connect USB
2) Get the ram dump image using QCT's Memory Debug App
3) Send em-mail to contact point or [email protected].
-------------------------------------------------------------------------------------------------------
I've been using CM10.1 for 1 month since I bought my Optimus G and it was great. No crashes and it was a joy to use. Today I started getting this message with the phone rebooting itself after a couple of seconds. I tried a wipe and flash CM10.1 again from scratch but I cannot get it fixed. The phone keeps rebooting over and over again. Now I'm trying to flash the stock rom but it doesn;t work as the phone keeps rebooting all the time. The LG support tool doesn't even connect to it long enough. Any suggestions?
edvar said:
I'm getting this:
-----------------------------------------------------------------------------------------------------------------
DemiGod Crash Handler : Kernel Crash! :
Press key to choose Dload Mode/Reboot/Fastboot
1)Volume Up: Dload Mode.
2) Volume Down: Reboot.
3) Power: Fastboot.
If you choose Dload Mode,
Please do following action.
1)Dload Mode. Please connect USB
2) Get the ram dump image using QCT's Memory Debug App
3) Send em-mail to contact point or [email protected].
-------------------------------------------------------------------------------------------------------
I've been using CM10.1 for 1 month since I bought my Optimus G and it was great. No crashes and it was a joy to use. Today I started getting this message with the phone rebooting itself after a couple of seconds. I tried a wipe and flash CM10.1 again from scratch but I cannot get it fixed. The phone keeps rebooting over and over again. Now I'm trying to flash the stock rom but it doesn;t work as the phone keeps rebooting all the time. The LG support tool doesn't even connect to it long enough. Any suggestions?
Click to expand...
Click to collapse
Dude I managed to flash the stock ROM in download mode with the tool but the phone had the same issue, kept rebooting no matter what I did , tried everything and nothing solved it, took it to warranty and they fixed it by replacing the logic board...
Enviado desde mi LG-E975 usando Tapatalk 4
LRC1710 said:
Dude I managed to flash the stock ROM in download mode with the tool but the phone had the same issue, kept rebooting no matter what I did , tried everything and nothing solved it, took it to warranty and they fixed it by replacing the logic board...
Enviado desde mi LG-E975 usando Tapatalk 4
Click to expand...
Click to collapse
What tool did you use? I'm trying to flash stock so I can get it fixed using the warranty
edvar said:
What tool did you use? I'm trying to flash stock so I can get it fixed using the warranty
Click to expand...
Click to collapse
Used the LG oficial tool, but put the phone in download mode first
The phone goes in download mode fine but the LG Tool doesn't recognize it's connected. I tried to use this other tool http://forum.xda-developers.com/showthread.php?p=44186257 but the phone just restarts into fastboot and doesn't do anything.
I forgot to mention I used this tool before to try and re-flash CM10: http://forum.xda-developers.com/showthread.php?t=2230994 . Now I don't even get the LG logo at boot anymore, just a Google logo.
edvar said:
The phone goes in download mode fine but the LG Tool doesn't recognize it's connected. I tried to use this other tool http://forum.xda-developers.com/showthread.php?p=44186257 but the phone just restarts into fastboot and doesn't do anything.
I forgot to mention I used this tool before to try and re-flash CM10: http://forum.xda-developers.com/showthread.php?t=2230994 . Now I don't even get the LG logo at boot anymore, just a Google logo.
Click to expand...
Click to collapse
UPDATE:
I managed to install stock using the KDZ Updater. When it begins the process the phone reboots into fasboot and I guess the KDZ Updater doesn't know what do to after that. With the KDZ Updater still running on the computer I just disconnected the phone and put it back in Download Mode. After that KDZ Updater started to do its thing and re-flashed stock! Now I can send the phone for repair and use the warranty
I have same issues with my LGE-975, EU version.
This can happen once per month. Or 10 times a day
It's clean install, did it two times just to be sure. Updated baseband from 10b to 10d. So now it's
LGE975AT-00-V10d-EUR-XX-APR-01-2013+0
CM 10.1.2-e975
kernel 3.4.0-CM+ [email protected] #1 Thu Jul 11 18:03:45 PDT 2013
buildnumber cm_e975-userbug 4.2.2 JDQ39E
eng.jenkins.20130711.175036 test-keys
The only trace in logs seems to be this (from last_kmsg):
pmmSendInitPowerSaveMsg: 615: Beacon count is zero, can not retrieve the TSF, failing the Enter Bmps Request
[10015.935661 / 08-12 21:41:00.454]
[10015.935722 / 08-12 21:41:00.454] [WLAN][706:E E ] pmmInitBmpsPwrSave: 485: pmmBmps: Init Power Save Request Failed: Sending Response: 1
[10015.935753 / 08-12 21:41:00.454]
[10015.935844 / 08-12 21:41:00.454] [WLAN][706:E :SME] pmcProcessResponse: 1367: Response message to request to enter BMPS indicates failure, status 235
[10015.935875 / 08-12 21:41:00.454]
[10016.935509 / 08-12 21:41:01.455] [WLAN][706:E E ] pmmSendInitPowerSaveMsg: 615: Beacon count is zero, can not retrieve the TSF, failing the Enter Bmps Request
[10016.935539 / 08-12 21:41:01.455]
[10016.935600 / 08-12 21:41:01.455] [WLAN][706:E E ] pmmInitBmpsPwrSave: 485: pmmBmps: Init Power Save Request Failed: Sending Response: 1
[10016.935631 / 08-12 21:41:01.455]
[10016.935692 / 08-12 21:41:01.455] [WLAN][706:E :SME] pmcProcessResponse: 1367: Response message to request to enter BMPS indicates failure, status 235
------------------------------------------------- Lines above are OK----------------------------------------------------
aaand now goes bang...
[10016.935722 / 08-12 21:41:01.455]
[10017.007628 / 08-12 21:41:01.525] mdm_errfatal: Reseting the mdm due to an errfatal
[10017.007689 / 08-12 21:41:01.525] subsys-restart: subsystem_restart_dev(): Restart sequence requested for external_modem, restart_level = 1.
[10017.007781 / 08-12 21:41:01.525] Kernel panic - not syncing: subsys-restart: Resetting the SoC - external_modem crashed.
[10017.007903 / 08-12 21:41:01.525] [<c0014478>] (unwind_backtrace+0x0/0x11c) from [<c084be9c>] (panic+0x90/0x1d8)
[10017.007995 / 08-12 21:41:01.525] [<c084be9c>] (panic+0x90/0x1d8) from [<c005c320>] (subsystem_restart_dev+0x134/0x174)
[10017.008056 / 08-12 21:41:01.525] [<c005c320>] (subsystem_restart_dev+0x134/0x174) from [<c0079cc4>] (mdm_errfatal+0x6c/0x88)
[10017.008147 / 08-12 21:41:01.525] [<c0079cc4>] (mdm_errfatal+0x6c/0x88) from [<c00cf328>] (handle_irq_event_percpu+0xb0/0x290)
[10017.008239 / 08-12 21:41:01.525] [<c00cf328>] (handle_irq_event_percpu+0xb0/0x290) from [<c00cf544>] (handle_irq_event+0x3c/0x5c)
[10017.008300 / 08-12 21:41:01.525] [<c00cf544>] (handle_irq_event+0x3c/0x5c) from [<c00d1dcc>] (handle_edge_irq+0x12c/0x168)
[10017.008361 / 08-12 21:41:01.525] [<c00d1dcc>] (handle_edge_irq+0x12c/0x168) from [<c00ceba4>] (generic_handle_irq+0x2c/0x40)
[10017.008452 / 08-12 21:41:01.525] [<c00ceba4>] (generic_handle_irq+0x2c/0x40) from [<c025a90c>] (msm_summary_irq_handler+0x7c/0xbc)
[10017.008514 / 08-12 21:41:01.525] [<c025a90c>] (msm_summary_irq_handler+0x7c/0xbc) from [<c00cf328>] (handle_irq_event_percpu+0xb0/0x290)
[10017.008575 / 08-12 21:41:01.525] [<c00cf328>] (handle_irq_event_percpu+0xb0/0x290) from [<c00cf544>] (handle_irq_event+0x3c/0x5c)
[10017.008666 / 08-12 21:41:01.525] [<c00cf544>] (handle_irq_event+0x3c/0x5c) from [<c00d2004>] (handle_fasteoi_irq+0xdc/0x148)
[10017.008727 / 08-12 21:41:01.525] [<c00d2004>] (handle_fasteoi_irq+0xdc/0x148) from [<c00ceba4>] (generic_handle_irq+0x2c/0x40)
[10017.008788 / 08-12 21:41:01.525] [<c00ceba4>] (generic_handle_irq+0x2c/0x40) from [<c000ede0>] (handle_IRQ+0x7c/0xc0)
[10017.008849 / 08-12 21:41:01.525] [<c000ede0>] (handle_IRQ+0x7c/0xc0) from [<c00085d0>] (gic_handle_irq+0x94/0x110)
[10017.008910 / 08-12 21:41:01.525] [<c00085d0>] (gic_handle_irq+0x94/0x110) from [<c0859500>] (__irq_svc+0x40/0x70)
[10017.008971 / 08-12 21:41:01.525] Exception stack(0xc0e05f28 to 0xc0e05f70)
[10017.009002 / 08-12 21:41:01.525] 5f20: 00000000 00000000 00000001 00000000 00000000 00000000
[10017.009063 / 08-12 21:41:01.525] 5f40: c0e58108 00000003 00000000 c0e58108 00000000 00000000 00000000 c0e05f70
[10017.009093 / 08-12 21:41:01.525] 5f60: c00ee2a4 c005de64 60000013 ffffffff
[10017.009185 / 08-12 21:41:01.525] [<c0859500>] (__irq_svc+0x40/0x70) from [<c005de64>] (msm_cpuidle_enter+0x70/0x78)
[10017.009246 / 08-12 21:41:01.525] [<c005de64>] (msm_cpuidle_enter+0x70/0x78) from [<c04bce70>] (cpuidle_enter+0x14/0x18)
[10017.009307 / 08-12 21:41:01.525] [<c04bce70>] (cpuidle_enter+0x14/0x18) from [<c04bd3f0>] (cpuidle_idle_call+0x1e0/0x3c0)
[10017.009399 / 08-12 21:41:01.525] [<c04bd3f0>] (cpuidle_idle_call+0x1e0/0x3c0) from [<c000f3c4>] (cpu_idle+0x88/0xf0)
[10017.009460 / 08-12 21:41:01.525] [<c000f3c4>] (cpu_idle+0x88/0xf0) from [<c082b508>] (rest_init+0x88/0xa0)
[10017.009551 / 08-12 21:41:01.525] [<c082b508>] (rest_init+0x88/0xa0) from [<c0d008b4>] (start_kernel+0x428/0x490)
[10017.110726 / 08-12 21:41:01.525] wcnss_8960: crash shutdown : 0
[10017.411443 / 08-12 21:41:01.525] Rebooting in 5 seconds..
[10022.420630 / 08-12 21:41:01.525] Going down for restart now
[10022.420661 / 08-12 21:41:01.525] pm8921_turn_on_19p2mhz_clk: Kick Start
[10022.420752 / 08-12 21:41:01.525] check battery fet
[10022.420813 / 08-12 21:41:01.525] pm_chg_batfet_get: get CHG_BATFET_ON=0
DemiGod Crash Handler : critical error LG G2 F320L, please help me?
DemiGod Crash Handler : critical error
Press key to choose Dload Mode/Reboot/Fastboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
3) Power : Fastboot.
If you choose Dload Mode,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get the ram dump image using QCT's Memory Debug App.
3) Send e-mail to contact point ....
no imei, no download mode, no recovery, can't KDZ, can't use plash tool,
I hope someone can help me figure out what the problem is with my phone because I am out of ideas. I've been using the peoples ROM with stock kernel and occasionally my phone calls would be very staticy , but toggling speaker phone removed that issue. Now any ROM I use that doesn't use the stock kernel causes that same issue except I can't toggle it off anymore. Also many kernels I use besides stock causes apps to force close and system process to force close, unless the kernel came with the ROM. I've tried wiping my internal storage, formatting everything, installing any kernel I can find, fixing permissions, clear long cache 100's of times, flashing kernelcleaner, and I really don't know what to do next. Any advice? I really don't want to be stuck on 4.1.2.
Can I get any help on this?
Sent from my SPH-L710 using xda app-developers app
dokosatchii said:
Can I get any help on this?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Maybe try a clean install. You could always take a logcat to see if it is phone related. May also be a defective earpiece
lvpre said:
Maybe try a clean install. You could always take a logcat to see if it is phone related. May also be a defective earpiece
Click to expand...
Click to collapse
Do you mean wipe internal/system/factory reset and the install a ROM? I've done that but no improvements. I'll try a logcat but have no idea how to decipher it.
Normally I'd agree with you about it being a faulty earpiece, but the same issue pops up if I connect headphones or bluetooth headset during a phone call, still the same static noise. Could it cause all these issues?
I created a logcat but not sure what I should be looking for. I ran a logcat while making a phone call, does someone have a similar logcat so I can compare against? If it turns out the same I guess its just a hardware problem and that I should replace the earpiece? Any advice would be great.
dokosatchii said:
I created a logcat but not sure what I should be looking for. I ran a logcat while making a phone call, does someone have a similar logcat so I can compare against? If it turns out the same I guess its just a hardware problem and that I should replace the earpiece? Any advice would be great.
Click to expand...
Click to collapse
What rom are you using? Sometimes a logcat with have an /e or /f if a file or service is causing the issue. Start the logcat then try to make a call. If you are still having issues, use odin, unified toolkit, or something similar and make your phone completely stock again. Since you did a full wipe (system, data, caches, factory reset), maybe the rom you flashed has a custom kernel that has voltage settings not compatible with your phone. But try the stock rooted rom and then go back to completely unrooted, out-of-the-box stock if that doesn't work.
lvpre said:
What rom are you using? Sometimes a logcat with have an /e or /f if a file or service is causing the issue. Start the logcat then try to make a call. If you are still having issues, use odin, unified toolkit, or something similar and make your phone completely stock again. Since you did a full wipe (system, data, caches, factory reset), maybe the rom you flashed has a custom kernel that has voltage settings not compatible with your phone. But try the stock rooted rom and then go back to completely unrooted, out-of-the-box stock if that doesn't work.
Click to expand...
Click to collapse
I reset the phone to stock using odin, and I still get the issue(sometimes), but it goes away when I toggle speaker phone once. I am starting to think either the speaker is bad or my phone is just faulty.
I have tried every rom possible, MIUI, Paranoid Android, Slimbean, the only one that works is the rom that uses stock kernel like FreeGS3 and The Peoples Rom and even then I still have to toggle the speaker phone to get it working.(not all the time)
ASIDE: When I flash other kernels to test whether it'll work just as ktoonz, etc. the phone just goes through a bootloop or process start to fail, could be related?
EDIT: I created a logcat while placing a phone call while on stock and while using slimbean and I see the following discrepancies:
Stock: 4.1.2
--------------------------------------------------------------------------------------------
[ 08-21 09:50:38.359 170: 170 D/AudioHardwareALSA ]
setParameters() realcall=on
[ 08-21 09:50:38.359 170: 170 D/AudioHardwareALSA ]
>>>> realcall start!!!!
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
setPhoneState() state 2
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
Entering call in setPhoneState()
[ 08-21 09:50:38.369 170:13648 E/AudioPolicyManagerBase ]
unknown stream type
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
getNewDevice() selected device 1
Slimbean ROM 4.3/4.2.2
--------------------------------------------------------------------------------------------
[ 08-21 10:07:52.803 343: 817 D/AudioHardwareInterface ]
setMode(IN_CALL)
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
Any idea's on how to get this AudioPolicyManager to run properly?
EDIT: After endless searching, guidance and effort, I am chalking this up to hardware problems. If anyone is experiencing this issue, I recommended returning the phone to sprint and getting it replaced.
Pretty much what the title says. My phone blue screens. This is the third time that it's happened in the past week...and I first installed it last week...lol
Got an LG G3 D855
Latest version of Paranoid Android
Did a completely clean install: using TWRP, wiped all available partitions, then flashed PA zip.
The first time it happened was the day I installed. I just kinda shrugged it off and went ahead with making it mine. And it happened earlier today and I went ahead and ignored that too. It just happened a third time (few hours after the second time; exact time after is shown below by uptime).
When it blue screened it gave me the following message on screen (without the astrisks)
*****************************
---------------------------------------------------------------------------------------
Subsystem Crash! : modem (susbsys-restart Resetting the SoC)
---------------------------------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash ! : modem (subsys-restart: Resetting the SoC)
Press key to choose Dload Mode or Reboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
If you choose Dload Mode,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get the ram dump image using QPST Configuration
---------------------------------------------------------------------------------------
Board Info
rev.:1.0 speed,pvs: 3,7 serial : muhSerial
---------------------------------------------------------------------------------------
ERR crash log report. Version 3
Error in file wl1trm.c, line 404
Error message: WL1TRM: wl1_trm_grant_callback: Invalid Parameter(%d %d %d)
Time of crash(m-d-y h:m:s): 8-14-2015 21:32:46
Uptime (h:m:s): 5:12:38
Build ID: MPSS.DI.2.0.1.c1.13-0046-M8974AAAAANPZM-1
param: (0x5, 0x0, 0x0)
aux_msg:
qsdm_dbg_msg:
*****************************
Also, from what I've been able to find out, I think that that file might have something to do with radio functions, but I can't be sure because I just did a quick search.
Help would be greatly appreciated!
You should look in your device forum for help on this. I don't think it's a ROM specific issue. I'm pretty sure its a device specific issue
Try to Flash official stock Rom via KDZ or TOT&DLL method.
Hi everyone,
I downloaded and installed the OTA manually using the instructions here. Everything went fine, but after restarting the Wifi does not work. If I go to settings and flip the switch, it flips, but soon moves back into the off position.
Any ideas what I can check, what could be causing this? Thanks!
Just noticed the MAC address for Wifi reads 02:00:00:00:00:00, like the device is not recognised. There's a discussion about this and related problems here: https://productforums.google.com/forum/#!topic/nexus/Qbeb7ZP0wOw
What could be causing this?
strophy said:
Hi everyone,
I downloaded and installed the OTA manually using the instructions here. Everything went fine, but after restarting the Wifi does not work. If I go to settings and flip the switch, it flips, but soon moves back into the off position.
Any ideas what I can check, what could be causing this? Thanks!
Click to expand...
Click to collapse
You could try flashing the vendor.img, system.img, and boot.img from the factory image through fastboot
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You could try flashing the vendor.img, system.img, and boot.img from the factory image through fastboot
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks SlimSnoopOS, will that preserve all my user data? Isn't that done already during the normal OTA process? Should I get the .img files from the OTA or from the full factory image?
I did a little more research on this by viewing the log over adb. The following status/error messages appear when I try to enable Wifi:
08-31 15:07:29.997 859 7849 D WifiService: setWifiEnabled: true pid=11646, uid=1000
08-31 15:07:35.069 522 857 E WifiHW : Failed to write wlan fw path param (No such device)
08-31 15:07:35.075 859 3272 E WifiStateMachine: Failed to reload STA firmware java.lang.IllegalStateException: command '2325 softap fwreload wlan0 STA' failed with '400 2325 SoftAP command has failed'
08-31 15:07:35.078 859 859 E WifiController: WifiControllerWifi turn on failed
I've been unable to find anything related online, but a lot of other people over at the Nexus product forums have this problem after upgrading. Can someone identify the error from these messages?
Thanks!
strophy said:
Thanks SlimSnoopOS, will that preserve all my user data? Isn't that done already during the normal OTA process? Should I get the .img files from the OTA or from the full factory image?
I did a little more research on this by viewing the log over adb. The following status/error messages appear when I try to enable Wifi:
08-31 15:07:29.997 859 7849 D WifiService: setWifiEnabled: true pid=11646, uid=1000
08-31 15:07:35.069 522 857 E WifiHW : Failed to write wlan fw path param (No such device)
08-31 15:07:35.075 859 3272 E WifiStateMachine: Failed to reload STA firmware java.lang.IllegalStateException: command '2325 softap fwreload wlan0 STA' failed with '400 2325 SoftAP command has failed'
08-31 15:07:35.078 859 859 E WifiController: WifiControllerWifi turn on failed
I've been unable to find anything related online, but a lot of other people over at the Nexus product forums have this problem after upgrading. Can someone identify the error from these messages?
Thanks!
Click to expand...
Click to collapse
Yes to both of your first two questions. When flashing factory image files one by one, only userdata.img affects that. Use the factory image.
Sent from my Nexus 5X using Tapatalk
strophy said:
Just noticed the MAC address for Wifi reads 02:00:00:00:00:00, like the device is not recognised. There's a discussion about this and related problems here: https://productforums.google.com/forum/#!topic/nexus/Qbeb7ZP0wOw
What could be causing this?
Click to expand...
Click to collapse
I am having same problem with MAC address = 02:00:00:00:00:00
---------- Post added at 11:09 AM ---------- Previous post was at 10:21 AM ----------
SlimSnoopOS said:
Yes to both of your first two questions. When flashing factory image files one by one, only userdata.img affects that. Use the factory image.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Flash factory image (boot.img, vendor.img, system.img) does not help my Nexus 5x (WiFi wrong MAC address)
xbing6 said:
I am having same problem with MAC address = 02:00:00:00:00:00
---------- Post added at 11:09 AM ---------- Previous post was at 10:21 AM ----------
Flash factory image (boot.img, vendor.img, system.img) does not help my Nexus 5x (WiFi wrong MAC address)
Click to expand...
Click to collapse
Thanks for trying that xbing6. My phone is still OEM locked so I'd like to try and fix this without removing the lock if possible. Unlikely, I know. I found a post where someone has resolved the problem by gaining root and doing a strange series of flashes and setting modifications:
http://chromloop.com/2016/08/how-to-fix-wifi-problem-updating-android-7-0-nougat/
Does anyone more knowledgeable care to theorize about how this happened and if there is anything we can do, beyond the root method or waiting for Google?
probably a hardware issue...
Hi there!
Does your WiFi keep flashing/blinking and showing "Turning on..."?
For example, like in this video: http://www.dailymotion.com/video/x2cuyjt_nexus-5-turning-wifi-on-frozen-problem_tech
I had a very similar problem on my G2 and I believe that these WiFi/BT problems are common to all LG devices, probably due to poor quality WiFi/BT chips used.
Did you drop your device? Did you leave it charging over a longer period, for example, during the night, and observed it getting very warm, or even hot, during the process?
I believe the root cause of your problem is a hardware issue. Someone in the forums suggested that replacing the battery may solve the problem; I can't confirm nor deny this, you might want to try it out.
Also, you might want to check out a detailed summary I've written about this issue here: http://forum.xda-developers.com/general/help/qa-wifi-stuck-mac-020000000000-g2-g3-g4-t3452133
Let us know if you managed to fix the problem!
Good luck!
NimbleWeasel said:
Hi there!
Does your WiFi keep flashing/blinking and showing "Turning on..."?
For example, like in this video: http://www.dailymotion.com/video/x2cuyjt_nexus-5-turning-wifi-on-frozen-problem_tech
I had a very similar problem on my G2 and I believe that these WiFi/BT problems are common to all LG devices, probably due to poor quality WiFi/BT chips used.
Did you drop your device? Did you leave it charging over a longer period, for example, during the night, and observed it getting very warm, or even hot, during the process?
I believe the root cause of your problem is a hardware issue. Someone in the forums suggested that replacing the battery may solve the problem; I can't confirm nor deny this, you might want to try it out.
Also, you might want to check out a detailed summary I've written about this issue here: http://forum.xda-developers.com/general/help/qa-wifi-stuck-mac-020000000000-g2-g3-g4-t3452133
Let us know if you managed to fix the problem!
Good luck!
Click to expand...
Click to collapse
Thanks for the ideas NimbleWeasel. I doubt it though - the wifi went from functioning perfectly to non-functional immediately after applying the update. Never been dropped, less than 2 months old, and doesn't get excessively hot. Google has now reached out to me for a bug report so I'll hopefully hear more from them soon and update this thread.
keep us posted!
Hi strophy,
What about the link, did you watch the video? Does your phone show the effect as in the video?
After reading through the posts again, I think that you might indeed be experiencing a different problem.
I am curious to see what Google will reply!
NimbleWeasel said:
Hi strophy,
What about the link, did you watch the video? Does your phone show the effect as in the video?
After reading through the posts again, I think that you might indeed be experiencing a different problem.
I am curious to see what Google will reply!
Click to expand...
Click to collapse
Hey mate, no my problem is quite different. Firstly, that video is a Nexus 5 running Android 4.x I think? I'm on Nexus 5X running Android 7.0. The wifi switch slides into the on position, stays there for 5 seconds, then slides back by itself. No hotspots are shown at any time. The MAC address also looks like the photo in this post: http://chromloop.com/2016/08/how-to-fix-wifi-problem-updating-android-7-0-nougat/
I don't think my problem is a hardware problem. Let's see what Google says...
My Wifi drops and reconnects whenever I take the phone out of my pocket and open an app that uses data. My data usage has gone up significantly with the Wifi drops. Appears there's others having problems on google product forums with no workaround at this time.
Any help would be appreciated!
ETA: My MAC address appears normal, not the one posted in other forums.
strophy said:
Just noticed the MAC address for Wifi reads 02:00:00:00:00:00, like the device is not recognised. There's a discussion about this and related problems here: https://productforums.google.com/forum/#!topic/nexus/Qbeb7ZP0wOw
What could be causing this?
Click to expand...
Click to collapse
I am facing the same issue. Hope Google finds a solution for this