I recently bought a nook color and flashed CM7 to the internal memory. It worked perfectly for about 2 weeks. Then the trouble started. My wifi would not connect. It would get to the point where it would say, obtaining IP address, then begin the process again without ever actually connecting. So i decided to try to reinstall CM7 hoping that would fix the problem. I attempted this, and to my disappointment, the nook wouldnt boot past the green cm7 logo. I reverted to stock from a backup i made initially, and the nook booted just fine into the stock OS, but the wi fi still would not connect (doing the same thing as in cm7). I reinstalled cm7 and again was greeted with the same boot issue as before. I then followed the "dummies guide to fixing my nook wont boot" and returned it to the stock image and reformatted the data and system partitions as the guide states. I then (again) flashed CM7 (nightly 134). This time, it booted as it should, but the wifi still will not connect, and also the softkeys are not present. In settings, if i select the CM7 settings, i am given a force close notification. I am beyond frustrated at this point and would greatly appreciate any help.
Thank you
I have the same problem with my wifi. It's really weird. It was working last night, then I backed up the current rom and when it rebooted the wifi wouldn't work again. I'm about to just remove cm7 because I don't have the time to fiddle with trying to figure out how to troubleshoot it. A buddy of mine at work is the one who flashed it for me but it hasn't been a great experienced. Rom Manager also doesn't show an updated version of cm7, I think the one that is flashed on my NC is like from may 25th or something.
idk what the hell's going on with it...i cant get it to work no matter what I do and it's driving me crazy. I posted here and on the CM7 forums and havent gotten any help yet, nor have i seen anyone else with the same problem (aside from the above poster).
Related
In addition to the home and talk buttons not working. The phone will not lock when I hit end, it just puts into a sleep mode.
Holding end only gives a reboot and shut down option. This problem surfaced after installing the new SuperD mod. I did a wipe and reinstalled it two nights ago and the problem was resolved, but it has resurfaced tonight.
Anyone have any thoughts on the matter? Should I go back to the old version?
Which new version? The beta or 1.10.2? If it's beta - then you def should go back to stable. If it's 1.10.2 - then you most likely have a hardware problem. A lot of people run Super-D with no problems.
Further more, sometimes your trout-keypad-v3.kl (located in /system/usr/keylayout/) can get corrupted and cause that. It's extremely rare but you may try either re-flashing or just pushing that specific file.
Word of advice (which you may already know): if anything goes wrong and you want to rule out software problem - install a base rom (like the defanged from Cyan's wiki), complete wipe and min options (no Apps2sd, no swap, etc) and see if it fixes the problem. If the problem is gone - you're in lock and something went wrong with the rom. If problem is still there- start looking for a new phone.
Good luck.
I did a fresh install. I repartitioned the sd card, reinstalled all apps. did a factory wipe, reinstalled the base defanged, then did super D. It wasn't the beta, i had upgraded to 1.10.2 and experienced the problems.
It would work fine for two days, then if my phone would shut off (battery has weird contacts) then it would boot back up and my settings would be all messed up, and the keys would work. I would try re installing the ROM, but no fix.
A wipe remedies the problem. I went back to cyanogen last night to see if the problem appears on this rom, so far it hasn't.
I never had this problem until i upgraded from 1.9.3
I'm on CM dal .32 test build 3.1
Today I tried setting up a VPN but failed. The screen became frozen and I decided to reboot my Nook Color. However, after rebooting my wifi is no longer working. It says "connecting" but then "disconnected" Scan option didn't show any network.
Anyone can help me?
CM7.0.3 with Nook Color no longer works
Hi,
I've run into the same issue with my nook color. I'm not sure if this is an issue with the kernel or the physical device. I know that this is not a router issue since I'm able to connect other machines to my router. Also, I no longer see any other hotspots with the Nook.
I tried some suggestions that I've found on other websites, which include
Shutdown Tablet and start again
Re-install Google Apps
Use Fix Permissions in Rom Manager
None of these work. Any suggestions or is this a known bug?
lazinase said:
I'm on CM dal .32 test build 3.1
Today I tried setting up a VPN but failed. The screen became frozen and I decided to reboot my Nook Color. However, after rebooting my wifi is no longer working. It says "connecting" but then "disconnected" Scan option didn't show any network.
Anyone can help me?
Click to expand...
Click to collapse
Same here, I was using nightly 115 with Dalingrin's 6/18 OC kernel when the problem started. I've since rebooted multiple times, fixed permission both from CWM and in Rom Manager, flashed nightly 117 without flashing OC kernel, and still haven't solved the problem.
Wifi just stays "Connecting" and then changed to "Disconnected" briefly and go back to "Connecting" again.
Just reflash your ROM or the latest ROM and DON'T mess with any OC kernels.
Does it work? If so, try the OC kernel again. If it fails, let Dal know in his OC kernel thread, and just re-flash your ROM again to return to the stock kernel. Wipe cache/dalvik as necessary, but don't wipe data and you're not going to lose anything.
One suggestion I have is if you're using AES on your router, try changing from WPA2 to WPA or changing WPA AES (or AES+TKIP) to just WPA TKIP and see if that fixes the problem.
There's a long standing issue with some routers regarding AES in Android, and apparently some laptops also had this issue on older kernels.
Flashing to the latest rom without messing with the kernel was the first thing I tried (other than turning wifi on and off multiple times). It didn't work.
What eventually worked was when I wiped data and factory reset it. Some how that fixed the wifi.
The strange thing is I had just recently factory re-setted coming from an old (pre 2.6.32) nightly a couple of days ago, and had not gotten around to installing much, and I did not restore from backup. i.e. the only thing installed when the wifi problem suddenly appeared were the google apps, Aldiko, QuickPic, Rom Manager, MoboPlayer, and a few ADW themes. None of which sound like they should do anything that messes up the wifi.
I doubt it has anything to do with the router, because I tried connecting it to my router (tkip), hotspot from my android phone (unlocked) and hotspot from my iphone (unlocked). My phone just did not see any network around at all, not even the 5-6 different network from other people in the building.
As mentioned, I have factory wiped my NC and all is fine again now, so I'm not too concerned right now, just curious what could have caused the problem.
After a few days running Dlev's 4.2 ROM, my wifi stopped working suddenly. When I try to turn it on it says error or unable to start wifi. I've exhausted several initial options I began walking myself back through various ROM's back to the original 2.1 stock ROM. Without success I even performed a master clear and several reflashes of the orininal stock ROM, nothing is working. I tried FXR Wifi fix and rescue. Does anybody have any ideas on what I should do?
Thanks,
-Digitalchaos
Kernel?
What kernel were you running with the custom ROM? Talon's being updated really frequently, so if it's Talon, you might try the latest version of that (0.4.4.22, as of this writing)
digitalchaos said:
After a few days running Dlev's 4.2 ROM, my wifi stopped working suddenly. When I try to turn it on it says error or unable to start wifi. I've exhausted several initial options I began walking myself back through various ROM's back to the original 2.1 stock ROM. Without success I even performed a master clear and several reflashes of the orininal stock ROM, nothing is working. I tried FXR Wifi fix and rescue. Does anybody have any ideas on what I should do?
Thanks,
-Digitalchaos
Click to expand...
Click to collapse
Did you try rebooting your router or device that gives you wireless signal? also see if other devices can connect.
It was Talon 0.4.4, but I've gone all the way back to stock ROM/kernel etc and that makes me think that this is a HW malfunction.
AT&T had me reboot the router too, my laptops are able to connect just fine. It's not really a connection problem either, Wifi will not turn on at all.
I called Samsung and they want me to ship them the phone, still debating that one since I will have to go without a phone.
-digitalchaos
So I had some escapades today, I had my SGS running jellybean, then I tried to change the screen density and bang, bootloop. I panicked and after some odin fiddling managed to get it booting Darky using odin. I was in a room with no signal at the time so I thought nothing of not having any signal, even so I then went ahead and used recovery to reinstall my Jellybean rom since that's a bit nicer than the 2.3 Darky.
Long and the short of it is, I can search for networks in my options and it will find them, but when I tell it to connect to one it says "Can't connect to this network right now. Try again later"
I have tried later and surprise surprise it didn't work. I have tried installing a different radio, clearing the dvalik cache and fixing permissions as well as a few other things. Please can anyone suggest something, this seems to be a very uncommon scenario and it's stressing me out that I can't find any solutions.
alzrnb said:
So I had some escapades today, I had my SGS running jellybean, then I tried to change the screen density and bang, bootloop. I panicked and after some odin fiddling managed to get it booting Darky using odin. I was in a room with no signal at the time so I thought nothing of not having any signal, even so I then went ahead and used recovery to reinstall my Jellybean rom since that's a bit nicer than the 2.3 Darky.
Long and the short of it is, I can search for networks in my options and it will find them, but when I tell it to connect to one it says "Can't connect to this network right now. Try again later"
I have tried later and surprise surprise it didn't work. I have tried installing a different radio, clearing the dvalik cache and fixing permissions as well as a few other things. Please can anyone suggest something, this seems to be a very uncommon scenario and it's stressing me out that I can't find any solutions.
Click to expand...
Click to collapse
check apn settings?
slaphead20 said:
check apn settings?
Click to expand...
Click to collapse
Yeah I've checked them and unfortunately they all seem to be in order still, though there are a lot more settings than any website offers things to put in them
same problem
i am having this same problem on all cyanogenmod 7,9,10. i have tried many radio and modem flashes. i can scan and see networks, but i can never connect to them.
have you made any progress?
Problem is EFS folder which tends to do with IMEI.
To fix it you need to copy the backup EFS folder from your SDCARD to the root of your device. (/)
If you don't have a backup you'll have to ODIN back to stock and re-root....etcetera
Sent from my GT-P7500 using xda app-developers app
thx
thank you for the response. I put it back to stock lastnight before bed so i will give this a try.
i have the gti9000m from bell in canada. I updated it through kies to 2.3.3 gingerbread and it all went badly. It would boot up and load to the os be on for a bit then reset. It turned out to be wifi problem, running it on airplane mode stopped it from rebooting. Then if i tried to turn on wifi it would quickly reboot.
So then i tired all the cyanogenmods, which worked it stopped rebooting all the time. however the wifi would connect and work for about a minute then it would drop. doing the
1.turnOn gps
2.turnOn wifi
3. turnOff gps
this would let the wifi work again for about a minute. I tried all the wifi fixer apk, and a bunch of wifi.zip mods, and then ping the router gateway constantly, none solved this problem. Very annoying because i need the wifi working for develpoment of apps. I have spent a great many hours on this problem. lots of people seam to have this problem but no solutions have wokred for me.
So, my questions are....
1. does your wifi work?
2. how the heck do i get mine to work?
back to stock
After going back to stock then upgrading connecting to network operators is fine.
wifi is still broken though
Hi guys and gals.
I've been flashing roms for years and I've soft bricked my devices dozens of times and have always been able to recover, except this time.
I was running Cyanogen mod 12.1 and all the problems started happening after a nightly update. Basically, the phone got super laggy and eventually started random rebooting. I thought it was a bad flash or something was wrong with the latest update so I did a clean wipe and flashed another rom, same thing happened. Eventually I Odined back to stock and it ran fine for a few days but the problems came back. Now the phone won't even finish boot anymore. I used NAND erase all in odin and and reflashed again, it seems to be better since it wont reboot its self anymore but I can't get past the T-mobile splash screen. Last night I tried reformating the NAND using a PIT file but I kept getting "Secure check fail : PIT". I was starting to thing the problem is hardware related but it won't RR in download mode and I think its too big of a coincidence that it happened after the Cyanogen update. Any ideas?
My first and always main advice is that if you are unsure about your hardware the first step is to Odin back to stock. The reason is because it is a bit for bit rewrite back to the way the phone was intended to be run as long as you do a factory reset from Stock Android Recovery before it boots. This is how your phone was when it came out of the box and it is a great way to check if it has a hardware issue by looking for bad behavior when using the original drivers.
If you flash back to stock completely clean and your phone is still acting crazy you might have bad blocks on your NAND, you might have issues with your RAM/CPU, or it might just be a loose hardware connection from heat or impact. But you can only truly diagnose those from Touchwiz because the drivers are first-party, not reverse engineered to be compatible. If you can reinstall all your apps and use it normally for a week then your hardware is good and CM was the problem and you should try another AOSP build.
I am on the 09/09 Nightly for CM and I can tell you that I have no lag or issues on my device at the moment for what that is worth. Good luck!
Thanks. I might just send it into samsung and see what happens.