MAC changing on mtc20k - Nexus 5X Q&A, Help & Troubleshooting

Hello, I have crashed my mac on cm 13. And can't recover it. I have it but can't change my phone's mac. Now it's 00:aa:00:bb:00:c2 and can't be changed. I tried nmac but it doesn't work. Maybe you have some experience in this?

Now migrate to the Pixel ROM and nothing changed. Maybe somebody know how to edit efs partition?
In the wlanmac.bin changed all 4 to my old mac, this changed it to other static mac but not my.

Related

How do I back up like this???

Running WM5, I want to change files in the Windows directory and when I dump to SD, I want the changed files to remain so that when I reflash the ROM from the SD the changed files are of course there.
Is it possible to do this? I realize that the current ROM-SD dump software works by starting from a certain memory address and that files that I change are going to be stored by the device at a different address and that address may not be included in the current d2s commands known.
Anyone have a clue how to do this? I'm guessing the key is actually unlocking the ROM so that files can be simply removed and so forth like what we can do with our ExtROM's. How do I do this?
Thanks!
Anyone? Please?
There has to be an app by now for gaining access to the ROM chip and changing files like we do with the ExtROM!!!

[Q] WLAN not working after Nandroid restore on another S3

Hi,
i tried to restore a Nandroid Backup into another Galaxy S3, ROM and Baseband Version is the same.
After Restore everything is fine except WLAN, i can see accesspoints and also can enter the psw but it will not propperly connect to the ap it tells me authentication failure but the psw is correct and it will also not connect to an open accesspoint, something must be messed up with the wlan.
Can anyone help? Else i will use my old way over Titanium Backup but this is more time intensive.
Greetz X23
Anyone? I have exactly the same problem after doing a nandroid restore on my replaced S3. How do I fix this without having to do a factory reset?
Fixed the "Authentication error occurred" problem
I finally solved the problem after trial and error. I found that it was a file called .cid.info in /data that I needed to delete. My WiFi now works again.
vpwrf said:
I finally solved the problem after trial and error. I found that it was a file called .cid.info in /data that I needed to delete. My WiFi now works again.
Click to expand...
Click to collapse
Hi. I just registered cause I am trying to resolve this exact issue.
My situation: Cracked my screen on my I9300 (still working and yes, not the t-mobile version but international) and got a brand new replacement phone (exact same model) so I can get my old one repaired.
Did a NANDROID restore and copied internal SD card content (external SD card was simply physically swapped). Everything seems fine, but WiFi is not connecting to any router (famous "authentication error occurred - incorrect password" message).
Flashing a newer version of my ROM (Android Revolution HD, currently on 20.0, flashing 29.0 on my new phone) works fine, WiFi working as it should. So it is not a hardware issue.
So my question really is (as I simply want to "clone" the software layer of my phone until Android Revolution HD for 4.3 is released):
What else did you modify/change/delete to get this to work? Simply deleting .cid.info after restoring from NANDROID did not resolve the issue.
Any hints are highly appreciated. Been playing around with it for a week now (on and off) but cannot resolve the WiFi issue. Checked several forums and googled like a lot, but without any success. What am I not getting?
I am fairly new to Android (6 months), sometimes missing some (to others) essential background information and vocabulary, but happy to learn and not completely retarded.
Thanks for your help!
Have you tried forgetting the networks then reconnecting? Otherwise try renaming the .rev file. Or you could try copying the .cid.info from a ROM where the WiFi works fine to the Nandroid restored data. That might fix it.
I tried forgetting the networks, without success. I do not know what you are referring to by .rev file, and I do not have another device to restore my NANDROID image to, to then copy the cid.info file. So I kept playing around and this is what worked for me:
I found a file called wpa_supplicant.conf in the following directory: etc/wifi
Opening that file revealed some (as I was assuming) device related information (such as device type, model name, serial number, etc).
I renamed that file to .bak and this resolved my issue. I even deleted that file later on.
After enabling WiFi again, the file was not recreated by the system, even after a system reboot. I am not sure what this file does and how it was created, but so far everything is working as it should.
I also found a second file with the exact same file name at a different location: /data/misc/wifi
The content of that file is different, but some of the information is identical. This file contains WiFi AP information (like AP that I connected to in the past). Deleting that file would break my WiFi and would prevent it from turning ON. So I strongly recommend not to delete that file!
Needless to say: Do not make any modifications to system files without a functional NANDROID backup!
So in the end it seems to have been what I suspected all along. Some system file that was related to my old device and that, if identical, would create issues on the new device. But all of this is pure speculation. I am not an Android/Linux expert and simply tried to apply some logic.
I hope that I will now face no more issues. In case I do, I will report back.
Thanks for your help!
So, after getting my S3 repaired and switching back to it (usual NANDROID restore process), I was facing the exact same issue.
The wpa_supplicant.conf file that I was talking about did not exist, so I tried renaming the cid.info and that worked.
skofox said:
I tried forgetting the networks, without success. I do not know what you are referring to by .rev file, and I do not have another device to restore my NANDROID image to, to then copy the cid.info file. So I kept playing around and this is what worked for me:
I found a file called wpa_supplicant.conf in the following directory: etc/wifi
Opening that file revealed some (as I was assuming) device related information (such as device type, model name, serial number, etc).
I renamed that file to .bak and this resolved my issue. I even deleted that file later on.
After enabling WiFi again, the file was not recreated by the system, even after a system reboot. I am not sure what this file does and how it was created, but so far everything is working as it should.
I also found a second file with the exact same file name at a different location: /data/misc/wifi
The content of that file is different, but some of the information is identical. This file contains WiFi AP information (like AP that I connected to in the past). Deleting that file would break my WiFi and would prevent it from turning ON. So I strongly recommend not to delete that file!
Needless to say: Do not make any modifications to system files without a functional NANDROID backup!
So in the end it seems to have been what I suspected all along. Some system file that was related to my old device and that, if identical, would create issues on the new device. But all of this is pure speculation. I am not an Android/Linux expert and simply tried to apply some logic.
I hope that I will now face no more issues. In case I do, I will report back.
Thanks for your help!
Click to expand...
Click to collapse
It did not work for me. Neither does deleting .cid.info works.
That sucks. It's so frustrating.
Try to play around with it, based on the info in this thread. Make sure you have a working NANDROID backup, to just state the obvious (no offense).
Can you elaborate a little further what you believe caused the issue?
Reflash ing the rom would probably fix this.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Es file explorer problem (Android 4.4.4)

