Samsung Note 9 Exynos IMEI Querry - General Questions and Answers

Hi,
I bought an IMEI changed Samsung Galaxy Note 9. Its rooted using Magisk, I m not a familiar with android ROM installations.
I want to upgrade android version from currently running 9 to android 10. But I dont want to loose the Changed IMEI.
What will happen if I flash official android 10 ROM onto my device, will the IMEI be changed to the factory one?
Thanks

Backup /EFS partition before changing ROM.
FYI:
EFS stands for Encrypted File System. Imagine the EFS as a big folder containing all of the important stuff that makes the "phone" part of your phone (i.e. what lets you communicate from one person with a phone to another) tick. It contains your IMEI, lots of files revolving around your SIM card and Wifi/Bluetooth (this includes your MAC address for all the radios of your phone), and lots of other things that should never ever under any circumstance be deleted or touched. It's sensitive, it's devastatingly important, and it's a huge pain. If you lose your EFS folder, you lose pretty much any chance of your phone being able to use data, Wifi, Bluetooth, and ( probaby) your phone will just not want to respond and reboot quite a lot.

Related

[Q] WP7 Easy Backup - Sharing Backups

Simple Question about WP Easy Backup
If I made a Full backup with this tool I Will get a Folder at Windows Phone Update with the name of Mobile ID like:
YYYYYYYY - YYYYYYYY - YYYYYYYY - YYYYYYYY
At properties folder theres a file with a .xml with a line like this:
<DeviceUrlId>zune-tuner://windowsphone/YYYYYYYY%20-%20YYYYYYYY%20-%20YYYYYYYY%20-%20YYYYYYYY</DeviceUrlId>
At restorpoint folder we got an active id.dat with a ID like:
{11111111-1111-1111-1111-111111111111}
and a folder with the same name:
11111111-1111-1111-1111-111111111111
In that folder there is a sub-folder called Data and there is a lot of files .dat and .hash
and a another .xml. The .xml got a line like this:
<DeviceId>YYYYYYYY - YYYYYYYY - YYYYYYYY - YYYYYYYY</DeviceId>
Now if I share my Backup with someone with the same device and change the information like:
YYYYYYYY - YYYYYYYY - YYYYYYYY - YYYYYYYY to:
XXXXXXXX - XXXXXXXX - XXXXXXXX - XXXXXXXX
<DeviceUrlId>zune-tuner://windowsphone/YYYYYYYY%20-%20YYYYYYYY%20-%20YYYYYYYY%20-%20YYYYYYYY</DeviceUrlId> to:
<DeviceUrlId>zune-tuner://windowsphone/XXXXXXXX%20-%20XXXXXXXX%20-%20XXXXXXXX%20-%20XXXXXXXX</DeviceUrlId>
{11111111-1111-1111-1111-111111111111} to:
{22222222-2222-2222-2222-222222222222}
11111111-1111-1111-1111-111111111111 to:
22222222-2222-2222-2222-222222222222
When the other person try to restore using the WP7 Easy Backup
The phone will recognize the mobile ID and install my Backup on the other device?
I'm Just courious.
i have tried it but with no luck, every device has its own "serial" i dont know how they name it, but we cant see it, and we cant manipulate it. and this serial wont allow you to do that. i even tried to backup 7720 on a custom ROM, and restore on a other ROM, that also dont work. its like the backup dont realize that this is the same device. and what i seen so far, every backup has its own code in the windows backup folder, try the same device after a update and the name changes also...
Backups are, so far as we know, encrypted with device-specific keys. I think these keys are in the hardware or at least the bootloader; they persist even across hard-reset.
Thanks
Just wanted to express my gratitude since I'm too young to post in the dev forums. Full Backup and restore worked perfectly for me. Got the error message after my phone rebooted due to the fake update, restored, and everything was picture perfect.
HTC HD2 (Back to the Future ROM, xmb Rom 8107.79) = HTC HD7 T9292
When I first bought my HD2 two years ago I was miserable until the official stock rom update helped smoothed out several issues, but even then it felt like a lot was missing in comparison to WM7. Now two years late after applying the Back to the Future ROM with the Mango update, added with this perfect backup solution, I'm really in love with my HD2/HD7 and can afford to hold out til atleast 2013 for the new Cortex-A15 superphones to drop. And even then I'll still hold on to my HD2/HD7 as an extra PMP.
Just a quick one on this. Is it possable to strip the device ID from the backup and create a Rom out of it and maybe modify it somehow for Root, etc ?
I would love to be able to create a rom with alll my Paid apps, then make it have root, then have my own custom rom that if something breaks I dont spend 2 hours installing like 60 apps...
... as I posted *just* a few responses further up:
"Backups are, so far as we know, encrypted with device-specific keys."
Unless you can figure out the decryption key - it's possible, probably without even disassembling the phone, but if you managed it you'd be the first success in a significant list of people to try - you can't even read the backup, much less modify it or flash it as a ROM image.

