Hey everyone here at XDA, just wanted to share my recent experience with loosing my phone service after flashing MIUI from the clockwork rom manager app. Basically, i flashed the rom from within the rom manager app and really liked the rom until I noticed that I had lost data and phone service. Apparently I was stuck in roaming, with a little triangle replacing the 4g icon in the notification bar at the top of the screen. I did a bunch of searching through forums and everyone who was having this issue was having it due to the loss of there IMEI. The people afflicted by loss of service did not have the correct IMEI or any at all on their phone.
But my IMEI was there and it was correct. So I restored the nandroid backup I made at the time of flashing MIUI but that didn't solve the issue so I restored the backup I made when I originally rooted my phone and installed CWM. That still didn't fix it. Some forum posts were saying the SIM card might have been fried, some were saying that they had totally lost the ERI folder, or something... I was getting worried. The last thing I tried was flashing a stock 4.1.1 rom via Odin and still I had no service. Well I needed a phone for work so I went on the VZW site Monday morning and switched my service to an old blackberry storm (I know, right?) that I had laying around and went to work. When I got home I looked on the web some more and found info about accessing the hidden menu with a code that wipes all data and settings. Is this different than the factory wipe from the settings menu? Anyway I wiped via the hidden menu and after that the little roaming triangle was gone. I switched my service back to the Gs3, which involved taking out the SIM card and registering it again, and after that my service, data, and 4g icon was back. Problem solved. I am wondering though if I could have used the hidden menu/wipe feature from MIUI, and for that matter what caused my phone to get stuck in roaming?
I would like to root, and explore other roms but now I'm worried about this happening again. It doesn't help that someone told me service providers can deny service for rooting your phone. I don't know if that's true or not. I know now that I should make a IMEI backup, even though I don't think that was my problem. I recently took the ota and am back on stock 4.1.2. Just wanted to share this with everyone, and bounce it around to see if anyone has any ideas, and maybe this could help someone who is having the same issue. As far as the hidden menu and wipe code, I don't remember what it was but you could look it up if you need to try it.
Thanks everyone
mattunden said:
Hey everyone here at XDA, just wanted to share my recent experience with loosing my phone service after flashing MIUI from the clockwork rom manager app. Basically, i flashed the rom from within the rom manager app and really liked the rom until I noticed that I had lost data and phone service. Apparently I was stuck in roaming, with a little triangle replacing the 4g icon in the notification bar at the top of the screen. I did a bunch of searching through forums and everyone who was having this issue was having it due to the loss of there IMEI. The people afflicted by loss of service did not have the correct IMEI or any at all on their phone.
But my IMEI was there and it was correct. So I restored the nandroid backup I made at the time of flashing MIUI but that didn't solve the issue so I restored the backup I made when I originally rooted my phone and installed CWM. That still didn't fix it. Some forum posts were saying the SIM card might have been fried, some were saying that they had totally lost the ERI folder, or something... I was getting worried. The last thing I tried was flashing a stock 4.1.1 rom via Odin and still I had no service. Well I needed a phone for work so I went on the VZW site Monday morning and switched my service to an old blackberry storm (I know, right?) that I had laying around and went to work. When I got home I looked on the web some more and found info about accessing the hidden menu with a code that wipes all data and settings. Is this different than the factory wipe from the settings menu? Anyway I wiped via the hidden menu and after that the little roaming triangle was gone. I switched my service back to the Gs3, which involved taking out the SIM card and registering it again, and after that my service, data, and 4g icon was back. Problem solved. I am wondering though if I could have used the hidden menu/wipe feature from MIUI, and for that matter what caused my phone to get stuck in roaming?
I would like to root, and explore other roms but now I'm worried about this happening again. It doesn't help that someone told me service providers can deny service for rooting your phone. I don't know if that's true or not. I know now that I should make a IMEI backup, even though I don't think that was my problem. I recently took the ota and am back on stock 4.1.2. Just wanted to share this with everyone, and bounce it around to see if anyone has any ideas, and maybe this could help someone who is having the same issue. As far as the hidden menu and wipe code, I don't remember what it was but you could look it up if you need to try it.
Thanks everyone
Click to expand...
Click to collapse
My suggestion, never use Rom Manager to flash!! Stick to TWRP(I prefer twrp), CWM or Odin.
Long story short, my phone was stuck in a bootloop and I wasn't able to format the phone/cache partition through recovery mode, and had to restore or something onto the phone (following this tutorial, I'm not really an expert with this type of stuff to be honest so I don't even 100% know what it is I did), which worked, however, even though my phone was formatted, it booted with Lollipop 5.0.2 (I'm probably being dumb, but I wasn't really expecting this when I restored to "stock firmware"), AND kept the wallpaper I had before the phone was stuck in bootloop, and to my knowledge I didn't back it up anywhere or anything, so I don't know if the phones been fully formatted (I've done it several times today) or what.
But since I've restored my phone, my operating network just doesn't work, like the title says. I can't make calls or texts, nor can I receive any, and the data doesn't work. The status of my phone says that it's "out of service", can't detect my network etc, with any SIM card I put in the phone. I've read somewhere that it might be something to do with the modemst1/modemst2 files or something that I flashed when restoring my phone, but honestly I don't fully know what to do and everything I read seems to be different.
If anybody knows what I can do to sort this out it would be absolutely awesome and much appreciated. Cheers!
Hello everyone.
I recently attempted to install a custom kernel (ElementalX) on my Nexus 5 D820. During this process, I encountered a bootloop while installing TWRP, which is probably the event that has caused the nightmare my phone has been in the past few weeks. Essentially, ever since then, LTE has not been working on my phone, and the rest of the cellular connectivity has been quite bad. Actually, LTE does work, but only for about 10 minutes. After this, if it is turned on, it will crash ALL cellular connectivity, including phone calls and texts, until I turn it off.
Initially, I believed that the custom kernel was the cause. I therefore flashed stock ROM back, thinking it would solve the problem (spoiler alert: it didn't). I then tried flashing many different stock ROMs, from KitKat to Lollipop and pretty much any variety of Marshmallow offered. This still didn't fix the problem. After this, I tried flashing individual radios from http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095, which still did not fix the problem.
I then realized that the problem wasn't in any of the files normally affected by flashing a new ROM and started reading up on the EFS partition. From what I can gather so far on my phone, I believe that I have a slightly corrupted EFS partition and that this is causing the stability issues on my phone. I tried restoring from a good qcn file as suggested here http://forum.xda-developers.com/goo...efs-backup-t2769023/post60421668#post60421668 and that has still not fixed my problem. I tried about 4 or 5 different qcn files, restoring in different order, wiping the block partitions like suggested here http://forum.xda-developers.com/lg-g3/general/request-3g-2g-lte-d850-t3300908 and that still didn't work.
But I didn't give up just there! I read from this post http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059 that you could edit NV items individually and figured that maybe I could try to edit the LTE NV items to their default values. Turns out, they were at their default values and they are fine.
At this point, I thought I had tried everything, but while attempting an NV item backup using Qualcomm NV Tools in EFS professional, I noticed an odd error that kept happening. All of the NV items would back up properly, BUT, the backup process would crash for NV items 33799 to 33802 and 33810 to 33812, every time, no matter what. Also, exactly when I tried reading these NV items, the phone cellular network goes down for about 10 seconds, as it normally does when LTE is activated. I therefore believe that these NV items may be corrupt and that cellular network stops working whenever they are read, which for some reason only occurs when LTE is turned on (I'm far from an expert in this field, correct me if what I'm saying makes no sense).
At this point, I've pretty much given up on fixing the phone, but thought I would reach out to xda-devs to see if anyone had any experience with this. Not having LTE is not a huge deal, but I would be quite happy if I could bring it back.
What I'm asking: If anybody with a Nexus 5 D820 could try doing an NV Backup using Qualcomm NV Tools and see if NV items 33799 to 33802 and 33810 to 33812 crash their phone, that would be much appreciated. If I know at least that this is a problem unique to my phone, it can point me in the right direction. On the other hand, if it's widespread across Nexus 5 devices, my problem may be something else completely.
What I'd really, really, really appreciate: If a kind soul could give me a full EFS backup of their working phone, I would be extremely grateful. I'm pretty sure that this would fix all my problems, and I would be forever grateful to the kind person that does this. Of course, you may wipe your ESN/MEID/IMEI before sending the file.
tl;dr
LTE doesn't work since flashing kernel. Probably corrupt EFS partition. If some can check if NV items 33799 to 33802 and 33810 to 33812 can be backed up on Qualcomm NV Tools, that would be great. If someone can send me a full EFS backup of their Nexus 5, that would be amazing.
I dont know if it is still relevant for you but i got the same issue..
I got two Nexus 5 D821 (dont ask why two of them )
Wanted to move a full backup from the first one to the second...
I didnt know about the efs partition and what it is so i also told twrp to backup it from my first device too... and restoring it on the second device screwed my imei (showed 0)...
SO DO NOT BACKUP EFS ON ONE PHONE AND MOVE WITH IT TO ANOTHER ONE!!!! EVEN IF IT IS THE SAME PHONE TYPE!!!!
I managed to get my imei back somehow with editing NV items, restoring backups from QPST files and so on... (Worked at least 20 hours so far)
The only advantage that I have is that the first phone i came from is still untouched on his efs, so i try to backup the nv data and got the same errors as you!
I am currently working on this and got the same errors backing up nv items from the untouched nexus...
So probably thats not the problem, just skip these values and try to restore the nv as parts
If you need the nv backups you can contact me at [email protected]
Perhaps I am able to help
Brother, did you solve the problem?
Hi,
My Samsung Galaxy Note 2 is rooted for couple of years. Currently running AICP ROM, Version 12.1-NIGHTLY. TWRP is installed and functional.
Couple of weeks back the phone stopped connecting to cellular networks. The SIM Card is not defective - it is working on another phone. (Even on this phone, the operator is recognised, but the signal strength is always zero.)
Otherwise the phone (?) is working fine. I can connect to WiFi and all other Apps works fine.
On checking for IMEI, it is showing fake IMEI - 004999010540000. This is not what is printed in the battery compartment. The EFS Partition is empty.
Samsung Service centre has suggested replacement of the motherboard. The cost is prohibitive factor.
I had a nandroid backup of the original ROM, however, the microSD Card has become corrupt and the backup is lost. (Original EFS Partition is no more available.)
I tried to connect the phone to ODIN/Samsung Kies, however, the phone is not connecting to these softwares. (I can browse the phone through file explorers on my computer and also copy-paste files.)
Is there some way in which I can restore the phone to working state? Or, I need to change the motherboard - as Samsung Service has indicated?
Thanks.
Vikas Garud
THE ORIGIN OF THE ISSUE:
Everything began 1 month ago. I was using my Nexus 5 like I always did. I had my WiFi turned on because I was chatting with my friends on Instagram and I left my smartphone charging. There were notifications and the notification light turned on showing me that I had two texts from Instagram app. When I tried to turn it on the screen, I pressed the power button, but the screen did not turn on. I pressed the power button again and again and again, but still the same. I tried to force-reboot my device and that's what I did. When the screen started again, my WiFi was stuck at "turning WiFi on...", also, my Bluetooth was not working properly too, because when I tried to turn it on, it automatically turned back off.
ATTEMPT TO FIX #1:
First thing I tried was unrooting and reinstalling stock using Nexus Root Toolkit. That didn't work... I tried doing a simple factory reset from the phone settings, also didn't work...
After those fails, I noticed that my MAC address was corrupted, showing this: 02:00:00:00:00:00 so I searched the Internet for stuff related to this MAC address error and found people with similar problem just like mine. I found solutions like deleting /persist/wifi folder (my friend did not recommended me to do so after I did this). So, I did the thing, AND IT DID NOT HELP. Tried returning to stock using Nexus Root Toolkit AND IT DID NOT HELP. I had an idea to delete my entire system using TWRP and I thought that reinstalling it would fix the problem. But I was noob at the moment, didn't know how to flash after deleting it. Anyway, I went on, and deleted system, but I didn't know how to reinstall and I was without a smartphone for 3 weeks. I was sooooooooo sad cause this was the worst issue I had to deal with... No smartphone... No WiFi.... life sucks (still does, I am sooo depressed for a stupid smartphone)... Well, obviously, NOTHING HELPED.
ATTEMPT TO FIX #2:
After those 3 weeks, I finally managed to find a way to reinstall OS on my smartphone again (using Nexus 5 factory image found in Google site for developers). I was sooo happy because at least I managed to turn the smartphone back on. So, step two was to check if WiFi worked. Well... not as I expected things to be. It didn't work... Obviously... Well, after doing simple experiments, I tried to do "the thing again". After deleting file .macaddr from /persist/wifi folder, without deleting the folder, only the file, WiFi turned back on!!! I went in tears thanking God. Sooooo much happiness!!! I desided to insert WiFi APs that I prevously saved in a wpa_supplicant.conf file, and guess what.... I F***** UP WIFI AND SENSORS!!! I was sooooo mad!
ATTEMPT TO FIX #3:
Well, the next day, I attempted to do a system delete again, but this time, I used another computer device, my family laptop. I deleted system, and this time, I didn't flash anything using Nexus Root Toolkit, but I used this Nexus 5 factory image again. WIFI WAS BACK ON!!! YEESSS!!! I was crying soooo hard!! I again thanked God!!! But it didn't last long... After two days, I turned on my WiFi to check my messages from Instagram, sadly, my WiFi was again stuck on "turning WiFi on..." and my smartphone rebooted by itself (again). So... guess what. I DEAR YOU TO GUESS WHAT HAPPENED NEXT!!! MAC address was back to this STUPID 02:00:00:00:00:00. I had enouch. I installed Termux, I installed a packet called "macchanger" and tried to change my MAC address to something random. I used command "macchanger -r wlan0" and I rebooted. This changed my MAC address to something random. Now, WiFi turns on and when I open an application to use WiFi with, it turns off immediatelly... Also, my MAC address is on changing again with command "macchanger -r wlan0" and is stuck in the previous randomized MAC address. Using "macchanger" command, I also noticed that my "permanent" MAC address is now: 00:00:00:00:00:00 (something that was never valid).
WHAT DO I DO?
DO I NEED TO BUY A NEW SMARTPHONE BECAUSE THIS ONE IS PRETTY F***** UP?
DO I NEED TO REPLACE THE ENTIRE MOTHERBOARD?
IS THIS EVEN A HARDWARE ISSUE?
IS THIS A SOFTWARE ISSUE?
DO I NEED TO REPLACE FIRMWARE? IF SO, HOW DO I DO THAT?
DOES THIS HAVE SOMETHING TO DO WITH /PERSIST?
WHAT DO YOU PROPOSE? BECAUSE I AM TIRED OF THIS STORY, REALLY...
SPECIAL URL: https://forum.xda-developers.com/t/...y-are-and-how-to-get-it-back-if-lost.3307793/
Retr0.Hacker said:
THE ORIGIN OF THE ISSUE:
Everything began 1 month ago. I was using my Nexus 5 like I always did. I had my WiFi turned on because I was chatting with my friends on Instagram and I left my smartphone charging. There were notifications and the notification light turned on showing me that I had two texts from Instagram app. When I tried to turn it on the screen, I pressed the power button, but the screen did not turn on. I pressed the power button again and again and again, but still the same. I tried to force-reboot my device and that's what I did. When the screen started again, my WiFi was stuck at "turning WiFi on...", also, my Bluetooth was not working properly too, because when I tried to turn it on, it automatically turned back off.
ATTEMPT TO FIX #1:
First thing I tried was unrooting and reinstalling stock using Nexus Root Toolkit. That didn't work... I tried doing a simple factory reset from the phone settings, also didn't work...
After those fails, I noticed that my MAC address was corrupted, showing this: 02:00:00:00:00:00 so I searched the Internet for stuff related to this MAC address error and found people with similar problem just like mine. I found solutions like deleting /persist/wifi folder (my friend did not recommended me to do so after I did this). So, I did the thing, AND IT DID NOT HELP. Tried returning to stock using Nexus Root Toolkit AND IT DID NOT HELP. I had an idea to delete my entire system using TWRP and I thought that reinstalling it would fix the problem. But I was noob at the moment, didn't know how to flash after deleting it. Anyway, I went on, and deleted system, but I didn't know how to reinstall and I was without a smartphone for 3 weeks. I was sooooooooo sad cause this was the worst issue I had to deal with... No smartphone... No WiFi.... life sucks (still does, I am sooo depressed for a stupid smartphone)... Well, obviously, NOTHING HELPED.
ATTEMPT TO FIX #2:
After those 3 weeks, I finally managed to find a way to reinstall OS on my smartphone again (using Nexus 5 factory image found in Google site for developers). I was sooo happy because at least I managed to turn the smartphone back on. So, step two was to check if WiFi worked. Well... not as I expected things to be. It didn't work... Obviously... Well, after doing simple experiments, I tried to do "the thing again". After deleting file .macaddr from /persist/wifi folder, without deleting the folder, only the file, WiFi turned back on!!! I went in tears thanking God. Sooooo much happiness!!! I desided to insert WiFi APs that I prevously saved in a wpa_supplicant.conf file, and guess what.... I F***** UP WIFI AND SENSORS!!! I was sooooo mad!
ATTEMPT TO FIX #3:
Well, the next day, I attempted to do a system delete again, but this time, I used another computer device, my family laptop. I deleted system, and this time, I didn't flash anything using Nexus Root Toolkit, but I used this Nexus 5 factory image again. WIFI WAS BACK ON!!! YEESSS!!! I was crying soooo hard!! I again thanked God!!! But it didn't last long... After two days, I turned on my WiFi to check my messages from Instagram, sadly, my WiFi was again stuck on "turning WiFi on..." and my smartphone rebooted by itself (again). So... guess what. I DEAR YOU TO GUESS WHAT HAPPENED NEXT!!! MAC address was back to this STUPID 02:00:00:00:00:00. I had enouch. I installed Termux, I installed a packet called "macchanger" and tried to change my MAC address to something random. I used command "macchanger -r wlan0" and I rebooted. This changed my MAC address to something random. Now, WiFi turns on and when I open an application to use WiFi with, it turns off immediatelly... Also, my MAC address is on changing again with command "macchanger -r wlan0" and is stuck in the previous randomized MAC address. Using "macchanger" command, I also noticed that my "permanent" MAC address is now: 00:00:00:00:00:00 (something that was never valid).
WHAT DO I DO?
DO I NEED TO BUY A NEW SMARTPHONE BECAUSE THIS ONE IS PRETTY F***** UP?
DO I NEED TO REPLACE THE ENTIRE MOTHERBOARD?
IS THIS EVEN A HARDWARE ISSUE?
IS THIS A SOFTWARE ISSUE?
DO I NEED TO REPLACE FIRMWARE? IF SO, HOW DO I DO THAT?
DOES THIS HAVE SOMETHING TO DO WITH /PERSIST?
WHAT DO YOU PROPOSE? BECAUSE I AM TIRED OF THIS STORY, REALLY...
Click to expand...
Click to collapse
You said you were rooted.
Any chance you made a backup, especially a backup from the efs partition?
User699 said:
You said you were rooted.
Any chance you made a backup, especially a backup from the efs partition?
Click to expand...
Click to collapse
What is EFS? What backup do I do. Cause, I'm a noob and all, and I am not the type of a developer... But, I guess I am able to do a backup using root. But how will this work? How will this help the situation. Could you explain to me friend? (If you are willing to do so of course)
Retr0.Hacker said:
What is EFS? What backup do I do. Cause, I'm a noob and all, and I am not the type of a developer... But, I guess I am able to do a backup using root. But how will this work? How will this help the situation. Could you explain to me friend? (If you are willing to do so of course)
Click to expand...
Click to collapse
Maybe you want to have a look on this thread: https://forum.xda-developers.com/t/...y-are-and-how-to-get-it-back-if-lost.3307793/
EFS stands for Encrypted File System. […]
It contains your IMEI, lots of files revolving around your SIM card and Wifi/Bluetooth (this includes your MAC address for all the radios of your phone), and lots of other things that should never ever under any circumstance be deleted or touched. […]
If you lose your EFS folder, you lose pretty much any chance of your phone being able to use data, Wifi, Bluetooth […].
Click to expand...
Click to collapse
If you had done a backup (e.g. via twrp) prior to rooting you might have also done a backup of that efs partition.
And if you had a backup you could restore that partition. Don't know if you somehow managed to mess this partition up (or if its related at all in your case. Someone with more knowledge hopefully sees your thread) but if you did, there would be no point in backing up that partition now (if its damaged, there is no use to backup a damaged partiton to restore it afterwards).
You can ask me everything you want, don't worry. But I don't know if I'll be able to explain it.
You could try to follow above mentioned guide. If it works, please upvote that guide so others find that helpfull content too.
User699 said:
Maybe you want to have a look on this thread: https://forum.xda-developers.com/t/...y-are-and-how-to-get-it-back-if-lost.3307793/
If you had done a backup (e.g. via twrp) prior to rooting you might have also done a backup of that efs partition.
And if you had a backup you could restore that partition. Don't know if you somehow managed to mess this partition up (or if its related at all in your case. Someone with more knowledge hopefully sees your thread) but if you did, there would be no point in backing up that partition now (if its damaged, there is no use to backup a damaged partiton to restore it afterwards).
You can ask me everything you want, don't worry. But I don't know if I'll be able to explain it.
You could try to follow above mentioned guide. If it works, please upvote that guide so others find that helpfull content too.
Click to expand...
Click to collapse
I did not mess with any partitions. I do not like to mess with my system. I never did. I always made a backup if I had to do something with the system. Before the incident, I never EVER messed with the system. I only started some experiments after the thing happened. I first deleted the whole content of /persist folder (which I restored, because I had a backup), then I deleted .macaddr file inside /persist/wifi folder which actually turned on my WiFi access again, only to f*** things up after doing something stupid, which is to replace wpa_supplicant.conf file inside the /data/misc/wifi folder with one I had with my previously saved WiFi Access Points and their passwords, which resulted to the corrupted MAC address again (02:00:00:00:00:00). No, my WiFi can be scanned successfuly and I am able to connect to it, but still, it does not work properly, because when it connects, it automatically disconnects when I try to use apps like Chrome and Instagram and other apps that need Internet to use. I am currently deleting and re-installing my Factory Image and this will be the last time...
Also, I will attach your URL for sure.
Thanks.
Retr0.Hacker said:
I did not mess with any partitions. I do not like to mess with my system. I never did. I always made a backup if I had to do something with the system. Before the incident, I never EVER messed with the system. I only started some experiments after the thing happened. I first deleted the whole content of /persist folder (which I restored, because I had a backup), then I deleted .macaddr file inside /persist/wifi folder which actually turned on my WiFi access again, only to f*** things up after doing something stupid, which is to replace wpa_supplicant.conf file inside the /data/misc/wifi folder with one I had with my previously saved WiFi Access Points and their passwords, which resulted to the corrupted MAC address again (02:00:00:00:00:00). No, my WiFi can be scanned successfuly and I am able to connect to it, but still, it does not work properly, because when it connects, it automatically disconnects when I try to use apps like Chrome and Instagram and other apps that need Internet to use. I am currently deleting and re-installing my Factory Image and this will be the last time...
Also, I will attach your URL for sure.
Thanks.
Click to expand...
Click to collapse
Another thing which would be helpful:
If your problem is still present you might want to have a look at the logs. That way it's easier to see what causes this behavior.
Code:
adb logcat > log.txt
Run this and try to reproduce the error.
Don't worry about messing with anything. We don't know what happened and sometimes the best of us do things they shouldn't do.
And it seems that also other things (like installing a custom OS) messed with partitions somehow.
But yes, doing a backup prior to modifing is extremly wise – keep up that habit!
I would suggest to try this solution I found:
Aniki43 said:
My Solution {Nexus 5 stuck on "Turning wifi on"}
MY Nexus5 got the same problem today WiFi just stopped working suddenly. The mac got some stupid address like 2.00.00.00. I tried every thing still nothing. I have already rooted my nexus so tried different roms but issue still remains.
Then i just remembered about the ROM UBUNTU Touch i have installed it and WiFi in Ubuntu start working again with original mac address. I am currently using Ubuntu touch and didn't try to reinstall or reset the android rom again.if some one try this and got WiFi working like me please inform me that if the WiFi still works if i reinstall android system.
If you want to download Ubuntu touch download it ubports
Click to expand...
Click to collapse
It is said that the "fix" stays after Android is reinstalled afterwards.
momojuro said:
I would suggest to try this solution I found:
It is said that the "fix" stays after Android is reinstalled afterwards.
Click to expand...
Click to collapse
I saw this thread before. I did not try to flash other OS than the one I use now. I was also thinking downgrading to Android 5.1.1 (because I am currently using 6.0.1 with MOB30H build) and I might try some time.
BTW there is another problem now. I installed a packet from Termux called "macchanger" and I used the packet in order to - what else - change my MAC address. The packet seems to work. It DID change my MAC address and I am now able to scan for local WiFi. But the thing is that every time my I try to connect ti the Internet, WiFi automatically closes, and the randomized MAC address is permanently stuck ( I think, because I can reset it sometimes, but still, it changes back the the one who got randomized first)
I may get a new smartphone for WiFi, calls and stuff and use my Nexus 5 in order to try and find a fix for it. Idk...