Related
AOKP JB Rom with Stock ICS Kernel
The one on rombot is a couple of days old so I have updated with one I build on 10/16.
Built from Hashcode and DHackers source. Give thanks to them!
Read this thread on how to install and thank Hashcode: http://forum.xda-developers.com/showthread.php?t=1886935
Link to Droid 4 folder with some roms, inverted gapps, safestrap, tools, etc:
https://www.dropbox.com/sh/mhmmrku5e4x8boj/hbd5BE-Nae or here: http://d-h.st/users/jsnweitzel
Use safestrap 3.05
Android 4.1.2
Working Camera now, no flash though.
As usually doing this stuff can break your device.
Thanks for this! Just finished DLing. Going to back up and test it out.
russia. megafon. No connection to the Internet. To create APN does not change anything.
hows the battery life?
For some reason every time I download the ROM then try to either install it safe-side on Safestrap 2.11 it won't open. I also notice that I'm unable to open the archive on my computer as thought the file is corrupt?
I just updated the op with a build I did this morning.
hi, i just flashed this ROM but i noticed my pictures from my SD card isn't showing up in my gallery, I tried googling it and its supposed to be a known issue for jellybean, i tried a few different things but nothing worked so now i'm using Quickpic.
but is there a way to connect the Quickpic app to the camera app or a way for the stock gallery app to rescan for all the pictures?
I don't seem to be having any trouble with reading my pics from the external sdcard.
The keyboard lights don't come on after the phone wakes up.
AOKP GSM edition, stock kernel. works fine.
http://d-h.st/rFH
olegfusion said:
AOKP GSM edition, stock kernel. works fine.
http://d-h.st/rFH
Click to expand...
Click to collapse
I didn't get mobile data with your build until editing build.prop.
Code:
--- build.pbak
+++ build.prop
@@ -139,7 +139,7 @@
# could use this property too. IKMAIN-732
#1 this is verizon wireless globle phone
#0 this is not verizon wireless globle phone
-ro.mot.phonemode.vzwglobalphone=0
+ro.mot.phonemode.vzw4gobalphone=1
# END Motorola, nfjb73, 21-jun-2010, IKMAIN-732
# BEGIN Motorola, nfjb73 23-jun-2010, IKMAIN-624
@@ -325,8 +325,7 @@
ro.cdma.subscribe_on_ruim_ready=true
persist.sys.moto_oem_telephony=false
persist.sys.moto_imsi_fix=false
-ro.config.not_world_phone=true
-
+ro.config.not_world_phone=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
@@ -357,3 +356,13 @@
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
+
+ro.ril.hsxpa=3
+ro.ril.gprsclass=12
+ro.ril.hep=1
+ro.ril.enable.dtm=1
+ro.ril.hsdpa.category=28
+ro.ril.enable.a53=1
+ro.ril.enable.3g.prefix=1
+ro.ril.hsupa.category=7
+
Not sure the ro.ril settings were absolutely needed. But no APNs showed up until I changed the world mode settings.
Also something is wrong with your keymap. The capslock and OK buttons don't do anything in Connectbot. OK should be DPAD Enter. CapsLock could be ALT, since it's not really needed for itself. (Shift-Shift is already caps lock after all.)
I don't think the caps lock and ok key work in any of the jb roms. You can double click the shift key for all caps. Anyone have them working?
Never mind the build.prop settings, they may be a red herring. It looks like every other reboot, data fails because the RIL is unable to read the IMSI because the SIM card isn't ready yet when it tries.
I've also found that I can successfully reset the RIL and get data working by going into Airplane mode, then in a root shell kill the existing rild, which forces it to restart. After it restarts toggle back out of Airplane mode and data is working.
Back to keymaps - also the arrow keys are all set to the wrong directions. I've manually edited my omap4-keypad.kl file to fix these issues.
jsnweitzel said:
I don't think the caps lock and ok key work in any of the jb roms. You can double click the shift key for all caps. Anyone have them working?
Click to expand...
Click to collapse
After I straightened out the arrow keys, the OK key started working as usual in Connectbot. It must have been looking for a particular layout and giving up when it didn't see what it expected.
I've found that setting CapsLock to Alt doesn't actually do anything useful, probably because nothing in the Keymaps file has anything defined for its Alt position.
Oh, and the CapsLock key wasn't working because the file had "CAPS" but the correct keyword is "CAPS_LOCK" - so it's working for that on mine now.
The SYM key used to bring up a dialog box with special characters, now it just brings up a dialog to select Input Method. That appears to be a JB-specific thing. Makes it pretty useless.
highlandsun said:
After I straightened out the arrow keys, the OK key started working as usual in Connectbot. It must have been looking for a particular layout and giving up when it didn't see what it expected.
I've found that setting CapsLock to Alt doesn't actually do anything useful, probably because nothing in the Keymaps file has anything defined for its Alt position.
Oh, and the CapsLock key wasn't working because the file had "CAPS" but the correct keyword is "CAPS_LOCK" - so it's working for that on mine now.
The SYM key used to bring up a dialog box with special characters, now it just brings up a dialog to select Input Method. That appears to be a JB-specific thing. Makes it pretty useless.
Click to expand...
Click to collapse
Can you email me these changes so that I can merge them into the mainline? Or feel free to submit a pull request on github?
highlandsun said:
Never mind the build.prop settings, they may be a red herring. It looks like every other reboot, data fails because the RIL is unable to read the IMSI because the SIM card isn't ready yet when it tries.
I've also found that I can successfully reset the RIL and get data working by going into Airplane mode, then in a root shell kill the existing rild, which forces it to restart. After it restarts toggle back out of Airplane mode and data is working.
Back to keymaps - also the arrow keys are all set to the wrong directions. I've manually edited my omap4-keypad.kl file to fix these issues.
Click to expand...
Click to collapse
On the RIL settings for GSM:
I can enable the new build.prop values DHacker has been working on which add the same data toggles specifically for these fixes. Allows the user to enable/disable certain RIL features via settings until it works right.
Hashcode said:
Can you email me these changes so that I can merge them into the mainline? Or feel free to submit a pull request on github?
Click to expand...
Click to collapse
PM'd you the diff. Let me know if you'd prefer it some other way.
Hashcode has put a new build up here: http://goo.im/devs/Hashcode/maserati/aokp/STOCK-JB-aokp_maserati_unofficial_Oct-18-12.zip
Haven't found a changelog. Anyone tried this on GSM yet. Does it work, or do we have to wait for Olegfusion to do his magic?
Lum_UK said:
Hashcode has put a new build up here: http://goo.im/devs/Hashcode/maserati/aokp/STOCK-JB-aokp_maserati_unofficial_Oct-18-12.zip
Haven't found a changelog. Anyone tried this on GSM yet. Does it work, or do we have to wait for Olegfusion to do his magic?
Click to expand...
Click to collapse
Hope in the changelog the earpiece volume is fixed, it is way too low. I end up having to put people on speaker phone just to hear them.
Just wanted to give this thread a bump and say THANK YOU to jsnweitzel for throwing these new builds out and feeding my crack flashing addiction!
Hi all,
I hope I can get some help here.
Yesterday I rebooted my S4 Active after I installed some app updates, and suddenly WIFI can't be enabled anymore.
First I thought the phone might be broken, but I tested a factory reset and WIFI works again.
But I don't want to reinstall all apps and lose app settings and so on. I also want to know what is causing this issue, it might happen again.
I am on official Stock Rom (Android 4.4.2) I9295XXUCNE5 I9295PHNCNE1. I am using this rom without any problems since a half year.
So I did some testing with adb and usb debugging, and for some reason the wifi kernel driver cannot be loaded. I tried loading it manually with:
Code:
insmod /system/lib/modules/dhd.ko
But this fails with:
Code:
insmod /system/lib/modules/dhd.ko
insmod: init_module '/system/lib/modules/dhd.ko' failed (Exec format error)
I looked into output of kmesg, and it shows this when trying to load the wifi module:
Code:
<3>[ 614.365997] QSEECOM: qsee_disable_clock_vote: Client error.Extra call to disable SFPB clk
<3>[ 614.362304] QSEECOM: qseecom_ioctl: Failed to vote for SFPB clock-6
<3>[ 614.362060] QSEECOM: qsee_vote_for_clock: SFPB Bandwidth req failed (-6)
<3>[ 614.361816] AXI: msm_bus_scale_client_update_request(): Client 3720895680 passed invalid index: 3
Again when I do a factory reset, WIFI works fine again, so it has to be a software bug somewhere.
After factory reset and working WiFi disable Play Store auto update.
Do one app update, test wifi, next app update, test WiFi,...
Easier to identify if an app is source of issue than do all in one update.
Not sure if insmod or other module related commands might need su credentials provided by rooting.
O-T said:
After factory reset and working WiFi disable Play Store auto update.
Do one app update, test wifi, next app update, test WiFi,...
Easier to identify if an app is source of issue than do all in one update.
Not sure if insmod or other module related commands might need su credentials provided by rooting.
Click to expand...
Click to collapse
That's kind of pain in the ass when you have like 100 apps installed
Well I know the last apps that got updated. But how can this damage wifi system driver? And yes insmod needs root , and my phone was NOT rooted prior this issue. I rooted it know in order to properly debug the problem.
best regards,
Andre
delta_ray said:
That's kind of pain in the ass when you have like 100 apps installed
Well I know the last apps that got updated. But how can this damage wifi system driver? And yes insmod needs root , and my phone was NOT rooted prior this issue. I rooted it know in order to properly debug the problem.
best regards,
Andre
Click to expand...
Click to collapse
Try flashing the NE5_PHN_wifi_150107.zip in CWM from the NE5 folder on my GDrive.
JASONRR said:
Try flashing the NE5_PHN_wifi_150107.zip in CWM from the NE5 folder on my GDrive.
Click to expand...
Click to collapse
Thanks I tried this. Unfortunately, the problem persists.
Do you know which files are used by the WIFI kernel module?
My guess is that some config file causes this problem.
delta_ray said:
Thanks I tried this. Unfortunately, the problem persists.
Do you know which files are used by the WIFI kernel module?
My guess is that some config file causes this problem.
Click to expand...
Click to collapse
Those are the files in the zip file. You can also try deleting data/misc/wifi/wpa_supplicant.conf and rebooting or even try deleting the entire folder.
You can also try my ROM, super WizCyan that is based on the PHN firmware with mostly S5 apps.
Can your rom installed without factory reset over stock rom?
A side note, Play Store also does not work anymore. I am online over LTE and can use Internet, but Play Store gets timeout while loading.
Some more debugoutput from logcat, but not helping much:
Code:
E/WifiHW ( 848): ##################### set firmware type 0 #####################
I/WifiHW ( 848): module is semco
E/WifiHW ( 848): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 848): ==========[WIFI] SEMCO MODULE ===========
E/WifiHW ( 848): return of insmod : ret = -1, Exec format error
If I just knew what is causing the driver fail.
delta_ray said:
Can your rom installed without factory reset over stock rom?
A side note, Play Store also does not work anymore. I am online over LTE and can use Internet, but Play Store gets timeout while loading.
Some more debugoutput from logcat, but not helping much:
Code:
E/WifiHW ( 848): ##################### set firmware type 0 #####################
I/WifiHW ( 848): module is semco
E/WifiHW ( 848): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 848): ==========[WIFI] SEMCO MODULE ===========
E/WifiHW ( 848): return of insmod : ret = -1, Exec format error
If I just knew what is causing the driver fail.
Click to expand...
Click to collapse
Unfortunately not, as most of the stock apps have been replaced by S5 apps. You can try but will get a lot of fc's. If you want to try without factory reset use super backup to backup calls, call logs, contacts and calendar and clear cache and data for these before flashing ROM as well as clear cache and dalvic and restore these after flashing the ROM.
Any specific reason why you do not want to wipe data. I always do it once in a couple of months and reconfigure all apps except for a couple of banking apps that I redtore with titanium backup to save the hassle of contacting the banks again. This helps to clear the clogginf od data and keep the phone smooth.
For playstore you can wipe cache and data for google play & play services and stop them from running.
---------- Post added at 01:20 PM ---------- Previous post was at 01:08 PM ----------
Did you try deleting data/misc/wifi/wpa_supplicant.conf and rebooting and/or deleting the entire data/misc/wifi folder
JASONRR said:
Any specific reason why you do not want to wipe data. I always do it once in a couple of months and reconfigure all apps except for a couple of banking apps that I redtore with titanium backup to save the hassle of contacting the banks again. This helps to clear the clogginf od data and keep the phone smooth.
For playstore you can wipe cache and data for google play & play services and stop them from running.
Click to expand...
Click to collapse
Just pure lazyness . But it seems like that I have to go for the factory reset and backup/restore all apps after.
However I hope to find the source of this issue, who knows when it will happen again.
delta_ray said:
Just pure lazyness . But it seems like that I have to go for the factory reset and backup/restore all apps after.
However I hope to find the source of this issue, who knows when it will happen again.
Click to expand...
Click to collapse
If it works after factory reset, then I would say there is corruption in data. Try deleting 'data/misc/wifi' folder flash the wifi zip and restart
I restored the /data/misc/wifi folder from an older working backup.
Still the same error, there must be something else causing the problem.
delta_ray said:
I restored the /data/misc/wifi folder from an older working backup.
Still the same error, there must be something else causing the problem.
Click to expand...
Click to collapse
I would suggest that you delete thd folder itself. Also you could try with the Ktoonez kernel from here
http://forum.xda-developers.com/showthread.php?p=51925641
delta_ray said:
I restored the /data/misc/wifi folder from an older working backup.
Still the same error, there must be something else causing the problem.
Click to expand...
Click to collapse
Have you changed LTE-modem (NON-HLOS.BIN) from what's in stock *NE5 ROM you informed in OP?
http://forum.xda-developers.com/showthread.php?p=56955843
O-T said:
Have you changed LTE-modem (NON-HLOS.BIN) from what's in stock *NE5 ROM you informed in OP?
http://forum.xda-developers.com/showthread.php?p=56955843
Click to expand...
Click to collapse
No haven't change LTE-Modem Software, still have the stock NE5 installed.
JASONRR said:
I would suggest that you delete thd folder itself. Also you could try with the Ktoonez kernel from here
http://forum.xda-developers.com/showthread.php?p=51925641
Click to expand...
Click to collapse
I guess I should get KT-SGS4-KK4.4-AOSP-jactive_eur-04.19.2014.zip?
This kernel works with my Stock 4.4.2 rom?
delta_ray said:
I guess I should get KT-SGS4-KK4.4-AOSP-jactive_eur-04.19.2014.zip?
This kernel works with my Stock 4.4.2 rom?
Click to expand...
Click to collapse
Not that one, get KT-SGS4-KK4.4-TW-eur-01.03.2015.zip, there is an issue with touchscreen which is being looked into, I am currently using KT-SGS4-KK4.4-TW-eur-01.09.2015_debug2.zip from the debug folder.
JASONRR said:
Not that one, get KT-SGS4-KK4.4-TW-eur-01.03.2015.zip, there is an issue with touchscreen which is being looked into, I am currently using KT-SGS4-KK4.4-TW-eur-01.09.2015_debug2.zip from the debug folder.
Click to expand...
Click to collapse
The kernel did not work on stock rom. Anyway I did another factory reset and restored most apps and settings using TitanBackup Root.
And guess what happened after restore of all the apps & settings?
WIFI is broken again.
Does somebody know all data files are used by WIFI?
delta_ray said:
The kernel did not work on stock rom. Anyway I did another factory reset and restored most apps and settings using TitanBackup Root.
And guess what happened after restore of all the apps & settings?
WIFI is broken again.
Does somebody know all data files are used by WIFI?
Click to expand...
Click to collapse
It seems that something in the settings is breaking the wifi. You can wipe the data of settings and wifi individually and check if it fixes the issue.
If you are doing factory reset, I always recommend to redo the settings again rather than restoring through TB.
Can you take a logcat and send the entire one to check if there is anything there.
Not sure if I mentioned it but I removed "wpa_supplicant.conf" multiple times, it doesn't solve the problem.
JASONRR said:
It seems that something in the settings is breaking the wifi. You can wipe the data of settings and wifi individually and check if it fixes the issue.
If you are doing factory reset, I always recommend to redo the settings again rather than restoring through TB.
Can you take a logcat and send the entire one to check if there is anything there.
Click to expand...
Click to collapse
How can I just reset WIFI settings?
Hi. When I changed in settings network mode to 2G only, signal icon started to flicker. After reboot I have no signal at all (it is impossible to call, send/receive SMS, use data connection etc.). In info (*#*#4636#*#*) preferred mode is set to "WCDMA preferred" and I cannot change it - I can chose another value from list but changes are not saved.
In settings phone says that none of SIM cards are inserted - but I can now access SIM 1 settings. However, everything is blocked and beneath the network type there is a description: "Invalid Network Mode (-1). Ignore.".
It happend when I was on latest official CM 13.0 nightly but this is probably not ROM's fault. Problem didn't disappear after clean flash, after restore or even after flashing whole set of images with official MiFlash tool.
After some research I found that setting ro.telephony.default_network from 22,22 to 10,10 should work, as 10 is for "LTE/GSM auto" when 22 is incorrect value. Separated by comma for two SIM slots. Ok, so I tried to edit build.prop with some apps without luck - access denied (rooted). I tried to mount system rw from Root explorer - nothing happens, still ro. From ADB - no, "dev/block/bootdevice/by-name/system is read-only". I even tried to change SELinux to permissive but still nothing
Every idea is welcome, I just need to get my phone to work as a phone again
Hi all,
After unlocking my phone which is a global version 64gb model, I had installed CM13. Wifi was working fine previously. After CM was installed I cannot get wifi to connect. It will show authentication failed and obtaining ip but won't obtain. It shows its mac address and scans wifi just fine. I can run wifi analyzers but it just won't connect. I have tried installing other roms, even installing the original roms and re-locking the device to stock with no success. I have reset my router and verified other devices can connect as well as trying other open wifi ssid's. I have also completely formating the whole phone and reinstalled roms from scratch, again no success. I have been searching through forums for about 2 weeks now and every recommendation has not worked. I love this phone but not having wifi is killing me. I am experiencing no other issues. One clue I do have which google is not providing answers to is the error i got when CM first installed and other times which i can't determine the scenarios to recreate which is
E:Unable to write to ums lunfile '/sys/module/g_android/parameters/file'
Unable to locate storage device.
Any help would be greatly appreciated.
Thanks Much
I have the same problem. I've installed CM 21.11 and gaaps stock via TWRP 3.0.2.0 and after this wi-fi can't authenticate. I did the same steps as topic starter and also tried different wi-fi settings in router and wi-fi without pass. Nothing helped
Please help! Any thoughts can be helpful.
I have exactly same issue as OP. I did everything like him and got no result.
Please help someone. I love my MI5 but i need wifi.
I have exactly the same issue and posted about it just a little earlier
http://forum.xda-developers.com/mi-5/help/wifi-connectivity-problem-t3517777
The difference being that the WiFi was working just fine even when I installed CM 13.1 for the first time. WiFi stopped to connect when I did a full Swipe in TWRP (all partitions).
It would be great if someone could help...
Try to give a chance to CM14.1 installed after a full wipe, I am using WiFi every day with wpa2 shared key and also radius auth 2.4 and. 5 GHz without problems and the overall performances are good
I have CM 14.1 at the moment and the problem is the same.
I'm no specialist but it doesn't seems to be a ROM related issue.
In this case I would try with stock MIUI after a full format and wipe, then in case of success again with CM14.1. Format is important because with encrypted data wipe isn't enough
matteo.gspace said:
In this case I would try with stock MIUI after a full format and wipe, then in case of success again with CM14.1. Format is important because with encrypted data wipe isn't enough
Click to expand...
Click to collapse
Thanks for your assistance.
Done that but didn't solve the issue...
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
I'm on MIUI EU 8.1.70 Nougat then i fastboot flash or recovery mode to MIUI Global 8.1.2.0 Marshmallow WIFI NOT WORK
But,
I managed to get the wifi working again with edl mode flashing with MIUI Global 8.1.20.
I will try to move to CM again, maybe this time wifi will work..
Wish me luck, will post the result later
RESULT:
Not Worked.
---------- Post added at 12:03 PM ---------- Previous post was at 11:23 AM ----------
Pekkuky said:
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
Click to expand...
Click to collapse
This method work, thanks a lot.
But, for me it's required a valid MAC-address
Pekkuky!
Thank you for your time sharing your knowledge on this topics many days old.
Awesome! You made my day. It work.
I just want to add my experience that might be useful for others.
I tried with a automatically generated MAC and it didn't work.
I followed your advice and repeated with a MAC address of an old e-reader and it worked instantly.
Thanks again!
Pekkuky, thanks a lot. Now I can use CM derived ROMs, great.
Later on after trying solution by Pekkuky, i have problem in turning on hotspot tethering and usb tethering. Anyone can confirm this or this is just me.
Hotspot tethering is working on mine. Before this fix it didn't.
Haven't tried usb tethering though.
Pekkuky said:
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
Click to expand...
Click to collapse
I was really thinking I would have to throw away the phone. Love for you, really, worked flawlessly. Used this website to generate a MAC http://www.miniwebtool.com/mac-address-generator/
Pekkuky said:
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
Click to expand...
Click to collapse
works like a charm
thanks mate, u saved my phone! :highfive:
using this website for generating an mac-adress too
http://www.miniwebtool.com/mac-address-generator/
Thanks Pekkuky for the trick. This problem appeared after flashing lineage os 14.1 using twrp. Then I tried different versions of global stable/developer roms (both fastboot and recovery) but nothing worked. Finally this trick worked Used the miniwebtool site for generating mac-address.
Hello,
Has anyone tried to modify the build.prop file on the OP10?
Like, audio.safemedia.bypass=true to remove the high volume warning (I don't know if it actually works)
If you know of any other cool lines to add feel free to share them here
Did you manage to edit it, I attempted however found the build.prop stops some access needed to allow r/w to the system
Line needed being:
ro.debuggable=1
So you want to add the line via
Magiskhide
you can add custom lines via terminal after the reboot
ALT Option
Flash
Mod
I didn't know about these solutions, I'm going to look into it.
Thanks
To save some time the first option , possibly due to how it loads the config does disable fingerprint. Assuming default setup.
(I did go in-depth with setting up the fingerprint details for the first module but for some reason the line to disable the audio warning just breaks it)
I did not try delayed as i kept trying all sorts of other options. The second however works with the fingerprint with no tweaks however i personally removed two lines for the stepping of the volume , keeping the line to disable the warning.
In summary, remove the first module if you have done it and experience the fingerprint issue, reboot twice to clear system cache, reinstall the first module but don't put in the custom line via terminal.
(leave setup in the zip as it won't be active till terminal activation, saves time)
Install the second module and reboot. You get safety net pass and the warning disabled.
I had to mess around with this as it was annoying me, i had missed the issue due to doing the pattern password then rebooting ect so i didn't realize the fingerprint issue till a hour later