Database Develop

Wi-Fi Problem

Hello Guys!
I have a strange problem since i'm on ICS. When i turn on Wi-Fi, the toggle goes on and off! it's going crazy. I tried multiple ICS rom's. wiped my phone multiple times. But when i'm in cm7, i do not have this problem!. Does someone know, how i can resolve this problem? i know all the ICS roms out there on the thread have working wi-fi, but i can't get it done
Please help me!
Gr. Rutger

B_sHorTy said:
Hello Guys!
I have a strange problem since i'm on ICS. When i turn on Wi-Fi, the toggle goes on and off! it's going crazy. I tried multiple ICS rom's. wiped my phone multiple times. But when i'm in cm7, i do not have this problem!. Does someone know, how i can resolve this problem? i know all the ICS roms out there on the thread have working wi-fi, but i can't get it done
Please help me!
Gr. Rutger
Click to expand...
Click to collapse
Make a clean flash. Wipe all, install rom, reboot, wipe cache , dalvik cache, flash new kernel. Maybe left some settings from older roms or kernels
Sent from Galaxy S ICS

martynas900 said:
Make a clean flash. Wipe all, install rom, reboot, wipe cache , dalvik cache, flash new kernel. Maybe left some settings from older roms or kernels
Sent from Galaxy S ICS
Click to expand...
Click to collapse
thanks for your answer!, but i tried all those steps. But with no succes
Strange part of the story is, that wi-fi allways worked on my phone, also with ICS, but with newer versions or something, it goes wrong

For what it is worth - I also had the wifi toggling problem on the last 2 ROMS that I tried:
Slim_ICS_sgs_2.6.zip
aokp_galaxysmtd_build-25-be18.zip
The problems started exactly a week ago.
I ended moving back to Slim_ICS_2.5.zip where everything works OK.
From what I understand the problem is limited to a small number of users...
I am wondering if it might not be related to recent changes in the source code (both of the above ROMS are compiled from source).
I am however very curious why some people are impacted (with the wifi toggling issue) and others are not. Maybe it is related to their LOCALs (mine is FR/fr) and/or regions... just a thought. All comments welcome!
The problem line is that I am going to sit on the fence for awhile and see if something needs to (or will) be changed at source level.
@+

Problem Custom Roms with some wifi in some phones like Velocity 4G x710s

i search whole vivid forum about this problem
some guys (like me ) have problem with wifi on custom Roms
in some kernel wifi stuck on "wifi is turning on ..." and some kernel wifi could be on but it's crazy (like couldn't off) and couldn't find any wifi signal.
phone go to s-off but problem not solved
phone like Velocity 4G x710s
any body have a suggestion or help

when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel

mohamed_moscow said:
when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel
Click to expand...
Click to collapse
i found some "bcmdhd.ko" in some kernel
which is best for me

Cant wait for release!!

Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.

ideaLduK said:
Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.
Click to expand...
Click to collapse
yes, upload that for us

Every kernel has it's own specific modules.
Thats why if you're S-ON you have to flash a CWM Zip and fastboot the img.
If you're S-OFF both are done in CWM.
This thread should be moved.

ok i find working file
tested with kozmik RC1 kernel and work well

Nottach said:
Cant wait for release!!
Click to expand...
Click to collapse
Hehe awesome.

I experienced the issue you described as a separate error from the common issue solved by a manual adb push for the wireless module.
Even though my phone is S-Off, I'd receive the error consistently when installing certain ROMs (but not all ROMs).
After multiple wipes (including formatting all SD drives, data and system partitions), I finally fixed the issue on my phone by fastboot flashing the kernel for the specific ROM I'm installing after doing a re-format/wipe and before starting the ROM installer through CWM.
It's a strange error, especially because everything seemed to be installed properly (including proper kernel info in the system) and my phone is S-Off, but this is the method I've found that works.
If anyone experiences the issue, I'd recommend doing a back-up, full wipe and re-format (including internal and external SD, basically everything you can wipe); and then fastboot flash the boot.img pulled from your ROM zip before going into CWM and installing (always be careful when fastboot flashing; if you're new to it, you definitely need to familiarize yourself and read a tutorial or two; don't blame me if you're new to flashing, don't read tutorials and end up accidentally flashing a kernel to the wrong partition or some other problem).
Hope this helps out some of the people experiencing this issue.

I can relate
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!

daspazz said:
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!
Click to expand...
Click to collapse
How did you get it working
Sent from my ADR6410LVW using xda premium

[Q] Problems accessing internet through 3G

