Hi,
I have strange internet provide that lets only one MAC address on network. Long story short, I have to change a Wifi MAC address on my 8525. Any ideas?
I would prefer something simple, maybe a simple aplication to do so.
I have read post like
http://forum.xda-developers.com/showthread.php?t=322225
but, it is complicated, since I need to be able to change it back to original on daily bases with no access to external computer.
Thanks
sadik007 said:
I have read post like
http://forum.xda-developers.com/showthread.php?t=322225
but, it is complicated, since I need to be able to change it back to original on daily bases with no access to external computer.
Thanks
Click to expand...
Click to collapse
Sadly that's the only way it can be done; the WLAN MAC address is stored at a fixed offset within the ROM - the post you mention above is a guide to patching the ROM to update it with the required MAC address.
Mark.
Mark Crouch said:
Sadly that's the only way it can be done; the WLAN MAC address is stored at a fixed offset within the ROM - the post you mention above is a guide to patching the ROM to update it with the required MAC address.
Mark.
Click to expand...
Click to collapse
1 thought as my cable provider is like that to a certain regard,
Get a wireless router. then register the mac of the router with the provider, everything else is transparent to the provider as it would appear to come from the router ans is all ip based, aqs no Mac based services ( ie: netbios ipx/spx ) are used on the internet only on local network
hope this helps
Hey guy/gals, I've got a nifty little trick here for you. Now, the trick I'm about to explain is a rather low-level trick that most of you may know, but its for those who don't or are new. So, at the school i attend, they have wifi throughout the school. They make the password something simple like "internet", and then wait for someone to figure it out and tell everyone. Once everyone start joining the network and using it, they just go through and blacklist (ban) the MAC addresses that aren't pre-approved. This was a huge mistake on their part. So here is a method that allows you to spoof your MAC (ghosting) address and regain access to the network.
Method 1: Go to the market and download 2 apps, "BusyBox" and "MAC Spoofer (changer)". Install BusyBox and run it to give it SU permissions. Then run MAC Spoofer and give it permissions. Turn on your wifi and try to connect to the desired network. If you are blacklisted, it will just loop over and over trying to connect. Don't stop it from looping. Press the home button and then open MAC Spoofer. Now, when you run MAC Spoofer there will be a black box in the center of the screen and it should say ">CHECKING FOR ROOT PERMISSION AND WIFI FILE: OK!" then on the next line it will show your original MAC address and your current one. In the entry box between the black box and the spoof button, you can enter your desired address and press "Spoof my MAC". It will then say ">ATTEMPTING TO MODIFY MAC ADDRESS:" and on the next 2 lines it will show your original and current MAC. On the last line it should say "**SUCCESS** MAC OF INTERFACE wlan0 CHANGED TO: (Whatever you chose)". Now you can exit the app and go back to your wifi network selection. Select the network you were trying to join and it should connect.
I hope this works for you all. If you have any questions or issues, just reply to this thread. Don't forget to give me a thanks!
Note: Your MAC will reset to the original MAC when you turn off your wifi or if your reboot your phone.
Note: I am running ME7 with 4.2.2 JellyBean and stock rom.
(Deleted)
I don't want to factory reset my phone nor do I want to reflash lineage os.
I just want to detect if there is some spy software on my phone. Software like flexispy, mspy, phonesheriff, ikeymonitor, thetruthspy, ....
I found one app that claim to find them but I doubt its effectivness (https://play.google.com/store/apps/details?id=com.antispycell.free&hl=fr)
One blog from some years ago claims that the anti-virus made a poor job to detect such softwares. (I can't find that page again)
Some site suggested to use an access point to sniff traffic. That's what I did with my raspberry pi but I got only a bunch of encrypted traffic from my phone (https). So it was not helpfull beside getting a list of IP or at best domain name. You can tell much with that. The next step would be to MITM with ssldump or sslsplit but that's more technically challenging for me
Is there other tool available ? an app ? a site of a good soul that maintain a list of file installed that such spy app and that you could find manually by using an (root) explorer of /system or /data ?
Thanks
Ok. So here's the deal:
My SGS3 I9300 exynos phone did the famous IMEI 0049 and SN null trick.
I cannot say what precipitated it but is simply stopped registering on the network, so no calling or data. All other functions operational.
After much searching and reading, I settled on flashing the stock 4.3 back. This succeeded only in doing absolutely nothing to alleviate this issue. I wiped the entire phone. Maybe I missed a critical section wipe, but since the stock ROM overwrites all? the CSC/BL/MODEM functions I thought it would set the default for EFS (which I believe is where these critical data live). I'm not a programmer so I cannot say diddly about the architecture and interrelationship of OS files, but I am technical and I know how SW and HW does what it does.
This phone is my own and I have all the rights to it.
I had loaded RRemix ROM a loong while ago and it was functioning fine. Probably a corruption of the EFS due to battery contact being loose. This is in my mind the most likely cause as the system may be accessing the EFS files, say making a call, or accessing data, and the power drops out and voila! Corruption. But again this is theoretical.
Needless to say I tried the usual hocus-pocus out there with no avail.
Getting to understand the system better it seems obvious that these critical identification numbers are hard-coded into the chips on the phone. Which explains the ability to 'fix' them with JTAG and other cable/box solutions and SW. However, I cannot see how the SW loses the ability to read the IMEI/SN that is hard-coded (fused?) into the main-board.
All my research pointed to the EFS files having something to do with this.
Way back when I loaded the custom ROM I did not come across the 'backup your EFS' as a necessary step, so I had nothing to go back on.
And loading the stock 4.3 ROM back on and not having that fix the issue, led me to believe something else was up.
Somewhere in the guts of this phone something is screwing up the layer between reading the registers where the numbers sit and the software layer that reports the numbers.
So, much searching led to the nv_data.bin file being a key component in all this fiasco.
Now, before I say any more, I believe that describing the next steps could be a big no-no here.
Now, understand, all I want to do is get MY personal device working again. I have the SN and IMEI numbers on the physical device.
Sure, I could have stolen it and am attempting to change these to avoid prosecution. Anyone can say anything online.
Therefore, before I can proceed, I need advice from moderators and VPP to either say 'Yes you may post this info' or 'No. Go away'.
Am I allowed to do the following:
1) Describe how I restored my IMEI (Not changed, overwritten, or subverted to my limited knowledge)
2) In the case of 1 not allowed, post the link to where I found the info to achieve this.
3) Submit the 'fix' to a moderator or developer to check whether this is indeed and restoration or a change.
If it's a restoration of existing functionality, I cannot see how this could be a problem. If its changing something, then it's a whole other sack of ferrets.
My reasons for posting are that xdadevelopers has given me years of joy with my SG devices. (Yes, I have the whole range exclusively) Many ROMS, customs, fixes, hints and saves deserves something back, and the difficulty in achieving this particular fix, warrants it.
But I don't want to break any rules, this being my first post.
So, please let me know what I can do to help others stuck in this position...
You can find it if you have the correct search parameters. Perhaps I can say that instead?
Thanks.
And thanks to all who have helped over the years.
T
[Edit] Just to clarify, the solution requires no special HW or 'boxes'. You do need root, however, and a hex editor. I had a reply explaining the use of Octoplus, which requires credits and registration. You will need none of those.
I can't speak English but I will try.
1- flash stock firmware.
2- root your device s3 .
3-in the web download " octuplus crack box"
4-in youtube see how install " octuplus crack"
5- before install stop your antivirus PC
6- open octuplus and connecte your phone with PC
7- chose your device i9300 .
8 click repair imie
9 click read info and do what OCTU said to do.
10- click repair or write the true imie in your device ( remove battery to see)and click repair.
11- restart phone .
12- see: call work fine
13- in phone go to mobile network\ access point names\ apn's
14- write your network.
TrinityTrip54 said:
Ok. So here's the deal:
Repair is ok Change or Modding is now:good::good::good:
Click to expand...
Click to collapse
How to restore corrupted or null 0049 IMEI on SGS3.
Right.
Thanks to the moderators for agreeing to let me share the solution. :good:
Thanks to the reddit poster who found this solution. I don't know how the hell you figured this out, but big-ups to you. For privacy I will not mention names or addresses.
You do need a rooted phone and I cannot assist anyone without root as I have not tried it.
Whether this only works to restore a corrupt IMEI or change it, I cannot say, but it managed to restore my existing one.
Preparation: Get your IMEI number from under your battery compartment. Say your IMEI no. is: 123456789101213, write/type it in the following fashion: 1 23 45 67 89 10 12 13
Now some funky transposition: Excluding the first number, transpose the subsequent pairs of numbers so that you have: 1 32 54 76 98 01 21 31. Can you see it? Swap 23 to get 32. 45 to get 54 and so on.
Now add 08 to the beginning and add A after the 1 so that the completed number is: 08 1A 32 54 76 98 01 21 31
Now you will need:
Rooted Galaxy S3 (This may work for all android devices that have an EFS folder. If anyone can confirm that would help others.)
Hex editor (PC based or Android app) - PC is faster and easier. I used hex workshop trial version but I'm sure any editor will do. I used the default install configuration.
USB Data cable (if using PC editor mentioned above)
You should probably back up the EFS folder entirely, just to be sure.
Using your favorite root explorer browse to root/EFS folder and copy the nv_data.bin file to an accessible area in sdcard. I use a /sdcard/Downloads folder.
Either open the file with your hex editor app or transfer the file to PC where you can open it with your hex editor program.
Open the file and jump to address 00550.
Now, get your modified IMEI number from the prep steps above and enter the values in the ASCII TEXT window to the right, NOT the HEX values window to the left. This may be different for other editors but hex workshop works like this.
Double check your address and entered data. When satisfied, save the file and transfer back to the phone if copied to PC.
Now, place the phone in Airplane mode, turning off the cell radios.
Go to the EFS folder and rename the original nv_data.bin file to something else. I used nv_databak.bin.
Copy the modified nv-data file into the EFS folder.
Turn off Airplane mode and do a full reboot.
Your IMEI number should be restored and cellular functions should work.
My previously garbled serial number was also restored.
I hope this works for you. I have no knowledge of any other method as I did not delve further into trying other numbers or such. I can't assist any more other than further clarifying the steps above if you don't understand something.
If anyone can decipher what is going on here, I would love to hear about it. I suspect something between the HW and SW layers is getting garbled or corrupted and this kick starts the process to get the correct data again.
Maybe.
May also contain nuts.
Hastalavista.
T
THANKS FOR POSTING THIS HERE!
I have this Samsung Galaxy S3 that I bricked 4 years ago and never wanted to sell it or even try to give it away. I searched for months for a frekin solution to this problem. Yesterday night i decided i wanted to try and install custom roms on it and so i wanted to give another shot at this stupid issue i had with the lost IMEI before doing so...and BAM! Today it's fixed!
I'm so thankfull I wanted to post here so that you know that you helped at least one person with this
Thanks a bunch!
@TrinityTrip54
Hi,
can you confirm that this is a permantent solution and remains when flashing new (custom) ROMs? Or is it just for the current installed ROM?
And I am having an issue with "jump to address 00550" in Hex Workshop. There is no address like this, just 540 and the next one is already 558. When inserting 00550 in the goto search field of Hex Workshop it jumps to 210. Any idea?
thanks anyway.
bert
I would like to know if there is a way to intercept the inserted passcode to unlock the phone.
What I aim to do is to detect and read the wrong pattern insertions and leave the default behavior for the sucessfull passcode.
The enviroment could be whatever up to the needed restriction, i dont know if is needed a rooted device or not, btw I would also consider LineageOS solutions.
I've read about DeviceAdminService and DevicePolicyController but can find out anything...
Thanks in advance
:angel: