Random WiFi-MAC Address Changes on Reboot - Nexus 5 Q&A, Help & Troubleshooting

Well hi folks...
from today on - made no changes to my rooted nexus5 with graviton n5 1.1, which worked without any problems from the day I got it - it keeps changing the WiFi-mac-address after rebooting. (first 3 octets stay the same, last 3 octets change randomly, see attachment)
The issue seems to be well known on some other devices, but obviously I´m the first one experiencing this on the Nexus5.
Anyone else having this problem and maybe got a solution for ? It´s pretty annoying to have lots of entries on my wlan-router, also persistent ip assingning is not possible any more.
Things I tried already to fix the problem:
- installed different custom (bricked and franco) and stock kernels
- wiping dalvic/cache
- restored EFS-Backup made on the second day I got the phone
- reverted back to full stock without root / unlocked bootloader
Any help / tips / tricks to get things fixed would be highly appreciated ...

This seems to be a nexus thing, but not everyone's phone does this. There is a fix for it (I applied it to my galaxy nexus) but I'll have to get hone before I can find the instructions...it requires some hex editing
Sent from my Nexus 5 using Tapatalk

Nobody any useable information regarding this problem?

Experiencing the same. Except for when I restore stock it returns to its original. So weird, maybe has something to with restoring a twrp backup checking Vendor partition?

Related

[Q] Question after rooting

I flashed clockworkmod and rooted a few days ago and all has gone well. I'm a bit concerned as I don't have the problem described when rebooting and losing the custom recovery - it doesn't get overwritten as it should do (I have rebooted many times now). Also I don't appear to have the file "install-recovery.sh" on my system (I have searched/browsed using root explorer).
Obviously this has been no problem to me but I would like get get an idea as to why I seem to be immune from what most others experience and is there any potential problem that anyone can forsee (like if i ever need to restore the default recovery). Any suggestions would be appreciated.

[Completed] [Q] ROM defaults to wrong country/language

Hello all.
I've searched these forums for a bit now, looking for someone in a similar situation; after around 10 pages of 'wrong country' and a loooot of Googling, I can't seem to identify the issue I'm having.
The problem is as follows: I own a Galaxy Express 2 (a rather unpopular device judging by what I've seen across the Interwebs). It came with a stock 4.2.2 ROM when I bought it some time ago. It was rooted within a couple of days - no problems whatsoever. Then the 4.4.2 update came out and I downloaded and subsequently flashed (via ODIN) the one for Vodafone Spain (as it was the only currently available ROM that was Kit Kat). I had noticed a few problems: certain items like LED flashing as notification in Accesibility settings were missing, others didn't work (Smart stay, tap to answer). Not really a problem, but it did raise a red flag. No other problems with the ROM itself, it was very stable.
Attempting to correct this issue, I had flashed 4.4.2 meant for Vodafone Romania (the carrier for where I live seemed the most obvious choice, I was hoping the aforementioned settings might work). They still did not. A few days ago, I got a rather annoying problem where Play Store would crash every single time it attempted to update any app. Naturally, I googled a few fixes, tried those, nothing worked. I had pondered flashing a recent Google Apps pack (like the ones you'd get when flashing CM), but was unsure if I'd do more damage - figured they might not play well if flashed forcefully over the pre-existing stock apps.
I then flashed CM (the release available for Galaxy Express 2, just out of curiosity, and Google Play worked flawlessly, even when updated to the latest version).
TL;DR: Stock 4.2.2 -> Stock 4.4.2 (Spain) (first language appeared as spanish) -> Stock 4.4.2 (Romania) (first language appeared as croatian) -> CM build currently out for Express 2 -> Emergency recovery via KIES 3 flashed another 4.4.2 it seems (but also loaded in Croatian)
The issues I'm currently having:
1) Ever since the Romania Vodafone 4.4.2 install (that would be the second stock ROM I've flashed), the first language I encounter is Croatian and it installs typical bloatware in another language (which I would also imagine would lead me to download incorrect applications from the Market, so I figure if I fix the phone's localization problem, the market will follow)
2) Ghost tapping on the keyboard (not noticed before, was not present on CM, hence I've ruled out a hardware issue, or on any installation previous to CM)
I have tried various fixes: via CWM recovery, tried wiping data/cache/dalvik, formatting /system and /boot before flashing a 4.4.2 for Romania (still loaded in Croatian), via ODIN. I'm fairly certain there's something residual I've mucked up on my phone, because the device identification when I connect it to my laptop via USB is from the previous install (now it has a different name).
IMEI number is fine (read about potential corruption of EFS). Currently, I was going to attempt flashing the stock ROM (4.2.2) from Sammobile, but after so many attempts (and hairs pulled out), I'm not holding out hope that that will fix it.
CSC is fine (correctly identified as CNX, which is the appropriate code for Vodafone, Romania), as confirmed by connecting to KIES.
Eventually, I would like to have 4.4.2 on it, if at all possible. I have a basic understanding of these things - but I can't understand why the phone would be fooled into thinking it's in another country. My assumption is that such information is stored somewhere that isn't wiped between flashing.
Really clueless at the mo'. I wanna try flashing stock, but I fear doing so will fix nothing, and my last hair will fall out - I feel that the problem would affect all installations.
(I wouldn't mind using CM, but it's a big buggy, and I need stability above all else).
It does in fact seem that my problem lies in the CSC. Samsung Kies, being what it is, seems to have incorrectly indicated where I am.
An appstore app has identified my CSC as being VIP (which is one from Croatia). I will attempt to correct this issue via whatever method I can find, and see what happens.
Update: As it happens, I've successfully flashed stock ROM (4.2.2), corrected CSC (and verified it with root explorer, to confirm it's the right one), flashed 4.4.2, it installed all the proper Vodafone apps (in English).
However the odd ghost tapping problem remains: even when holding my finger on the touchscreen, it behaves as if I were tapped eratically everywhere near the original tapping point.
The device name is still read as incorrect when plugged into USB. I am certain this is software related now, or rather, some freakin' leftovers I can't seem to find and clean.
Hi,
This is from the S4 section, so don't use any files from here, but the advice may help perhaps..
http://forum.xda-developers.com/showthread.php?t=2611340
Other than that, I can't find anything relevant on XDA for your device. It could be hardware if flashing stock firmware didn't help. You can ask about it here if you wish,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!

