After I updated to the newest nightly cm 13 22/7, I cannot search any wifi signal. Anyone has the same problem? And later on, I flashed the snapshot rom, my nexus 6p was bricked. It keeps showing the cm logo without any further action. What can I do?
st0123123 said:
After I updated to the newest nightly cm 13 22/7, I cannot search any wifi signal. Anyone has the same problem? And later on, I flashed the snapshot rom, my nexus 6p was bricked. It keeps showing the cm logo without any further action. What can I do?
Click to expand...
Click to collapse
You didn't flash the latest vendor.img...
Look on the CM page and you will find the link and how to flash.
Related
Is anyone else having the problem where if you turn off your phone and turn it back on it'll sometimes freeze at the Samsung logo. If you do a battery pull and turn the phone back on again, it'll boot like normal.
Firmware: MDL
ROM: Cyanogenmod 10.1 RC2
Recovery: TWRP
What twrp version?
xBeerdroiDx said:
What twrp version?
Click to expand...
Click to collapse
TWRP 2.5.0.2
I used your HOW-TO guide to complete everything
Loki+TWRP+Motochopper CASUAL
Wiping Device
Flashing ROM
How long has it been doing this/at what point did it start?
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
emckai said:
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
Click to expand...
Click to collapse
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
jd1639 said:
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
Click to expand...
Click to collapse
RC2 is a 4.2.2 build.
Last night I decided to just try and let it hang and see if it'll get past it but 2 minutes later it never did. So I just held the power button (10 seconds) to shut it down and restart.
Sorry, didn't read your whole post and missed the rc2.
jd1639 said:
Sorry, didn't read your whole post and missed the rc2.
Click to expand...
Click to collapse
No problem. Just wondering what is causing this issue, seems like some people in the Cyanogenmod thread is also having this issue.
It's happening on the cm10.2 roms too and seems to be related to the recovery used. See if twrp 2.6.3.0 works for you.
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
I switched custom recovery. TWRP to CWM and everything is booting just fine. (knock on wood) I'll turn off and on my phone a couple more times and see if it's actually the custom recovery.
cwm has had far fewer problems on the S4 than twrp. i've always rolled with cwm touch across my devices just out of preference. glad i havent had to deal with any of these twrp issues. glad you're sorted. cheers
Just rebooted my phone a couple of times (about 10 times) and it didn't hang at samsung logo anymore.
Thanks everyone!
emckai said:
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
Click to expand...
Click to collapse
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
CZ Eddie said:
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
Click to expand...
Click to collapse
x2 to all of the above. Known issue for S4s on 4.3 and 4.4 and although a couple of ROMs have claimed that they're "solving" it as of yesterday's nightlies it ain't fixed....
Just hold down power till the Samsung screen disappears then immediately let go. It'll try again. Repeat, repeat, repeat as necessary and eventually it will work.
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
CZ Eddie said:
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
Click to expand...
Click to collapse
I've been using the same kernel since yesterday afternoon and haven't hung once either. I've tried it with CWM and TWRP because my hangs used to occur when I rebooted system from recovery and both have worked just fine.
So much for my first post!
Just as the title says, after flashing crDroid AOSP build 4 from stock 4.4, I am having issues with the WiFi. When I first tried to set it up the list of available networks would not show, and then after when I went into the WiFi settings to manually turn it on, toggling it had no affect whatsoever.
I am using TWRP.
Has anyone experienced a similar problem, or have any idea what I could do to fix it? I would greatly appreciate any help!
raveglow said:
So much for my first post!
Just as the title says, after flashing crDroid AOSP build 4 from stock 4.4, I am having issues with the WiFi. When I first tried to set it up the list of available networks would not show, and then after when I went into the WiFi settings to manually turn it on, toggling it had no affect whatsoever.
I am using TWRP.
Has anyone experienced a similar problem, or have any idea what I could do to fix it? I would greatly appreciate any help!
Click to expand...
Click to collapse
I had a similar problem going from 4.4 back to 4.2.2 (Miui) I had to flash a different radio, maybe try the one for 4.4 from this thread.
http://forum.xda-developers.com/showthread.php?t=2527484
Make sure your kernel support PRIMA driver or flash a dePRIMAtor package.
Hi guys.
I bought my Nexus 4 (after selling me old Galaxy S2) a few hours ago and I'm running into some issues.
Whenever I'm on a ROM that isn't Stock, my wifi or wifi + BT aren't working. The WiFi status is always 'Turning on wifi...' and never changes, and occasionally its the same for Bluetooth.
I've tried installing CM11, Carbon and AOKP, changing kernels, even flashing the stock radio to see if anything changes, but it all stays the same.
Another thing I've noticed (I don't know if it has anything to do with the WiFi, but it could be) is that on AOKP and on the Carbon, I can't click the top right button in the notification bar (the one that shows you all the toggles).
The thing is that whenever I flash back to Stock 4.4, everything is ok, and both the WiFi and BT are working as planned.
I'm actually clueless after trying anything I could think of. Does any of you have any idea what's going on?
Thanks in advance.
Ardethian said:
Hi guys.
I bought my Nexus 4 (after selling me old Galaxy S2) a few hours ago and I'm running into some issues.
Whenever I'm on a ROM that isn't Stock, my wifi or wifi + BT aren't working. The WiFi status is always 'Turning on wifi...' and never changes, and occasionally its the same for Bluetooth.
I've tried installing CM11, Carbon and AOKP, changing kernels, even flashing the stock radio to see if anything changes, but it all stays the same.
Another thing I've noticed (I don't know if it has anything to do with the WiFi, but it could be) is that on AOKP and on the Carbon, I can't click the top right button in the notification bar (the one that shows you all the toggles).
The thing is that whenever I flash back to Stock 4.4, everything is ok, and both the WiFi and BT are working as planned.
I'm actually clueless after trying anything I could think of. Does any of you have any idea what's going on?
Thanks in advance.
Click to expand...
Click to collapse
Hello, you have to flash older radio to enable wifi. Try version 84. Just flash the zip from CWM.
http://forum.xda-developers.com/showthread.php?t=2087227
toycz said:
Hello, you have to flash older radio to enable wifi. Try version 84. Just flash the zip from CWM.
http://forum.xda-developers.com/showthread.php?t=2087227
Click to expand...
Click to collapse
Hi, thanks for the reply.
I noticed that a lot of my sensors are dead as well when not using a stock rom.
I've had nothing but Android devices for the past 4 years, but in this case, I don't know whether the radio solution can solve the problem, since it looks more like a Kernel issue, or am I wrong?
Isn't the radio supposed to affect only wifi and BT? What about the other sensors?
Will try that soon though, phone has 2% battery.
Ardethian said:
Hi, thanks for the reply.
I noticed that a lot of my sensors are dead as well when not using a stock rom.
I've had nothing but Android devices for the past 4 years, but in this case, I don't know whether the radio solution can solve the problem, since it looks more like a Kernel issue, or am I wrong?
Isn't the radio supposed to affect only wifi and BT? What about the other sensors?
Will try that soon though, phone has 2% battery.
Click to expand...
Click to collapse
I'm having a similar issue. On nexus 4 phone with current stock ROM running 4.4.2, I tried Cyanogenmod 10.1.3 but wifi was always in trying to connect mode, never managed to turn it on/off. The same behavior is on miui ROM but on stock everything works fine!
tushargok said:
I'm having a similar issue. On nexus 4 phone with current stock ROM running 4.4.2, I tried Cyanogenmod 10.1.3 but wifi was always in trying to connect mode, never managed to turn it on/off. The same behavior is on miui ROM but on stock everything works fine!
Click to expand...
Click to collapse
Are you running the .98 radio with 4.4.2?
4.4.2 WIFI and Bluetooth connection issues
Ardethian said:
Hi guys.
I bought my Nexus 4 (after selling me old Galaxy S2) a few hours ago and I'm running into some issues.
Whenever I'm on a ROM that isn't Stock, my wifi or wifi + BT aren't working. The WiFi status is always 'Turning on wifi...' and never changes, and occasionally its the same for Bluetooth.
I've tried installing CM11, Carbon and AOKP, changing kernels, even flashing the stock radio to see if anything changes, but it all stays the same.
Another thing I've noticed (I don't know if it has anything to do with the WiFi, but it could be) is that on AOKP and on the Carbon, I can't click the top right button in the notification bar (the one that shows you all the toggles).
The thing is that whenever I flash back to Stock 4.4, everything is ok, and both the WiFi and BT are working as planned.
I'm actually clueless after trying anything I could think of. Does any of you have any idea what's going on?
Thanks in advance.
Click to expand...
Click to collapse
If the custom roms you are using are based on 4.4.2 it may be a problem with the newer kernel. This article recommends flashing the 4.4 kernel as a possible fix.
http://www.androidpolice.com/2013/1...-still-suffer-from-assorted-bluetooth-issues/
im currently running the cm 10.2 rom on my sprint galaxy s 4 and its flawless but when i download one of the cm 11 nightlys through the update system under settings. it will install but then when it finally boots up i can get past the lock screen, then it will freeze and restart. what are some things i should do or look at to fix this.
kjrehrer said:
im currently running the cm 10.2 rom on my sprint galaxy s 4 and its flawless but when i download one of the cm 11 nightlys through the update system under settings. it will install but then when it finally boots up i can get past the lock screen, then it will freeze and restart. what are some things i should do or look at to fix this.
Click to expand...
Click to collapse
You should do a clean wipe of factory data/cache/dalvik. Then install cm 11 nightlies with a kk gapps package
Anyone try this yet? Impressions?
Sent from my Nook HD CM11.
I tried it last night. I flashed over the 3-6 nightly and had many force closes and network issues. I did not try and do a clean flash.
On an attempt to just hit update and go it got stuck in a reboot loop. Attempting a clean install results in network seen but not connecting. Rolling back to 10.1.3.
Edit now it seems no matter what version I try installing networking is hosed. I feel kinda stupid here guys.
Edit: Had to go through reflashing cwm-5 the m4 rom, gapps, and all that as if I wee going from 10.2 rather than update 'just working' Most annoyed.
I should have left well enough lone. I had installed the 3/8 nightly and it was working great.
Then I saw the 3/8 snapshot and decided to install it.
The Snapshot seems to be no good. It throws errors when logging in and I also lost WiFi.
I have re-installed the 3/8 Nightly and am a happy camper again.
In fairness leaving well enough alone would have left you with B&N's stock environment. We tinker, it's what we do.
I gave this a shot myself and got a bunch of fc's. Went back to the last nightly. From what I heard the M should be more stable so much for that.
Sent from my SCH-I545 using xda app-developers app
I updated from 01/18 to the M4 and it has been very stable.
See http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for important considerations in switching between the two branches snapshot/stable and nightlies of CM11. The blog explains why going from some of the most recent nightlies to M4 might be a downgrade and as such can cause the problems reported above.
I don't know if I just have bad luck (or a bad device), but I haven't had a single official CM11 build without random reboots and screen flashing / flickering. Anyone else here?
You should not flash the m4 if your nightly is newer than 20140308 otherwise you will get FC's.
adwait.bhandari said:
You should not flash the m4 if your nightly is newer than 20140308 otherwise you will get FC's.
Click to expand...
Click to collapse
Not true.
M4 was taken from the nightly branch on 2/28. If you have flashed a nightly to your device newer than 2/28, you will be downgrading if you flash M4 afterwards - resulting in unpredictable results.
Based on this thread, the results will be WiFi issues and possible boot issues.
If you want to switch to the monthly builds, do not take anymore nightly builds, and wait until April to take the M5. If you want to stick with the nightly s, then do not flash the monthly's.
pyrofool said:
I tried it last night. I flashed over the 3-6 nightly and had many force closes and network issues. I did not try and do a clean flash.
Click to expand...
Click to collapse
need to do wipe data/factory reset and not restore the old data. otherwise, "android.process.acore stopped unexpectedly" for me.
I guess I got lucky. I dirty flashed m4 over 10.1.3 stable and everything is running perfectly. I wasn't expecting it, but m4 is much speedier than 10.1.3, only downside is battery life seems to be not as good.
Beware!
There was a post I found a while back on the official Cyanogemod site that went into details about Nightlies, Milestones, Release Candidates, and Stable Releases. What would be most important for users of CM11 at this time which was explained in the post is that you either stick with updating from nightly to nightly OR milestone to milestone. If you're on a nightly and you update to a milestone snapshot, you risk damaging and messing up the OS. Vice-versa as well and should also apply to RCs and Stables. Nightlies are bleeding edge and have the latest code while a milestone snapshot is more stable, but has older cold. So going from nightly to milestone snapshot would be one heck of a messy downgrade.
srry for dis messy post btw qq