GUIDE SGS4 GSM vs CDMA, Unlocking, Rooting,Info on XDA, Flashing,4 noobs & beginners

GUIDE SGS4 GSM vs CDMA, Unlocking, Rooting,Info on XDA, Flashing,4 noobs & beginners
First off: if you find this useful, please hit the THANKS button, instead of posting thank you in the comments
Over the course of the past three months (and more specifically, over the past week), I'd like to think I've gone from complete noob to proficient android ROM flasher/ phone dude. However, it took many, many hours of searching for info scattered across this site and others, so I figured I'd give compiling all I've learned a shot, into one comprehensive thread that really covers all the stuff you need to learn from the ground up.
Will do so in the next couple 10 posts, topics being:
*Step (-1): What type of network/ phone technology does your phone use?
*Step (0): is your phone networked locked?
*Step (0.5): DECIDING YOU WANT TO ROOT YOUR DEVICE!/ Put a custom operating system on that thaaaang
*Step1: figure out what your device is- specific phone and model
*Step2: figure out how to root (gain root access to) your device looking at XDA forums
*Step3: Follow instructions, root device
*Step4: backup all your apps and app data
*Step5: Install a custom recovery either ClockWorkRecovery (CWR) or Team Win Recovery Project (TWRP), and do a nandroid backup!
*Step6: Choose which ROM or multiple ROMS you want to try out, and download the zipfile to your phone's internal memory or
*Step7: Step 7: flash the ROM and restore your apps!
NOTE: YOU TWEEK YOUR PHONE/ FOLLOW MY ADVICE AT YOUR OWN RISK
I just learned this stuff myself, so I thought now would be a good time to explain it, while I can still remember what if feels like to have no idea what I'm doing haha.
Before I go further, there are similar intro threads to this...for example, this one does a decent job of explaining that by modding your phone, you may void the warranty (although there are ways to restore your device to a state such that you can't tell you ever modded, it, like triangle away, etc.) http://forum.xda-developers.com/showthread.php?t=1118120
I posted this here because a couple of these steps use the Galaxy S4 i9500 as an example...so if you have that phone this thread should be particularly helpful.
Step(-1): What type of network/ phone technology does your phone use?
If you are OUTSIDE the USA, 99% chance the answer to this question is GSM, meaning your phone number is attached to a little plastic sim card that you can put into/ out of your phone...you should check anyways though to be sure.
If you are in the US, you may have a phone which uses CDMA, a technology that does not use Sim cards (true if your carrier is Verizon or Sprint). Phones that JUST use CDMA are sort of "Hardwired" to their networks, making it much more of a hassle to switch carriers; plus, basically everywhere else in the world uses GSM, so if you plan on traveling outside the USA, you probably won't be able to use your phone abroad. If you have a fancy new smart phone, it may have the hardware to use both CDMA and GSM networks, (for example, all Iphones models 4s and above), so check your phone specs.
In the US, the major carriers that use GSM are ATT and Tmobile. I prefer getting phones from these guys, because I know I'll be able to relatively easily use my phone anywhere in the world, and easily switch between cheap, prepaid, contract free plans (like straight talk or ultramobile), which rent out the networks of major carriers like ATT and Tmobile.
Step(0): is your phone networked locked?
ans: This is mostly a non-issue to folks outside the US, or if you don't plan on switching your carrier, but if you plan on travelling abroad or switching your carrier, and have a CDMA phone, you have a tough road ahead that I cannot advise you on . I would suggest checking out this site and buying a slightly used android gsm phone (att or tmobile branded) http://swappa.com/ .
However, if you have a GSM phone you got in the US, your phone may be configured so that putting sim cards from different carriers in it won't give you any service (aka "locked" or "network locked"). Check by taking a friend's Sim card using a different network than you and popping it into your phone; if you have service/ can make and receive calls, the phone is NOT locked. There are probably more sophisticated ways of checking if your phone is network locked, but above is probably the most straightforward.
There are some methods of unlocking your phone for free, but if you have a newer phone it may not work. Plenty of online sites that sell you unlock codes for between $7-$25, and send the code over email either instantly or a day at most after you buy it. Definitely worth it in my opinion; one site I've used a bunch is http://www.cellunlocker.net/
NOTE: if you have your phone on a contract, you are still obligated to pay your carrier throughout the time of your contract, else you pay some cancellation fee. So be aware of that.
Step 0.5 DECIDING YOU WANT TO ROOT YOUR DEVICE!/ Put a custom operating system (ROM)
SO, now let's say you've network unlocked your awesome GSM android smartphone, and you want to travel with it to another country, like for example, India. Because you unlocked it, you can buy a cheap local Sim card and use it in your phone, fully enjoying mobile 4g data (well, more like 3.5G, using HSPA+, not so much 4G LTE in India yet, but I digress). OR, you can use a $45 a month prepaid plan where you get unlimted everything and have no contract, instead of paying $80 a month or some garbage. AWESOME!
However, let's say you got a Tmobile phone and want to use the phone's capability of being a portable wifi hotspot, broadcasting the mobile data it's getting to your computer...turns out you can't do that in India (or on cheap prepaid plans in US, for that matter). I discovered that since I was using a Tmobile branded phone, the Tmobile "stock" operating system of the phone won't let you use the wifi hotspot unless you have Tmobile's special "hotspot plan"...it also hard codes a bunch of shi**y bloatware apps on your phone that suck. Some BULLS**T, eh?
Luckily, there are plenty of free and easy ways to "root" (gain root acccess) to your phone (and plenty of resources telling you how to do so!), and install custom android operating systems on your phone, which
1.) don't have any stupid bloatware apps
2.) let you use all the hardware features of your phone regardless of carrier
The result is a more powerful phone that runs faster, uses less battery life, and is generally just way more badass. Probably the best resource for how to do all of this is the xda-developers forums (http://forum.xda-developers.com/ ) Very vibrant community, and lots of people will help...just follow the rules though, explained tongue and cheeck in the following video ( http://www.youtube.com/watch?v=JmvCpR45LKA ). The main site for xda-developers is www.xda-developers.com, they also do cool vides and stuff on what's up with phone stuff. HOWEVER, if you are not careful you can mess up your phone, so that it's about as good as a paperweight (called "bricking" your phone). So just read all the instructions before you do stuff, yeah?
The following is more or less the beginning steps I did to root and install a custom ROM on a friend's Galaxy S4, which is an international model and so not network locked. The same general process could be applied to your phone as well, but again--this is only a general guide--your phone can (and probably will) have it's own exceptions to the general process. LOOK THEM UP!
Steps 1,2,3: find device model, research how to gain root, ROOT!
Step1: figure out what your device is- specific phone and model
ans: for example, my friend's phone I am setting up for him is the Samsung Galaxy S4 model i9500
**************************************************
Step2: figure out how to root (gain root access to) your device
ans: Off all the devices on xda forums (http://forum.xda-developers.com/index.php?tab=top), found my device ( http://forum.xda-developers.com/galaxy-s4) , found the proper forum (http://forum.xda-developers.com/galaxy-s4/help) , then searched in that specific forum to find the proper thread http://forum.xda-developers.com/showthread.php?t=2419762 , see Q4
**************************************************
Step3: Follow instructions, root device
ans: Instructions are at http://forum.xda-developers.com/showthread.php?t=2292615
NOTE: You must have the proper USB drivers installed, meaning either installing the sdk (software developer kit) from google and getting adb (android debugging bridge) set up (this is the best way to do it, really, especially if you want to mess around with phones more...tutorial on how to setup adb here http://androidcentral.us/2013/08/how-to-install-android-adb-and-fastboot-on-windows/ ) . If you can already transfer music and stuff from your computer, it may work without adb. Be sure your USB cable is not too beat up, and if possible, is the one that came with the device.
adb is very useful for communicating between pretty much any android phone and your computer. You can use it to push files on the computer through the terminal interface, even if the phone's file system doesn't show up for whatever reason on the computer when you connect it via USB ( more on that here http://log.amitshah.net/2012/05/using-adb-to-copy-files-to-from-your-android-device/ ), and a cool little program to send files from your computer to the device in a slightly more straightforward way, if you already have adb installed (http://www.xda-developers.com/android/push-files-to-your-device-with-quick-adb-pusher/)
Also, make sure you have USB debugging enabled. It should be in the Develpors options, which you may have to "activate" to see...see here http://gs4.wonderhowto.com/how-to/enable-hidden-developer-options-your-samsung-galaxy-s4-0146687/
If you are rooting a samsung device, you will probably have to use a program called ODIN. Other android devices allow you to do root through a method called flashboot. In general there are tons of ways to root devices, just make sure the one you are using has been tested and you follow the instructions exactly.
CONGRATS! you are rooted. That's half the battle. Rooting the phone will add a "Super User" app of some kind, which will basically controll which apps have access to the internal files of the phone (located on the "root" of the phone's flash drive). Some apps that are very useful for flashing custom ROMS (like ROM manager) and backing up your apps and their associated data (like Titanium backup) require root access, so you'll need to have rooted your phone first, and then when you open those apps for the first time, tap "allow" when it asks about granting root access.
some cool apps can only be downloaded if your phone has Root, like this gameboy emulator: https://play.google.com/store/apps/details?id=eu.codlab.src.game&hl=en
and here are some good Root apps to have, apparently
http://www.youtube.com/watch?v=jX4ir9r84YA
Step4: backup all your apps and app data
When you do eventually install a custom ROM on onto your phone, it will start out with little to no apps. The best way to get up and running again as quick as possible is to back up all your apps and data with Titanium Backup (mentioned above), which requires root access. Here's a great video on How to use the free version: http://www.youtube.com/watch?v=gQWoWfTA88k ....the video makes a good point in that if you are backing up your apps for a new ROM you are about to flash, you should only backup the User apps. Backing up and restoring the system data as well might cause some problems in the new ROM
While you don't need to to buy the pro version, I would recommend it--7 bucks, but it allows you to restore all the apps you've backed up much faster by letting you back them up into a zip file that you'll later be able to flash on your phone. Very useful, more on that in a bit...video talking about that here: http://www.youtube.com/watch?v=dRR5FONGJUA
Step5: Install a custom recovery either ClockWorkRecovery (CWR) or Team Win Recovery
By "custom recovery", i mean a custom version of the boot/ recovery interface, which lets you do a lot more with your device besides just restore it to factory settings. These custom recoveries will let you do a full backup of your device (often called a "nandroid backup"--this should be the first thing you do after you root your device!), as well as flash custom phone operating systems (ROMS) onto your phone; useful if you want to fully use all the hardware features of your phone, and not have the bloatware apps from the manufacurers hard-coded into your phone.
It's worth noting here that it's VERY important to install the correct version of CWR or TWRP. Usually to download CWR for your device, you can just download an app called ROM manager (again, after you've rooted your phone), which will recognize your device and then install the proper CWR version on it.
NOTE: If you have a more esoteric model of phone (like I do--the Samsung Galaxy S3 T999L, an LTE version of the S3 that came out in 2013, a while after the initial S3 launch), you may have to flash a custom recovery of a similar and more popular phone model to flash some custom ROMS (in my case, I had to flash the the Galaxy S3 model T999 version of CWR). For weird esoteric cases like this, it may be worth it to buy a useful app, ROMToolbox pro, which will let you flash a custom recovery for a userdefined device onto your phone in the paid version (it's like $5). Most times you shouldn't have to worry about this stuff, but just make sure you read any instrutions on XDA forums carefully before doing stuff.
As mentioned before, before messing around with your phone anymore, do a nandroid backup--super easy and essential if you make a mistake installing the wrong ROM or Recovery. Doing a nandroid backup will create a .zip file that contains a full "image" of your phone--all your data, apps, settings, a snapshot of your phone exactly the way it was when you took it. In creating this backup you can save it to your phone's micro SD card, or the phones internal memory. Regardless, always a good idea to save a copy on your computer too when you are done.
For the Samsung galaxy S4 i9500, looks like TWRP is the recovery to flash: http://forum.xda-developers.com/showthread.php?t=2361122
Step6: Choose which ROM or multiple ROMS you want to try out, and dl zipfile to phone
Now comes the fun part. Do some research on what custom ROM you'll want to try out. Some basic principles about ROMS:
Roms based on the Stock OS: These ROMS are based on the manufacturer firmware/ OS that the phone shipped with. So for Samsung devices, for example, these types of ROMS are Touchwiz based (because "TouchWiz" is the name Samsung has given to it's proprietary software that is responsible for a lot of the bell and whistle tricks you see in Galaxy S4 commercials, for example) These Roms are usually about 700 MB in size, and may still have some of the samsung apps installed if you do like to use them.
AOSP or AOKP ROMS:
AOSP (Android Open Source Project) ROMS are those that ship with "vanilla" android, meaning they don't have any manufacturer bloatware--they come with more or less the bare bones apps required to run the system. These ROMS will be much smaller, around 100-150 MB in size. The most popular of these is CyanogenMod, which is often referred to as just CM (for example, CM11.0.1 stands for CyanogenMod version 11.0.1). The guy who made clockworkrecovery, Koush (a legendary android developer of sorts, it seems), now works for the CyanogenMod development team ( think)
AOKP is the name of another popular AOSP based ROM. AOKP stands for Android Open Kang Project, Kanging being some jargon for stealing code and messing with it or something. Apparently it was used as a joke and then stuck, in the same sense that their mascot being a unicorn stuck (which I think is awesome haha).
IMPORTANT POINT ABOUT AOSP ROMS:
If you flash an AOSP Rom, the google play store will NOT be installed by default. In order to fix that, you'll need to flash another zip file containing the play store app as well as other basic google apps (gapps for short) as soon as you flash the Rom itself. You can find the proper gapps zips that go with the proper AOSP roms here: http://goo.im/gapps
There are couple apps that will let you download the ROM files directly to your interal storage from the app itself, like Rom Manager. However, to make sure you have the most up to date version of the ROM, you should visit the ROM's website directly.
Custom ROMS will often have a most recent stable build, and a most recent "nightly" build. The nightly builds may have some new experimental features, but may be a little buggy.
Step 7: flash the ROM and restore your apps!
So here's a pretty good short video walking through how to flash a ROM, although uses a different recovery interface besides CWR or TWRP : http://www.youtube.com/watch?v=nxTwGwtUBbk ....this does a good job of explaining the basic idea, however--
A.)you get the zip file of the ROM you want to flash on your internal or removable SD card
B.) reboot into recovery mode (often by holding down the volume down key and power button at the same time when your power is off, but you should look up what it is for your specific device)
C.) do a Wipe or Factory Reset. THis should not wipe the data on your SD card or phone's Internal SD card
D.) Wipe the Cache or the Dalvik Cache, whatever it is called (though on TWRP, the wipe feature does both a factory reset and cache wipe at once)
E.) install from SD card the zip file containing the ROM you are going to flash
F.) If the Rom is an AOSP based ROM, install the zip file containing the proper package of google apps
G.) reboot system
Again, the above are just general steps. If you want to see someone flashing a ROM with the recovery you are using (and I would recommend CWR or TWRP), just search for it on Youtube.
Now, if you plan on restoring your apps by flashing a Titanium Backup zip file, you first want to reboot into the new ROM, and skip the part when it asks you if you want to restore your phone using your google account (you can do that later). Then reboot into recovery and flash the Titanium backup zip file. got this info here: http://www.s3forums.com/forum/galax...backup-pros-update-zip-restore-your-apps.html
And that's about it! let me know if I got anything wrong. If you do have questions, I'll try my best to answer them, but again, I've just learned all this stuff as well, so I may not know.