[Q] Issues after restoring 05Q Backup (calls.. dirty system?)

Well, Hello.
Yesterday, I decided to re-get myself into rom flashing, as I was sick about oneplus usual delays about lollipop.
After I flashed cleanly first blisspop, and then switched to paranoid, I was not surprised about battery drain so I decided to comet-back stock by flashing the backup I've already made before all of this.
Now I have really enough about custom roms and bad battery-life, on this part imho stock has been better for me than whatever.
Globally no problems, but one annoying : call/dialer on the cm stock app.
The app/contacts works great, it is just that when I have finished to type the number and press the call icon, then black screen, the hardware buttons are active but when pressing back or whatever it doesn't respond..
Calls are working because I hear the voice but so can't stop it.
I was blocked on this screen, so recovery and reboot each time, pretty annoying.
Here would you think that a flashable zip file of the stock app would end the problem ?
Does I have to wait for the next ota to resolve this, or do I have to re-flash the 05Q ?
I tried first some alternative call app, like exdialer etc but it does nothing..
Ideas ?
I think this is solvable..
+ When editing the local user profile (top-left corner status bar) it is not working properly, the picture doesn't want to change as editing accounts etc..
→
To sum up,
I think that I will have to do again a clean stock-rom flash process,
Can I refer myself to these threads ?
1° : [GUIDE] Return your OPO to 100% Stock (Current Build - XNPH05Q)
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
2°: [GUIDE] Identifying and Fixing Corrupted Partitions
http://forum.xda-developers.com/oneplus-one/general/guide-identifying-fixing-corrupted-t2993500
I don't know what's broken in my system, so don't really know what to do for now,
to my mind it would be logic to re-install the stock system properly, so..
Thank you by advance, and waiting for your answers.

