Related
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.
Hello.
At first, I am new in the forum, so hi to everybody and thanks for the job in this site.
I have a very big problem with Note 4 ( I can't use it right now). Since I rooted the phone and changed the rom (to Cyanogenmod 12) all apps stop constantly and in random way. I have tried everything (I think so), return to the stock rom (android 5.0.1), make wipes (cache, data...) and reinstall the rom from Samsung switch.
I don't know what to do.
More info: All apps stop but the gapps stop with more frequency. I sent the device to the technical service but they take it back because I have modified the software (knox 0x1).
Sorry for my english. I am from Spain.
Thanks.
Third party apps or system apps?
Did you install any battery saving or ram booster apps?
GrippingSphere said:
Third party apps or system apps?
Did you install any battery saving or ram booster apps?
Click to expand...
Click to collapse
All of them
No, I don't believe in those apps. The only thing that I did for imrpoving the performance was to intall CM12 (It works fine at first)
I thought that CM12 doesn't work well with the Fast Charging... Could it be?
Thanks.
It seems like you might've flashed a gApps package for an earlier version of Android than what Cm12 is (5.1.1).
Try a full device wipe, reflashing CM12 & a gapps for 5.1.1
Jishy420 said:
It seems like you might've flashed a gApps package for an earlier version of Android than what Cm12 is (5.1.1).
Try a full device wipe, reflashing CM12 & a gapps for 5.1.1
Click to expand...
Click to collapse
I tried that and It didn't solve the problem. I also reflashed the stock rom (with Odin). Without effect, the problem was not resolved...
Thanks for your help.
Hi guys, I had to give up using CM Roms since the phone reboots every time I try making a call or receive one, I understand there is some king of bug with the dialer framework included in the GAPPS package and that installing the Google Dialer from the play store should solve it but in my case i hasn't. This is what I've tried to no avail:
- Intalled Google DIaler from PlayStore/APK and set it default with all the permissions enabled.
- Installed Google Dialer apk as system app and set it default with all the permissions enabled.
- Installed the full GAPPS package.
- Removed the stock dialer and did all things above.
Hope someone can help me out here,
Thanks.
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Sam Nakamura said:
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Hi Sam, that's what I mean when I've set it as default.
pitrus- said:
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Click to expand...
Click to collapse
Hey pitrus, this issue actually started while only having CM dialer installed since I mainly flash pico gapps.
Will try it again since its been like a month since I gave up on it. Let you know later.
J3RI3L said:
Hi Sam, that's what I mean when I've set it as default.
Click to expand...
Click to collapse
Well, okay.. Thanks for clarification :good:
Maybe you'd like to give Banks a shot, I think it's worth to try...
https://download.dirtyunicorns.com/gapps/Banks/
I never had this specific problem, only when it wasn't set to be default but a also only use one dailer.. The one that is default on cm based roms..
Sent from my OnePlus2 using XDA Labs
Guys I've had no luck, tried with a clean install of CM14 and still facing the same problem. Just today did a CM14.1 install and it is still present for me.
I guess that I could flash just CM and not gapps but I rely on Google services for a lot of stuff. Will keep trying though.
I'm having the exact same problem, random reboots during calls only, sometimes I don't even have time to answer. I'm running CM13 and only have one phone app, also set as default. When running stock and Cyanogen all was fine, this only started after flashing CM13.
Developemt for Cyanogen stopped that's why I switched, maybe coming from another rom is causing this? I did a full wipe when flashing and have updated to several nightlies and the problem remains. Maybe I'll try another rom and test it for a while.
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
It's a problem related to Gapps
rtorresz said:
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
Click to expand...
Click to collapse
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
pitrus- said:
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
Click to expand...
Click to collapse
I've installed them all with the same result, last time I was using Pico Gapps with Seraph's CM14 and it happened eandomly, sometimes I could make and receive calls normally but a most of the time it would reboot as soon as the phone started ringing.
Currently I've tried a lot of solutions so I'm not really sure of what's wrong.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
rtorresz said:
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
Click to expand...
Click to collapse
Its happening to me as well just as you describe it. It is very weird. In thinking of flashing the stock OOS 2.2.0 just to check whether it makes any diference.
Yesterday I restored my phone back to stock, but the problen remains.
This definitely has something to do with mobile data. If I disconnect mobile data I can make calls without any problem, when I'm connected to a wifi network too (I'm guessing because the phone has no need to use mobile data).
Some suggest that this might be related to VoLTE and operators not supporting it, but I can't find anyway to see if this is even exists or if its activated in OOS.
Later today I'll try Hydrogen and see what happens.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Kinda solved now
rtorresz said:
Yesterday I restored my phone back to stock, but the problen remains.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Click to expand...
Click to collapse
It seems I have solved my problem with the reboots and I think might help with your droped calls as well.
Firstly I flashed this OOS 3 firmware https://www.androidfilehost.com/?fid=24591020540821656, it comes with a hybrid TWRP, after that flashed the official CM14.1 and pico Open Gapps.
I think the firmware file did the trick or maybe it was the recovery since I haven't had a reboot in the past 2 days when receiving calls or making them.
Hope it helps
It's been a few days since I tried the last solution and so far my problem seems to be solved.
What worked for me was flashing the latest modem from H2OS 2.5 which also is supposed to enable VoLTE, but I can't confirm this since my carrier does not support VoLTE yet. To do this I first flashed CM 14.1 and then the modem, it worked fine since the first boot. Since my battery life wasn't the best in Nougat I went back to CM13 and the phone is still working fine.
I am on stock rom and rooted using the Super SU method. The only things I've flashed are the wifi fix, and edited build.prop to unlock tethering. My camera app will not open, and I get this error every single time. Doesn't work in instagram, snapchat, nothing. Anyone know what may be causing this?
Anyone? I would really like to get my camera working again
had the same problem today. restarted the phone and it worked again
ckret said:
had the same problem today. restarted the phone and it worked again
Click to expand...
Click to collapse
I've restarted several times even gone so far as to install a new OS. I'm thinking about undoing the changes just to fix this.
Try booting in Safe mode
ckret said:
Try booting in Safe mode
Click to expand...
Click to collapse
Camera still doesn't work
your cam may be disconnected from the motherboard. try claiming warranty
Wiped and installed the AOKP ROM and that fixed it.. Could've been the ROM or could've been the wipe, although I wiped several times before and it didn't fix it.
did you get the error again?
I had the same problem and I installed AOKP rom which fixed it at the beginning but after less 1 day the error back again.
now I'm on stock rom .35 (rooted with Magisk) and no camera error so far after 4 days
As far as i know, it is due to custom kernel, you may have installed that.. try flashing stock rom without any custom kernel..
Mayanknagpal.nm said:
As far as i know, it is due to custom kernel, you may have installed that.. try flashing stock rom without any custom kernel..
Click to expand...
Click to collapse
yes, I had custom kernel first time I got the error.
but then I got it also with custom rom.
now I'm on stock rom and stock kernel....but does it mean that I can never flash custom rom/kernel because of that error?
marcol87 said:
yes, I had custom kernel first time I got the error.
but then I got it also with custom rom.
now I'm on stock rom and stock kernel....but does it mean that I can never flash custom rom/kernel because of that error?
Click to expand...
Click to collapse
Custom roms do not have that error... and on stock rom you can use elementalX 2.0 , it is made for the .67.. so the camera issue is resolved.. i think this will help
I had this error on Stoneware .67 (stock based ROM) and resolved it by dirty flashing Stoneware and Magisk v.13 again.
and I had this error also on AOKP rom
I have been having this problem on the Stock ROM, non-rooted, for quite some time now. I have no idea what's causing this error. When I open it sometimes, it just throws an error. If I close it and open it again, it works as it should. It's very annoying.
I had the same thing, flashing roms didnt fix it so i flashed stock via RSD lite and everything was back to normal.
Same issue here, completely stock unrooted. This is not the first Android device I've had that's struggled to connect to the camera consistently... how hard can it be?
Can people getting this error try to disable the image stabilisation in video mode please? One of the errors I see when downloading a bug report refers to the stabilisation code and I've not had the "please restart camera" message since switching it off. Could be coincidence though as it's not like I get it every time the camera loads...
Hello ,
I tried rooting my Moto G5 using Moto G5 toolkit (flashing superSU). t
Then I flashed TWRP and Flashed the WLAN_CUSTOM
Now i get that generic warning screen of unlocked boot loader however My phone is not rooted. and I cant open camera at all , getting error as " Camera Busy - Camera unable to start. If this happens again, please power off your phone and restart."
Can someone help me fix this camera issue? or just help me to revert back as it was previously no root nothing, I guess this TOOLKIT has some bugs in it.
Any help will be appreciated as I am newbie with this android development.
the.MindHacker said:
Hello ,
I tried rooting my Moto G5 using Moto G5 toolkit (flashing superSU). t
Then I flashed TWRP and Flashed the WLAN_CUSTOM
Now i get that generic warning screen of unlocked boot loader however My phone is not rooted. and I cant open camera at all , getting error as " Camera Busy - Camera unable to start. If this happens again, please power off your phone and restart."
Can someone help me fix this camera issue? or just help me to revert back as it was previously no root nothing, I guess this TOOLKIT has some bugs in it.
Any help will be appreciated as I am newbie with this android development.
Click to expand...
Click to collapse
I had the same issue as you after using the toolkit, did you fix it?
Hi, I'm here to ask for your help because I don't know what to do.
Since the update to xXx 9.6 no limits my Oneplus 5 runs in slow motion, the applications take a lot of time to open it is unusable. Even the startup animation is slow.
I've already reformatted everything, flash with unbrick tool but it's the same.
I have the impression that only when I format in F2FS it works normally but I can't find a compatible Rom. Thank for your help.
Have you tried another aosp rom or just the stock rom some tweaks of the xxx might be causing some issues
Thesuprememonkey said:
Have you tried another aosp rom or just the stock rom some tweaks of the xxx might be causing some issues
Click to expand...
Click to collapse
I have try xXx, Stock Rom and Lineage OS
mrsachou said:
I have try xXx, Stock Rom and Lineage OS
Click to expand...
Click to collapse
That's weird do you have any heavy syncing apps ?? When did you start noticing the problem ? immediately after 9.6xxx update or after installing a certain app ? Have you tried changing the kernels ? Try decrypting and then Omni since it's a stable 8.1 rom
Thesuprememonkey said:
That's weird do you have any heavy syncing apps ?? When did you start noticing the problem ? immediately after 9.6xxx update or after installing a certain app ? Have you tried changing the kernels ? Try decrypting and then Omni since it's a stable 8.1 rom
Click to expand...
Click to collapse
I start notice when i install the new Snapchat.
I'm gonna try thanks
You formatted the data (which wipes everything on your device ) or just wiped the partitions? If you completely formatted and are experiencing the exact same issue on LOS and xXx there are several possibilities -- 1) You have a hardware issue; 2) You are using corrupt or mismatched firmware; 3) A third party app is causing the issue. The last one is very easy to check--just boot your OP5 into Safe Mode and see if the issue persists. If you encountered the issue on stock OOS and did a clean install after formatting your data then it shouldn't be a firmware issue.
It's very important that you completely format all the data on your phone--not wipe the partitions or format them individually because you need a fresh start in case it's just an issue with corrupted data. My guess based on everything you wrote is that you have a hardware problem and need to have your phone serviced.