Hi,
I am experiencing problems with my Galaxy Note when doing any type of browsing through 3G. The problem started when I first upgraded to ICS 4.0.3. At that time I wanted to limit some applications from accessing the internet through 3G, so DroidWall was installed. Eventually the device was upgraded to 4.0.4. However, after that upgrade, the phone started behaving awfully when using internet through 3G. That is the only problem and since it happened after I installed DroidWall, I don't see any other cause of the issue.
So far I have re-installed the official ICS quite a few times. UK versions as well as Germany. Also installed 4.0.3 again. No luck.
DroidWall was also re-installed, but it doesn't help at all.
It is actually really strange to describe the issue as the Internet through 3G is not completely inaccessible. Its more like most of the modules that require Internet does not connect. For example, when trying to browse, I get the following error:
goo gl/77nTx
Also when I browse the Apps on Play, it shows only the text, but not the picture for example and it also does not allows me to download:
goo gl/xSX9I
The only option that I am currently considering is re-partition, but that might cause even more problems. So I am completely open for suggestions if someone has experienced this before or have an idea what might be causing it and how to fix it.
Sorry for not being able to provide the links properly and if that way is also against the rules, please excuse me and remove the links. I just couldn't figure out a better way to describe the situation without screens.
Thanks,
Nikolay

nikolay8601 said:
Hi,
I am experiencing problems with my Galaxy Note when doing any type of browsing through 3G. The problem started when I first upgraded to ICS 4.0.3. At that time I wanted to limit some applications from accessing the internet through 3G, so DroidWall was installed. Eventually the device was upgraded to 4.0.4. However, after that upgrade, the phone started behaving awfully when using internet through 3G. That is the only problem and since it happened after I installed DroidWall, I don't see any other cause of the issue.
So far I have re-installed the official ICS quite a few times. UK versions as well as Germany. Also installed 4.0.3 again. No luck.
DroidWall was also re-installed, but it doesn't help at all.
It is actually really strange to describe the issue as the Internet through 3G is not completely inaccessible. Its more like most of the modules that require Internet does not connect. For example, when trying to browse, I get the following error:
goo gl/77nTx
Also when I browse the Apps on Play, it shows only the text, but not the picture for example and it also does not allows me to download:
goo gl/xSX9I
The only option that I am currently considering is re-partition, but that might cause even more problems. So I am completely open for suggestions if someone has experienced this before or have an idea what might be causing it and how to fix it.
Sorry for not being able to provide the links properly and if that way is also against the rules, please excuse me and remove the links. I just couldn't figure out a better way to describe the situation without screens.
Thanks,
Nikolay
Click to expand...
Click to collapse
Have you tried removing DroidWall completely & accessing 3G?

May be the droidwall has messed up ur iptables.
u mite need a factory reset. but do it on a safe kernel.

I've tried with and without DroidWall. It doesn't make any difference.Tried with different version of ICS. Again no difference.
Factory Reset as well as deleting the cache also tried. No difference. It is like you described maybe IPTables has been messed up. Just wonder why Factory Reset and re-install didn't help at all. It looks like a permanent change that has been made and I have no idea how to fix it.
Nokia, did you mean I might have to do factory reset after changing the kernel? And what did you mean by 'safe kernel'?
Thanks for the responses

nikolay8601 said:
I've tried with and without DroidWall. It doesn't make any difference.Tried with different version of ICS. Again no difference.
Factory Reset as well as deleting the cache also tried. No difference. It is like you described maybe IPTables has been messed up. Just wonder why Factory Reset and re-install didn't help at all. It looks like a permanent change that has been made and I have no idea how to fix it.
Nokia, did you mean I might have to do factory reset after changing the kernel? And what did you mean by 'safe kernel'?
Thanks for the responses
Click to expand...
Click to collapse
Safe Kernel means, any kernel with "EMMC_CAP_ERASE" command removed frm it..in Stock ICS kernel EMMC_CAP_ERASE exists & doing Factory Reset/Wiping Cache will hard brick your phone..there r many safe kernels like Hydracore, Philz, Speedmode etc etc.. here is the link for the kernel repository.. u wl get all the safe kernels here:
http://forum.xda-developers.com/showthread.php?t=1789397

where did u do the factory reset from? settings ior cwm?
first of all, check if your access point settings are correct. may be try removing and re entering them again after confirmation that it has the right details
installing ics again and again mite not work cuz its a non wipe rom and doesn't clear all settings as all ur data is preserved.
what I would suggest is to install a wipe GB rom using pc odin. Make sure u have backup. The links can be found in one of the stickies in android original dev section. thread by Dr ketan.

