I'm at a loss here as I've never seen this problem before. Initial research didn't offer much help. I'm still researching, though.
All of a sudden, my unlocked A2017U began randomly generating a mac address every time wifi is toggled on. I have never seen this before. I thought it was the rom and installed a few others. Same thing. I reflashed the B19 bootstack, formatted data, among other things, in an effort to get this to stop. No dice. I get a new mac every time wifi is enabled.
I dread returning the phone to stock and starting all over to get to a modified state. This is a pain in the butt as I use mac filtering for wifi clients. Anyone experience this before? Any ideas?
Edit: Now I'm really confused. I used DrakenFX's B32 files to flash stock. Once set up, I tested wifi. I got a legit MAC and it remained static through toggling. I then wiped and flashed a custom rom and the random mac problem returned. I don't get it. The random MAC's always begin with 00:d0:d0.
Edit 2: Phew! That was pissing me off! I narrowed it down to both EAS enabled ROM's. The problem began with one, and persisted on a clean install of the other. I eventually restored AEX and I got the same, legit MAC as on stock. Problem solved. I'm just no sure why the other two ROM's were causing the problem to begin with.
Related
Hi folks.
So after a sleepless night and a lot of guessing and clicking around with no luck, I finally decided to ask for help.
The story:
Yesterday, I decided to open up my lovely N4 to perform the thermal pad mod (that can be found on these forums), as it was going really hot around the CPU at time and it seemed like a good solution.
Now, I'm no stranger to disassembling microelectronics without breaking them (few weeks ago, I successfully resoldered a broken power button in my old T989 that I've been using before N4).
What couldn't let me sleep at night:
And here is where the problem emerged. After re-assembling my sweet little phone (yes, i did it perfectly right), I tried to boot up and all i could see was an endless and really annoying bootloop, but as the device booted up, I did not worry much. While doing some research, I read that there's people experiencing bootloops with 4.3, so I thought that after disconnecting the battery, it just might've had happened on its own (I was using stock 4.3 with faux kernel before the nightmare started)
At this point, I booted into recovery and tried to flash the rom over, but unfortunately nothing positive happened. Then I tried factory reset and flashing different roms, also with no luck. This is when things started to get really frustrating, as no matter what I flashed, the bootloop was (and is) still there. But then I tries to restore a backup that I did right after getting my N4, back in November, and it WORKED. Why do i still have a problem then? Because it was 4.1 and OTA was giving me error every time I wanted to flash the update, so I kept flashing till i get some results. And then one of the N4 toolkits wiped my entire internal memory and I ended up with only being able to use sideload. Then I tried ALL of the N4 toolkits that can be found in here, to wipe everything and bring my phone back to everything stock, but the bootloader is locked so it cant do it, and it cant unlock it because I cant boot into the system.
Conclusion:
The phone works fine, and it proved it. But no matter what I try to flash (other than the old backup), the persistent bootloop is still there smiling at me like an a****le.
Any ideas?
So as of today, the WiFi on my family's Nexus 7 tablet no longer wants to enable. Upon doing a factory reset, we found we could no longer get past the "Select a network" screen. It just got stuck on the message "Turning on wifi". There was no skip button as there would be usually and nothing else could be pressed. I suspect a hardware issue, because I've tried many solutions and the closest I've come is just making the device work again. It was unrooted at the time of the issue. When recovery was accessed we were met with a "No command" message.
So the first thing I did was get to work on re-flashing the device. I started back with the original OS from Google's stock ROMs. Fastboot worked great, but I was still facing the same problem on first run of the device. The wifi simply would not enable. After this, however, the recovery menu seemed to have fixed itself. Through this I did a reset process as well...with no results.
The last thing I tried, which restored basic functionality to the device, was installing the Paranoid Android custom ROM. At this point, you could access regular apps and other things. I reinstalled the Gapps and the device was back to normal, with the exception of the wifi. The wifi is a big reason we use the tablet. It would be preferable to find a fix, as we would rather not have to replace something that only has one problem.
As of now, the device is rooted, with superuser on Paranoid Android 4.4.2.
Anyways, I really hope there's a solution to this. It's a great tablet.
I've been getting reboots semi randomly for the last week or two and I was wondering if I could get some help on trying to figure out why.
Going back two weeks ago I was having some pretty poor battery life compared to some other users so I tried to do a full purge and restart. I went through the file manager on twrp and deleted any folder for any app that I wasn't using in a possibly misguided attempt to curb any file conflicts. After I did this I did a fresh install of cataclysm and Franco. After running into some reboots I tried with Kylo kernel and had the same issue. I then tried full wipe with Ubermallow and Kylo and had the same issue. Then I did a full lock, unlock, flash stock, root and recovery, and fresh install of chroma and Franco aaaaaand it still reboots.
I've had reboots randomly while listening to music but only 3-5 of them and in every install I've done I've had the same two apps do it. Starbucks app will reboot when using auto fill to log in, either through swiftkey or last pass, and Lyft will reboot the phone seemingly randomly.
What I want to know is whether or not this could be a hardware issue and if not how to get this to stop or if anyone else has had the same issue. It's seems so random yet specific and it's happened on so many different installs that I have no idea. I have been rooting my phones since the OG Droid so I have a pretty good idea of what I'm doing but I have never had an issue like this that lasts through so many installs of so many different things.
Info
Gil Smash said:
I've been getting reboots semi randomly for the last week or two and I was wondering if I could get some help on trying to figure out why.
Going back two weeks ago I was having some pretty poor battery life compared to some other users so I tried to do a full purge and restart. I went through the file manager on twrp and deleted any folder for any app that I wasn't using in a possibly misguided attempt to curb any file conflicts. After I did this I did a fresh install of cataclysm and Franco. After running into some reboots I tried with Kylo kernel and had the same issue. I then tried full wipe with Ubermallow and Kylo and had the same issue. Then I did a full lock, unlock, flash stock, root and recovery, and fresh install of chroma and Franco aaaaaand it still reboots.
I've had reboots randomly while listening to music but only 3-5 of them and in every install I've done I've had the same two apps do it. Starbucks app will reboot when using auto fill to log in, either through swiftkey or last pass, and Lyft will reboot the phone seemingly randomly.
What I want to know is whether or not this could be a hardware issue and if not how to get this to stop or if anyone else has had the same issue. It's seems so random yet specific and it's happened on so many different installs that I have no idea. I have been rooting my phones since the OG Droid so I have a pretty good idea of what I'm doing but I have never had an issue like this that lasts through so many installs of so many different things.
Click to expand...
Click to collapse
What about complete stock ROM (official firmware + kernel)? OR CyanogenMOD?
If your phone fine with stock or CM so it s the ROM/Kernel bug u installed and need to report to its developer
:good:
Hey everyone. I got my replacement N6P in the mail today, and I am needing some advice. I went through the typical setup for it. Bootloader unlock, decrypt, root, etcetc. However, I am running into an issue where I cannot copy anything from my computer to the device. I am getting an error that states "The device has either stopped responding or has been disconnected." I dug around XDA a bit and found a bunch of possibilities, but none of them resolved my issue. I have tried just about everything I can think of except for reflashing to stock and starting again. I am hoping it is an easy fix, but I think a reflash may be needed. Has anyone else seen this before, and does anyone have any ideas for me to try?
EDIT: I have done literally everything I can think of, including flashing back to stock. Tried machines running Windows 10, 7, and Ubuntu. Tried three different cables. Absolutely nothing is working. However, I can push and pull files fine. No clue what is causing this.
EDIT2: It has something to do with MTP. Certain filetypes transfer without any issues, but most do not. I can get around this by changing the extension of the file before sending it over, then changing it afterwards. My previous N6P never had this issue. Is there anything that I can do to resolve this, or am I stuck with network transfers and renaming junk?
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
OmegaFighter said:
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
Click to expand...
Click to collapse
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Choose an username... said:
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Click to expand...
Click to collapse
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
OmegaFighter said:
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
Click to expand...
Click to collapse
good