Random Reboot on Lollipop 5.1

Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
The_Wolf91 said:
Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
Click to expand...
Click to collapse
Flashed Android 5.0.1 and no random reboots (as I also said when i wrote my first post).
I don't know if the "question" is clear, but can you help me reading the "last_kmsg" which I attached in first post? Thanks
Same exact thing happening to me also.
Sent from my Nexus 5 using XDA Free mobile app
The same is happening to me. And it looks like a hardware problem cuz when the phone reboots it keeping reboot until I keep pressing the power button while boots.
I have a bad experience about it. In my Nexus S when updates to Jelly Bean the same occurs until phone suddenly die. (I live in Brazil so, guess what? I have now a wonderful paper weight)
No luck with 5.1.1
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Try another (custom) kernel.
beekay201 said:
Try another (custom) kernel.
Click to expand...
Click to collapse
I just flashed ElementalX kernel but no luck, random reboot happened on 5.1.1 too. By the way it was quite obvious because it happened already on 5.1 Google's factory image (stock kernel so)..
I have exactly the same issue with nexus 5 since upgrading to 5.1.0.
I went back to 5.0.1, which solved it for a few days, but now this happens with 5.0.1 as well.
also, before random reboots happen, the power button becomes extra sensitive, so one keypress causes the screen to turn on and off again, or to display the shutdown menu.
this does not happen when the phone is stable.
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Sent from my Nexus 5 using XDA Free mobile app
noob424 said:
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Click to expand...
Click to collapse
Same here.
LG Nexus 5 - Lollipop 5.1.1 LMY48B
Unlocked bootloader;
Rooted;
ClockWorkmod 6.0.4.5 (not flashed - just boot on image when used);
Wipe factory reset (in cwm). Flashed 5.1.1 image files (boot, radio, bootloader, system and cache).
Random reboots, and sometimes with apps optimizing.
I have the same problem with N5 since upgrading to 5.1.1 - never had any problems before. Doing it several times an hour now. Trying a cache clean next, after I wait for the optimising apps to finish yet again!
Hi all,
I had the same problem. Everything stock, up to datę, no root. Phone was rebooting itself several times in a row.
Right now it seems that problem dissapeared. Reboots in my case was caused probably by application Autoguard Dash Cam Blackbox. After removal no reboots for 2 months and no memory leak.
cleared cache and it happened again within a minute...
Does seem to be linked to the power button
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
simbapenn said:
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
Click to expand...
Click to collapse
I have N5 kit kat 4.4.2 in Chrome watching videos randoms reboot its happens
This is happening to my fiance's N5. It happens when she's using it and also when it's not being used. When it reboots, it optimizes the apps and says the battery is at 0 when it was a full charge. Only way to turn it back on is to connect it to a charger. Frustrating.
FYI the update to 6.0 did not solve the restart problem. It's either hardware related, app related or a bug that's still in the OS.
I'm selling my Nexus because of this, has been happening for a few months now.
It's not software related, it has to do with the actual power button. Some people had success changing it out, soldering it etc., but I don't have that time or knowledge.
Google wouldn't help, as I'm out of warranty. So I guess it's goodbye Nexus. Really unfortunate given that the phone works fine, it's just a quality issue.. will have to re-evaluate buying another Nexus in the future.
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
---------- Post added at 04:41 PM ---------- Previous post was at 04:20 PM ----------
I have been using this awesome app on my nexus 5, just so I don't have to use the power button here is the play store link.
https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree
maccboy2010 said:
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
Click to expand...
Click to collapse
Confirmed the update will NOT fix this issue.

Hardware issue G955F ?

Hi,
I have repeatedly weird issues with my phone. Both on stock rom as well as on custom rom (Renovate ICE) i get permanently apps crashing and the phone rebooting /crashing very often. Its mostly unuseable.
I also had issues in reflashing stock in the first place, as described here: https://forum.xda-developers.com/galaxy-s8+/help/reflash-stock-fails-mismattached-t3754609 it took many attempts.
Today I wanted to give it a new try flashing the newest Renovate ICE version and now after using Aroma installer (which in the first run threw an error also, only the 2nd run workd) the phone is again not booting at all but stuck on initial logo.
I am feeling this must be a hardware issue. Is there any means to test this (e.g. memory failure, or something similar) ? Any experiences like that by anyone?
Im not sure if I can try to return the phone (it is just a few weeks old) given that i flashed custom firmware. Recent Renovate ROM claims it would Reset Knox to 0x0 but since it does not even boot Im not sure about that either.
Any suggestions?
Thanks

Categories

Resources