Android Guide For Beginners

You might be confused of many terms in Android if you are a new developer or new to android. Here I got some meanings of these terms. Please give me some thanks if this topic helps you.
i. Root - Talking root access means that you have gained the full control of your device. You have made the system directory as read/write. When you buy a device there may be some files which the manufacturer deter to modify or delete since doing this may hamper the working of your device. But by gaining root access you can have the control of your visuals and looks of your phone. It is somewhat similar to the Administrator of Windows OS.
ii. The bootloader is a line of code that is executed even before your Android operating system boots up. The bootloader’s code is specific for each make and model of the many Android devices. Bootloaders come “locked” because the device manufacturer doesn’t want you tinkering with the software that they worked so hard to optimize for that particular piece of hardware. Unlocking the bootloader allows you to tinker with the phone’s firmware, or even replace it with a custom firmware (aka: ROM). It is important to note that unlocking your bootloader will erase all data stored on your phone, essentially putting it back to a “factory reset” state, so you’ll want to save any pictures, music, or any other important files that are on your device.
iii. Recovery - Once your bootloader is unlocked and you have rooted your device, you will need a custom recovery. A recovery is a piece of software that is called up separate from the actual Android operating system. Its purpose is to make changes to the Android OS at a core level, such as delete user data, apply updates and more. The stock recovery is limited in function, so if you are planning on modifying/hacking/rooting your phone, you will need to install a “Custom Recovery” such as Clockwork Mod Recovery. A custom recovery will allow you to make backups, restore them, wipe partitions, install custom software and more.
iv. Backup / Nandroid - Once your custom recovery is installed, you will want to make a backup (also known as a Nandroid). A Nandroid is simply a complete and total backup of your phone. It will store all of your data, apps, settings, SMS messages, and more, basically allowing you to restore your phone to the exact state that it was in when you made the backup.
v. Wipe - Now that your backup is made, you don’t have to be afraid of making changes to your phone or losing data, since you can always restore it (just be sure to not delete the backup!). Now you can “wipe” your phone without worry. Wiping is deleting all the user data from your phone, essentially resetting it to its factory state. You can also wipe (ie: delete) other partitions of your phone like the cache partition. It is always recommended to wipe your phone before installing a custom ROM (we’ll get to that in a second). You can wipe your phone via the custom recovery you installed.
vi.Flashing - Flashing is the process of installing some sort of software or code via your custom recovery.
vii. Flashable ZIP - A flashable ZIP is the actual file that you install or “flash” via the custom recovery to make changes to your phone’s software. It is a normal .zip file that contains the lines of code to modify your software. These Flashable ZIPs can be used to flash a ROM, Kernel, Radio, mod, and more, which we will define below.
viii. ROM - A ROM is the main firmware or operating system that your phone runs. Just like Windows 7 runs on your PC, or Mac OSX runs on your Macbook, a ROM is the main software you interact with to use your phone. It includes all the system apps (messaging, email, phone), the launcher, the notification bar…everything really. Google’s Nexus line runs a “stock” Android ROM (meaning it’s unmodified) while manufacturers make significant changes to the look and feel of their ROMS before they ship them with your phone (for example: note the difference between the Samsung Galaxy S III’s software and the software on LG’s Nexus 4) . Code-savvy developers have taken the manufacturers’ code and created their own “Custom ROMs”. These ROMs can dramitically enhance the look and feel of your phone, and often add tons of useful features. Two very popular custom ROMs are CyanogenMod and MIUI. A ROM is made for a specific model phone and comes in a Flashable ZIP file that is installed (“flashed”) via your custom recovery.
ix. Kernel - Unlike a ROM the Kernel does not alter the look and feel of your phone, but is a “deeper” line of code that rests beneath the surface, so to speak. It tells the software how to interact with the hardware.
Deleted
guitarboy021 said:
Thank you so much man. This is EXACTLY what I was looking for! I saw ur post on my thread and followed it. Thanks man. Ill definitely give this one a try.
Sent from my LG-E988
Click to expand...
Click to collapse
Thank you. Go to this thread of mine to know about Custom Recovery and flashing it http://forum.xda-developers.com/showthread.php?t=3046718
Thanks a lot!
seemeandyou said:
Thanks a lot!
Click to expand...
Click to collapse
If you are helped then please hit the thanks button

