Hi,
I need to change my mac address. My phone is Xiaomi Redmi Note 4 (with Mediatek X20 processor), with 64GB storage and 3GB RAM. Running latest MIUI Global Stable 8.0.40. Bootloader is unlocked, installed latest cofface's TWRP, and rooted.
I tried several apps (ChameleMAC & Change My Mac don't work), the MTK Engineering Mode method by changing through byte string access in WiFi_NVRAM also didn't work (the 'write' function doesn't do or change anything). Wanted to try the hex editor method, but can't find the /nvram/APCFG/APRDEB folder in /data or /dev folder.
I'm out of ideas. Anybody know a method to change mac address that's actually /U] work for Redmi Note 4 (nikel) with Mediatek X20 processor?
I'm running AOSP rom on RMN4 and can change MAC address with ChameleMAC or MTK Engineer Mode. You must root, then use app called SELinuxModeChanger to set into Permissive, then ChameleMAC can working after that.
http://forum.xda-developers.com/showthread.php?t=2524485
longnt2007 said:
I'm running AOSP rom on RMN4 and can change MAC address with ChameleMAC or MTK Engineer Mode. You must root, then use app called SELinuxModeChanger to set into Permissive, then ChameleMAC can working after that.
http://forum.xda-developers.com/showthread.php?t=2524485
Click to expand...
Click to collapse
THANK YOU!
SELinuxModeChanger is the key.
No success with SElinuxModeChanger or SELinux Toggler
longnt2007 said:
I'm running AOSP rom on RMN4 and can change MAC address with ChameleMAC or MTK Engineer Mode. You must root, then use app called SELinuxModeChanger to set into Permissive, then ChameleMAC can working after that.
http://forum.xda-developers.com/showthread.php?t=2524485
Click to expand...
Click to collapse
Your success in changing the MAC-Adress gave me hope to do the same... (I need to change the MAC-Adress because two of our Redmi Pro have somehow the same MAC-Adress...and this causes constat WIFI-Problems...)
But unfortunately, both apps didn't work for me... (Redmi Pro, SuperSu 2.82, BusyBox)
The Toggler couldn't be installed at all... And the ModeChanger "can't get root" (although SuperSu states, it has root rights...)
Any ideas? Thanks in advance!
UPDATE!
I could install the SELinux Toggler by flashing the ZIP with TWRP... and could finally change the WLAN-MAC-Adress (after a few attempts) with SELinux set to permissive and writing a new MAC-Adress within the Engeneer Mode...
The only strange thing is, that after the first reboot the MAC-Adress changed again to a completely new one. But since then, it stays the same so far...
This App Also Work Like Charm :-
https://play.google.com/store/apps/details?id=net.xnano.android.changemymac
Related
Help
Sent from my Redmi Note 3 using XDA-Developers mobile app
Do you mean by change SElinux to premsive or enforcing
Changer is working with both for me....
android_smater said:
Do you mean by change SElinux to premsive or enforcing
Changer is working with both for me....
Click to expand...
Click to collapse
It's not working for me. I am using a system less root using magisk
Sent from my Redmi Note 3 using XDA-Developers mobile app
Download terminal emulator from google play and then enter code "su" grant root access after that enter code "getenforce" click ok you will see either enforcing or permissive if there is enforcing then enter code "setenforce 0" linux mode will be changed to permissive if you want to change to enforcing then enter "setenforce 1" and again check your linux mode via entering "getenforce". Hoping its may help
maxpaynebeck said:
It's not working for me. I am using a system less root using magisk
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, there is your reason. Selinux mode changer doesn't wait for root access, and system less root always takes a bit more time to receive a root request from application. That's why Selinux mode changer will never have root request granted.
You can try using some scripts etc (I never tried it) or you can perform normal root.
Sent from Note 3, Xiaomi Redmi Note 3.
muklshakya123 said:
Download terminal emulator from google play and then enter code "su" grant root access after that enter code "getenforce" click ok you will see either enforcing or permissive if there is enforcing then enter code "setenforce 0" linux mode will be changed to permissive if you want to change to enforcing then enter "setenforce 1" and again check your linux mode via entering "getenforce". Hoping its may help
Click to expand...
Click to collapse
How about using magisk... Any tips
I downloaded the DirecTV Now app on New Year's Eve hoping for $35/cable. Instead, I was greeted with the same Error 40 that everyone with a rooted device got. It took me a couple of days of researching and playing and reflashing and..., but I've finally figured out the simple(r) method to bypass this stupid root check for DirectTV Now (AKA Error 40, QP1005)
This applies to the TX5Pro, but it should work on any s905x based AMLogic SoC running Marshmallow 6.0 (A95X, CQ9, TX5, TX3, X96, NEXBOX, +many more.) As I understand it, they all have similar Android builds using the p212 board and firmware. I also have a M8S s812 running Kit-Kat 4.4.2 that I'll work on breaking, next.
First things, first: If possible, find your firmware and do a clean flash. Not a requirement, but if you've been playing with this for a while and you've ended up here, you've probably mucked up your /system files in some way or another. I managed to screw up my su binary location a few times and couldn't get it back without a lot of work. Reflashing was a three-minute, headache-free task.
That said, you'll want to adb over tcp/ip as these devices don't like to play the USB cable game.
Code:
adb connect deviceipaddress:5555
Follow up with
Code:
adb shell
and
Code:
su
to get into a root shell (if you don't get one by default.) Mine came with SuperUser from ClockworkMod preinstalled as a system app. Mount your system folder
Code:
mount -o rw,remount,rw /system
and edit your build.prop file with Vim.
Code:
vi /system/build.prop
If Vim is new to you, search the interwebs for a Vim cheat sheet.
Here's the trick with this... DirecTV Now's shared object file in lib/armeabi/libdrmagent_downloadable_jni.so looks for a few keywords within a few properties. Those properties are:
Code:
ro.build.product
ro.build.tags
ro.build.type
ro.build.display.id
...and the keywords are:
Code:
"release-keys, OnePlus2, OnePlus, Z26CL, STUDIO_C, user" are keywords that it favors, while "cm, cyanogen, cyanogenmod, debug, userdebug, A0001" are disqualifying keywords. Supposedly, "test-keys" is a bad word, too.
In my case, I needed to edit my build.prop to eliminate any sign of the bad words. Example:
Code:
ro.build.display.id=p212-userdebug 6.0.1 MHC19J 20160909 test-keys
to
ro.build.display.id=p212-user 6.0.1 MHC19J 20160909 release-keys
Run through the file and replace anything that says userdebug with user and test-keys with release-keys until you get to "#end build properties" Then save and reboot.
After reboot, install Hide My Root (I used the one from Amphoras) and hide the Su binary. This is where things might be getting tricky for some of you... on the TX5Pro, the SuperUser app is a system installed app, meaning it can't be uninstalled (it can, but it's not exactly a simple task for everyone) so you'll need to go into settings -> apps -> superuser and disable the app from there. Reboot again. Now, with the su binary hidden and the app's manifest not showing up in the system, the error 40 message should go away. This option will allow you to quickly restore su and SuperUser without needing a bunch of additional steps. You'll still need to set the device location service to "battery saving" (or use mock locations) but that's a simple task anyone can figure out.
The app is a choppy on high def feeds for some reason. I can't tell if this is processing/memory issue or a feed (wifi) issue. By default, the app doesn't work on ethernet, meaning you'll have to use wifi until you can fix that issue. But hey, one thing at a time, right? Anyway, I hope this helps anyone with this particular headache.
Thanks for pointing me in the right direction...
Got DirecTV NOW working on my nexus 6 running pure nexus ROM... I just did the edits with super su root and root explorer. Then disabled super su and rebooted.
Now to update the the build.prop files on the lineage os 13.0 nexus 10, and my wife's kltevzw (on ting gsm network) running lineage os 14.1
hi please help i flashed wrong twrp recovery i think now my amlogic smartbox failed to boot in recovery mode and the main problem is my smartbox Encryption Unsuccessful Factory reset, when i click factory reset nothing happend please guide how to solve this
Sent from my SM-N910G using Tapatalk
jameson.donaghy said:
I downloaded the DirecTV Now app on New Year's Eve hoping for $35/cable.
Click to expand...
Click to collapse
Any chance that you tried this out with Data Free TV/"Sponsored Data" with an AT&T wireless account? i.e. running the box through a Cellular Hotspot or tethered to your phone. I've been looking at if one could use one of therse Android TV Boxes to basically get Data Free TV.
my live tv app detect root try with magisk also but no success in my s905x help me guys
Sent from my SM-N910G using Tapatalk
is anyone help me out
Sent from my SM-N910G using Tapatalk
I edited my build.prop files to try and "hide" the root and I still get the error. I also tried root cloak with xposed and still nothing
Thanks so much
This really helped. I used Xposed module to hide those keywords. Worked a charm!
Hey, guys. Redmi note4x (mido) After installing supersu using twrp to get root successfully, but then I found that using USB to connect the computer has a problem: USB can not be used, connect USB after the phone shows charging. Including USB debugging, mtp can not be used. Is this the reason for the kernel?
Please forgive me for bad English
Wrong place. But I think disabling adb fixes mtp. Not sure. Worth trying though.
Sent from my Redmi Note 4 using Tapatalk
Hawkeye007 said:
Wrong place. But I think disabling adb fixes mtp. Not sure. Worth trying though.
Click to expand...
Click to collapse
All MIUI stable version I have tried, almost all have this problem.
Now I have found a solution: do not use supersu. I downloaded and installed the latest beta magisk su. At present everything is normal, but the shortcomings are obvious. There are a lot of applications can not identify su files. Even if the use of magisk comes with the su get root but still prompted no root privileges. Probably this is the problem of compatibility bars
Andy，xu said:
All MIUI stable version I have tried, almost all have this problem.
Now I have found a solution: do not use supersu. I downloaded and installed the latest beta magisk su. At present everything is normal, but the shortcomings are obvious. There are a lot of applications can not identify su files. Even if the use of magisk comes with the su get root but still prompted no root privileges. Probably this is the problem of compatibility bars
Click to expand...
Click to collapse
No problem just go to /device /system and edit build.prop and add these lines
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
And save then restart also enable USB debugging ,it will solve ur issue.
Hello guys,
Been lurking here for ages and already benefited tons from the help posted here. However, this is one issue that I can't seem to figure out.
I have the MTK variant of the RN4 and I'm trying to enable the Camera2 API so that I can take RAW pictures, use Google HDR+ etc.
I am rooted on MIUI 9 (though as it's MTK, it is still Android 6.0) and I edited the build.prop file using ES Explorer (I added the persist.camera.HAL3.enabled=1 line). I've rebooted the device, used checker apps and Lightroom to check if there's RAW support, but without luck.
Do you guys have any other ideas as to how I can enable Camera2 API support?
I don't have bootloops, I don't have any issues other than the fact that there's no Camera2 API support. Restarting the device does not erase my mods to the build.prop file.
Any help is appreciated!
Forget about it since GCam is supposed to work on Snapdragon devices only.
Kavute said:
Forget about it since GCam is supposed to work on Snapdragon devices only.
Click to expand...
Click to collapse
I wouldn't mind using other apps such as Lightroom if I can get RAW to work. Any ideas as to whether that's possible?
I've had a similar problem before, but MIUI would revert my changes to the build.prop. I solved it by using a systemless root via Magisk.
What I did:
1. Unroot your phone
2. Flash Magisk using TWRP (link to Magisk thread).
3. Download the "camera2api-enabler.zip" from this thread
4. Add the zip (Module) using the Magisk Manager app that comes installed after you flash Magisk
5. Reboot, and you should see the camera2api enabled.
If you do run into a boot loop after installing Magisk, you may need to flash the LazyFlasher zip file after Step 2.
yohyah said:
I've had a similar problem before, but MIUI would revert my changes to the build.prop. I solved it by using a systemless root via Magisk.
What I did:
1. Unroot your phone
2. Flash Magisk using TWRP (link to Magisk thread).
3. Download the "camera2api-enabler.zip" from this thread
4. Add the zip (Module) using the Magisk Manager app that comes installed after you flash Magisk
5. Reboot, and you should see the camera2api enabled.
If you do run into a boot loop after installing Magisk, you may need to flash the LazyFlasher zip file after Step 2.
Click to expand...
Click to collapse
Thank you! I'll look into Magisk. I have to admit that I'm tempted if only to get this and Super Mario Run working.
But I do like having sys root access, I've just fixed the Cell Standby battery drain with an edit to the build.prop file, as MIUI 9 doesn't have the option to disable VoLTE.
So I'll give it a thought.
Thank you! and if anyone has any other tips, preferably something that doesn't alter my setup too much, it'd be ace.
rottensong said:
Thank you! I'll look into Magisk. I have to admit that I'm tempted if only to get this and Super Mario Run working.
But I do like having sys root access, I've just fixed the Cell Standby battery drain with an edit to the build.prop file, as MIUI 9 doesn't have the option to disable VoLTE.
So I'll give it a thought.
Thank you! and if anyone has any other tips, preferably something that doesn't alter my setup too much, it'd be ace.
Click to expand...
Click to collapse
Hi!
If it isn't work, you should try out this:
Go in Engineer mode https://forum.xda-developers.com/showthread.php?t=2313812 or download the Engineer mod apk from play store. (It's working just on stock ROM)
Swipe left to Hardware testing, and there will be the Camera option.
I think, after you find this, you can get through the settings (where will be a raw capture option)
Recently, I tried to change Mac on my phone Xiaomi Redmi note 4 (Snapdragon).
rooted + supersu + twrp + busybox.
i tried many methods with miui roms and LOS/AOSP custom roms.. nothing works.
Even i found MAC Address path after many research and trying to change manually but no luck..
here is path
/sys/devices/soc/a000000.qcom,wcnss-wlan/wcnss_mac_addr
Nothing works.
There is app called "WiFi Mac changer" by Osama abukmail with I able to spoof Mac successfully but the story is the same : problem of autentication.
I found this post is related to this issue.
https://forum.xda-developers.com/nexus-4/help/nexus-4-mac-changer-spoofing-t2180809
Please any Dev figure out how to edit those files in RN4