I flash something new daily, I always flash back to my clean rooted backup before flashing something new. Lately it seems like it's running really glitchy. Is there a certain point where you just need to sbf back to stock or what ?
kickenwing13 said:
I flash something new daily, I always flash back to my clean rooted backup before flashing something new. Lately it seems like it's running really glitchy. Is there a certain point where you just need to sbf back to stock or what ?
Click to expand...
Click to collapse
thats usually a good indication to wipe data, format system, then flash rom of choice.
droidstyle said:
thats usually a good indication to wipe data, format system, then flash rom of choice.
Click to expand...
Click to collapse
I do that before each rom change, but I installed CM10 and it's much better.. Thanks
I've Flashed LIquid and for some reason I keep running like 1.5k and it'll get laggy and freeze up. I've cleared the rom, cache, system format, everything before I flashed both times but it still persists. I have a task manager that says there arn't any processes other than play store and swiftkey but its running into the red.. Any help?
jesseag7 said:
I've Flashed LIquid and for some reason I keep running like 1.5k and it'll get laggy and freeze up. I've cleared the rom, cache, system format, everything before I flashed both times but it still persists. I have a task manager that says there arn't any processes other than play store and swiftkey but its running into the red.. Any help?
Click to expand...
Click to collapse
Back in the day of my droid x I would flash stock, reroot, and unlock just to get a clean base .. it seems fine now for me.. but im getting a lot of data drops on cm10
This is Crazy I've flashed a Different rom and did the wipe factory reset and everything before hand and its still running High. After being Idle for about 3 hours it is burning hot and is running with like .05mb free out of 1.6 mb. I think I'm going back to Stock root
jesseag7 said:
This is Crazy I've flashed a Different rom and did the wipe factory reset and everything before hand and its still running High. After being Idle for about 3 hours it is burning hot and is running with like .05mb free out of 1.6 mb. I think I'm going back to Stock root
Click to expand...
Click to collapse
I had good luck using ODIN to flash a fresh base. I then rerooted and unlocked. I then created a backup, installed beans rom and it's sweet, smooth, good battery life... It may be worth trying.
kickenwing13 said:
I had good luck using ODIN to flash a fresh base. I then rerooted and unlocked. I then created a backup, installed beans rom and it's sweet, smooth, good battery life... It may be worth trying.
Click to expand...
Click to collapse
Maybe i'll try that then becuase this is getting unbearable. I'm running 3 system processes and its at 91% capacity..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay so apperently its the Media Storage Process that is killing my memory. for most people it just kills thier battery but mine has been having an adverse affect on my processing power and RAM. But glad its figured out incase anyone else has the same problem as me. They should really post that somewhere on the OP of the Jellybean ROMs because its kind of a big deal...
Related
ok im sending my phone back to Samsung, (wifis now working it just says error) and the internet has no answer for it.. i bought this phone used, i wanna send it back with factory settings, but i nocticed when i flashed the basic rom to it, the kernal was the same as well it didnt change the radio.. can someone show me wich to use so it looks like i havent modded it at all?? (after that i will relock the bootloader)
thanks
j
wifi error ? probably kernel's fault , i have been same situation with WIFI error after i flashed new kernel
hmmmm
you didn't say which model , so , if it is i9023 , KF1 radio.
maybe format /system and /boot before you flash ROM could help
i have tried 5 different kernals, no help, i have teh i9020t thanks
have you tried whole new rom with everything and anything be wiped and formated ?
qtwrk said:
have you tried whole new rom with everything and anything be wiped and formated ?
Click to expand...
Click to collapse
sure have, i have tried at least 3 roms, 3 kernals, and 3 radios.
Flash your initial nandroid back.
polobunny said:
Flash your initial nandroid back.
Click to expand...
Click to collapse
yeah, its not working,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is there a way if i can mount the SD that if i have my cmw backup folder, i can just copy and paste?
how the heck do i fix my cache partition??
Update Clockworkmod Recovery, then try again.
same with me(i9023),open WIFI lead to crash or sometimes reboot itself.I've tried 12 roms and 4 basebands.Still couldn't be fixed.
Wish you can solve this problem,and share with me,thank you!
polobunny said:
Update Clockworkmod Recovery, then try again.
Click to expand...
Click to collapse
ive tried that, other versions as well, im having issues,, with the cache partition, ive been able to restore my backup, but the phone is running super slow, still giving me the same error above.
jerkwagon said:
ive tried that, other versions as well, im having issues,, with the cache partition, ive been able to restore my backup, but the phone is running super slow, still giving me the same error above.
Click to expand...
Click to collapse
You should be fine with 5.0.2.0 to restore your backup. That cache error happened back with 3.0.0.5 and 3.0.24 as far as I'm aware.
it did help! but the phone is crapped out, reboots, overheats and is mega slow.
More and more people keep having this problem. Your phone suddenly has tons of force closes, and becomes unfunctional. Well we seem to have a problem with our recovery, possibly causing a corrupt partition. There is a solution .......use odin to flash the stock recovery tar found in development. Boot into stock recovery.. wipe data, and cache 3 times each ,and boot the rom back up. Then use rom manager to flash the tmobile gs2 cwm recovery. This does work. And has been proven numerous times.
Here is the stock recovery http://forum.xda-developers.com/showthread.php?t=1360943.
If for some reason you still have this issue after following my advice. Use odin to flash the stock firmware tar found here http://forum.xda-developers.com/showthread.php?t=1342348. After your done. Let it boot. If u get the force closes. Then proceed to power off, boot into stock recovery, and then wipe your data/cache, and reboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Excellent post... Thx
another good one Silver Thanks....im curious as well to see how many are really having this issue<<<
Is there a difference between the TMobile GS2 CWM recovery and the CWM recovery flashed using this method (http://forum.xda-developers.com/showthread.php?t=1340526)?
I had the described problem, but wiping and reloading the intended ROM in CWM recovery fixed it.
That is good but alot of times that does not work. It can actually get to the point where it will not read the internal sd card
How are you guys flashing....and what are you flashing that is giving you these issues.
I have yet to experience these issues on T-Mobile or skyrocket roms.
What are the exact steps you follow when flashing a from to begin with?
Sent from my SAMSUNG-SGH-I727 using XDA App
I have experienced this on stock, and custom roms. And im not the only one. Alot of people have had this issue
Lets put it this way enough people have had this problem, and more will to the point where i made this thread, and asked a mod (jayharper08) to sticky it.
yes ALOT have......they may not have known it was a known issue and solved it. but it is there.
I am not saying you guys are not having issues...there has to be a reason I am not which is why I ask.....What steps exactly do you guys use to flash a rom and what roms. The process to fix it is great but if we could prevent it in the first place wouldn't that be better????.
silver03wrx said:
I have experienced this on stock, and custom roms. And im not the only one. Alot of people have had this issue
Lets put it this way enough people have had this problem, and more will to the point where i made this thread, and asked a mod (jayharper08) to sticky it.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using XDA App
Silver,
Question...based on several of your other posts in threads, if we have 2.3.6 and use http://forum.xda-developers.com/showthread.php?t=1340526 to root/install recovery, are things ok?
Or should we still follow this thread to update CWM via ROM Manager?
Thanks.
^^^
That was my question too. What's the difference between the two recovery's?
I was having the issue too. I had the issue on stock(pure from store) as well as stock rooted, skyrocketeer, and cm7.
One thing I have tied it to, which I am not sure is the true reason but I was too impatient to test it thoroughly, is excessive SMS messages.
I have over 32k messages currently stored on my HTC Inspire. These have been moved from my G1, to Nexus One, to Inspire with no issue at all. When importing to my Skyrocket, the messages will import fine for a while. Afterwards, I would get random FCs, screen freezes up(can't do anything, not even turn off the screen), and network disconnects. I can force a reboot by holding the power button and it will work for about 5 minutes and then repeat the issues as before.
At first I thought it was the specific device having radio issues so I exchanged it for a new unit at Best Buy. I was still having the same issues with the new unit so I just figured I could cut my losses (on screen protectors and phone case) by just returning the until outright. I figure I will wait for the ICS update for this phone, hoping it will be more stable. Maybe at that point I can compare with other phones available as well.
I have had this problem repeating several times even after flashing the Rom and repeating steps as mentioned. I think it does it with a certain number of apps that downloaded from the market.
silver03wrx said:
More and more people keep having this problem. Your phone suddenly has tons of force closes, and becomes unfunctional. Well we seem to have a problem with our recovery, possibly causing a corrupt partition. There is a solution .......use odin to flash the stock recovery tar found in development. Boot into stock recovery.. wipe data, and cache 3 times each ,and boot the rom back up. Then use rom manager to flash the tmobile gs2 cwm recovery. This does work. And has been proven numerous times...
Click to expand...
Click to collapse
Is this a problem that develops as you start flashing more and more ROMs? Is there a known cause?
I'm new at this stuff - just rooted and tried my first ROM this week. I'm tempted to try others but if chances are good that I'll run into problems/issues even if I'm going about things the right way - I might hold off on making a change given that the phone is stable right now.
Thoughts?
NO rom does not cauz this issues. What causes issue is when you restore data from ur backups. Plus there is problem with cwm it does not fully wipe data because cwm was not particularly made for our phone. That being said you do not have to worry about a thing. I am flashaholic and i used to flash every other day since i m with Sky ice cream rom by Sean i don't flash a lot. Don't worry just try out all the roms you won't have problem by roms at all. There was only one rom that had problem Alien the first or second build.
Locoman_ said:
Is this a problem that develops as you start flashing more and more ROMs? Is there a known cause?
I'm new at this stuff - just rooted and tried my first ROM this week. I'm tempted to try others but if chances are good that I'll run into problems/issues even if I'm going about things the right way - I might hold off on making a change given that the phone is stable right now.
Thoughts?
Click to expand...
Click to collapse
Thank for the reply.
BTW, I'm using Sean's Sky IC too. Sooo nice.
Do you need to go into download mode to flash the recovery in ODIN? Or do you do it when the phone is just turned on regularly?
You have to go to dload mode in order to flash recovery. and use odin.
nutsngum said:
Do you need to go into download mode to flash the recovery in ODIN? Or do you do it when the phone is just turned on regularly?
Click to expand...
Click to collapse
I tried this process and I wanted to flash a new ROM. But in recovery mode it wouldn't read my SD card, and when I transferred the .zip to my internal memory and I tried to install it said I had no space.
Any ideas?
Since I see this is the most annoying thing people keep complaining about. Yet I dont know why anyone shutdown there phone and cares.. Just saying
Common ICS leak bug: shutdown/Reboot "stick"
Fixes: try whatever you want
1. Pull battery after first boot
2. Superwipe before installing my superlite
3. After install take a nandriod backup and reload that backup
4. Using adb
adb shell rm /system/app/shutdown.apk
OR
Using Root Explorer:
Set RW and remove /system/app/shutdown.apk
Reboot(even if you have to pull battery)
I see some willy-nilly thank you's but nobody responding to say if it worked for them or not.
Didn't work for me
sgh-i727r
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------
---------
---------
---------
I tried. I really did.
you make me laugh
<installing android source> bbl.
So does this work or not?
Didn't work for me. After the leak was installed, my phone would shut down just fine. It was only after I rooted it that it would not shut down.
Just make a tibu backup of the app then un install it. I'm running mhx's ics rom and I don't have the issue anymore. I couldn't reboot on my previous 3 flashes so MHX must be doing something right.
Swyped from my Galaxy S2 Skyrocket using XDA premium
Well whatever the fix does or doesn't do with other ROM's, it appears to be working great [already built in] on MHX's ICS ROM found here:
http://forum.xda-developers.com/showthread.php?t=1573621
Did not work for me
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2 Beta-5
bts0uth said:
Just make a tibu backup of the app then un install it. I'm running mhx's ics rom and I don't have the issue anymore. I couldn't reboot on my previous 3 flashes so MHX must be doing something right.
Swyped from my Galaxy S2 Skyrocket using XDA premium
Click to expand...
Click to collapse
CZ Eddie said:
Well whatever the fix does or doesn't do with other ROM's, it appears to be working great [already built in] on MHX's ICS ROM found here:
http://forum.xda-developers.com/showthread.php?t=1573621
Click to expand...
Click to collapse
I'm confused.. you're saying this didn't work but mhx is doing something right with his rom. mhx is the op..
I am on 4.2 ICS-Superlite and i still have the issue on SGH-I727R :/
The issue went away for me with 4.2 Super lite. I even went all the way back to GB on 2.3.5 to get rid of that blasted thing on my i727. What process are you using?
Sent from my SAMSUNG-SGH-I727 using xda premium
btm fdr said:
I'm confused.. you're saying this didn't work but mhx is doing something right with his rom. mhx is the op..
Click to expand...
Click to collapse
It isn't working for some other peoples custom ICS ROM's, but MHX's custom ICS ROM isn't having any shutdown problems.
CZ Eddie said:
It isn't working for some other peoples custom ICS ROM's, but MHX's custom ICS ROM isn't having any shutdown problems.
Click to expand...
Click to collapse
I guess i'll have to retry a flash then :/ it's still doesn't work for me even if I am on ICS-Superlite 4.2
I'll post back the results!
chokesmaster said:
I guess i'll have to retry a flash then :/ it's still doesn't work for me even if I am on ICS-Superlite 4.2
I'll post back the results!
Click to expand...
Click to collapse
I reset factory data/ wiped cache & davlik three times each..
Then wiped all the mounted devices except EMMC.
Then ran Dark's Super cleaner thingy wipe.
Then ran a kernel cleaner.
Then flashed 4.2.
Then flashed ROMracer's exploited kernel twice.
Then reset to factory data, cleared cache & davlik again.
Then booted up and left it alone for five minutes before touching anything.
Hope that works for you!
It's how I flash all my ROM's these days.
Though I just started wiping factory data afterwards.
CZ Eddie said:
I reset factory data/ wiped cache & davlik three times each..
Then wiped all the mounted devices except EMMC.
Then ran Dark's Super cleaner thingy wipe.
Then ran a kernel cleaner.
Then flashed 4.2.
Then flashed ROMracer's exploited kernel twice.
Then reset to factory data, cleared cache & davlik again.
Then booted up and left it alone for five minutes before touching anything.
Hope that works for you!
It's how I flash all my ROM's these days.
Though I just started wiping factory data afterwards.
Click to expand...
Click to collapse
Which kernel cleaner are you using? I remember using one for my Captivate that said something about being compatible with all Samsung devices. I've only used darkside's superwipe so far though.
Sent from my SAMSUNG-SGH-I727 using XDA
CZ Eddie said:
I reset factory data/ wiped cache & davlik three times each..
Then wiped all the mounted devices except EMMC.
Then ran Dark's Super cleaner thingy wipe.
Then ran a kernel cleaner.
Then flashed 4.2.
Then flashed ROMracer's exploited kernel twice.
Then reset to factory data, cleared cache & davlik again.
Then booted up and left it alone for five minutes before touching anything.
Hope that works for you!
It's how I flash all my ROM's these days.
Though I just started wiping factory data afterwards.
Click to expand...
Click to collapse
Which kernel cleaner did you run? Do you have a link?
Duh, q's been asked already....I was good until I cleared cache then I got the shutdown lockup. Now I'm looking for a fix because I got everything the way I like it. Not a big deal though but would be nice to fix.
EDIT: SUCCESS
This is the darkside wipe:
http://forum.xda-developers.com/showthread.php?t=1487706
And this is the kernel cleaner:
samsung_ultimate_kernel_cleaning_script_by_lippol94.zip
I don't remember exactly where I got it from. But I think it was this thread:
http://forum.xda-developers.com/showthread.php?t=1166954
The filename is the same as what I'm using.
And it's mentioned in seanszreamz thread.
http://forum.xda-developers.com/archive/index.php/t-1377087-p-11.html
Got it fixed with NexusMod ICS Beta 3 + Dark side super wipe
I have been trying to fix this problem and browsing threads with similar issues all night for about 6 hours and nothing seems to work.
I have been running on stock ICS 4.0.4 which I rooted and unlocked awhile back with no problems. I finally had the time to attempt to flash cm10 and I wanted to give it a shot, so I backed everything up, wiped data, wiped cache, wiped davlik, format /system. The ROM I attempted to flash was the newest version of cm10 nightlies 12-28 and gapps. After flashing everything went well and the phone booted up in cm10, but it is stuck on roaming. I tried everything that I could find in the forums and nothing seems to be working. I wiped again and tried to restore from my backup and the problem is still there, so I even went a step further and used Odin to flash fully stock unrooted/locked ICS 4.0.4 again and still have the same issue. The IMEI numbers matched up both times after flashing and I also made a backup before and even restored it to my phone as well, so I know that's not the issue.
Most of the threads I read said people were having success with "reprovisioning" their phone, but when I dial *2767*3855# nothing happens on my phone at all. Am I doing something wrong? Are there any other solutions out there that I might have missed?
Please help me so I don't have to return to the Verizon store when they open.
Thanks in advance!
You have to change to ruim/sim in mobile network settings
Should be under cdma subscription settings. Flashing to cm 10.1 changes it to Nv.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also system select you should change to automatic, not home.
I can't find any of those settings in my settings menu. I am back on stock ROM unrooted and locked with everything reverted to factory settings.
Ahh no idea on stock rom or tw. This is for cm.
It's strange to me because after wiping everything and restoring to factory locked settings, you would think it would go back to what it's automatically set to...
I got it!!!
Basically I used Odin to port a stock ROM that was already rooted and went through the flashing procedures as usual. Then I used what you gave me above and it is now working. Thanks so much for your help it's really appreciated!
And to think after all the trouble I went through reflashing everything that was all I had to do :laugh:
Thanks a lot!
xNali said:
I got it!!!
Basically I used Odin to port a stock ROM that was already rooted and went through the flashing procedures as usual. Then I used what you gave me above and it is now working. Thanks so much for your help it's really appreciated!
And to think after all the trouble I went through reflashing everything that was all I had to do :laugh:
Thanks a lot!
Click to expand...
Click to collapse
I'm new to odin and am having the same problem you are having. How did you unlock the bootloader and put cwm or twrp without data. I can't get the ez tools because wifi doesn't even work.
Ok. I was wrong wifi does work. In all my panic I did the wifi password wrong. How embarassing... And it's fixed!
Glad to see you sorted it out. Was going to suggest flashing back to cm 10.1 to access the settings.
Don't let this experience turn you off. Cyanogen mod is really great.
If you don't want to deal with the roaming problem I'd recommend flashing cm 10 12/16 nightly. Everything works peachy with the exception of the Bluetooth bass bug. You can fix it by making a call though.
Cm10.1 has low call volume but it runs really smooth. When you flash it you have to either not flash gapps so you can change the settings I mentioned in previous post, bypassing getting stuck on activation, and then flash gapps OR use the four corner trick to bypass activation (if you flashed gapps). After you change the mobile network settings, reboot and data should be fine.
It's really not that hard of a process. I got stuck in roaming the first time I flashed 10.1 but I understood what the problem was before hand. I flashed 10.1 and gapps immediately, like I always do with cm, and was stuck on the activation screen. I forgot the four corner code to bypass the activation process also. When I tried to restore a nandroid I couldn't cause it moved all the files around.
To make an already long story short, I had to download 10.1 to my SD card to flash without gapps and make the settings change.
On 1.55 firmware and S-off with OTA ROM. Running xposed.
My phone decided to restart on its own... Then stuck on Verizon logo, decided to hold volume down/-. Phone goes to "safe mode", which I've never heard of, till I google it... Thought to myself, I'll just reset n go back to my rom.... Nothing.... No more safe mode on bottom left. All the verizon junk apps r back from frozen. And to top it off my 64gb sd card was totally wiped out! All data gone.. Luckily I backup occasionally so it wasn't exactly end of world.
I decided to run my nandroid n find that it's corrupt or not installing right... Give up n totally start over... Hard reset phone... Wiped everything cept internal memory. Installed cleanrom ...
Everything worked cept gps n wifi.... Reinstalled cleanrom again over w/o wiping n gps is working again cept wifi. I can tether but can't get on wifi...
So....
1. Watch out for safe mode... N backup often
2. Is there anyway I can get wifi back?
3. Is there another recovery that does backup rom well on m8?
Kensai said:
On 1.55 firmware and S-off with OTA ROM. Running xposed.
My phone decided to restart on its own... Then stuck on Verizon logo, decided to hold volume down/-. Phone goes to "safe mode", which I've never heard of, till I google it... Thought to myself, I'll just reset n go back to my rom.... Nothing.... No more safe mode on bottom left. All the verizon junk apps r back from frozen. And to top it off my 64gb sd card was totally wiped out! All data gone.. Luckily I backup occasionally so it wasn't exactly end of world.
I decided to run my nandroid n find that it's corrupt or not installing right... Give up n totally start over... Hard reset phone... Wiped everything cept internal memory. Installed cleanrom ...
Everything worked cept gps n wifi.... Reinstalled cleanrom again over w/o wiping n gps is working again cept wifi. I can tether but can't get on wifi...
So....
1. Watch out for safe mode... N backup often
2. Is there anyway I can get wifi back?
3. Is there another recovery that does backup rom well on m8?
Click to expand...
Click to collapse
Sounds to me like your kernel doesn't match your rom. . You can try flashing the stock kernel or the stock rom over top to see if that fixes it.
Thanks, I'll look around for a stock kernel. :thumbup:
http://forum.xda-developers.com/showthread.php?p=51703075
I actually found this... It's one of your posting. Would this work as stock kernel?
Kensai said:
http://forum.xda-developers.com/showthread.php?p=51703075
I actually found this... It's one of your posting. Would this work as stock kernel?
Click to expand...
Click to collapse
I literally just removed that from afh last night. Lol.
Any of the stock rom or firmware update zips posted would have a stock boot.img you could flash with flashify or fastboot.
Here's one for 1.12.605.11
http://forum.xda-developers.com/showthread.php?t=2712793
I flashed the suggested kernel. I backed up my current one before flashing n found its the same one I currently use. I tried dirty flashing cleanrom again. Still no wifi n battery drain more now. Dunno if xposed may be a culprit?
My next move is to just try the stock ruu that you made. I just have to manually install the tethers n power settings...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}