Modifying MAC Address On HTC 10 (Viper Rom 3.20) (Android 6.0.1)

Ok so essentially im trying to spoof my mac address on my newly purchased verizon HTC 10 its a great phone but of course i got caught up in how pretty the phone was and purchased it without realizing that Verizon prevents you from unlocking the bootloader ( cant say i'm surprised it is verizon after all ) no big deal so i purchased sunshine to get s-off which worked very well, flashed twrp recovery and easily installed viper rom, after installing all my apps, i thought that surely spoofing my mac would be no problem, after all i spoofed the mac on my jailbroken iphone with a simple terminal command that modifed the mac in NVRAM. Then the great train wreak began, first i started with the play store apps which would spoof the mac however they failed to authenticate with any network that had any kind of security so that was a no-go, then i used busy-box commands to try and attempt to spoof the mac same issue failed to authenticate, so then i just figured id go into the filesystem and modify some files, however every tutorial i could find pointed to a /efs directory which was not present at all or a /persist directory which was also not present there were a few other directories none of which i could find. Eventually i just got so pissed i took the wifi firmware files ( and if anyone was wondering the model of the chip is a bcm 4359 which is apparently a really good chip ) and went into a hex editor and found macaddr=%2 and changed %2 to equal the mac im trying to spoof. Of course when i applied the modified firmware files the wifi failed to turn on at all, so i thought maybe its the viper rom, perhaps it lacks directorys that a stock 6.0.1 rom has, but after restoring my backup its the exact same filesystem layout as viper, what i don't understand is why its so easy too spoof a mac address on an IOS DEVICE, but on an open source operating system such as android its giving me this much trouble, maybe i'm just stupid and missing something really obvious but surly it cant be this difficult to spoof a mac on android, any help would be greatly appreciated.

Cloned TWRP backup to another Mi4C - same BT MAC on both [SOLVED]

Hello
Just noticed the problem - about mont ago I got second mi4c for my wife(2/16). We swapped the phones for a while as she claimed she'd need the 3/32gb version, I took the cheaper one. Couple of days later it turned out she'd need a new battery more than any extra RAM/storage, so we swapped back and I was too lazy to install stuff again on both phones and just cloned her system/data via TWRP from 3/32 to 2/16 and let it run (unfortunately at the same time I did a clean install for myself instead of cloning 2/16 to 3/32). So, we end up using same BT MAC adress taken from the 3/32.
So, my question is - how to recover her own Bluetooth MAC address in as few steps as possible?
Both phones run CM13.1 by TS
Is it sufficient to run a clean install of ROM on her phone? Or do I have to flash original firmware via miflash first or is it even worse? Or maybe it's enough to delete a file that keeps the BT MAC and it recreates itself with proper MAC upon reboot?
I tried to google for that, but I haven't found anything useful
---------
EDIT:
Solved by myself - I tried to modify /data/misc/bluedroid/bt_config.conf - but it was not enough
To recover the original BT MAC you need to remove whole /data/misc/bluedroid folder and reboot. After that it's build again with proper MAC, but beware - you'll lose your current BT pairings. So, if cloning someone's elses TWRP backup, delete the given folder through TWRP manager before rebooting.

Categories

Resources