Related
Long story short, I tinkered to much and was completely stupid and forgot to make a back up of my original wpa_supplicant file when I was attempting to get ad-hoc to work correctly. Now for the life of me I can not get the wifi on the device to even turn on. I have tried multiple wpa_supplicant files that claim they were supposed to be compatible with android 4.0.4. I have succesfully rooted the device (obviously had to be rooted to replace the file I lost) All in all this really isn't a horrible device for the price and really want to get the wifi on the device working again.
Does anyone have a stock wpa_supplicant file for android 4.0.4 that will work with my device, or does anyone have any helpful tips?
I would greatly appreciate anyones help. I could care less about ad-hoc now and just want my wifi to work. lol
Oh and yes I did set the correct permissions on the files I have attempted use in root explorer.
nkemm2 said:
Long story short, I tinkered to much and was completely stupid and forgot to make a back up of my original wpa_supplicant file when I was attempting to get ad-hoc to work correctly. Now for the life of me I can not get the wifi on the device to even turn on. I have tried multiple wpa_supplicant files that claim they were supposed to be compatible with android 4.0.4. I have succesfully rooted the device (obviously had to be rooted to replace the file I lost) All in all this really isn't a horrible device for the price and really want to get the wifi on the device working again.
Does anyone have a stock wpa_supplicant file for android 4.0.4 that will work with my device, or does anyone have any helpful tips?
I would greatly appreciate anyones help. I could care less about ad-hoc now and just want my wifi to work. lol
Oh and yes I did set the correct permissions on the files I have attempted use in root explorer.
Click to expand...
Click to collapse
Just for clarification purposes I have the device they are referring to in this thread: http://forum.xda-developers.com/showthread.php?t=1954572
Beyond a working wpa supplicant file I guess another option for my device would be flashing a rom onto it but I haven't been able to find any solid information on this. I'm assuming time will tell, eventually someone will figure something out with this device.
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
After trying for a few weeks now, I've still had no success. One idea has come to me though- installing a rom. Would downloading a custom ROM change my hosts file? Also, if so, could anyone recommend one that is similar to default android? One last idea that I've got at the moment is sonehow completely wiping the hard drive of the phone and reinstalling androud on it, though I have no idea whether that is even possible, and if so, how to do it. I would really appreciate some help here!
Thanks again,
Louis
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
J2270A said:
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
Click to expand...
Click to collapse
I'm not entirely sure I understand you here, but I'll try. What would unlocking the bootloader do to my phone? Would it enable r/w on the system folder? Also, what is a reflash of the system image? How would I do that?
I'll try these things if I can, but would still appreciate help.
Look around on http://wiki.cyanogenmod.org/w/Basic_concepts?
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
J2270A said:
Look around on [I can't post urls yet ]
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
Click to expand...
Click to collapse
Ok, so from what I can work out, cyanogen does not support my device. Would doing it for a similar device work? Are there any ROMs that support my device?
under the line, restoring the phone via the official ways actually just wipes the user data, not including the HOSTS file which is what I need to wipe. What I really need it is basically a ROM that completely wipes my phone and reinstalls some version of android.
Any other ideas?
While there may not be official support for a phone for a custom ROM, you may be able to find unofficial ports/versions if you search for it in the forums.
From what I know, a system reinstall via official methods wipes data and almost everything else, then downloads from its servers system files to be installed to the phone. At least, my phone was reverted to a stock ROM when I restored it after using a custom ROM. It may be different for some, but generally, this is what I think.
Important: only use a ROM made for your device model only, do not use the ones made for a similar phone, the small differences are no longer small in this case and will cause a system error(?)
Generally, once you have successfully unlocked boot loader using a method for your phone, the instructions afterwards are generally the same for all phones. You'll be able to get better answers in the threads specifically for your phone, so try to look for one and look for the already tried methods,
Here's one:
<You'll need to quote to copy link>
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Ish Takkar said:
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Click to expand...
Click to collapse
I have this problem with my S3 and I always delete the "hosts" file! I should find witch process make this file!!
after I came across many amendments on my phone (j7p)
twrp ,root, xsposed, Nonencrypt kernel,deleting systemapps.....
i found that my phone doesnot remeber my wifi paswword /ssid
after each reboot , also after disconnect & connect to wifi ....
I could not determine the cause of the problem.
I restored my efs via twrp, but the problem still present
so i came to a temporary solution, and i posted here in order to be helpfull to others
or if someone have a better solution... so he can guid us
first off all backup your efs and keep it in safe place
now open your phone buildprop it is in your root/system ( you should have root access,afaik) via (buildprop edditor or totalcommander..or other
then scroll down to that string
ro.securestorage.support=true
change the value into false
ro.securestorage.support=false
save it and enter your wifi info...again
try to reboot your phone.. if the problem Disappeared, then it is secure storage issue
here i donot have a specific solution ,since i use a moded kernel
but maybe you can get ride of it by deleting ss-data in efs folder (via total-commander .apk or es file explorer.apk ...)
this file contains decryption of your wifi passwords..., and other
the problem will disappear untill you flash new thing from recovery
here you can take another backup of your efs beside the original one, and give it ashot from recovery after you make Major modification
at last I hope some of Veteran members give us better idea
Thanks a lot. By the way, can you use your front flash with the modded kernel?
It's not working for me.
I don't use it but i want to know if it's an issue with the kernel or i messed up a step somewhere.
Zhiro90 said:
Thanks a lot. By the way, can you use your front flash with the modded kernel?
It's not working for me.
I don't use it but i want to know if it's an issue with the kernel or i messed up a step somewhere.
Click to expand...
Click to collapse
sorry for my late reply
j7P doesn't have separate front flash (led) ....afaik
the screen only turn into white when you are using front flash cam
as for me I updated my J7p firmware ...so I am using stock kernel at now
BTW there is no need to modded kernel if U use USBotg pendrive
in clear steps from stock firmware u install twrp via odin
then U can root your phone , put supersu *zip in USBotg pendrive
attach it to your phone, mount this USB in twrp then flash any *zip file... such as SuperSU,,, and then you can install xposed ....
so there is no need to modded kernel , unless you need to get backups for your phone
Regards
Bootup password
I cant change ro.securestorage.support value to false... triggers bootup password then it rejects all password, cant get through... I then have to restore my build.prop and give up
nazgul67 said:
I cant change ro.securestorage.support value to true... triggers bootup password then it rejects all password, cant get through... I then have to restore my build.prop and give up
Click to expand...
Click to collapse
you should set it to false
not true
My bad, i mean setting it false. Then some bootup password is required.
nazgul67 said:
My bad, i mean setting it false. Then some bootup password is required.
Click to expand...
Click to collapse
NM
since the problem still presnet , so i think it is not secure storage issue
any how there is a new domed kernel without this issue (remembering wifi password)
give it a shot
https://forum.xda-developers.com/ga...el-theflash-kernel-v1-0-t3616374#post72618392
Regards
xcorona said:
NM
since the problem still presnet , so i think it is not secure storage issue
any how there is a new domed kernel without this issue (remembering wifi password)
give it a shot
https://forum.xda-developers.com/ga...el-theflash-kernel-v1-0-t3616374#post72618392
Regards
Click to expand...
Click to collapse
Im using default ROM and Kernel. I can see wifi passwords now. One of my apps is setting my selinux to permissive I dont know which is it. Maybe its because of my root, im just thankful for it ?
My phone so far:
SM-A320FL with the current stock Android 8.0 DBT. Flashed with Odin3.
Magisk 18.1 thx topjohnwu
[*]Xposed 90 beta 3 thx rovo89
Xposed systemless over Magisk module "Xposed Framework"
TWRP 3.2.3 for SM-A320 thx McFy
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
I also encountered the following problem which I found a solution for:
After every reboot all of the paired Bluetooth devices are lost. I had to pair them again. Pretty annoying, especially the pairing with my car.
After searching around I found the solution within a Xposed thread, which I adapted to my phone.
There are two ways to solve this problem.
You lose all of your saved Wifi passwords and you need to pair all Bluetooth devices again.
First Method:
Go into Magisk and look for the module:
libsecure_storage companion for rooted Samsung devices
Follow the instructions that are given with the module. It works fine with my SM-A320FL.
Second Method:
First of all you need ROOT access and a root explorer (e.g. ES File Explorer) on your phone. You also lose all of your saved Wifi passwords.
Every time you do something on your phone make a BACKUP
Download the file at the bottom
Extract the Zip file to your hard drive
Copy the extracted system folder to your SD card
Copy the four files (2x libsecure_storage.so and 2x libsecure_storage_jni.so) within the subfolders (lib and lib64) to their respectable positions. The folders lib and lib64 are found in the systems folder on your phone. I didn't need to override any files.
Add the following line at the bottom of the build.prop file (system folder):
Code:
ro.securestorage.support=false
Reboot
Now the paired Bluetooth devices should stay paired.
I had to delete all Wifi connections and enter the password again to get them going. That's because the Wifi passwords are stored encrypted.
simple_s said:
My phone so far:
SM-A320FL with the current stock Android 8.0 DBT rom. Flashed with Odin3.
Magisk 16.4 thx topjohnwu
Xposed 90 beta 3 thx rovo89
TWRP 3.2.1 for SM-A320 thx McFy
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
I also encountered the following problem which I found a solution for:
After every reboot all of the paired Bluetooth devices are lost. I had to pair them again. Pretty annoying, especially the pairing with my car.
After searching around I found the solution within a Xposed thread, which I adapted to my phone.
To solve the problem I did the following steps:
First of all you need ROOT access to your phone. You also lose all of your saved Wifi passwords.
Every time you do something on your phone make a BACKUP
Download the file at the bottom
Extract the Zip file to your hard drive
Copy the extracted system folder to your SD card
Copy the four files (2x libsecure_storage.so and 2x libsecure_storage_jni.so) within the subfolders (lib and lib64) to their respectable positions. The folders lib and lib64 are found in the systems folder on your phone. I didn't need to override any files.
Add the following line at the bottom of the build.prop file (system folder):
Code:
ro.securestorage.support=false
Reboot
Now the paired Bluetooth devices should stay paired.
I had to delete all Wifi connections and enter the password again to get them going. This is because the Wifi passwords are stored encrypted.
Click to expand...
Click to collapse
cool, i mean nice fix...working also on s9+
thx for this
Working here too!
Galaxy S9 with Magisk root.
Installed Xposed v90-beta3 yesterday, problem that BT connections were gone. Also WIFI passwords were incorrect. Not a problem that I had to re-enter WIFI passwords, but BT connections were gone each (re)boot.
This fixed the problem.
Thnx!
Deleted
Thanks works for my S9
Ok, I noticed that you said \system\lib and \system\lib64
And no overwrite is required because they don't exist...
That's because the files are actually in \system\vendor\lib and \system\vendor\lib64
The question is...
As you mentioned, no overwrite while on github says place them in their respective location... Which path is the right path...
I used Vendor, before I found this thread...
Because I simply searched for the file name...
Dante63 said:
Ok, I noticed that you said \system\lib and \system\lib64
And no overwrite is required because they don't exist...
That's because the files are actually in \system\vendor\lib and \system\vendor\lib64
The question is...
As you mentioned, no overwrite while on github says place them in their respective location... Which path is the right path...
I used Vendor, before I found this thread...
Because I simply searched for the file name...
Click to expand...
Click to collapse
I put the files in system / lib
And but pairing stays now
Alex-V said:
I put the files in system / lib
And but pairing stays now
Click to expand...
Click to collapse
Same, pairings stay for system vendor lib...
Maybe as long it's lib, doesn't matter which one ?
Deleting WIFI Passwords is not mandatory (at least for me). I had to reinstall Xposed and clear Cache (not Dalvik/ART) in order to get it working again. Without reinstalling Xposed and clearing cache the lib files got deleted every reboot.
Thanks.
For S7e with Oreo, beside forgetting paired devices on every bluetooth off/on, enabling bluetooth took noticeably longer time.
Placing libs in /system/lib and /system/lib64 did not work (build.prop edited, of course), placing them in /system/vendor/lib and /system/vendor/lib64 helped.
Is there a way to avoid replacing the files? On the xposed issue page (https://github.com/rovo89/Xposed/issues/294) ahronshor mentions backing up /data/system/secure_storage/com.android.bluetooth/, and then copying it back in place. Maybe that's the way to go, provided you are before rooting a freshly installed original firmware.
Another thing. I have flashed a new firmware (G935FXXS3ERKE), then flashed TWRP back even before rebooting. Then booted to TWRP and installed "remove encryption.zip", SuperSU and xposed, and finally booted the system (for the first time after update).
Bluetooth works now, on new firmware's original libraries and build.prop (btw, .so files are identical with previous G935FXXS3ERJ2, build.prop has just dates and versions changed). Off/on, restart - paired devices stay where they should, bluetooth enable time as usual.
Maybe the libsecure_storage.so patch (jnl was not modified at all) was to stop trying to read encrypted bluetooth data and to create an unencrypted container. It seems once the Bluetooth data file on /data is unencrypted, original code manages it correctly.
Thanks! Works on Note 9 Oreo 8.1
Reporting this solved my problems on J7 2017 with Oreo 8.1. Magisk 18 and Xposed. Thanks.
simple_s said:
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
Click to expand...
Click to collapse
How did you solve the backup problem? I also can't make backup. It gives me some error.
The BT problem is solved. Note 9.
There is a magisk module that can do the trick without need to xposed.
Sent from my SM-N960F using Tapatalk
is there a way to fix the issue on stock 8.0 (last update december 2018 patch) without rooting?
It happens to me during last month...
thanks!
Ninolina said:
How did you solve the backup problem? I also can't make backup. It gives me some error.
The BT problem is solved. Note 9.
Click to expand...
Click to collapse
I couldn't solve it.
iltoffa said:
is there a way to fix the issue on stock 8.0 (last update december 2018 patch) without rooting?
It happens to me during last month...
thanks!
Click to expand...
Click to collapse
I don't think so.
I added new informations to the guide.
Apparently there is a Magisk module for some phones who does the same thing. You find it in Magisk under
libsecure_storage companion for rooted Samsung devices
It works perfect on my SM-A320FL.
My personal solution has been to remove IFTTT which was installed. From that, no disconnections found at all
(I posted this on the Android Mods Thread on accedent)I have a LG Nexus 5 HammerHead and tried to flash the newest Kali NetHunter using TWRP 3.5.2. After I flashed the ROM successfully, I have notice that the phone itself says no wifi networks found when swipe down to look at the wifi connections. I go to the wifi settings it says "Searching for wifi networks" with a spinning wheel of death(the loading icon). I've tried configuring it to use 2.4 Mhrz and didn't work, set it up to where it would only find good connections and still didn't work, I even did a factory reset and actually made it worse. I even reflashed it and see if that fixed it, nope. I connected it to the internet using a Ethernet adapter that is made for phones using a micro USB connection, updated the apps, updated and upgraded Kali NetHunter itself in the terminal and wifi connections is still not finding any connections at all. Could It be that Kali NetHunter doesn't support the internal wifi card that is built into my phone, could it be that twrp is having some errors on their end, or is it a bug that Offensive Security is not aware about? Please Help?
This may happen cos of wi-fi firmware. These files are called fw_bcmdhd.bin and fw_bcmdhd_apsta.bin. There are two versions of firmware:
1. https://github.com/LineageOS/androi...c531cd30abd21d93c5a04/bcmdhd/firmware/bcm4339
2. https://github.com/LineageOS/androi...5f8949fe77780d922c973/bcmdhd/firmware/bcm4339
You need to find where these files are stored in your rom, replace them with files from version 1 or version 2, restore permissions for these files if necessary and reboot your phone.
z3DD3r said:
This may happen cos of wi-fi firmware. These files are called fw_bcmdhd.bin and fw_bcmdhd_apsta.bin. There are two versions of firmware:
1. https://github.com/LineageOS/androi...c531cd30abd21d93c5a04/bcmdhd/firmware/bcm4339
2. https://github.com/LineageOS/androi...5f8949fe77780d922c973/bcmdhd/firmware/bcm4339
You need to find where these files are stored in your rom, replace them with files from version 1 or version 2, restore permissions for these files if necessary and reboot your phone.
Click to expand...
Click to collapse
Honestly, I have been trying to find these files and can't seem to find them. I even put the file name on the search bar of my windows 10 and it can't find them either. I think its just missing firmware on Offensive Security's end in this situation. I've had a troublesome experience with their kali linux products such as kali linux itself on having missing firmware after installation. Thank you for helping me out and hopefully these files should do the trick after I re-flash NetHunter with the firmware you have provided. As a matter of fact would the files belong in the firmware folder?
Martisabolt said:
Honestly, I have been trying to find these files and can't seem to find them. I even put the file name on the search bar of my windows 10 and it can't find them either. I think its just missing firmware on Offensive Security's end in this situation. I've had a troublesome experience with their kali linux products such as kali linux itself on having missing firmware after installation. Thank you for helping me out and hopefully these files should do the trick after I re-flash NetHunter with the firmware you have provided. As a matter of fact would the files belong in the firmware folder?
Click to expand...
Click to collapse
You will not find them in the search bar of your windows)
And no, firmware is not missed. Without wi-fi firmware you will be unable to enable Wi-Fi at all. In your case Wi-Fi can be enabled but you didn't see any networks.
Also /firmware - is incorrect place. It is a mount point of the /modem partition.
Wi-Fi firmware can be located at /system/firmware or /system/vendor/firmware/. Try to find them in TWRP. Boot into TWRP, mount System partition, open File Manager and review all the paths i've listed here. But i can't be sure cos i've never used Kali NetHunter.
z3DD3r said:
You will not find them in the search bar of your windows)
And no, firmware is not missed. Without wi-fi firmware you will be unable to enable Wi-Fi at all. In your case Wi-Fi can be enabled but you didn't see any networks.
Also /firmware - is incorrect place. It is a mount point of the /modem partition.
Wi-Fi firmware can be located at /system/firmware or /system/vendor/firmware/. Try to find them in TWRP. Boot into TWRP, mount System partition, open File Manager and review all the paths i've listed here. But i can't be sure cos i've never used Kali NetHunter.
Click to expand...
Click to collapse
Ok, I've been to those locations and in the system's folder, no firmware folder. However, in the sys folder, there is and does not show any firmware files in TWRP.
Give me the links to ROM files u flashed
This came directly from kali.org.
What was your base ROM before installing Kali? Stock Android 6.0.1?
yes
Well, Wi-Fi firmware in stock android 6.0.1 is located at /system/vendor/firmware/ folder. I've looked in the kali installer script and didn't find any scripts which can modify or delete this firmware. So we can try to install different firmwares into stock folders. I've attached 2 flashable zips for you. Try the -DHD version first. Flash it in TWRP and reboot your phone. If it doesn't help, then try -STOCK version.
It this will not help then i'm out of options
z3DD3r said:
Well, Wi-Fi firmware in stock android 6.0.1 is located at /system/vendor/firmware/ folder. I've looked in the kali installer script and didn't find any scripts which can modify or delete this firmware. So we can try to install different firmwares into stock folders. I've attached 2 flashable zips for you. Try the -DHD version first. Flash it in TWRP and reboot your phone. If it doesn't help, then try -STOCK version.
It this will not help then i'm out of options
Click to expand...
Click to collapse
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Martisabolt said:
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Click to expand...
Click to collapse
Don't hurry to kill your phone) Try to revert to complete stock 6.0.1 and re-lock bootloader by this instruction:
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
How to flash a factory image | Return to stock | Unroot your Nexus 5 Hello Nexus 5 Users! I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to...
forum.xda-developers.com
And if your wi-fi will not work then yes, something bad happened with hardware
z3DD3r said:
Don't hurry to kill your phone
Click to expand...
Click to collapse
I tried both packages and thery didn't break my ROM. Unhappily they did not help.
I use the Re4son Kernel and can set wlan0 to monitor mode. But airodump is blind then.
@r.mutt @Martisabolt
Hammerhead kernel source (Marshmallow)
These are the complete Nexmon files seperately arranged.
Either you use a proper file manager with root permission, or just use the TWRP fiile manager and insert/copy them into the according sections.Maybe set the correct permission, while you're there and of course know your stuff. :>
Martisabolt said:
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Click to expand...
Click to collapse
Hi Mate, Sorry for the delayed reply. Now i can afford nexus 5. Faced same issue as you. Thanks @z3DD3r for the hint.
Follow below instruction If you want wifi.
*Boot to Twrp
*locate /advanced/filemanager/vendor/firmware
You are there
(Note: 100% you can't see the files as discussed in above thread. But those are hidden(while installing nexmon from nethunter store i have seen those already exists in same folder))
*At bottom you see permisson blue box
*Click the same-select chmod 755-swipe to confirm
Now reboot to system. Here you go.