Okay guys. Tried everything. Changing the Kernel included as advised above. Got tired and decided to risk it and try a re-partition. Seems like this completely erased everything and the phone is now working as it did. It was a really risky move, especially for someone who hasn't done it before, but it worth it.
Thanks for all the input. Hopefully this will help anyone that experience this specific and strange issue.
Nikolay

so u used a PIT file with ICS?

[Q] Need some help changing ROM on G1

Hi guys, I have an old G1 at home that I've been using as a time killer, to play chess and some music. I want to try changing the ROM on it, because I have some problems with it, but i'm not sure where to begin. I'll give a quick rundown of the phone's problems and what I'm trying to do. This is an old machine I bought for my dad awhile ago. It's not been used for some time and I wanna to do something with it. It has a lot of problems which I don't understand. For example I cannot connect to google nor through a data plan on a simcard or through Wifi. I've seen threads having some tips on this but none helped. Same problem with some applications - facebook, teamviewer and so on. They just won't connect, although wifi works fine with the browser, so I don't know what going on. There are other problems as well and I think it's running slower than it should because it won't even manage to do stuff a generic G1 should - videos have to be heavily converted to even run - trying any video player is useless - it'll lag as hell. I have to convert to a specific audio and video format with lowered fps, then it runs ok, but still only using the generic video player. Anything else will just become a comic book.
Anyway - this is a phone I got off eBay and it already came rooted and with the Super D rom loaded (kernel 2.6.29.6-SuperD) So because all the problems I want to reflash it completely to try find out, whether it's all hardware related or the rom's unstable... Now, because it is already rooted and I'm new to this, I don't know where to start.
I have looked through a few rooting/flashing guides, but my problems is: I don't know whether I need to do it all, or can skip a few steps, because it being rooted already. For example whether I need to downgrade anything again, or not before going on. My first important question is, is there a point in flashing anything higher than android 1.6? As the phone is very limited with it's resources, I'm not sure, whether for example flashing the 2.2 froyo CM rom will do any good. Secondly: there are several different guides out there and I don't know which one is good for me. I believe I tried the one click thing once, but it didn't work then, but not sure what was the problem. I presume it is because I either didn't have to do all of it, or I didn't do something else I was supposed to.
So all in all, if someone could point me to a good guide, that would take in account the option, that it already is rooted and I just need to change the Rom, it would be greatly appreciated.

Magicnet2 said:
Hi guys, I have an old G1 at home that I've been using as a time killer, to play chess and some music. I want to try changing the ROM on it, because I have some problems with it, but i'm not sure where to begin. I'll give a quick rundown of the phone's problems and what I'm trying to do. This is an old machine I bought for my dad awhile ago. It's not been used for some time and I wanna to do something with it. It has a lot of problems which I don't understand. For example I cannot connect to google nor through a data plan on a simcard or through Wifi. I've seen threads having some tips on this but none helped. Same problem with some applications - facebook, teamviewer and so on. They just won't connect, although wifi works fine with the browser, so I don't know what going on. There are other problems as well and I think it's running slower than it should because it won't even manage to do stuff a generic G1 should - videos have to be heavily converted to even run - trying any video player is useless - it'll lag as hell. I have to convert to a specific audio and video format with lowered fps, then it runs ok, but still only using the generic video player. Anything else will just become a comic book.
Anyway - this is a phone I got off eBay and it already came rooted and with the Super D rom loaded (kernel 2.6.29.6-SuperD) So because all the problems I want to reflash it completely to try find out, whether it's all hardware related or the rom's unstable... Now, because it is already rooted and I'm new to this, I don't know where to start.
I have looked through a few rooting/flashing guides, but my problems is: I don't know whether I need to do it all, or can skip a few steps, because it being rooted already. For example whether I need to downgrade anything again, or not before going on. My first important question is, is there a point in flashing anything higher than android 1.6? As the phone is very limited with it's resources, I'm not sure, whether for example flashing the 2.2 froyo CM rom will do any good. Secondly: there are several different guides out there and I don't know which one is good for me. I believe I tried the one click thing once, but it didn't work then, but not sure what was the problem. I presume it is because I either didn't have to do all of it, or I didn't do something else I was supposed to.
So all in all, if someone could point me to a good guide, that would take in account the option, that it already is rooted and I just need to change the Rom, it would be greatly appreciated.
Click to expand...
Click to collapse
First thing I would do is just factory reset it through recovery (power on while holding home) and see if all works after this. Super d is for sure one of my favorite donut ROMs and it shouldn't be having the issues you have.
If that does little or nothing than write down all info from bootloader (power on while holding camera) here and the version of recovery you have (written in recovery screen)
Sent from my Nexus 7 using Tapatalk 2

