Hi guys,
I have Tmobile LG V10 H90120j which its Wifi MAC address changes on every reboot.
Long story:
It was originally Lollipop, I updated to stock MM v20e then v20j. It was still OK after that.
Then I tried to root it using tungkick's method. However, the bad luck began, I forgot to change the Process to Upgrade instead of Refurbish when upgrading the TOT file. The phone bootloop to TWRP after that. Big thanks to @tungkick, he helped recover it.
I realized that from then the Wifi MAC address keeps changing on every reboot. The phone also cannot automatically get APNs from provider (I have to manually add them).
The really bad problem is the MAC issue. Only registered devices can connect to my home and my company Wifi networks. I can temporarily workaround by manually changing MAC address on rooted ROM after every reboot, but it's not an actual fix.
Factory Reset or Restoring to stock v20j can't help.
I did some search and found that some others also had the issue. Some said this method also can fix it: youtube . com /watch?v=8ejnFB5i5o8
But I can't see any nvram folder in my device.
Anyone has any ideas about fixing this, please help
Thanks.
anyone?
I have this with the T-mobile LG G5 H830 that is rooted on 20j (Nougat) with the dm-verity patch applied as well. I have 7 days left to return the phone). I also cannot find the nvram file/folder on my device (I am searching my LG G Pad 8.0 X to see where it is at via Root Explorer).
You mentioned you went back to stock (in TWRP, did you format the system and data directories and wipe the caches before; I ask because if you did not, I was going to do that, then re-stock).
My only other guess is the bootloader unlock would cause it (but then my LG G Pad 8.0 X is bootloader unlocked and doesn't do this). There was a CM7MAC.zip file (which I know is supposed to be for CM rom but I wonder if that fix would work for us).
uglyhoodlum said:
Hi guys,
I have Tmobile LG V10 H90120j which its Wifi MAC address changes on every reboot.
Long story:
It was originally Lollipop, I updated to stock MM v20e then v20j. It was still OK after that.
Then I tried to root it using tungkick's method. However, the bad luck began, I forgot to change the Process to Upgrade instead of Refurbish when upgrading the TOT file. The phone bootloop to TWRP after that. Big thanks to @tungkick, he helped recover it.
I realized that from then the Wifi MAC address keeps changing on every reboot. The phone also cannot automatically get APNs from provider (I have to manually add them).
The really bad problem is the MAC issue. Only registered devices can connect to my home and my company Wifi networks. I can temporarily workaround by manually changing MAC address on rooted ROM after every reboot, but it's not an actual fix.
Factory Reset or Restoring to stock v20j can't help.
I did some search and found that some others also had the issue. Some said this method also can fix it: youtube . com /watch?v=8ejnFB5i5o8
But I can't see any nvram folder in my device.
Anyone has any ideas about fixing this, please help
Thanks.
Click to expand...
Click to collapse
crazyut said:
I have this with the T-mobile LG G5 H830 that is rooted on 20j (Nougat) with the dm-verity patch applied as well. I have 7 days left to return the phone). I also cannot find the nvram file/folder on my device (I am searching my LG G Pad 8.0 X to see where it is at via Root Explorer).
You mentioned you went back to stock (in TWRP, did you format the system and data directories and wipe the caches before; I ask because if you did not, I was going to do that, then re-stock).
My only other guess is the bootloader unlock would cause it (but then my LG G Pad 8.0 X is bootloader unlocked and doesn't do this). There was a CM7MAC.zip file (which I know is supposed to be for CM rom but I wonder if that fix would work for us).
Click to expand...
Click to collapse
Been months, I cannot recovery my memory well. But I might not format the system and wipe the caches in TWRP before going back to stock. Still having the issue, and applying workaround after every reboot .
Bootloader unlock is unlikely the cause, cuz I rooted another H90120j (my cousin's) after that. I followed strictly the guide and made no mistake. The phone's still working well now.
Well I think you can give it a try. Looking forward to your good news
My 13th day is Saturday so I am going to get T-mobile to exchange it for a new one (since about 1/2 the posts on this topic says it's a hardware problem with certain chipset mac addresses and I hope that batch of phones that WA gets is different than the batch that HI gets) and reboot that several times before I leave.
I only found out I had this problem since Shaw Cable use MAC address for the 10 devices include in the Shaw Go wifi (wifi public hot spots) and when I put the original address in while still in HI, then got back to Calgary (after a couple of reboots had occurred during my trip) noticing Shaw would not auto-connect like it does on the other devices which are all rooted and sim unlocked (LG G Pad 8.0 X, Samsung Galaxy Note Edge, Moto X Play).
If not for Shaw, I would have been none the wiser until I got an employer that only used MAC address and by then, I'd be stuck with the phone.
I notice that this problem allegedly was based on a chipset and/or the Android software itself (there doesn't seem to be a consenus one direction or the other) when I googled this (and subsequently found your post on XDA). I have had several generations of Samsung Galaxy S and Note Series as well as Moto Triump (Sprint), the LG G Pad X, and Moto X Play and have never seen this phenomenon.
Since you say your cousins device is working well and you did the same thing with it as with yours, I suspect it's a hardware fault in our devices. I already returned a V20 to Freedom/WIND since that bootloader is locked and no root possible (will try to get T-mobile to give me the V20 instead of the G5 since I have to go through all this drama; the Freedom V20 was rebooted more than 7 times on purpose and no mac address change occurred).
uglyhoodlum said:
Been months, I cannot recovery my memory well. But I might not format the system and wipe the caches in TWRP before going back to stock. Still having the issue, and applying workaround after every reboot .
Bootloader unlock is unlikely the cause, cuz I rooted another H90120j (my cousin's) after that. I followed strictly the guide and made no mistake. The phone's still working well now.
Well I think you can give it a try. Looking forward to your good news
Click to expand...
Click to collapse
Related
Phone Details
Model:
Sharp-ADS1 (FX Plus)
Android Version:
2.2.2
Basband Version
M76XXTSNCJNLYA6050_ATA_MC50.00
Kernel Version
2.6.32.9-perf
Software Version
AT8A_MC50.00
Hardware Version
AT8A_TSPFW_V16
Okay. I got this phone off amazon as an unlocked phone. I has been working fine for several months, but it is short on internal memory because the internal memory it is almost completely consumed by bloatware. I rooted it using Super One Click 2.2 so I could delete some bloatware. After rooting I could not connect to my wifi (which I always have been able to connect to with this phone without issue). All I get is "Acquiring IP Address". Here is what I have tried so far that has not worked.
1. Factory Reset (4 times).
2. Master Hard Reset with wipe.
3. Router reboot and unplugging it.
4. Clearing Router mac address table.
5. Unrooting phone and factory reset.
6. Custom "ADD WIFI Network"
7. Using "Static IP" workaround.
8. Changed Router SSID and network security to OPEN (no security).
None of the above have worked. I think I know what might have caused the problem. I performed the root with the Super One Click app. During the rooting process it came up and said, "Busybox not installed. Would you like to install it." I figured it was needed for rooting so I let it install Busybox. After doing some searching on connection issues after rooting, I found other people blaming busybox for the problem. I have no idea what Busybox is or if it is the cause. I assumed that if I did a master hard reset that it would fix the phone, but it remained rooted even after the master hard reset, which tells me that some of the things that rooting the phone did cannot be undone by a master hard reset. I used Super One Click to unroot the phone, but the problem still persist.
I believe the only way to fix this problem is to flash the phone with the original rom (or other good rom). I need a walk through on how to do this and a source for the rom. Can anyone help me? Thanks
I have the tmobile version after flashing the security patch rom my wifi has stopped working as well as bluetooth searched for related problems and came up short.... possibly looking for a backup of persist/prima folders any help would be appreciated
Can anyone send me a copy of etc/firmware/wlan/prima
I'm having the same problem.
I have two nearly-identical LG K7 on T-Mobile and one is connecting to Wifi and bluetooth while the other is not.
I coped the etc/firmware/wlan/prima folder from one to the other but that did nothing. I'm curious as to whether you've got a resolution or not.
For anyone interested, I got a reply via PM. Use LG up and the version j .kdz. This will complete factory reset, including recovery partition, so... you know... back up.
Hi, I have been following this forum for a long time but I had never logged on. I commented my problem, although I saw several threads that deal with the subject, I did not see any updated or that I clarify the doubts well.
I'm from Argentina and buy aliexpress LG V10 H900, refurbish, came with Android 5.1. Seeing through several forums I saw that ATyT released an official update to 6.0 Marshmallow, to update via LGUP (via OTA I did not get to be outside the USA). I did not have problems to flash it, but when I started to test the functions, I found that the fingerprint reader does not work, it does not let me directly enter the settings. LG VPN error when starting, does not allow me to uninstall preinstalled apps (restarts the cellphone), among other errors.
Then I found out that you can not go back to Android 5.1, nor is there another ROM to try. I made a complete wipe from the cel options after the update. When I wanted to start from recovery I could never, try with all the key combinations and I could never, it is as if I did not have recovery ... Nothing work for me.
Sorry if the post was long, I hope to solve it and give me their experiences and opinions. Thanks and greetings to the community
So I'm not sure what I did because it's been a while since I messed around with this phone (bought a Honor 8 Pro after that), but I most likely flashed something wrong. So the first weird thing is that apparently my device went from "griffin" to "sheridan", not sure how that's possible. The second thing is that when I flash a stock ROM, I have no wifi (it doesn't detect any network) and in settings it says my IP Address is unavailable. I tried nearly everything. Resetting WiFi settings, rebooting, reflashing stock ROM etc. Nothing seems to work. Help please?
My phone says sheridan too when i boot in bootloader mode. Anyone know whats os this?
jericho246 said:
So I'm not sure what I did because it's been a while since I messed around with this phone (bought a Honor 8 Pro after that), but I most likely flashed something wrong. So the first weird thing is that apparently my device went from "griffin" to "sheridan", not sure how that's possible. The second thing is that when I flash a stock ROM, I have no wifi (it doesn't detect any network) and in settings it says my IP Address is unavailable. I tried nearly everything. Resetting WiFi settings, rebooting, reflashing stock ROM etc. Nothing seems to work. Help please?
Click to expand...
Click to collapse
Most likely you have flashed incorrect firmware. But this problem is common even with locked/stock devices, possibly could get fixed in the next update. The problem is that there is no way to downgrade firmware (otherwise this can be fixed by flashing 7.0 stock rom including firmware)
Downgrading the Firmware isnt a problem. Downgrading the bootloader and gpt isn't possible. Anyhow, my wifi and BT are broken too and going down to 7.0 and than installing all OTAs won't fix my issue.
Hey all,
My phone updated today and ever since I cannot move past the initial lock screen. When unlocked, the UI appears to crash and send me back to the lock screen. My pin code works for turning the phone off, restarting the phone and putting it into emergency mode, which indicates some sort of UI crash.
Because this is a new account I can't post a link to a video of the issue directly, but the YouTube video code is: 8ZhlH-Tt-NU
I have tried the standard fixes like wiping the cache partition and booting into safe mode, but these don't seem to make any difference. Unfortunately I never logged into my Samsung account on this device, so their 'Find My Mobile' service is not an option. I am however signed into my Google account on the device and it does have wifi/network enabled.
The phone is running PPR1.180610.011/G965FXXU2CSA8
On the phones internal memory is a bunch of photos from a recent trip to Japan, I'm a fool for not backing these up sooner but I would hate to lose them.
Has anybody experienced anything like this before, and is there any way for me to get back into the phone, or atleast recover the photos that I took?
Thanks!
Edit:
One potential route out of this I can see is sideloading the same or a subsequent OTA update using ADB to hopefully fix the issue. Unfortunately despite some digging I can't find any updates that will allow installation from: PPR1.180610.011/G965FXXU2CSA8
If anybody has any information on this specific firmware version (Is it beta 3? beta 4? ect.), its installation path and where files relating to it may be listed/hosted it would be appreciated. Also how disasterous would it be to take a mismatched OTA upgrade and modify the metadata to allow it to be sideloaded onto the phone? I assume this would almost certainly break the OS completely but I'm not too sure.
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
profi_fahrer said:
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
Click to expand...
Click to collapse
Thanks for the reply Profi I had no idea using HOME_CSC would retain user data. I have tried flashing a few different versions of Pie (wish HOME_CSC) using Odin but with no luck, every time the phone boots I have the same problem. Do you know if there is a sure way to downgrade to Oreo while retaining user data? I have seen a few posts of people attemping this and getting stuck in bootloops, eventually requrining them to factory reset.
To give a final update on this. I attempted the Oreo downgrade, upon reboot the phone was stuck in a bootloop so I updated to Pie again. When the phone booted I tried the pin code as quickly as I could, and after some glitchy graphics on the screen it unlocked. From here I turn on the stay awake while plugged in feature in the developer options and managed to transfer all my data over to PC.
I don't believe it was the firmware changes that actually made any difference, because any further attempts to put my pin in, to remove the pin code for example, failed and cause the same crashing behaviour.
All data is recovered, I have factory reset the phone and all appears to be behaving as normal again. If anybody stumbles upon this with the same issue, all hope is not lost, but unfortunately I was unable to determine a realiable way to overcome it. It seems in this case it was just dumb luck.
Thanks for the assistance.