Related
I am posting a new thread because I'm experiencing the issue with several diffrent ROMs so obviously it's a general issue not a ROM specific one. Also I have read through countless pages of posts with no luck so hopefully someone can shed some light. Over the past few days I've flashed (forgive my spelling) dude's .5, ravenge, cynogen 3.4 and I have been having issues with the phone not waking after either I put to standby myself or the screen times out. I know it's not an issue with my phone or card because I go back to virtudude's ROM without the issue. I have tried everything, formatting my partition, ext2, ext3, wipe, no wipe, everything I can think of and still have the issue accross mutiple ROMs. I know it's not just me because my friend with a G1 is having the same issue, as well as many people posting in the threads. Can someone please point me in the right direction to fix this issue please?
My phone:
G1 with JF 1.42
Newest SPL 2005
Newest 26I radio
8gb SD card, class6, ext2 or ext3 partition (same issue on either)
Thanks in advance for any help!
me too
I noticed this same problem, its related to wifi, when I disable wifi my phone wakes up, also I have searched everywhere too for a solution. I think the compiled wifi deiver in these roms are not compiled right. So its either this or some other problem.
Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.
I am doing a test, im leaving wifi on while the screen is off in settings, will report back
This happens to me also but its only with hero I also have the new radio and spl. I can run hero with no problems as long as I don't use apps to sd or lucids txt. The wired thing is that after I use any apps to sd it works great but only for a day sometimes a few hours. Then I will start to see freezing up or it won't wake up at all, unless I reboot or pull battery. I've tried to reformat my card, resize my partition I'm also lost on this one fresh out of ideas.
Do you guys think it might have somthing to do with the sdcards? Im useing a 4g class 6 transcend micro SD, its only about 2 weeks old. Jason what other roms gave you these problems?
defconoi said:
Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.
Click to expand...
Click to collapse
I personnally don't see the correlation between locking and WiFi, I was at work the other day and flashed a ROM and it was doing it. I have my WiFi off at work so that wouldn't have been the case that day. I do notice the bottom of the phone getting hot though.
In response to the other person with the sd card question I really don't think it's that as I have a class 6, have formatted every way possible. Unless the issue has to do with apps2sd, I use apps2sd on every ROM.
Glad to see I'm not the only crazy one on xda!
joe v said:
Jason what other roms gave you these problems?
Click to expand...
Click to collapse
Almost every ROM to come out in the last couple weeks has done it. TheDude's .5, Ravenge's ramjet, Cyanogen's 3.4.1, and the Cyanogenized Rogers ROM.
You know looking at these the one thing these all have in common is being Cyanogenized. And the only ROM to come out in the past few weeks that hasn't had that issue is Virtuedude's Rogers ROM, which isn't Cyanogenized.
If any devs are reading this thread if you can make a version of your most recent ROM without Cyan's build kernel and boot and see if that helps. I'd be happy to test it for you to try and get to the bottom of this. If you wanna shoot me an email hit up jasonsyn at gmail.
I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.
indiekid97 said:
I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.
Click to expand...
Click to collapse
Yeah but I've had the new SPL and Radio for a month and this just started a week or so ago...
I am having the exact same issue. I usually have wifi bluetooth and 3g disabled (saves battery) I noticed this started after grabbing the new spl, ever since it's been freezing in standby randomly. I'm going to try Virtudude's rogers rom to see if the combination of Cyanogen's boot image and the new spl is causing the freezing. Hopefully seeing as Virtududes rom isn't based on Cyanogen's boot image it won't freeze. I'll report back with my results.
I thought my button got worn out. I never had the symptoms on rc33. When I switched to cupcake back during hatkuros prime just before dudes first releases I noticed it. I thought if it wasn't my button it might be somehow related to jf kitchen since almost all my roms touch it at some point. Just speculation though, donno what causes it.
Hey what recovery image are you all running?
I'm gonna flash the new Cyanogens 1.2 Recovery image and see if that's the issue.
Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.
Jason Syn said:
Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.
Click to expand...
Click to collapse
try holding down menu or the power button...i had this issue and my sd card would "unmount unexpectedly" and then this ended up into my sd bein fried
for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.
dbhatesyou said:
for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.
Click to expand...
Click to collapse
Ok I'll be happy to but I'm a linux virgin...would you mind giving me step by step in adb and I'll give whoever the log that can make sense of it.
This happens to me also on The Dudes Roger built. I don't have WiFi enabled so it isn't that it seems pretty random and just I get no response from the phone and have to so the soft reset (Call Menu Power) and then it'll work again. Normally only happens like once a day though so I can live with it but it is a inconvenience and can be annoying if it does it when you actually need to use your phone for something with some importance.
well if you're on linux and have it to where adb runs from terminal , just type
Code:
adb shell reboot
but before all that ddms (dalvik monitor) just type ddms in terminal it will boot up and show everything your phones basically working with.. and issues,
now if your linux terminal doesnt work well with adb (cant get it to work , google "50-android.rules" and "51-android.rules" n see if those help, and also set your echo path right )
now if you're on windows just hit windows key + r type cmd , and set yourself into the sdk/tools directory, then type ddms that will start the dalvik monitor (try and save a log) make sure the log saves before rebooting the phone, when you're done you can just ctrl+c and type adb shell reboot, and your phone should reboot.
[just the basic]
i've ran into this intermittently...most of the time while using the browser or using the onscreen keypad during a phone call.
I'm on JF CRB43(which is 1.51 i think) with the Hard SPL and JF Recovery.
Only thing I've been able to do to get the phone to wake up is wait. eventually it'll come around. or pull the battery, which i try not to do.
I am one of the many who have been experiencing the random reboots. I have seen talk about it, but have not seen anyone really looking into why this is happening. Some people claim it happens only when docked, or when SD card is in etc. Yet others post that they still get the reboots without doing those things either.
I have been monitoring my reboot problem very closely. I have yet to determine the cause other than it only happens when the device is put into sleep mode manually or automatically, and I am looking for some help from some of the DEV's around here.
When our TF's do this reboot, it is a system crash. When this happens, a ROMDUMP file is placed on the internal "sd card".
These can be viewed with a simple txt editor, like windows notepad. I myself can not read the code and understand what info it is revealing to me. According to an Asus tech on the phone this file can tell you what went wrong and made the device reboot. However the buggers won't tell you crap over the phone and want me to send the device in with the ROMDUMP files.
When I try and read the files, I do see one thing in common, in 99% of them, right near the end of the file, or the very last line before the crash, this line is present,
Kernel panic - not syncing: Fatal exception in interrupt
<2>[ 162.985309] CPU1: stopping
If our reboot issue is kernal based, which would indicate it's a firmware issue;
I was thinking one of the talented DEV's around here could fix us up.
Hell maybe even just a reflash of the current firmware would fix the issue.
Anyway, if a DEV around here want to or willing to look into this, I have some ROM dumpfiles they can look at, just send me a PM.
For reference,
I have a B60K modle
Stock 3.1
GPS 1.3.1
Wifi 5.1.42
BluT 6.17
Kernal 2.6.36.3-00001-gf377a2b [email protected] #1
Build HMJ37.US_epad-8.4.4.5.2-20110603
Thanks.
I don't have any more dumps recently, deleted them so I can't pull up and see what mine said to give you, but wanted to just say I was having these multiple times a day every day and it started once I bought an AData 16GB SDCard for the dock. Then I ended up removing that card and bought a MicroSD 16GB card instead and it has quit doing the random reboots, so definitely seemed to be something with my SDCard in the dock.
Post your whole log here (as .txt or .zip) and I will look at it.
I've had these once or twice but have always deleted the file.
The Kernel Panic is the kernel's way of telling you that something unrecoverable has happened and the integrity of the whole OS is in question. Think of a kernel panic like a BSOD on Windows.
I've never seen that specific one before, but a quick Google search indicates it may be a problem with I/O operations - like bad RAM or a bad SD card.
sassafras
Thanks for the response. I have included 4 RAMDUMP files. I find these 4 special because they all happened in quick succession. Four separate reboots all within 8 mins of each other without any interaction of the device myself. I never touched the device, I just sat there and staring at the device rebooting 4 times in 8 mins. On the final reboot the device never came back on. AT this point I picked up the device and had to hold the power button down for over 10 seconds for the device to come back on to an Asus splash screen. This was mins after I did a fresh factory reset via the OS options internally then a hard reset using the hardware buttons.
...It's a bug alright...
It doesn't seem to be caused by the same problem though, just that the watchdog program invokes a kernel panic and reboots. Weird. I'll backtrace it later and see what's up.
sassafras
went a whole day without a reboot. I did have an odd lock up/freeze at the lock screen where i couldnt unlock the device or get it to rotate the screen. It was locked up tight. Held hte power button down for 20 secs before it shut down. Rebooted, no new RAMdump created. No issues since.
sassafras_, Did you have any luck reading those ramdumps?
I did - sort of.
They're all related to the watchdog program assuming it's soft locked up. Which it may very well have been, but since you weren't using the device at the time, it's hard to know for sure.
The function's that were called immediately prior to the fault were different, which to me indicates that it's just buggy software. Honestly, without doing a backtrace I wouldn't know, but I can't without a system.map from around the time of the lockup. I'm going to assume it's just buggy code from 3.1 and wait and see if the 3.2 release lowers the rate of these. If not, then maybe I'll do some more digging.
sassafras
sassafras_ said:
I did - sort of.
They're all related to the watchdog program assuming it's soft locked up. Which it may very well have been, but since you weren't using the device at the time, it's hard to know for sure.
The function's that were called immediately prior to the fault were different, which to me indicates that it's just buggy software. Honestly, without doing a backtrace I wouldn't know, but I can't without a system.map from around the time of the lockup. I'm going to assume it's just buggy code from 3.1 and wait and see if the 3.2 release lowers the rate of these. If not, then maybe I'll do some more digging.
sassafras
Click to expand...
Click to collapse
Is there any progress on this issue? I bougth a brand new tf and during day random reboots maybe 50 times. And that romdumps are appeared on my internal storage. I dont have external sd by the way. Im stuck.
Hi.
Im having a same problem with my Transformer. Its a week old B60 and its reboots probably 50 times a day and give me log files.
Also im using Honeycomb 3.2
I really want to find out what is going on
i guess its a hardware issue or something.
i'm going to give back my TF today and take back a new one.
if i get same errors, i'll let you know.
I posted a workaround that helps immensely for rooted tablets somewhere around here. I can't find it tonight, but it's in one of the other 'random reboot' threads.
sassafras
sassafras_ -
Did you ever find anything with this issue? I am on my second TF and it is exhibiting the same random reboot while sleeping issue as the first. I know you have a post on another thread indicating how to tell the kernel to ignore "oops" conditions - have you received any feedback on how that is working? I assume this requires root access, I haven't yet rooted my device.
I have collected a few ramdump log files, but as of now only one out of 6 shows a kernel panic. I am new to Android, and I am trying to make sense of the dump logs. It appears that these dumps are maintained in a ring buffer, so the last entries are usually somewhere in the middle, is that correct? All of them also have some garbage at the end, but I assume that is just another effect of the ring buffer strategy.
Like I said, I am new to Android, but I am a long time embedded and real-time programmer, and pretty handy in Linux. It seems to me that the log files aren't providing enough information, but I'm not sure how to debug kernel/system crashes in Android. If anyone could point me in the right direction of where I should look next to get more information on these crashes, perhaps we could get to the bottom of this problem.
From what I can tell via the logs, when the TF is sleeping, it wakes up from time to time for various reasons, then suspends when it is done. It looks like it is during this wake/suspend cycle that something occasionally goes wrong and causes the tablet to reboot.
I am hoping that this is a software/firmware issue (or a hardware issue that can be worked-around with software), because I really like the TF platform and this issue makes keeping apps like IM or email running while it the device sleeps kinda iffy.
Any help from the awesome experts here at XDA would be greatly appreciated, and I look forward to learning more of the gory details and inner workings of Android.
I have had the same issues. Configuring the kernel to ignore oops only helped a bit. The tf would still freeze in standby eventually (once a day or so). My supplier (i.e. not Asus) replaced it and my new tf (a SBK v2 one, unfortunately) has not rebooted once in 2+ weeks. So my guess is that it was a hardware issue (memory, something not coming out of backup mode properly, ...?). Not sure if one could work-around it in software.
Now, this was probably not very helpful but I thought I'd share my experience here. And possibly my tf suffered from an entirely different defect, although the symptoms were the same (ramdump logs from random reboots in standby, independent from wifi on/off, sync on/off, and lots of other settings I tried).
flipflipflip -
Thanks for your reply! I was hoping that it wasn't a hardware issue, and since I got two in a row with the identical problem I was thinking that maybe a software fix could get around it. After reading about your experience, I went ahead and returned it and ordered another one from a different source. Hopefully the third time's a charm!
I'm keeping my fingers crossed that this one is not an SBK v2, but I'll be happy just to have one without sleep-apnea!
This did give me a chance to load up ADB and poke around a bit under the hood of the last one, so if nothing else it is a learning experience. Hopefully I will have something to contribute to the community once I get my hands on a working device.
I know it's been a while (had a big work-related headache), but just wanted to post and let people know that I finally received a TF101 (B50!!) that seems to be working just fine - so I guess it was just a combination of bad luck and a hardware issue after all.
The only issue I have now is that sometimes when it is sleeping, it loses its internet connection (it still seems to be connected to the AP) - but I think I can work around that.
Cheers!
I've got this Samsung Focus on AT&T, the other day I decided to force the newest update. I made sure I had all the correct languages and everything. The update went through and most of the phone works. (cellular connection is indeed corruption, and I know about the fix for that.)
Basically what's happening is, the Phone liveTile shows the accumulated missed calls but when I tap on it, the animation freezes then goes back to the homescreen. I can call people through the People app or by using TellMe, and people can call me. I suppose the only thing I can't do is check to see who has called me.
Is this a known issue? Is there a fix? please let me know! as for the backup...
Apparently the backup I did got corrupted in some way, so there's no going back to that (the currently existing back up for some reason is after the update, though I haven't tried using it yet).
restart it. if doesn't work. reset the phone
Yeah, I definitely tried restarting it. I even ran the Samsung tools and that didn't fix anything (including my data issue... I tap on "cellular" in the settings and it doesn't open. ****e.) To modify a classic Bill Gates quote... "I guess that's why they're not shipping 8107 yet."
I think I have an old mango back up from the fall, but oh jeez, that's a lot of backtracking.
I'll keep refreshing this thread to see if any experts have any ideas for a little bit, after a while I'll just reset the phone I guess.
The phone app thing isn't a huge deal at the moment, but no cellular data?! How am I supposed to win arguments without a cellular data connection?
read the thread more carefully, and apply the correct updates - core os update is not enough...just read...please!
Bad update, you need correct language file, i had the same problem on my Titan... Phone live tile, in settings Mobile network etc doesnt work after bad update.
I had the following in my cab sender folder:
- diff-7.10.7720.68-7.10.7740.16-armv7-retail-microsoft.pks_2cb1bfdd82133914239b8ee1a78e61e9000d124a.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.lang_0c0a.pks_97df86b81a40df06bb2b15c6739e2ee772e53bbf.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.lang_040c.pks_2d74e8c5f6a835f1fe4c62b488c96ac2d7f01c29.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.lang_0407.pks_b50019ef50d52090d408d854c0708ddbf520706c.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.lang_0409.pks_bfd9c047a7b27c28208c8a717f8d7511fb2586f1.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.lang_0410.pks_9ecf9b052b6cc3161462e998dac8204a0f754556.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.pks_c9b7f3bc5bb340ba30473b566b4557de0cf3322e.cab
Will simple reapplying work perhaps? I mean, I'm pretty sure those are the only ones I needed, I did read the thread quite a few times.
Update reapplied and now it's working!!!!
Now I just need to figure out my internet sharing issue.
I received an OTA Update in early to mid May. I am now forgetting which version I received at that time. ( I forget as I have done so many downgrades/upgrades/factory resets in my troubleshooting the last month!) Up until these issues, I've never rooted or flashed a ROM, or unlocked boot loader or anything. My N5 had always been completely stock.
First Issue
It all started with just the sim card. I get "no sim card" message, even though it was in there. This was my original SIM card and I had never ejected it since I bought it new. I found I could turn it off, pop it out and back in, and boot it again. Sometimes it will see the sim card again. It may take 20 times, but finally work.
I naturally got a new sim card, as well as confirmed said sim cards worked in other phones. My wifi and bluetooth were working fine at first. Working with google support, they recommended a factory reset to fix the sim card issue. Immediately after the factory reset, my bluetooth would no longer turn on nor show a MAC address. At this point, my wifi was fine.
Second Issue
In addition to the sim card slot issue, now my Bluetooth no longer works! Around this time, I received another OTA update, this time it was 5.1.1 LMY48B. I had hoped it would fix the issues, but no dice! I start reading up on the XDA forums as I am determined to start rolling back to see if this will fix anything. I unlocked the boot loaded, rooted, etc following the threads on XDA
Third Issue
I do all sorts of flashing to hammerhead-krt16m_4.4 to hammerhead-ktu84p_4.4.4 to hammerhead-lrx21o_5.0 to hammerhead-lmy48b_5.1.1 . On the final flash back to 5.1.1 my wifi now no longer works!!!!!!!!!!! It is stuck at wifi turning on and no MAC address shows. It also seems my cell data is very very slow now!
After many calls to google, I think I finally succeeded in getting a “ticket routed up”. My phone is from the play store around 10/31/2013. They keep pushing I am out of warranty. I attempt to ask for a refurb N5 without luck so far. I am not very confident anything will come from google. This being my only handset now, it is just not an option to send this to LG. My current state is my voice/txt and cell data are working. Data seems a little slow but usable. Wifi and bluetooth won't turn on. I also still have the sim car slot issue upon rebooting. After a bunch of reboots it will eventually see sim card.
What else can I try? Is there a better way to attempt to repair/reload my radio drivers? Perhaps there is corruption of sorts? I have not tried a custom ROM or radio or kernel…… I did take to a local tech. They looked at everything literally under a microscope and did not see any issues that way. I am in the USA and have a lgd820. Although we are quick to assume a hardware issue, I am wondering if there is some sort of incompatibility with the first run of N5 and lollipop….. who knows!
I’ve read all sorts of threads on the internet. It seems I am not the only one. We are very quick to assume it must be a bad motherboard, it just seems too coincidental to me!
Here is a collection of threads……
Within the N5 Sub
http://www.reddit.com/r/Nexus5/comments/2g0i3m/no_wifi_or_bluetooth/
http://www.reddit.com/r/Nexus5/comments/253y8d/my_nexus_wont_activate_wifi_and_bluetooth/
http://www.reddit.com/r/Nexus5/comments/2pur0v/wifi_stuck_on_turning_on_mac_and_ip_addresses/
http://www.reddit.com/r/Nexus5/comments/361ecw/help_wifi_and_bluetooth_stopped_working/
http://www.reddit.com/r/Nexus5/comments/2h4co7/wifi_wont_turn_on/
http://www.reddit.com/r/Nexus5/comments/2hpj2w/can_no_longer_connect_to_wifi_stuck_at_wifi/
http://www.reddit.com/r/Nexus5/comments/2wjk38/wifibluetooth_issues/
http://www.reddit.com/r/Nexus5/comments/2zboet/no_wifi_no_bluetooth_and_reboots_whenever_i_press/
Other Links
http://forum.xda-developers.com/google-nexus-5/help/wifi-stuck-t2721643
http://forum.xda-developers.com/google-nexus-5/help/bluetooth-t2733672
https://productforums.google.com/forum/#!topic/nexus/IJSOuc7gw0w;context-place=forum/nexus
https://productforums.google.com/fo...otification#!category-topic/nexus/1H6ZiIMYrtw
https://productforums.google.com/forum/#!topic/nexus/ke-OEPLbRSQ
https://productforums.google.com/fo...xus/lollipop|sort:relevance/nexus/NbO-AGvRCLk
http://code.google.com/p/android/issues/detail?id=80028
I found this, but not really sure it’s the same thing….. http://forum.xda-developers.com/showpost.php?p=52441901&postcount=47
Prodeje79 said:
I found this, but not really sure it’s the same thing….. http://forum.xda-developers.com/showpost.php?p=52441901&postcount=47
Click to expand...
Click to collapse
Hi,
This link was actually what i was going to suggest. It seems you've tried pretty much everything in the book except that.
I think its worth a try. Same as any other learning process, take your time and read the whole thing once or twice until you feel comfortable with the process. Then go for it.
Darn it, I should have downloaded those programs BEFORE rooting my phone again. Now I a struggloing to get my SIM card detected again to get data to DL them! whooops!
How would I go about attempting to read my files first to see if they are accessible and potentially write down my old MACs first?
EDIT: I found this but not sure how to get that working? I have Windows 7 and CMD prompt at this point. what program is that using?
https://www.reddit.com/r/Nexus5/comments/2j6vao/how_to_changefix_your_wifi_mac_address/
beekay201 said:
Hi,
This link was actually what i was going to suggest. It seems you've tried pretty much everything in the book except that.
I think its worth a try. Same as any other learning process, take your time and read the whole thing once or twice until you feel comfortable with the process. Then go for it.
Click to expand...
Click to collapse
OK, I went through those steps. everything appeared to go through correctly. Still no wifi nor bluetooth
EDIT: I rebooted a second time. WHen it first boot up, wifi was on and connected to my works AP. I quickly went in and snagged a screen shot of MAC address. Oddly enough, it did not match what I had input via hex editor. Within a few moments the wifi stopped working. It is back to the turning wifi on issue..... bluetooth still not working as well.
Very interesting.....
EDIT2: I get access denied when attempting to read either files within their corresponding folders under persist.
I was able to copy my stock files into my sdcard download folder and read them there without issue. Thus seeing my default addresses for both!
Perhaps it is normal, but I am never able to edit the old or new files under persist. I basically renamed original folders to bluetoothold and wifiold. I could delete them perhaps.
Note that I put my phone into airplane mode before doing anything noted in the steps.
Any other ideas? Given that it is showing my original MAC address the one time it worked, this makes me think that it is not reading the files .macaddr at all
I have the same problem. Funny thing is, the phone is just over 2 years old and the motherboard was replaced just 9 months ago (so, brand new one).
In my case, I received and Android update 2 days before I found the phone burning hot and restarting on it's own. Then the same chain of events you describe started to unleash. Now I can't be sure if this is software related, hardware related or both.
Can't seem to find a solution to the issue either.
Prodeje79 said:
I received an OTA Update in early to mid May. I am now forgetting which version I received at that time. ( I forget as I have done so many downgrades/upgrades/factory resets in my troubleshooting the last month!) Up until these issues, I've never rooted or flashed a ROM, or unlocked boot loader or anything. My N5 had always been completely stock.
First Issue
It all started with just the sim card. I get "no sim card" message, even though it was in there. This was my original SIM card and I had never ejected it since I bought it new. I found I could turn it off, pop it out and back in, and boot it again. Sometimes it will see the sim card again. It may take 20 times, but finally work.
I naturally got a new sim card, as well as confirmed said sim cards worked in other phones. My wifi and bluetooth were working fine at first. Working with google support, they recommended a factory reset to fix the sim card issue. Immediately after the factory reset, my bluetooth would no longer turn on nor show a MAC address. At this point, my wifi was fine.
Second Issue
In addition to the sim card slot issue, now my Bluetooth no longer works! Around this time, I received another OTA update, this time it was 5.1.1 LMY48B. I had hoped it would fix the issues, but no dice! I start reading up on the XDA forums as I am determined to start rolling back to see if this will fix anything. I unlocked the boot loaded, rooted, etc following the threads on XDA
Third Issue
I do all sorts of flashing to hammerhead-krt16m_4.4 to hammerhead-ktu84p_4.4.4 to hammerhead-lrx21o_5.0 to hammerhead-lmy48b_5.1.1 . On the final flash back to 5.1.1 my wifi now no longer works!!!!!!!!!!! It is stuck at wifi turning on and no MAC address shows. It also seems my cell data is very very slow now!
After many calls to google, I think I finally succeeded in getting a “ticket routed up”. My phone is from the play store around 10/31/2013. They keep pushing I am out of warranty. I attempt to ask for a refurb N5 without luck so far. I am not very confident anything will come from google. This being my only handset now, it is just not an option to send this to LG. My current state is my voice/txt and cell data are working. Data seems a little slow but usable. Wifi and bluetooth won't turn on. I also still have the sim car slot issue upon rebooting. After a bunch of reboots it will eventually see sim card.
What else can I try? Is there a better way to attempt to repair/reload my radio drivers? Perhaps there is corruption of sorts? I have not tried a custom ROM or radio or kernel…… I did take to a local tech. They looked at everything literally under a microscope and did not see any issues that way. I am in the USA and have a lgd820. Although we are quick to assume a hardware issue, I am wondering if there is some sort of incompatibility with the first run of N5 and lollipop….. who knows!
I’ve read all sorts of threads on the internet. It seems I am not the only one. We are very quick to assume it must be a bad motherboard, it just seems too coincidental to me!
Here is a collection of threads……
Within the N5 Sub
http://www.reddit.com/r/Nexus5/comments/2g0i3m/no_wifi_or_bluetooth/
http://www.reddit.com/r/Nexus5/comments/253y8d/my_nexus_wont_activate_wifi_and_bluetooth/
http://www.reddit.com/r/Nexus5/comments/2pur0v/wifi_stuck_on_turning_on_mac_and_ip_addresses/
http://www.reddit.com/r/Nexus5/comments/361ecw/help_wifi_and_bluetooth_stopped_working/
http://www.reddit.com/r/Nexus5/comments/2h4co7/wifi_wont_turn_on/
http://www.reddit.com/r/Nexus5/comments/2hpj2w/can_no_longer_connect_to_wifi_stuck_at_wifi/
http://www.reddit.com/r/Nexus5/comments/2wjk38/wifibluetooth_issues/
http://www.reddit.com/r/Nexus5/comments/2zboet/no_wifi_no_bluetooth_and_reboots_whenever_i_press/
Other Links
http://forum.xda-developers.com/google-nexus-5/help/wifi-stuck-t2721643
http://forum.xda-developers.com/google-nexus-5/help/bluetooth-t2733672
https://productforums.google.com/forum/#!topic/nexus/IJSOuc7gw0w;context-place=forum/nexus
https://productforums.google.com/fo...otification#!category-topic/nexus/1H6ZiIMYrtw
https://productforums.google.com/forum/#!topic/nexus/ke-OEPLbRSQ
https://productforums.google.com/fo...xus/lollipop|sort:relevance/nexus/NbO-AGvRCLk
http://code.google.com/p/android/issues/detail?id=80028
I found this, but not really sure it’s the same thing….. http://forum.xda-developers.com/showpost.php?p=52441901&postcount=47
Click to expand...
Click to collapse
+1
I'm facing the same issues and I tried all the possible steps I could find on internet trying to repair the problem.
Actually, since the latest updates I was encountering some issues with the WiFi only: not turning on either off and not showing properly the MAC addres. So I decided to factory reset, even SDcard and since yesterday I have tried all the possibile guide I found to internet to fix the MAC address not showing and the WiFi not turning on/off but nothing worked. I tried even to flash again the old factory images, such as KitKat, Lollipop, etc., to lock the bootloader again and to dismantle the phone in order to clean the motherboard, but nothing worked. Phone still gives me MAC address 02:00:00:00:00:00 alternatively with the correct one, I can't figure out on what it depends because sometime it seems to work: it shows the correct MAC, it connects to wifi network; suddenly it doesn't!
I'm really going crazy to understand what's wrong.
You'll have to dig up my final posts on this , but in a nutshell, send into LG for repair, select cheapest option they offer. Receive mint phone. My cost was $45 and about one month... I picked up a cheap $20 phone to get me by.
In other news.... I now have a 6p!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Renton91 said:
+1
I'm facing the same issues and I tried all the possible steps I could find on internet trying to repair the problem.
Actually, since the latest updates I was encountering some issues with the WiFi only: not turning on either off and not showing properly the MAC addres. So I decided to factory reset, even SDcard and since yesterday I have tried all the possibile guide I found to internet to fix the MAC address not showing and the WiFi not turning on/off but nothing worked. I tried even to flash again the old factory images, such as KitKat, Lollipop, etc., to lock the bootloader again and to dismantle the phone in order to clean the motherboard, but nothing worked. Phone still gives me MAC address 02:00:00:00:00:00 alternatively with the correct one, I can't figure out on what it depends because sometime it seems to work: it shows the correct MAC, it connects to wifi network; suddenly it doesn't!
I'm really going crazy to understand what's wrong.
Click to expand...
Click to collapse
I've had my Oneplus One since the beginning of 2015, up until now it's been honestly fantastic, with very few issues whatsoever, certainly nothing that has bothered me at any rate. That's up until last night;
My phone was lying on my desk next to me with the screen on updating some applications whilst I was writing on my computer - suddenly, it starts to vibrate, one continuous long note, I naturally picked it up and looked at it, at which point the phone turn itself off in my hand. That was unfortunately the last I ever saw of my phone alive. This happened at about 6PM yesterday evening, since then I've tried everything within my power to get it to work. I can't access the bootloader, in order to get to fastboot (which would allow me to fix all my issues by enabling me to refresh the device), nor can I access my recovery. The phone turns on and displays nothing, it vibrates, but that's it.
The phone was running the latest COS13.1.1 update (X1) which I had flashed the day before, it was running the stock kernel for the ROM, the ROM was however rooted.
I know a fair amount about android, I also know a fair amount about the OPO, to me, I think something about the LOGO partition has gone wrong. The LOHO partition being responsible for the images shown in the bootloader, fastboot, splash screen etc.... I'm just not sure how that would have happened.
Either way, I don't know what to do, the one doesn't register to my computer in fastboot or adb , so both those routes seem closed. I primarily use a Mac for my work, I'm yet to try plugging the phone into a PC.
I've submitted a ticket to OP, and have spoken to an adviser who moved my case to a 'specialist', but I'm yet to hear back on that one.
Any help would be massively useful, because I need this phone for my work, and just general communication.
Thanks for reading,
Ben
Here, try this http://http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732