Hi. Thanks for the quick reply. I've already reset it multiple times, but it didn't change anything. What most angers me, is the Wifi issue (because I know my dad has been using his dataplan and it worked fine and when I tried it later, it just didn't work anymore) and the video thing.
As for the info:
Hboot-1.33.2005 (Drea11000)
Clpd-4
Radio-2.22.23.02
Recovery is ClockworkMod Recovery 2.5.0.7

Magicnet2 said:
Hi. Thanks for the quick reply. I've already reset it multiple times, but it didn't change anything. What most angers me, is the Wifi issue (because I know my dad has been using his dataplan and it worked fine and when I tried it later, it just didn't work anymore) and the video thing.
As for the info:
Hboot-1.33.2005 (Drea11000)
Clpd-4
Radio-2.22.23.02
Recovery is ClockworkMod Recovery 2.5.0.7
Click to expand...
Click to collapse
Yes it is strange, try finding a ROM called donut by Laszlo, search is down right now but it should be within the first five pages or so in developers thread. Put on sdcard along with this
http://www.androidfilehost.com/?fid=23212708291678371
First flash super wipe in recovery and then flash new ROM
If it all does not work still we will go from there
Sent from my Nexus 7 using Tapatalk 2

Right, so I've got some new info on this. I wanted to go reflash, but just for the sake of it, I re-wiped though recovery and nothing changed. then on the second time, the market suddeny started working through wifi, which it has not for the past few months, even after 3 or 4 wipes. So it started working, but the signal kept failing. It found the first application, downloaded, installed, then "network problem" so I reflashed using the files you mentioned. It worked beautifully on the first fly, for which I am grateful. This was my main concern - I had no idea, whether I needed to change the radio or bootloader or anything prior to trying to flash the rom. So the rom works nice, the market and facebook and teamviewer do connect now using wifi, but I keep loosing the signal. Better said - he stays connected to wifi, just that the applications keep throwing network errors and loose connection. So I presume, it will be either hardware related, or I was wondering, if a change of radio might help... Secondly, I keep getting one more problem I had with the old Rom and that is - when using ES File explorer, when I close by pushing the back button, it closes and then an error says it stopped working and needs force closing. Wondering how this kind of error can transfer between different Roms. Again - posibly hardware related? I don't know.
Anyway, the rom works nice, so I'll try it out and see if it's better than the previous one. One question though - when flashing to a different Rom, do all of them have specific requirements for radio and bootloader and recovery and so on, or is the setup I have ok for flashing anything, that is suited for the G1?
EDIT: One more thing I just remembered. The Superwipe, as I read the description, was supposed to wipe everything + the SD card as well. First of all I noticed that it took just about a second or two, which I thought was a bit too quick, but the SD card was not wiped at all, so I'm thinking, that theoretically there could be a file on there, that causes the problems, that have transfered from Rom to Rom, as it was not wiped at all. I'll reformat the SD card, superwipe it, reflash the Rom and see what will happen. Will post the results first thing tomorrow.

It only wipes ext partition not fat32
Only newer ROMs will require a different bootloader/radio, which also will give you more ram so it is preferred. See ezterrys post on the 2708+ update or read the through the thread below this on where I discussed the benefits of upgrading with another dream user
Sent from my Nexus 4 using XDA Premium 4 mobile app

Right, so from what I see from the other thread of yours, CM5 should be a good Rom to try. I will definitely wanna go there, cause while the current Rom seems a bit better than the Super D, it seems it uses up more memory - can't install as many apps as before and I'm keeping it pretty low on apps. And I definitely want to see, whether it will improve any of the lingering problems I've been having, or whether it'll be worse. So judging by what you told the other guy, I already have the right bootloader as I have the 2005 with fastboot enabled, but I'll have to update the radio. Here's what I'm not sure and that is, which to choose. Should I stay with the current SPL and get the same radio the other guy had (RADIO-2.22.19.26i) or should I go straight for the 13d SPL with radio-2.22.27.08? I would say, for now would be safer to stay with current SPL, update the radio and then flash Rom + Gapps and see what it does. Plus if I remember right, you said that to get the ramhack I need the 13d spl, which doesn't support fastboot...

You got it all, well you don't need to change radios, the one he has is a Europe version, yours is more us. Both work fine for cupcake, donut and eclair ROMs. You can try out the other if you were getting poor reception but not needed
Cm5 will work fine for you as of now, just full make a backup, wipe, superwipe, fastboot -w whatever, then flash ROM, then gapps then reboot
The ram hack is awesome but so is learning fastboot. I do recommend you at some point upgrade to the .13d SPL but I think its a good idea to flash a few things first and be comfortable before doing so. If you have issues having fastboot is helpful in fixing things
Sent from my Nexus 4 using XDA Premium 4 mobile app

Ok. So what I did is partition the SD card using the nice "Mini tool partition wizard" and went for a 250 MB ext4, made a backup, left the radio be so far, wiped, flashed the CM5 and Gapps and I have to say I'm impressed at how swift the Rom works. It appears to be generally faster than both the SuperD and Laszlo Donut Roms. I have been testing it only a short while yet, but the wifi, although it shows constantly weak signal (one or two lines), it hadn't lost connection yet, which gives me hope and the apps2ext seems to work perfectly right away. At least I'm able to move them around and it installs straight there, without any failure so far and the apps work so thumbs up.
This deserves a big thanks to you for the supplied info. Before I wrote this thread, I was about to try one of the long guides - which would take me through downgrading and everything - you saved me a lot of stress man I'll play around with this and will try going for the ram hack a bit later. I'll let you know any bugs I notice...
P.S.: You were right to suggest getting familiar with fastboot and adb - it's a great thing and it's good to know I've got it set up and running fine.

Nexus 6 Shamu With Bell Canada Crashing When Trying To View Voicemails or R/S Calls

My title was abit too long, cause it was copied from a reddit post I made on Cyanogenmod's reddit. R/s means "Receive or Send"
I tried going to Cyanogenmod's Reddit, asking for help with this issue, but there was no luck at all, one user did respond to me and tried to help me out, but hasn't responded for the past 3 days. Looking around for more help, I was directed here to ask. If at all, I'm doing something wrong, can you please tell me.
FYI: My Nexus 6 is using Cyanogenmod 13.0 NIGHTLY, running 6.0.1
Besides that, the reddit post is basically this:
"Please direct me in the correct area, at the moment I don't see much to go to for some help, but I felt like making post.
After a while, I've been using Bell Canada on my phone without any issues, but I never tried voicemails or calls. Recently, trying to get into my telegram account cause they won't send a SMS (For what ever reason), the app offered to call my phone, waiting for the timer to tick down before they call my phone, it just shut it's self off.
I was aware of my phone crashing due to voice mails, cause before I activated my sim card, I had a voicemail that wouldn't go away, trying to view it, the phone would crash. I was hoping this would've been fixed after a couple updates, but it doesn't seem like it was fixed at all. I can't even tell if this issue is my problem (the phone/sim card) or cyanogenmod.
If anyone knows any fixes for this, I'd be really happy, because currently my phone is useless to most things I'd use it for, other than SMS."
On the reddit post, the user that was replying to it did mention something about c-apps not being compatible with Cyanogenmod 13.0 and told me to try to uninstall it, but when I tried to uninstall it through adb, apparently such a directory doesn't exist. I do hope I can get some help here, because I'm currently on a plan with unlimited text and calls, paying alot of money for it, but one feature is completely useless.
--Something I want to add, I tried the same sim card in my HTC One M7 running Android 5.1 with Cyanogenmod 12, calls worked perfectly fine with it.

Please do correct me if I'm doing something wrong, but reading the forum rules, I don't see anything about "bumping", so... Here's my bump.
I haven't had a reply for 5 days now, the possible answer to why my topic wasn't replied to, is most likely because noone knows how to fix this or why this might be happening.
But, I do wish I could get a post or something to show that people do see this, or maybe a post telling me that my issue has a unknown fix.
Edit; I see this rule #5, but, I don't know if that applies to bumping, I don't know how else I could explain my issue. I've explained it the best I've could.

I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.

Darth said:
I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.
Click to expand...
Click to collapse
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.

MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.

MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
Look in the Nexus 6 Android Development and Nexus 6 Original Android Development subforums, there are tons of options available.
Read over this- [HOW-TO] The Nexus 6 All-In-One Beginner's Guide. A brief guide to clean flashing ROMs. Using TWRP, wipe everything except internal storage (system, data, cache, dalvik). Flash the ROM and then gapps package (some ROMs based on stock don't require gapps so look in the thread). There you go, you have a clean flash of a new ROM.
If you have issues with CM13, try ROMs based off of AOSP like Chroma, Pure Nexus, Dirty Unicorns, AOSiP, etc...

Darth said:
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.
Click to expand...
Click to collapse
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.

MoonieHorse said:
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.
Click to expand...
Click to collapse
You will not "brick" flashing a rom. You can have issues, sure, but that's what the nandroid backup is for.
Honestly, if you're that worried, I'd restore the stock image and not tinker with it.
But if you leave it as is, I doubt you'll fix your issue.