I have three SG Players, two 5.0 and one 4.0 that have been having trouble connecting to my home wifi.
The 4.0 is running CM11 (cm-11-20140323-UNOFFICIAL-ypg1) with the Impulse r6 kernel.
One 5.0 is running CM11 (cm-11-20140113-UNOFFICIAL-venturi) with the Jan12 US kernel.
The other 5.0 is running CM10.2 (cm-10.2-20131105-UNOFFICIAL-venturi) with the Nov4 US kernel.
I poked around and discovered that they all have the same MAC address, and the two 5.0 players have the same serial number. I tried various MAC spoofers and changers without any success. I tried wiping and reflashing one of the 5.0 and the 4.0, but the addresses did not change.
Does anybody have any suggestions on how to change the MAC addresses?
For the 5.0 player you need to edit the /vendor/firmware/nvram.txt . There is a line that starts: macaddr=
Make sure it sticks, you got to remount,rw /system before you edit!:good:
You should be able to make up any "valid" mac you want...
Been meaning to fix this but... working on other stuff at the moment.:cyclops:
As @Meticulus said, the same thing applies with the 4.0, only that the file is /vendor/firmware/nvram_net.txt.
zaclimon said:
As @Meticulus said, the same thing applies with the 4.0, only that the file is /vendor/firmware/nvram_net.txt.
Click to expand...
Click to collapse
You path is correct for 5.0 too... typo :cyclops:
Gentlemen,
Thank you for the help. I was not able to try your suggestions as the computer here at work is locked down.
As both of you mentioned a text file, I looked through the cm-11-20140323-UNOFFICIAL-ypg1.zip file, found and edited /system/vendor/firmware/nvram_net.txt to modify the mac address. After saving the modified .zip file, I flashed it and my 4.0 now had the revised MAC address.
I then took the opportunity to update one 5.0 and the 4.0 to the latest CM11 (cm-11-20140414-UNOFFICIAL-venturi and cm-11-20140421-UNOFFICIAL-ypg1, respectively), after modifying the MAC address for each .zip file.
Thank you for fixing the headset button on the 4.0!
Related
Since data drops on PPP builds still appear to be a major problem for some users, I decided to post this workaround for converting any sense PPP build to RMNET. I have only tested this on Mdeejay Revolution build but should work with any sense build. I have used this for more than 10 days now without any problems whatsoever: everything worked like on the original build.And no data drops.
All attached files were extracted from Sergio's CoreDroid version 0.5 which is an RMNET build. Hope he doesn't mind.I am not at all a developer
The steps are outlined below:
1. Download and extract the attached files on your PC
2. Open the Android folder of your build on your PC, and copy + replace the zImage and rootfs with the extracted ones.
3. Boot into Winmo and transfer your android folder to your SD card; also transfer the extracted module folder to your SD
4. Boot into Android; after initial setup, reboot again.I recommend a clean fresh install (ie without any old data image; you may re-use your data.img after setup is complete)
5. Use Root explorer to copy and replace the 2 files in the extracted modules folder into \system\lib\modules.
6. Reboot and enjoy
UPDATE 7/11/2010
[08/11/2010]After further testing of this update, I have found the screen to be laggy and had a SOD. I tried reinstalling after that and had no data connection but wifi worked ok. I have therefore abandoned using the update and sticking with the original one above. Of course if it works for you stick with it.
I have tested a newer nexus kernel of 5/11/2010 (found here) on Mdeejays Desire Revolution build (Desire based build). Both wifi and data work, and camera is 5MP. However only a clean fresh install appears to work.
Just download the file NewRMNET, extract contents unto desktop, copy all 3 into the Android folder of your build. Then boot into Winmo and transfer to SD card. Boot into android 2-3 times. That's it.
Once again the rootfs.img file is from Coredroid v0.5
Please leave feedback. I dont use BT or wifi Hotspot so will not know if they work.
Cheers.
Hmmmm... I think I'll try this as soon as I get home. Will edit this post with an update in a few hours.
EDIT:: Seems this actually broke my ROM all together.. Sucks... Oh well. I've been meaning to test a few other ROM's out anyway. This just gives me a good excuse to finally do it.
I'm downloading now....gonna try it and see.i'll let you know how it does!!Thanks
Hi,
Thank you for sharing.
So does that mean that for Sergio's CoreDroid version 0.6 ROM ... it already has RMNET right?
CoreDroid 0.5 is RMNET, 0.6 is PPP.
tried it and it didn't help any.and now my wifi doesn't work,just gettin an error message.going back to the way I had it before!
Yz450rider14 said:
tried it and it didn't help any.and now my wifi doesn't work,just gettin an error message.going back to the way I had it before!
Click to expand...
Click to collapse
Wifi will not work if the bcm4329.ko and tun.ko files contained in the modules folder are not replaced in \system\lib\modules folder with root explorer or a file explorer with root rights.
Yz450rider14 said:
tried it and it didn't help any.and now my wifi doesn't work,just gettin an error message.going back to the way I had it before!
Click to expand...
Click to collapse
Was that an internet temper tantrum?
Seems to work well.. so far no problems and data is slow but steady.. Better than constant connection loss.. I created a folder set> 'root/system/lib/modules' in my android folder to make wifi work perfectly...No need to use root explorer. and if I switch zimage again, its easy to delete.. Thanks!
stonesolouk said:
Since data drops on PPP builds still appear to be a major problem for some users, I decided to post this workaround for converting any sense PPP build to RMNET. I have only tested this on Mdeejay Revolution build but should work with any sense build. I have used this for more than 10 days now without any problems whatsoever: everything worked like on the original build.And no data drops.
All attached files were extracted from Sergio's CoreDroid version 0.5 which is an RMNET build. Hope he doesn't mind.I am not at all a developer
The steps are outlined below:
1. Download and extract the attached files on your PC
2. Open the Android folder of your build on your PC, and copy + replace the zImage and rootfs with the extracted ones.
3. Boot into Winmo and transfer your android folder to your SD card; also transfer the extracted module folder to your SD
4. Boot into Android; after initial setup, reboot again.I recommend a clean fresh install (ie without any old data image; you may re-use your data.img after setup is complete)
5. Use Root explorer to copy and replace the 2 files in the extracted modules folder into \system\lib\modules.
6. Reboot and enjoy
Click to expand...
Click to collapse
This work around is a great idea, however changing the zImage file is changing the kernel. I believe coredroid v.05 uses mychiprimas r11 kernel to be rmnet. the internet is great but then there is low incall volume as well as low notification and ringtone volume. Those are a downer for me.
I read somewhere that Hastarin was making a RMNET kernel to try out but I dont know how that turned out.
Try this low volume fix here; worked great for me.
R3BrotherJr said:
This work around is a great idea, however changing the zImage file is changing the kernel. I believe coredroid v.05 uses mychiprimas r11 kernel to be rmnet. the internet is great but then there is low incall volume as well as low notification and ringtone volume. Those are a downer for me.
I read somewhere that Hastarin was making a RMNET kernel to try out but I dont know how that turned out.
Click to expand...
Click to collapse
awesome!!
stonesolouk said:
Try this low volume fix here; worked great for me.
Click to expand...
Click to collapse
thank you so much for the sound fix, does anyone know if bluetooth is working normally with the RMNET workaround?? I mean a2dp and FF, RW, play/pause, as well as in call??
can someone comfirm??
THANK YOU SOOOOOO MUCH!!! Sick and tired of PPP failing!!!! Again many thanks.
R3BrotherJr said:
I read somewhere that Hastarin was making a RMNET kernel to try out but I dont know how that turned out.
Click to expand...
Click to collapse
I did it, but turns out RMNET in the EVO tree is broken.
I'm not sure what the OP has done here. I would presume he's provided a Nexus based kernel and files to convert a particular build to RMNET.
If so that's a step backwards in my opinion. PPP with the recent patches to the kernel and wrapper is about as stable as we could hope for and we have a lot of fixes since the Nexus tree was last updated.
PPP still has to reconnect if your phone hops between towers/bands but seems to do so relatively reliably now. I have no idea how RMNET handles that situation.
Of course I realize others out there may want to live with RMNET and without the other fixes/features (working compass, g-sensor fixes, light sensor, etc). Each to their own.
stonesolouk said:
Since data drops on PPP builds still appear to be a major problem for some users, I decided to post this workaround for converting any sense PPP build to RMNET. I have only tested this on Mdeejay Revolution build but should work with any sense build. I have used this for more than 10 days now without any problems whatsoever: everything worked like on the original build.And no data drops.
All attached files were extracted from Sergio's CoreDroid version 0.5 which is an RMNET build. Hope he doesn't mind.I am not at all a developer
The steps are outlined below:
1. Download and extract the attached files on your PC
2. Open the Android folder of your build on your PC, and copy + replace the zImage and rootfs with the extracted ones.
3. Boot into Winmo and transfer your android folder to your SD card; also transfer the extracted module folder to your SD
4. Boot into Android; after initial setup, reboot again.I recommend a clean fresh install (ie without any old data image; you may re-use your data.img after setup is complete)
5. Use Root explorer to copy and replace the 2 files in the extracted modules folder into \system\lib\modules.
6. Reboot and enjoy
Click to expand...
Click to collapse
Is it possible that this fix be included by the chefs ... because I can't really follow the instruction.
Thank you, thank you, thank you so much!
Sent from my GT-P1000 using XDA App
Did a fresh copy of mdeejay revolution 2.3 and this kernel yesterday evening. No datadrop at all! Also did the wifi and volume fix, wonderful.
Many Many Many Thanks!!!!!
WiFi Hotspot
WiFi hotspot dont works with this.
i1magic said:
Is it possible that this fix be included by the chefs ... because I can't really follow the instruction.
Click to expand...
Click to collapse
All this really does is to swap the build back to using the old nexus kernel, presumably if the chefs wanted the old kernel in their build they'd already be using it.
hastarin said:
PPP still has to reconnect if your phone hops between towers/bands but seems to do so relatively reliably now. I have no idea how RMNET handles that situation.
Click to expand...
Click to collapse
I seem to recall someone saying that it is handled by Android (as opposed to the kernel), since RMNET is the "official" way to do things in Android.
Awesome!
Thanks for making this.
Can't wait to try it with some of the great builds here.
Was getting tired of all the build lately only using busted PPP based kernels.
What good is a data phone if the data connection is a joke.
I have been having trouble connecting to my work VPN with the G-Tablet. I have since tried going to ZPad 3.0 in hopes this would fix the issue. However, no luck. The VPN server is reporting an event error of 20209.
After a few hours of looking on other forums it turns out this have been an issue since Android 2.1. They have either intentionally left out the encryption module from PPPD or it was forgotten in the build. The 'fix' is to copy the PPPD file from a version prior to 2.1 (Android 1.5?) and save it to the System/xbin directory. However there is an argument over if should go into system/bin for 2.2.
Does anyone have more information on this - or better yet a fix/update? Any help on this would be appreciated.
which ROm are you using
stock ROM doesn't have VPN at all.
justauser said:
stock ROM doesn't have VPN at all.
Click to expand...
Click to collapse
I'm using ZPAD 3.0 ROM at the moment.
I have narrowed it down to a problem with the MPPE 128 encryption. I have found a PPPD that is supposed to fix the problem (see link below), but I don't now how to get it to the system directory. How do you mount system as R/W?
Alternate PPPD:
H***://melko.hiljanen.com/~qvr/android/ppp/
Root explorer will allow you to mount it that way
Sent from my DROIDX using Tapatalk
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
vectorcharlie said:
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Ditto!!!!!!!!
Tried your link, getting the same error I've seen in the past:
Code:
pppd: This system lacks kernel support for PPP. This could be because
the PPP kernel module could not be loaded, or because PPP was not
included in the kernel configuration. If PPP was included as a
module, try `/sbin/modprobe -v ppp'. If that fails, check that
ppp.o exists in /lib/modules/`uname -r`/net.
See README.linux file in the ppp distribution for more details.
I think(?) we need a customized kernel with ppp. So far, we have NTFS and CIFS support that's been added by some of the devs, here.
vectorcharlie said:
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No luck. The PPPD file didn't make a difference. I guess I should not have been surprised. The L2TP connections are supposed to work so I may try that tomorrow - if I can convince the network admin to make the changes on the vpn server.
The lastest info I have been able to collect on this issue is that it has been known at google since 2.0 was released. They were having a problem keeping a connection using MPPE 128 over PPTP so instead of releasing something that did not work right, they removed support for it until a later date. Said date has not been determined.
I will keep you posted as I find out more.
roebeet said:
Tried your link, getting the same error I've seen in the past:
Code:
pppd: This system lacks kernel support for PPP. This could be because
the PPP kernel module could not be loaded, or because PPP was not
included in the kernel configuration. If PPP was included as a
module, try `/sbin/modprobe -v ppp'. If that fails, check that
ppp.o exists in /lib/modules/`uname -r`/net.
See README.linux file in the ppp distribution for more details.
I think(?) we need a customized kernel with ppp. So far, we have NTFS and CIFS support that's been added by some of the devs, here.
Click to expand...
Click to collapse
I came across this too. Since the ppp directory exists under system/etc I have made the assumption that there is support for it (at least under ztab 3.0). In order to check using the method above we would need a terminal app or some other way to run the commands. If there is a way to do it natively I am too new to know.
Any devs willing to tackle this issue?
Newanzer said:
No luck. The PPPD file didn't make a difference. I guess I should not have been surprised. The L2TP connections are supposed to work so I may try that tomorrow - if I can convince the network admin to make the changes on the vpn server.
...
I will keep you posted as I find out more.
Click to expand...
Click to collapse
No luck. The Net Admin decided it would be too much work just for a tablet test (and his iPAD VPN work just fine thank you). Anyone willing to try a L2TP test?
I have tried L2TP in Vegan with no success. used my android phone to verify settings and it works fine from there.
nephelim said:
I have tried L2TP in Vegan with no success. used my android phone to verify settings and it works fine from there.
Click to expand...
Click to collapse
Ok so that is 2 ROMs down:
TNT Stock - No option
Vegan - Not functional
Just need TNT light and Zpad Clean v3.0 tested. I'm suspecting that it will be no for both. This is starting to creep higher on my list of needs. Does anyone know of a ROM VPN works in?
I confirm that the advent vega rom has the same problem.
Unable to use vpn.
Newanzer said:
Ok so that is 2 ROMs down:
TNT Stock - No option
Vegan - Not functional
Just need TNT light and Zpad Clean v3.0 tested. I'm suspecting that it will be no for both. This is starting to creep higher on my list of needs. Does anyone know of a ROM VPN works in?
Click to expand...
Click to collapse
Do you need tun.ko/kernel support for this stuff? Clemsyn compiled that into one of his kernels - check his thread in the Development forum out, and give that kernel a try with the Vegan ROM, that might get you closer.
rcgabriel said:
Do you need tun.ko/kernel support for this stuff? Clemsyn compiled that into one of his kernels - check his thread in the Development forum out, and give that kernel a try with the Vegan ROM, that might get you closer.
Click to expand...
Click to collapse
That could be worth the check. I would like to see a list of exactly what his kernel supports before I try though.
[EDIT]: Checked change log. VPN module in kernel not mentioned.
Looking over the list of known issues at Google, this problem has been known for a while. The fact that Google hasn't addressed it worries me a bit. It is possible that since phones are the largest part of their OS client, VPN isn't a high priority. They may be waiting for the open source community to solve their problem for them.
Was able to get VPN working
YOU WILL NEED TO HAVE ROOT AND BUSYBOX INSTALLED. PLEASE MAKE A BACKUP IN CASE SOMETHING GOES WRONG.
1st you will need the new kernel found at the below address.
http://forum.xda-developers.com/showthread.php?t=903505
2nd you will need to insert the tun.ko included in with the kernel into /system/lib/modules/2.6.32.27-cyanogenmod folder on the tablet using root explorer.
3rd you will need to install the latest version of vpn from
http://code.google.com/p/get-a-robot-vpnc/downloads/list
4th install a terminal emulator and then you will need type the following commands
su (press enter)
cd /system/lib/modules/2.6.32.27-cyanogenmod (press enter)
insmod tun.ko (press enter)
You should now be able to connect on VPN.
there is very easy installation get and run vpn frome purevpn........
brainyjd said:
YOU WILL NEED TO HAVE ROOT AND BUSYBOX INSTALLED. PLEASE MAKE A BACKUP IN CASE SOMETHING GOES WRONG.
1st you will need the new kernel found at the below address.
http://forum.xda-developers.com/showthread.php?t=903505
2nd you will need to insert the tun.ko included in with the kernel into /system/lib/modules/2.6.32.27-cyanogenmod folder on the tablet using root explorer.
3rd you will need to install the latest version of vpn from
http://code.google.com/p/get-a-robot-vpnc/downloads/list
4th install a terminal emulator and then you will need type the following commands
su (press enter)
cd /system/lib/modules/2.6.32.27-cyanogenmod (press enter)
insmod tun.ko (press enter)
You should now be able to connect on VPN.
Click to expand...
Click to collapse
Sorry for asking this noob question, but is this VPN fix only for Cyanogenmod, or will work with others, such as TnT Lite?
I'm running TnT lite and there no's VPN setup option.
tnt is missing the vpn shortcut
use VPN Show
Kazuyuki Eguchi/Tools
found in android market to access the vpn menu
i have used with sucess on most roms open vpn and open vpn settings
with out problems just by install them and setting it to auto run at start
with install to xbin and create a folder on internal sd "openvpn"
then place a vpn.conf file there
then connect this cause an error but causes super user to give it root rights
after that all my vpn,s work with out going near openvpn
purevpn said:
there is very easy installation get and run vpn frome purevpn........
Click to expand...
Click to collapse
Please elaborate...
Thanks!
I noticed after loading the cm7 alpha that my NT's MAC address had changed. I'm speculating that we're all using the same one rather than something unique. At this stage in the game it doesn't matter much unless someone has two devices on one network. But if I'm correct it's something that should be dealt with eventually.
This is my "new" MAC, 08:00:28:12:03:58. What's yours?
LordGibson said:
This is my "new" MAC, 08:00:28:12:03:58. What's yours?
Click to expand...
Click to collapse
Yep, the same as yours.
This thread on the Kindle Fire discusses the issue some.
I am using the SD Card version of CM 7 and do not believe I am experiancing this issue. I' m not 100% sure but I use MAC Address filtering on my wifi router and had no problem connecting when running the ROM.
I'm on stock right now and do not have the SD handy but I will verify later.
Obviously if my mac address had changed I shouldnt have been able to connect without adding the "new" mac to the router config.
Edit: Confirmed that I am NOT affected by this when running off the SD Card.
Land Master said:
I am using the SD Card version of CM 7 and do not believe I am experiancing this issue. I' m not 100% sure but I use MAC Address filtering on my wifi router and had no problem connecting when running the ROM.
I'm on stock right now and do not have the SD handy but I will verify later.
Obviously if my mac address had changed I shouldnt have been able to connect without adding the "new" mac to the router config.
Click to expand...
Click to collapse
Agreed. It sounds like it didn't affect you. That's how I noticed - had to authorize the new address on a dozen networks this week
LordGibson said:
This thread on the Kindle Fire discusses the issue some.
Click to expand...
Click to collapse
Later in that thread they talk of using the stock wlan_loader to restore the original MAC. I gave it a go but that didn't work. It didn't fail but didn't restore the MAC.
Figured I give the NVS stuff a try. I was able to create nvs_map.bin using the instructions from this thread but no matter where I put the edited file the driver stated: "No Nvs, Setting default MAC address".
For those with a single Nook this isn't a problem but as soon as two are on the same network problems will ensue.
LordGibson said:
This thread on the Kindle Fire discusses the issue some.
Click to expand...
Click to collapse
Quick Workaround: Use the instructions in the mentioned Kindle Fire thread. You will need to save the calibration file as /system/etc/wifi/WifiBackupCalibration. Make sure the permissions are correct.
Details: The wlan_loader program is called by /init.omap4430.rc with the option to load the eeprom calibration file but that file doesn't exist (simple typo WifiBackupCalibration versus WiFiBackupCalibration, capital F). If wlan_loader can't find that file it uses the default MAC address. I'm not sure what the long term fix is because it looks like our two options are the default MAC or one that you hex edit into the calibration file. I let the development team know of the typo. Hopefully they have resources on how to give a distinct MAC to each.
I still had my old MAC from a previous dhcp lease file and it is now working great with the stock Nook MAC.
EDIT: This is only for those using the initial CM7 alpha as it is already fixed in the next version.
jeffml said:
Quick Workaround: Use the instructions in the mentioned Kindle Fire thread. You will need to save the calibration file as /system/etc/wifi/WifiBackupCalibration. Make sure the permissions are correct.
Details: The wlan_loader program is called by /init.omap4430.rc with the option to load the eeprom calibration file but that file doesn't exist (simple typo WifiBackupCalibration versus WiFiBackupCalibration, capital F). If wlan_loader can't find that file it uses the default MAC address. I'm not sure what the long term fix is because it looks like our two options are the default MAC or one that you hex edit into the calibration file. I let the development team know of the typo. Hopefully they have resources on how to give a distinct MAC to each.
I still had my old MAC from a previous dhcp lease file and it is now working great with the stock Nook MAC.
Click to expand...
Click to collapse
I posted a link to this thread in the Alpha ROM thread, I'm also going to PM Celtic later today and see what he says about it - this a pretty strange bug but it probably has a very easy fix.
Hi!
How do I change the WiFi mac address of an Amaze phone?
I got two Amaze phones that I put Sport's CM10.1 on them.
Problem is both have the same (well known!) mac address. Seems like either CM10.1 picks a fixes address, or perhaps the process or rooting it cause the mac address to be reset?
I tried searching for ways to change it. Some posts require using busybox, however, that's temporary.
Some posts refer to change it in an nvram.txt data somewhere in /data/misc/ (or similar, don't have it handy), however, I do not have that file in any of the phones. I do not know what format I would have to put it in if I were to venture to do it. I found one example of a different phone and it was a rather complex file with all sorts of settings, which makes me cautious about even trying something and possibly breaking the format of the nvram on the phone.
Thanks!
[/COLOR]
ihama said:
Hi!
How do I change the WiFi mac address of an Amaze phone?
I got two Amaze phones that I put Sport's CM10.1 on them.
Problem is both have the same (well known!) mac address. Seems like either CM10.1 picks a fixes address, or perhaps the process or rooting it cause the mac address to be reset?
I tried searching for ways to change it. Some posts require using busybox, however, that's temporary.
Some posts refer to change it in an nvram.txt data somewhere in /data/misc/ (or similar, don't have it handy), however, I do not have that file in any of the phones. I do not know what format I would have to put it in if I were to venture to do it. I found one example of a different phone and it was a rather complex file with all sorts of settings, which makes me cautious about even trying something and possibly breaking the format of the nvram on the phone.
Thanks!
Click to expand...
Click to collapse
flash any sense 4.x rom on any of your device,i heard that sense 4.x roms change the mac adress of your device,dont knw what is the reason though...read it alnog yor research and readings...
http://forum.xda-developers.com/showthread.php?t=2201216
hatim_rajput said:
[/COLOR]
flash any sense 4.x rom on any of your device,i heard that sense 4.x roms change the mac adress of your device,dont knw what is the reason though...read it alnog yor research and readings...
http://forum.xda-developers.com/showthread.php?t=2201216
Click to expand...
Click to collapse
Thanks for the reply, however, this is not a great solution, as it's rather invasive. I'm also finding that this image I am on is stable and yields good battery and it has the latest 4.2.2, so I am trying to avoid major changes like a rom from a different device might be (I'm new to this too ..).
Here is what I have tried:
brute-force search on the zip file that Sport posted
brute-force search on the phone itself via a root shell
searching various other files and forums
the brute-force search on the phone found the mac address. This is what i did:
find -exec grep -iH '00:d2:8b:43:9f:fd' '{}' \;
which yielded:
/sys/devices/platform/msm_sdcc.4/mmc_host/mmc3/mmc3:0001/mmc3:0001:2/wl12xx/ieee80211/phy1/macaddress:00:d2:8b:43:9f:fd
/sys/devices/platform/msm_sdcc.4/mmc_host/mmc3/mmc3:0001/mmc3:0001:2/wl12xx/ieee80211/phy1/addresses:00:d2:8b:43:9f:fd
/sys/devices/platform/msm_sdcc.4/mmc_host/mmc3/mmc3:0001/mmc3:0001:2/wl12xx/net/wlan0/address:00:d2:8b:43:9f:fd
However these files are in a "/proc/-like" mounted device that is read-only. These files look like status files from the OS, so even if I had been able to change them, it looks like the changes would vanish after reboot, and even if that would not be the case, it would not have changed anything.
Any ideas?
This is the solution for permanently changing the MAC of the WiFi in the Amaze (ruby) phone:
su -
mount -o remount -o rw /system
cd /system/etc/firmware/ti-connectivity
calibrator set nvs_mac wl1271-nvs.bin 00:d2:8b:XX:YY:ZZ
cd /
mount -o remount -o ro /system
change the XX YY ZZ to any other (hex) numbers as you please.
(The assumption is that you are connected with adb shell)
I hope I got the right place to post.
I have a Measy U4K miniPC stick that came with an Android 4.1.1 ROM. Measy did not make this ROM public, nor have they provided the promised 4.2.2 update.
However, the TV Box CS918S has had multiple releases of 4.2.2 ROMs and has the very similar architecture. I can flash the ROM but wifiand SD card don't work. After a lot of investigation and meddling I have traced this to the Wifi Power pin being different, the CS918S uses dld01 whilst the U4K uses aldo1.
I have used both Windows and Ubuntu based kitchens to try to amend the ROM to work on the U4K but with no joy. The key files that controlled config in the 4.1.1 builds such as sys_config.fex, bootloader.fex and script.bin seem no longer to matter. In fact, script.bin no longer exists.
From what I can see u-boot.fex has the config compiled in. I've tried hex modding to change dldo1 to aldo1 but then the image won't flash, presumably due to CRC error.
Can anyone help me out with this?
For ref the latest firmware can be downloaded from [link deleted as I do not have privilige yet]