I use Es file explorer on daily basis, and it's worked perfectly until I upgraded to Android 4.4.4. When I tried to copy file from phone to win pc shared folder (like I done many many times before), it starts for a couple of seconds and then stop, say "time left: computing..." and after that "task failed". I tried everything, reinstalling app, flashing rom again (Viper 3.0.1), flashing firmware again because I know that wifi won't work without new firmware (wifi working properly), but i flashed again just in case. Then I tried another rom (ARHD) and it is the same. Then I revert back to Android 4.4.3 (Viper 2.5.0), and it worked again! Then I tried dirty-flash Viper 3.0.1 and it don't working anymore... I tried also Go file master, but it won't work ether.
So I think it is problem with android 4.4.4, because I tried two different apps with two different 4.4.4 roms and result is the same.
Can anyone who is on android 4.4.4 try to send some file, let's say around 100-200mb, with Es and see if it works? Thanks!
Program is free and on Play Store.
Login credentials help
snebojsa said:
I use Es file explorer on daily basis, and it's worked perfectly until I upgraded to Android 4.4.4. When I tried to copy file from phone to win pc shared folder (like I done many many times before), it starts for a couple of seconds and then stop, say "time left: computing..." and after that "task failed". I tried everything, reinstalling app, flashing rom again (Viper 3.0.1), flashing firmware again because I know that wifi won't work without new firmware (wifi working properly), but i flashed again just in case. Then I tried another rom (ARHD) and it is the same. Then I revert back to Android 4.4.3 (Viper 2.5.0), and it worked again! Then I tried dirty-flash Viper 3.0.1 and it don't working anymore... I tried also Go file master, but it won't work ether.
So I think it is problem with android 4.4.4, because I tried two different apps with two different 4.4.4 roms and result is the same.
Can anyone who is on android 4.4.4 try to send some file, let's say around 100-200mb, with Es and see if it works? Thanks!
Program is free and on Play Store.
Click to expand...
Click to collapse
Hello, as an ES File Explorer user, I would like to help you solve your issue. Have you tried using your administrator's logon credentials? You're supposed to type them into the fields as you add your computer (in LAN tab).
Also, you should know that if your IP address to your computer is re-assigned, the connection will be broken, as the IP you originally typed in will no longer work. Maybe in 4.4.3 the IP was the way you wanted it. Try to make it right this time. I will try to recreate your issue on my phone (running 4.4.4 as well) and get back to you.
furboom1240 said:
Hello, as an ES File Explorer user, I would like to help you solve your issue. Have you tried using your administrator's logon credentials? You're supposed to type them into the fields as you add your computer (in LAN tab).
Also, you should know that if your IP address to your computer is re-assigned, the connection will be broken, as the IP you originally typed in will no longer work. Maybe in 4.4.3 the IP was the way you wanted it. Try to make it right this time. I will try to recreate your issue on my phone (running 4.4.4 as well) and get back to you.
Click to expand...
Click to collapse
Thanks for trying to help.
Like I sad, tried everything, and I'm very familiar about ip. First, I totally uninstall es, reboot the phone, install es again from market. There is no assigned lan computers jet. Then, in lan tab, click on scan, and ip address of my computer are showed. When I click on it I can see shared files and folders on my computer, and I can access them. So connection is fine. When I tried to copy large file, 100-200 MB, it starts for couple of seconds and transfer couple of MB, then stop and sad task failed.
Interesting thing is that when I tried to copy FROM pc TO phone, it works without issues and I can transfer large files without any problem. So the problem is copying from phone to pc.
I tried this on three different places, it means 3 different routers, 3 different pcs, 3 different operation systems (XP, WIN7, WIN8.1), and the problem is there.
Like you can see in my first post, I tried to re-flash firmware and rom again, tried different rom, but could not solve the problem. Only when I revert back to android 4.4.3, everything worked again, but again on 4.4..4 not working like described.
Can you try to copy some large file from phone to pc (like one episode of some series) and tell if it working for you? Thanks.
Have you tried contacting the app developer? Its possible the app just hasn't been updated to be compatible with 4.4.4.
ES is a great app. Its been my go-to file explorer for some time now (although I don't use the particular function you are having a problem with). Hope you get the issue sorted out.
No, I haven't, but yes, that could be the problem. But I tried one or two similar apps and have the same problem...
Anyway, I currently using Sambadroid for transferring files and it's working, but like es better and hope it will work like it should in next version.
In Sambadroid I access files on the phone from pc explorer...
So, I tried 2-3 sense roms and the problem is there, but today I installed aosp rom to try it, and ES works without any problems. Strange...

Need advice

I have bricked my fire tv that has rbox's custom mod installed ( I wiped my sd partition and restarted the device before replacing the restore.img) so totally my own stupid fault... but I have a guy on this forum that's kindly trying to assist me in restoring it as he has the ability to get access to the emmc chip. He has a complete back up of his flash but what he is needing to know though is : where/how the FireTV is storing unique stuff like serial number/Device ID and whatnot. MAC addresses of Wifi and LAN would come to mind too. But he's pretty sure this contains IDs that are unique.
Would the following be possible : If we would know in what part this information is stored. He could try to make a backup of this from my device once it shows up as eMMC, and then later restore it
Any advice really appreciated as just want to return my fire tv to a working state.
Paul
Paul1672 said:
I have bricked my fire tv that has rbox's custom mod installed ( I wiped my sd partition and restarted the device before replacing the restore.img) so totally my own stupid fault... but I have a guy on this forum that's kindly trying to assist me in restoring it as he has the ability to get access to the emmc chip. He has a complete back up of his flash but what he is needing to know though is : where/how the FireTV is storing unique stuff like serial number/Device ID and whatnot. MAC addresses of Wifi and LAN would come to mind too. But he's pretty sure this contains IDs that are unique.
Would the following be possible : If we would know in what part this information is stored. He could try to make a backup of this from my device once it shows up as eMMC, and then later restore it
Any advice really appreciated as just want to return my fire tv to a working state.
Paul
Click to expand...
Click to collapse
The only thing you need to restore to make it functional is boot and system. What exactly do you mean by "wiped my sd partition"?
Paul1672 said:
I have bricked my fire tv that has rbox's custom mod installed ( I wiped my sd partition and restarted the device before replacing the restore.img) so totally my own stupid fault... but I have a guy on this forum that's kindly trying to assist me in restoring it as he has the ability to get access to the emmc chip. He has a complete back up of his flash but what he is needing to know though is : where/how the FireTV is storing unique stuff like serial number/Device ID and whatnot. MAC addresses of Wifi and LAN would come to mind too. But he's pretty sure this contains IDs that are unique.
Would the following be possible : If we would know in what part this information is stored. He could try to make a backup of this from my device once it shows up as eMMC, and then later restore it
Any advice really appreciated as just want to return my fire tv to a working state.
Paul
Click to expand...
Click to collapse
best bet is to have him DD each partition individually back onto your device from the prerooted roms, but you should confirm with Rbox about what partitions would need to be flashed.
edit whoops didnt see your reply
I stupidly went into advanced settings and wiped sd partition (been over a month now and can't exactly remember) feel so stupid
Think there was something else I wiped also bout can't be sure on exactly what, but it was in the advanced menu
rbox said:
The only thing you need to restore to make it functional is boot and system. What exactly do you mean by "wiped my sd partition"?
Click to expand...
Click to collapse
If he uses the boot and system from his complete flash will either of them contain any unique data (IDs, MAC, SerialNumber)?
Paul1672 said:
If he uses the boot and system from his complete flash will either of them contain any unique data (IDs, MAC, SerialNumber)?
Click to expand...
Click to collapse
No. Which is why those were the ones I said...
once its bootable again, is the pre-rooted image enough to fully restore it?
Where is the FireTV taking all those unique IDs from, do we need to backup/restore this from my device, or is it hardcoded somewhere on a chip?

[Q] Broken WiFi MAC Address

I tried changing my wifi mac address on my g3 using the Mac Spoofer (app) and it broke my wifi and now it wont turn on.
I still have my original mac address, tried changing it back on the same app and it didn't work.
I tried other apps but they won't even open because they can't detect my mac address.
Under wifi settings, Mac is shown as unavailable.
Can anyone help me to change it back?
Thanks!
This is the app that ruined my life
I fixed it! Just went to data/misc/wifi and deleted everything in it!
help
I did the same thing with the same app. Can you explain a little where you went data/misc/wifi. I tried file manager but can't get there. Thanks
mbsylve said:
I did the same thing with the same app. Can you explain a little where you went data/misc/wifi. I tried file manager but can't get there. Thanks
Click to expand...
Click to collapse
/data is a system mount, you'll need to root the phone.
how to root my phone ?

Categories

Resources