Hello guys, after I flashed a custom rom my phone went into a bootloop. I decided to flash stock , via odin. After I flashed the stock rom for my region (open european) I got many FC messages , the phone was unusable.
I started digging and flashing roms. Now I have i9505xxugng8 which is a nordic country rom.
When I try to open wifi , the button gets green for one second but then it stays deactivated.
1. Tried to remove battery
2.Tried to delete the wpa_supplicant.conf file from /data/misc/wifi or /system/etc/wifi
3.Tried the non-hos bin.
Nothing worked. I'm desperate.
kplusonline said:
Hello guys, after I flashed a custom rom my phone went into a bootloop. I decided to flash stock , via odin. After I flashed the stock rom for my region (open european) I got many FC messages , the phone was unusable.
I started digging and flashing roms. Now I have i9505xxugng8 which is a nordic country rom.
When I try to open wifi , the button gets green for one second but then it stays deactivated.
1. Tried to remove battery
2.Tried to delete the wpa_supplicant.conf file from /data/misc/wifi or /system/etc/wifi
3.Tried the non-hos bin.
Nothing worked. I'm desperate.
Click to expand...
Click to collapse
refer this thread
Hopefully your answere is in here.
Sent from my Ozcan GT-i9500 using XDA mobile app
Rooted !
Open root explorer > System > Build.prop change this in the build.prop:
ro.securestorage.support=true TO ro.securestorage.support=false Save , Reboot
kplusonline said:
Hello guys, after I flashed a custom rom my phone went into a bootloop. I decided to flash stock , via odin. After I flashed the stock rom for my region (open european) I got many FC messages , the phone was unusable.
I started digging and flashing roms. Now I have i9505xxugng8 which is a nordic country rom.
When I try to open wifi , the button gets green for one second but then it stays deactivated.
1. Tried to remove battery
2.Tried to delete the wpa_supplicant.conf file from /data/misc/wifi or /system/etc/wifi
3.Tried the non-hos bin.
Nothing worked. I'm desperate.
Click to expand...
Click to collapse
I had the same problem and got it fixed easily. After the rom was flashed, I simply factory reset my phone. The wifi worked perfectly then
I had the same problem. It is probably a bug in the software. Try to install a custom rom that doesn't has the ng8 at the end. It worked with my s4 I9505
Ps.Sry for my bad englisch
Related
HI, everyone
i got a problem with my defy recently.
i was running CM7 by Epsylon3.
As we all know, this rom comes with defy basebandswitcher v4.0, and it works well.
Yestoday, i want to update this "BBS" to v4.1. but when i uninstall v4.0 and install v4.1(http://forum.xda-developers.com/show....php?t=1203297), open it , it shows "unable to detect your baseband configuration, it's possibly damaged."
then i reinstall v4.0, but i cant find it in app drawer. i'm sure it's installed and i can see it in "setting-->applications-->manage applications" also in "dev tools-->package browser".
i tried the method in this thread: http://forum.xda-developers.com/showthread.php?p=21844497 . I renamed "system/etc/motorola/bp_nvm_default" and reset it to default use v4.1. but no new filefolder "bp_nvm_default" generated. and the problem still exist.
i also flashed offical SBF file 3.4.2_179-4.4(VFSBLUR) , 3.4.2_177-005(NORDIC) and reflashed CM7. still cant find app with v4.0 and the same message with v4.1.
Edit:half fixed... I reflashed stock sbf (different versions) several times , then flash CM7-11 again, after a bootloop, pull out the battery, power up, the "BBS" v4.0 bundled worked normally. but v4.1 still doesn't work.
Another question, i got a FOTA (com.motorola.process.system) FC. Maybe i should repost another thread. There is no responding here. Sorry for my poor english....
Hi.
I have a problem with my device.
Recently i try-d to flash miui v5 from:
miuiandroid_jfltexx_jb-3.9.13.zip md5sum: 7c097742b0f84b1ea5ab39acd5b56dc3
After i made wipe data, syste, preload flash failed, so i made another one and it succeeded.
After reboot i saw only greenish android logo which went nowhere.
So i tried third time with philz recovery and it booted up.
And then there was no sound at all.
Then i wiped data and flashed back stock firmware:
I9505XXUAMDM
After that no sound, no wifi and no calling.
Well then i tried older firmware-s.
And now i just tried latest cm10.2 21.09.2013
Well wifi started to work again, but no sound.
Tried calling, but app just freezes and i cant heare anything.
I am just wondering that how wifi just started working again?
Maybe sound and calling can be fixed somehow similar way.
Kristjan
Pls help, i have same problem, tried several rom not ok, when make call then phone freezes.
Morgue666 said:
Hi.
I have a problem with my device.
Recently i try-d to flash miui v5 from:
miuiandroid_jfltexx_jb-3.9.13.zip md5sum: 7c097742b0f84b1ea5ab39acd5b56dc3
After i made wipe data, syste, preload flash failed, so i made another one and it succeeded.
After reboot i saw only greenish android logo which went nowhere.
So i tried third time with philz recovery and it booted up.
And then there was no sound at all.
Then i wiped data and flashed back stock firmware:
I9505XXUAMDM
After that no sound, no wifi and no calling.
Well then i tried older firmware-s.
And now i just tried latest cm10.2 21.09.2013
Well wifi started to work again, but no sound.
Tried calling, but app just freezes and i cant heare anything.
I am just wondering that how wifi just started working again?
Maybe sound and calling can be fixed somehow similar way.
Kristjan
Click to expand...
Click to collapse
I thing more, 2G/3G internet working fine, also can send and receive sms.
Morgue666 said:
I thing more, 2G/3G internet working fine, also can send and receive sms.
Click to expand...
Click to collapse
Do you solve problem?
Thanh_GSM said:
Do you solve problem?
Click to expand...
Click to collapse
nop, just noticed that problem is related only in sounds.
calling crashes just because cant somehow andoid cant use speakers
also found error useing logcat:
getDeviceForStrategy() speaker device not found"
somehow i managed to get emergency download before boot up.
intructions said to start up kies and start recovery from there.
well did that, entered model and s/n and it flashed newest firmware and now its fully working again
got same problem yesterday after updating to latest omega... no sound at all, tried doing restore, tried again full wipe, tried changing kernels, after that tried different roms - no success, sound is lost somehow.
problem was resolved only after flashing through Odin 3.09 NEE firmware I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.
Omega rom killed my sounds!
darkmanlv said:
got same problem yesterday after updating to latest omega... no sound at all, tried doing restore, tried again full wipe, tried changing kernels, after that tried different roms - no success, sound is lost somehow.
problem was resolved only after flashing through Odin 3.09 NEE firmware I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.
Click to expand...
Click to collapse
I will try one last time to install Omega v12 before I revert to stock that you mentioned....very disapointed...S4 is such a buggy crap bag
Still love omega rom and everyones effort tho...
OK sound is back after flashing thru odin 3.04 - I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar.....but I am now going to try flashing omega v12 with cwm recovery instead of twrp and see if that makes any diff or just breaks again!
OK!!!! I flashed via odin - CWM recovery 6.0.3.2 and then flashed the omega v12 zip without wiping in CWM but allowing aroma to do the work for me. And I HAVE SOUND and CALLS and no crashes thus far...Hope this helps anyone out there.
I made a series of poor choices and now I'm in a bad place.
I rooted my Note 3 with towelroot, and was trying to change the build.prop file to change the DPI (I didn't know there were apps for this). I couldn't get it to save changes, and in trying I set the file's permissions to 777. Then I got the changes made, but didn't change the permissions back.
So reboot, won't boot. ADB wouldn't find the device, so I used instructions in this thread (http://forum.xda-developers.com/showthread.php?t=2703006 to restore. And it worked! My phone booted, I was able to root and change the DPI and everything was great for a couple hours. Now the WIFI won't work at all. It hangs on "Turning on..." when I try to turn it on from settings. Thinking maybe the modem was the problem, I went to this thread (http://forum.xda-developers.com/showthread.php?t=2698464) and tried flashing NC2, NB4, and MLG firmwares. None of them made any difference. In settings < About Device Baseband is N900AUCUCMLG and build number is KOT49H.N900AUCUCMLG.
I reset to factory and it fixed it for a short time. Then right back to WIFI failure. Maybe if it's not the modem firmware, the problem was disabling Knox through SuperSU? Or rooting itself? That's really all I've done.
Anybody know what the problem could be? Should I ditch the whole thing and just put a custom ROM on it? Grateful for any help.
Update!
I got the wifi to work, temporarily. Deleting or renaming the data/misc/wifi directory and rebooting allows me to connect to a wifi network. The problem is that it only lets me connect to that network. If I try to switch ssids or leave the area it will revert to wifi not turning on until I delete or rename the data/misc/wifi directory and reboot again. Not sure what else to try here.
Any help would be appreciated.
Now with logcats
Checked out adb logcat, errors:
E/SecureStorage(21019): [ERROR]:SPID(0x00000000)Client SS library: connect: Connection refused
E/SecureStorage(21019): [ERROR]:SPID(0x00000000)SS_ConnectToDmnSndCmnData error
Anyone with a fix? Got the same problem today. It's fixed after a restore but if I change the network, wifi turns greyed out.
rstoops said:
I made a series of poor choices and now I'm in a bad place.
I rooted my Note 3 with towelroot, and was trying to change the build.prop file to change the DPI (I didn't know there were apps for this). I couldn't get it to save changes, and in trying I set the file's permissions to 777. Then I got the changes made, but didn't change the permissions back.
So reboot, won't boot. ADB wouldn't find the device, so I used instructions in this thread (http://forum.xda-developers.com/showthread.php?t=2703006 to restore. And it worked! My phone booted, I was able to root and change the DPI and everything was great for a couple hours. Now the WIFI won't work at all. It hangs on "Turning on..." when I try to turn it on from settings. Thinking maybe the modem was the problem, I went to this thread (http://forum.xda-developers.com/showthread.php?t=2698464) and tried flashing NC2, NB4, and MLG firmwares. None of them made any difference. In settings < About Device Baseband is N900AUCUCMLG and build number is KOT49H.N900AUCUCMLG.
I reset to factory and it fixed it for a short time. Then right back to WIFI failure. Maybe if it's not the modem firmware, the problem was disabling Knox through SuperSU? Or rooting itself? That's really all I've done.
Anybody know what the problem could be? Should I ditch the whole thing and just put a custom ROM on it? Grateful for any help.
Click to expand...
Click to collapse
Found the fix.
Use Root Explorer.
Delete the files below that are inside /data/misc/wifi/
wpa_supplicant (folder)
wpa_supplicant.bak.conf
wpa_supplicant.conf
Go to build.prop press menu and select Text Editor than find this line:
ro.securestorage.support=true
change it to:
ro.securestorage.support=false
Save. Reboot, wifi should be fine.
Hello guys, after I flashed a custom rom my phone went into a bootloop. I decided to flash stock , via odin. After I flashed the stock rom for my region (open european) I got many FC messages , the phone was unusable.
I started digging and flashing roms. Now I have i9505xxugng8 which is a nordic country rom.
When I try to open wifi , the button gets green for one second but then it stays deactivated.
1. Tried to remove battery
2.Tried to delete the wpa_supplicant.conf file from /data/misc/wifi or /system/etc/wifi
3.Tried the non-hos bin.
Nothing worked. I'm desperate.
baghy said:
Hello guys, after I flashed a custom rom my phone went into a bootloop. I decided to flash stock , via odin. After I flashed the stock rom for my region (open european) I got many FC messages , the phone was unusable.
I started digging and flashing roms. Now I have i9505xxugng8 which is a nordic country rom.
When I try to open wifi , the button gets green for one second but then it stays deactivated.
1. Tried to remove battery
2.Tried to delete the wpa_supplicant.conf file from /data/misc/wifi or /system/etc/wifi
3.Tried the non-hos bin.
Nothing worked. I'm desperate.
Click to expand...
Click to collapse
Try this steps
1. Rooted ! Open root explorer > System > Build.prop change this in the build.prop:
ro.securestorage.support=true TO ro.securestorage.support=false Save , Reboot
2. Either flash a diff kernel.
Have a nice day.
Hello repulsa, i Tried your method but it didn't work
It may be a hardware problem? But I've never dropped it
Tried hard reset?
Send from my Galaxy S4 using Tapatalk
Yes I tried.
Problem solved , I flshed a cm11 based rom with a custom kernel and everything works
baghy said:
Yes I tried.
Problem solved , I flshed a cm11 based rom with a custom kernel and everything works
Click to expand...
Click to collapse
I think you should fully wipe in the custom recovery before flashing the stock rom with Odin.
baghy said:
Yes I tried.
Problem solved , I flshed a cm11 based rom with a custom kernel and everything works
Click to expand...
Click to collapse
i might try this however.. im having trouble with the bluetooth and not on the wifi toggle/module. are you using the M9 build or the nightlies?
The Wi-Fi problem is knox related , I don t think switching go cm11 would solve the Bluetooth problem.
Now I'm using the latest version of miui and works well.
Sent from my iPhone using Tapatalk
baghy said:
The Wi-Fi problem is knox related , I don t think switching go cm11 would solve the Bluetooth problem.
Now I'm using the latest version of miui and works well.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I also have this problem. Went from CM11 to stock (GF was supposed to use the phone and preferred stock...).
And now, no wifi, tried most things, checked build.prop, deleted wpa_supplicant, pulled battery, cleared cache.
Nothing works.
I'd be ok with going back to CM11, but the S-View cover won't work with it.
Any more ideas?
crazyrobban said:
I also have this problem. Went from CM11 to stock (GF was supposed to use the phone and preferred stock...).
And now, no wifi, tried most things, checked build.prop, deleted wpa_supplicant, pulled battery, cleared cache.
Nothing works.
I'd be ok with going back to CM11, but the S-View cover won't work with it.
Any more ideas?
Click to expand...
Click to collapse
I don't think this is your problem, but just to put this out there in case other people stumble upon the thread....
This can be caused by using a custom kernel in a CM11 based ROM that was built after about August 3rd (give or take a few days)
CM changed the way the Wifi and data are managed by the kernel. So older customer kernels aren't compatible.
crazyrobban said:
I also have this problem. Went from CM11 to stock (GF was supposed to use the phone and preferred stock...).
And now, no wifi, tried most things, checked build.prop, deleted wpa_supplicant, pulled battery, cleared cache.
Nothing works.
I'd be ok with going back to CM11, but the S-View cover won't work with it.
Any more ideas?
Click to expand...
Click to collapse
Solved my issue...
Booted to recovery, wiped data and cache, booted straight to Download mode, flashed stock rom, booted straight to recovery, wiped data and cache again, booted, profit.
Wi-Fi not going on / bootloops (SOLVED)
baghy said:
Hello guys, after I flashed a custom rom my phone went into a bootloop. I decided to flash stock , via odin. After I flashed the stock rom for my region (open european) I got many FC messages , the phone was unusable.
I started digging and flashing roms. Now I have i9505xxugng8 which is a nordic country rom.
When I try to open wifi , the button gets green for one second but then it stays deactivated.
1. Tried to remove battery
2.Tried to delete the wpa_supplicant.conf file from /data/misc/wifi or /system/etc/wifi
3.Tried the non-hos bin.
Nothing worked. I'm desperate.
Click to expand...
Click to collapse
1) Flash Wifi fix/NON-HLOS from this post. See here how to flash a modem.
2) Solved those FC / Bootloops problem flashing that KT-SGS4 Kernel.
3) See here how my same Wi-Fi / Bootlop problems were all solved.
I have an unlocked Galaxy S5 from "Three" Ireland (3IE) that restarts many times during the day but only when I leave it idle. Either on its own or while charging.
When its not charging at home, the restarts drain the battery very quickly.
Unrooted, latest stock ROM for this carrier (Android 6.0.1 G900FXXS1CQD1_G900F3IE1CPJ3_G900FXXS1CQA3)
I searched the forum and tried the following in this order:
1. Replace the battery
2. reset factory settings (and reinstall everything)
3. Flash stock ROM using ODIN v3.12.3 (same ROM version)
Nothing helped. :crying:
I didn't reset factory settings (again) after flashing stock ROM since I don't think that will make a difference. Any ideas?
kdizzy07 said:
I have an unlocked Galaxy S5 from "Three" Ireland (3IE) that restarts many times during the day but only when I leave it idle. Either on its own or while charging.
When its not charging at home, the restarts drain the battery very quickly.
Unrooted, latest stock ROM for this carrier (Android 6.0.1 G900FXXS1CQD1_G900F3IE1CPJ3_G900FXXS1CQA3)
I searched the forum and tried the following in this order:
1. Replace the battery
2. reset factory settings (and reinstall everything)
3. Flash stock ROM using ODIN v3.12.3 (same ROM version)
Nothing helped. :crying:
I didn't reset factory settings (again) after flashing stock ROM since I don't think that will make a difference. Any ideas?
Click to expand...
Click to collapse
Did you have any custom rom installed before? Try flashing latest bootloader for the phone and checking, if all else fails try a custom rom and see if the problem persists.
Mufrad said:
Did you have any custom rom installed before? Try flashing latest bootloader for the phone and checking, if all else fails try a custom rom and see if the problem persists.
Click to expand...
Click to collapse
No custom ROM while the phone was in my possession. It could have been before I got it (I'm not the original owner) but when I did get it I was on stock and unrooted (at least according to "Root Checker").
Didn't I get the latest bootloader when I flashed the latest stock ROM? I remember seeing the files "boot.img" and "modem.bin" in ODIN.
Also if you have any suggestions for a good custom ROM I'm all ears :angel: (I like bug-free*, speed and battery life. In that order of importance)
* - I know there's no such thing as "bug-free" but you get the idea
kdizzy07 said:
No custom ROM while the phone was in my possession. It could have been before I got it (I'm not the original owner) but when I did get it I was on stock and unrooted (at least according to "Root Checker").
Didn't I get the latest bootloader when I flashed the latest stock ROM? I remember seeing the files "boot.img" and "modem.bin" in ODIN.
Also if you have any suggestions for a good custom ROM I'm all ears :angel: (I like bug-free*, speed and battery life. In that order of importance)
* - I know there's no such thing as "bug-free" but you get the idea
Click to expand...
Click to collapse
Sometimes you have to flash bootloader again separately, specially if it was changed to an later version than the one you are flashing through odin, and I would suggest a custom touchwiz rom which is close to stock but with bloat removed and some speed tweaks maybe for the most bug free experience. But also maybe give stock android roms a try, most bugs should be ironed out.
Mufrad said:
if all else fails try a custom rom and see if the problem persists.
Click to expand...
Click to collapse
OK, last night I tried a couple of things:
1. I flashed Slim6 6.0.1.build.2.1 and twrp-3.2.3-0-klte (with wiping) - didn't help.
2. I took the sim card & sd card out - didn't help.
3. I ran logcat from ADB using USB debugging to see if I could get the error before the restart - While the phone was connected and logcat was running, the phone never restarted. Even when the screen timed out and turned off. (I guess the phone doesn't count this as "idle")
oh, and thanks for all the assistance so far
The fact that it happens on custom ROM leads me to think hardware. The fact that it doesn't happen if I keep the phone "busy" leads me to think software. What should I try next?