Related
Hello,
I own a Motorola Milestone (rooted, unlocked). Two days ago a weird thing appeared: when i try to activate the wifi, it goes into a Turning on - turning off - turning on etc. loop and i can stop it just if i activate the airplane mode, restart the phone and deactivate the airplane mode. It does not see any wireless network, i can't stop it and i can't connect to any network.
If i try to see the MAC in the wifi settings -> advanced, it writes 00:00:00:00:00:00 when it is in the loop mode. In the service menu, the MAC Address appears Unavailable.
I tried to reflash different firmwares to solve the problem, but no luck. I reflashed the original rom on it, but also: no luck. I tried everything possible with no luck.
In sys/devices/virtual/net/ i don't have any eth0 folder which i think that contains the network drivers.
I didn't drop the phone, i didn't drop anything on it. It appeared from nowhere. There aren't any other problems with the phone. The bluetooth works fine so, i don't think it's a hw problem (i found somewhere that the two hw modules are the same...it's possible that i should got it wrong).
How can i solve it?
PS: i wrote this here because i saw that this happened to different persons around the world but nobody gave an answer. So, i don't think it's phone related.
If this happened to me I would try this:
1: Nandroid backup+Titanium backup
2: Run WiFi Fixer.apk
if it won't help:
3: Try some other ROMs
btw I don't really understand how did you come up with an idea that this is "Milestone Android Development" thread...
1. I don't have any Titanium Backup or nandroid backup
2. WiFi fixer doesn't work
3. i tested CM7, FroyoMod 2.3.3, CM6, original sbf file...nothing works
I posted this here because the other Milestone threads are not read by most of you.
then RMA it.
After you try to enable wifi, paste kernel log (output from 'dmesg' or 'logcat -b kernel' commands) and main log (logcat) to pastebin.com and post links to it here for inspection.
Is your /pds/wifi/nvs_map.bin file in place?
Hello kabaldan,
I was waiting for your reply master.
The /pds/wifi/nvs_map.bin is there but i can see it only in terminal, with ls, after su. In default file explorer from CM7, the folder is empty.
Here is the output of dmesg: http://pastebin.com/Ngz9iaQU
I'm currently using CM7 RC15 (the last night build).
PS: I promise to donate as soon as i get my money from the company i'm working for.
sdiodrv_data_xfer_sync() transfer error! STAT = 0x108011
Click to expand...
Click to collapse
Sorry to say that, but this is a hardware failure. The wlan sd card does not respond to commands sent to it.
You should send your phone for repair.
Dear all,
I have flashed my MZ605 (32GB) using EOS 3.0 for MZ601 with TWRP and that has worked quite well for some time, but last week I was fiddling with the navigation app and the tablet suddenly froze. The only way to get it back to life was doing a volume-up+power. Now the system still boots: i get to the lock screen, but as soon as I unlock (no password, just swiping to the right), I receive a shower of f/c messages and no icons apear. The settings screen still seems to work, but since the stream of f/c messages doesn't stop, it's very hard to do anything at all. I tried all the standard stuff first: Flashing EOS 3.0 using TWRP and Factory Reset: It seems to do nothing at all. Everything stays the same! When trying to delete cache, userdata, etc. Right after displaying the message "updating partition details", it complains that it is not able to access certain files in /data/media (a bunch of mp3 files)
Figuring that something must be wrong with the filesystem, I fired up the console of TWRP and did an e2fsck (e2fsck -vfcp) on partition 8,9 and 10, resulting simply in "unable to set superblock flags". I tried formatting the thing by hand but when doing mke2fs, it acts like it it's creating the fs (you see the numbers fly by), but when mounting the fs again, nothing changed at all!
About the partition table: Accessing the kernel messages (dmesg) with ADB says that the primary gpt table is corrupt and will try to use the backup table. It then merrily continues booting. However, when checking the partition table with gdisk (using ADB): it says nothing is present. Using the recovery options show that the primary table contains garbage and the backup partition table doesn't seem to contain anything. :S This contrasts with the fact that kernel still sees the partitions and that they are mountable both when booting normally as well as with TWRP
As a last resort I downloaded RSDLite 5.7 and the most recent SBF image. It flashes the whole thing without any errors, but when booting the system: nothing changed at all???
For the tl;dr people: Sorry! In a nutshell: fs seems to be frozen: mke2fs does nothing, fastboot flash does nothing and even sbf flash doesn't do anything at all. However the device still boots, albeit with a shower of f/c on unlock screen.
Any suggestions what to? I have been googling for many days now and reading this forum. Nothing has helped so far...
My next try would be to redefine the gpt partition table using gdisk and then hope that'll fix the frozen that. After that I would of course do a wipe all and flash a new ROM. The problem is, I can't find the standard partition layout details for the Xoom anywhere, nor do I have any other ideas what to do in case this does not work
If anyone has any hint or idea, please let me know. Thanks!
Nobody?
If anyone could please tell me their partition layout, like start - end - type for each partition. It'd really appreciate it!
Thanks!
No one?
Hello,
have you fixed it ?
Nope
jkd said:
Hello,
have you fixed it ?
Click to expand...
Click to collapse
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
ioish said:
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
Click to expand...
Click to collapse
Actually I have the same problem, I have read several forums and I have not found an answer
jkd said:
Actually I have the same problem, I have read several forums and I have not found an answer
Click to expand...
Click to collapse
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
ioish said:
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
Click to expand...
Click to collapse
my xoom caracteristic:
- Recovery: TWRP v2.6.3.0 (RunAndHide05 Edition), I can not tell if it's a bigpart or no recovery. Also I am unable to change recovery is cwm or another version of TWRP. I always find my TWRP recovery v2.6.3.0.
- ROM omni: 4.4.2-20140102-1218 + 0100-wingray-HOMEMADE (I don't know if is bigpart rom)
- kernel:2.6.39.4-ElementalX-Xoom-2.1+
Hello, everyone and thanks in advance.
I'm not sure the entire sequence of events because I've spent so much time trying to fix the issue that I can't remember what caused it. Sometime after flashing the custom kernel here to try to get safety net to pass checks I rebooted and the stock deodexed ROM told me that encryption was not possible and I had to restore to factory.
So... I didn't. I thought that sounded like a bad idea. Instead I connected with adb and rebooted into fastboot and flashed TWRP to recovery again in case TWRP had been replaced and then I rebooted into TWRP. From there I wiped data and reflashed the 20C deodexed ROM. I figured that would be the safest way to get rid of the message and the phone had just been reset anyway so I wasn't really losing any ground.
Problem is... now it only reboots into TWRP. It will not boot system. I have tried a ton of things since then like flashing the original boot and recovery. I have also tried flashing the boot and recovery from here.
No luck. I've even reflashed TWRP just in case. I bet this is simple but I can't figure it out. Any help is appreciated. Thanks!
I ended up not figuring out a way to solve this from where I was at. Somebody probably could have but nobody saw it in time.
What I ended up doing instead was putting the phone into download mode (holding volume up and plugging the phone into a computer) and then I used LGUP (with uppercut.exe) to flash the 20A KDZ on there. When Android booted it still complained that the data partition was unencrypted so this time I let the phone wipe it. It rebooted... wiped it and now it is starting Android for the first time in a day. That feels pretty good actually.
I guess I'll start over now with recowvery since I'm on stock 20A.
codahq said:
I ended up not figuring out a way to solve this from where I was at. Somebody probably could have but nobody saw it in time.
What I ended up doing instead was putting the phone into download mode (holding volume up and plugging the phone into a computer) and then I used LGUP (with uppercut.exe) to flash the 20A KDZ on there. When Android booted it still complained that the data partition was unencrypted so this time I let the phone wipe it. It rebooted... wiped it and now it is starting Android for the first time in a day. That feels pretty good actually.
I guess I'll start over now with recowvery since I'm on stock 20A.
Click to expand...
Click to collapse
I discovered something in doing this again (because it happened again). When you want to wipe data so that it is unencrypted... don't. From TWRP instead of wiping just format it. So TWRP -> WIPE -> Format -> (Type yes). Wiping for some reason changes the partition information enough that stock can't find the data partition or can't use it or something along those lines. It then freaks out and wants you to factory reset. I think it needs stock recovery to do that so that process fails and then you have the boot loop to TWRP over and over.
That's my working theory anyway. I did it all again but did format instead of wipe and it seems to be working. I'm leaving this here for posterity. Hopefully it will help somebody.
Thank you so, so, so, so, so, .................. much.
You saved my day! I ran into the same exact issue you had. Lots of blessings and best wishes to YOU and this XDA community!
BTW, I found another thread with an easier way to fix this. Go to the terminal in TWRP and run these commands:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
That should fix it. You may or may not have to reflash your rom after, but it got me up and running without any fuss.
rjcarter3 said:
BTW, I found another thread with an easier way to fix this. Go to the terminal in TWRP and run these commands:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
That should fix it. You may or may not have to reflash your rom after, but it got me up and running without any fuss.
Click to expand...
Click to collapse
Do not use the above commands unless the following one commands doesn't work. Using the above commands wipes your whole misc partition and deletes your WiFi Mac address (you'll end up having a Mac address that changes every reboot). I did make a guide in the guides section to fix this, but better to use the correct way so you don't have to fix it later. Here is the correct code to get out of TWRP bootloop:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Yup, if sure does. Any suggestions for how to fix it?
rjcarter3 said:
Yup, if sure does. Any suggestions for how to fix it?
Click to expand...
Click to collapse
Yes I created a guide some while ago located here:
https://forum.xda-developers.com/lg-g5/how-to/guide-fix-wifi-mac-address-changing-t3533841
Note: This fix will stick as long as you don't flash another ROM or wipe system / data when updating a ROM. If you do either of those, you'll need to redo this fix. Unfortunately there doesn't appear to be a permanent fix. I tried to manually edit my misc partition with a Mac address and flash it back, but it didn't work. But my temp fix does work
I didn't realize that by no permanent fix you really meant permanent. I flashed back to stock and it still persists. I guess a full restore isn't really a full restore.
rjcarter3 said:
I didn't realize that by no permanent fix you really meant permanent. I flashed back to stock and it still persists. I guess a full restore isn't really a full restore.
Click to expand...
Click to collapse
Well, that is why it's not recommended to use those commands and also why I stated that any time you flash a new ROM, even stock, you'll need to redo that fix. However, once you do it, it will stay until you flash a different ROM or wipe system for whatever reason.
jeffsga88 said:
Well, that is why it's not recommended to use those commands and also why I stated that any time you flash a new ROM, even stock, you'll need to redo that fix. However, once you do it, it will stay until you flash a different ROM or wipe system for whatever reason.
Click to expand...
Click to collapse
Oh, ok - I didn't see you say stock, but it doesn't matter. This phone isn't a daily driver for me, so I'm fine to do some experimenting with it. Just really interesting that flashing a full factory restore KDZ file doesn't fix the issue. I flashed to 20A, relocked my bootloader and did OTA updates all the way to 20F and then LGUP back to 20A. Still changed every time.
There seems to be some debate in the other thread if this problem existed even before wiping any misc directories. I think you even mentioned that it appears to be from formatting data to remove encryption. Isn't removing encryption central to the process of rooting altogether? ie, wouldn't this problem exist in any rooted G5 phone and not just those who ran those commands I posted above? I realize that wiping misc will break your fix, but is that what causes it in the first place?
rjcarter3 said:
Oh, ok - I didn't see you say stock, but it doesn't matter. This phone isn't a daily driver for me, so I'm fine to do some experimenting with it. Just really interesting that flashing a full factory restore KDZ file doesn't fix the issue. I flashed to 20A, relocked my bootloader and did OTA updates all the way to 20F and then LGUP back to 20A. Still changed every time.
There seems to be some debate in the other thread if this problem existed even before wiping any misc directories. I think you even mentioned that it appears to be from formatting data to remove encryption. Isn't removing encryption central to the process of rooting altogether? ie, wouldn't this problem exist in any rooted G5 phone and not just those who ran those commands I posted above? I realize that wiping misc will break your fix, but is that what causes it in the first place?
Click to expand...
Click to collapse
Well, technically formatting data shouldn't have anything to do with it as the WiFi Mac address is stored in your misc partition. Reason I thought it might be from formatting data before was because I didn't realize I wiped my misc partition. When first rooting the T-Mobile version it was pretty much necessary to run those commands which wipe it and no one had known about the other commands that were safer, so a lot of people ended up with this issue quite awhile ago and not knowing why. I only figured out why with talking with autoprime after posting my guide to fix it. Also, wiping misc partition after doing my fix doesn't break my fix, wiping your data from TWRP, or flashing a new ROM or stock will break the fix as the fix is stored in data/misc/wifi. Also, reason that flashing a kdz of stock doesn't fix it is because the kdz doesn't rewrite your misc partition. Technically, you should be able to pull your misc partition, edit it to have Mac address again and push back with adb, yet when I tried it didn't fix it.
jeffsga88 said:
Do not use the above commands unless the following one commands doesn't work. Using the above commands wipes your whole misc partition and deletes your WiFi Mac address (you'll end up having a Mac address that changes every reboot). I did make a guide in the guides section to fix this, but better to use the correct way so you don't have to fix it later. Here is the correct code to get out of TWRP bootloop:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
Worked like a charm, you are the ****ing man, Thanks man.
Skyline GTR78 said:
Worked like a charm, you are the ****ing man, Thanks man.
Click to expand...
Click to collapse
Hey, can you check to see:
a) if you have the same wifi mac address after successive reboots
b) if you do, can you browse to
"/system/etc/wifi"
and open this file in a text editor:
"bcmdhd.cal"
And see if the Mac address is located in the top of the file matches the one in your settings menu? I just want to verify this is the correct hardware address when I use the manual fix for this.
---------- Post added at 03:22 PM ---------- Previous post was at 03:14 PM ----------
jeffsga88 said:
Well, technically formatting data shouldn't have anything to do with it as the WiFi Mac address is stored in your misc partition. Reason I thought it might be from formatting data before was because I didn't realize I wiped my misc partition. When first rooting the T-Mobile version it was pretty much necessary to run those commands which wipe it and no one had known about the other commands that were safer, so a lot of people ended up with this issue quite awhile ago and not knowing why. I only figured out why with talking with autoprime after posting my guide to fix it. Also, wiping misc partition after doing my fix doesn't break my fix, wiping your data from TWRP, or flashing a new ROM or stock will break the fix as the fix is stored in data/misc/wifi. Also, reason that flashing a kdz of stock doesn't fix it is because the kdz doesn't rewrite your misc partition. Technically, you should be able to pull your misc partition, edit it to have Mac address again and push back with adb, yet when I tried it didn't fix it.
Click to expand...
Click to collapse
Thanks - has anyone verified that those who've rooted but not run those commands did not exhibit the MAC changing issue (ie, that it's definitely the cause of the problem and doesn't just duplicate the problem)?
Also, I was trying to follow your directions for the manual fix, created the config file but when I run the command from the terminal, I get this:
sush: cat: /sdcard/config: No such file or directory
Any ideas? Thanks!
rjcarter3 said:
Hey, can you check to see:
a) if you have the same wifi mac address after successive reboots
b) if you do, can you browse to
"/system/etc/wifi"
and open this file in a text editor:
"bcmdhd.cal"
And see if the Mac address is located in the top of the file matches the one in your settings menu? I just want to verify this is the correct hardware address when I use the manual fix for this.
---------- Post added at 03:22 PM ---------- Previous post was at 03:14 PM ----------
Thanks - has anyone verified that those who've rooted but not run those commands did not exhibit the MAC changing issue (ie, that it's definitely the cause of the problem and doesn't just duplicate the problem)?
Also, I was trying to follow your directions for the manual fix, created the config file but when I run the command from the terminal, I get this:
sush: cat: /sdcard/config: No such file or directory
Any ideas? Thanks!
Click to expand...
Click to collapse
Ok, first let's try and keep this on topic, this thread is about TWRP bootlooop not the wifi Mac address. Anything else about the wifi Mac address ask in my wifi Mac address guide thread. I just don't want to get way off topic for people looking to figure out the TWRP bootlooop. Anyways, I will answer both questions though.
So, first answer is the Mac address that's in the bcmdhd.cal is based on what it gets from the config file. If that config come doesn't exist and your wifi Mac address isn't in your misc partition, it will just make up a random Mac address, hence the random Mac address every reboot. If you're wanting your real wifi Mac address, it may be pretty hard to figure it out, why I say just pick something you like and it will stay that each time you reboot.
Second answer, make sure you create the config file (with no extension) at root of internal sd card. Then, copy and paste the command exactly into the terminal and it'll work.
Code:
su -c "cat /sdcard/config > /data/misc/wifi/config"
Hopefully that'll help, if you have any more questions regarding the fix for the wifi Mac address feel free to ask me in that thread.
jeffsga88 said:
Do not use the above commands unless the following one commands doesn't work. Using the above commands wipes your whole misc partition and deletes your WiFi Mac address (you'll end up having a Mac address that changes every reboot). I did make a guide in the guides section to fix this, but better to use the correct way so you don't have to fix it later. Here is the correct code to get out of TWRP bootloop:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
Thanks! Had to use it after trying to upgrade Lineage on my h830 today. :good:
Fixing with stock recovery
If I've managed to get into the same situation, but tried to fix it by using LGUP to flash the .KDZ of the stock 20a ROM (including stock recovery), and then found that it still does this recovery loop type of thing (shows T-mobile logo for 10 seconds, then boots into stock recovery erasing the data, then repeat) how would I fix it?
Thanks,
Elliot
jeffsga88 said:
Do not use the above commands unless the following one commands doesn't work. Using the above commands wipes your whole misc partition and deletes your WiFi Mac address (you'll end up having a Mac address that changes every reboot). I did make a guide in the guides section to fix this, but better to use the correct way so you don't have to fix it later. Here is the correct code to get out of TWRP bootloop:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
You saved me with this command :good:
Works fine on LG G6 as well!
jeffsga88 said:
Do not use the above commands unless the following one commands doesn't work. Using the above commands wipes your whole misc partition and deletes your WiFi Mac address (you'll end up having a Mac address that changes every reboot). I did make a guide in the guides section to fix this, but better to use the correct way so you don't have to fix it later. Here is the correct code to get out of TWRP bootloop:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
I don't usually post on xda as I am not a dev nor am I a mad custom rom lover, but man You have saved me a sleepless night, Thank you! If you are ever in Cork, Ireland I would love to buy you a coffee or a beer!!!!
Ok guys after lots of tests, I've managed that the fastest and easiest way to have wifi fixed on Stock android rom is to delete some lines (they are 2-3) in a file located on "/persist" folder.
PROCEDURE
1) You need magisk (or any other form of root) and a file manager that can edit (with root permissions) systems files.
Once you have done it, go on root "/persist" and find the file "wlan_mac.bin", open it with a text editor and delete all lines in it(let it empty but don't delete it, just delete lines in it), after save and reboot phone, done.
2) This is faster, it is going to do same thing but without magisk. Just flash the WiFi_fix.zip (see file below in attachment) from Twrp and it will replace the corrupted wifi_mac.bin with an empty one.
Optional: if you know how to generate a xiaomi vendor mac address, just replace the empty wlan_mac.bin from my WiFi_fix.zip file with yours.
Comment:
*This is the fast and easy but not the best one. I'm finding a workaround.
Anyway this method isnt a problem you are going to use base Mac Address and not the vendor one. In therms of warranty I don't think it will change something.
PS: Actually this will be fixed on custom rom that used to edit that file.
Good work!
I have same problem. When i flash stock rom via mi flshtool i can't connect to wifi. It shows wifi but after entering pwd it shows only saved. Can't connect at all.can u explain procedure when flashed stock rom. Flashing persist.img via fastboot will fix? Without rooting. Sorry for my bad English.
---------- Post added at 03:30 PM ---------- Previous post was at 03:23 PM ----------
So you are saying after flashing stock rom i have to unlock bl and root. And then edit system????? Sorry im a noob to Mi A1
kishanb1988 said:
I have same problem. When i flash stock rom via mi flshtool i can't connect to wifi. It shows wifi but after entering pwd it shows only saved. Can't connect at all.can u explain procedure when flashed stock rom. Flashing persist.img via fastboot will fix? Without rooting. Sorry for my bad English.
---------- Post added at 03:30 PM ---------- Previous post was at 03:23 PM ----------
So you are saying after flashing stock rom i have to unlock bl and root. And then edit system????? Sorry im a noob to Mi A1
Click to expand...
Click to collapse
Just connect phone in fastboot on pc. open cmd (you need fastboot and adb drivers installed on PC) and write this:
fastboot oem unlock (to unlock bootloader)
fastboot boot twrp-oreo-3.2.1-2.img (you need last official twrp from XDA for that. Name can be different, you have to write extaclty of your file)
Phone will boot on twrp. From install/flash magisk and reboot phone. Now you have magisk and root.
Download and installa a file manager like MixPlorer, Root explorer, MtManager and many others.
Go on "root" and find the folder "persist". In it you will find the file "wclan_mac.bin" just edit. If you still have issue I will made something that is going to do it automatically.
Thanks mate. I'll try ?, you save the hours of works. Thanks again
Has someone tried erasing then flashing persist.img?
Your method is not the fastest nor the best to reset the WiFi connection, You do not need to be root.
You must do the following:
The persist.img file must be downloaded from the following link
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
“persist.img” file and move it to phone memory “/sdcard”.
1.- Enter fastboot mode, , you must have unlocked the bootloader
2.- Execute TWRP with the command fastboot boot twrp.img
3.- Open Terminal in TWRP Custom Recovery (go to "Advanced"> "Terminal").
4.- Type the following command:
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
Click to expand...
Click to collapse
5.- Restart and with it the wifi will work.
Procedure taken from https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
speedunderx said:
Your method is not the fastest nor the best to reset the WiFi connection, You do not need to be root.
You must do the following:
The persist.img file must be downloaded from the following link
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
“persist.img” file and move it to phone memory “/sdcard”.
1.- Enter fastboot mode, , you must have unlocked the bootloader
2.- Execute TWRP with the command fastboot boot twrp.img
3.- Open Terminal in TWRP Custom Recovery (go to "Advanced"> "Terminal").
4.- Type the following command:
5.- Restart and with it the wifi will work.
Procedure taken from https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
Click to expand...
Click to collapse
It is dangerous, I dont advise it.
SevenSlevin said:
It is dangerous, I dont advise it.
Click to expand...
Click to collapse
It works perfectly, it's more dangerous what you do.
deleted, double post.
speedunderx said:
It works perfectly, it's more dangerous what you do.
Click to expand...
Click to collapse
I don't think you have the idea of what you have done.
I will tell 2 points of the fact that it is dangerous:
1) for the not experted doing these things can easily bootloop/soft brick phone.
2) You flashed with "DD" and you have flashed a backup of another one so you are using his MacAddress.
Now tell me how safety is it if I know your MacAddress? (everyone who is going to flash it will have same MacAddress)
PS. in this case your MacAddress are:
Bluetooth: f4:f5:dB:e9:b6:dc
WiFi: f4:f5:dB:e9:b6:dd
check them on "settings, system, about phone, status".
SevenSlevin said:
I don't think you have the idea of what you have done.
I will tell 2 points of the fact that it is dangerous:
1) for the not experted doing these things can easily bootloop/soft brick phone.
2) You flashed with "DD" and you have flashed a backup of another one so you are using his MacAddress.
Now tell me how safety is it if I know your MacAddress? (everyone who is going to flash it will have same MacAddress)
PS. in this case your MacAddress are:
Bluetooth: f4:f5:dB:e9:b6:dc
WiFi: f4:f5:dB:e9:b6:dd
check them on "settings, system, about phone, status".
Click to expand...
Click to collapse
You're wrong, you should read the tutorial, and with regard to the Mac I have the usual Mac, so you know a Mac is the physical code of the hardware, therefore you can not change it just read, the problem is that when you install RR you delete the WiFi module that uses the stock firmware, while the custom ROM uses drivers, persist.img helps to restore the Bluethoot module and wifi and sometimes the imei.
speedunderx said:
You're wrong, you should read the tutorial, and with regard to the Mac I have the usual Mac, so you know a Mac is the physical code of the hardware, therefore you can not change it just read, the problem is that when you install RR you delete the WiFi module that uses the stock firmware, while the custom ROM uses drivers, persist.img helps to restore the Bluethoot module and wifi and sometimes the imei.
Click to expand...
Click to collapse
There's a persist.img in our fastboot ROM. Can we use that instead of what you linked?
Edit - Flashed the persist.img from the Fastboot ROM in EDL mode. I ended up with no sensors. Trying to reflash the entire ROM now. :'(
Edit 2-
1. Dirty Flashed ROM. Re-setup fingerprints. Reset network settings. Emptied out wlan.bin file, everything works except wifi.
2. Restored my personal backup of persist, re-setup fingerprints. Everything is now working.
oreo27 said:
There's a persist.img in our fastboot ROM. Can we use that instead of what you linked?
Edit - Flashed the persist.img from the Fastboot ROM in EDL mode. I ended up with no sensors. Trying to reflash the entire ROM now. :'(
I've already done it and have same your issue in past. Problem is that, that persist.img found on fastboot firmware stock, seems to non be complete and has "corrupted" (incomplete) WCNSS_qcom_wlan_nv.bin and WCNSS_wlan_dictionary.dat. And also it doesnt make the folder /persist/wifi_bin where are located other 2 folders "minus" and "plus".
In your case you have finished with no wifi, that isnt correct. You have wifi but you need to put phone next to router cause with those "corrupted" files it has really low range. To fix that you just need files that I've wrote above from someone that has correct files. In this case you ave done a backup, you just needed to copy wifi_bin folder, WCNSS_qcom_wlan_nv.bin and WCNSS_wlan_dictionary.dat from your backup.
Anyway actually I think you are using the hardware mac address that in most of phones starts with: 00:0a:f5 (it is the prefix of vendor Airgo networks that produce those chipsets and works under Qualcomm). I've seen also mac starting with: 00:00:00 that is the prefix of Xerox Corporation.
To turn back to your back vendor (XIaomi) mac address your last hope, as I know, is to use bluetooth mac. Considerading that you have a backup of it (it is located in /persist/bluetooth) and you have never touched it.
Click to expand...
Click to collapse
SevenSlevin said:
oreo27 said:
There's a persist.img in our fastboot ROM. Can we use that instead of what you linked?
Edit - Flashed the persist.img from the Fastboot ROM in EDL mode. I ended up with no sensors. Trying to reflash the entire ROM now. :'(
I've already done it and have same your issue in past. Problem is that, that persist.img found on fastboot firmware stock, seems to non be complete and has "corrupted" (incomplete) WCNSS_qcom_wlan_nv.bin and WCNSS_wlan_dictionary.dat. And also it doesnt make the folder /persist/wifi_bin where are located other 2 folders "minus" and "plus".
In your case you have finished with no wifi, that isnt correct. You have wifi but you need to put phone next to router cause with those "corrupted" files it has really low range. To fix that you just need files that I've wrote above from someone that has correct files. In this case you ave done a backup, you just needed to copy wifi_bin folder, WCNSS_qcom_wlan_nv.bin and WCNSS_wlan_dictionary.dat from your backup.
Anyway actually I think you are using the hardware mac address that in all phones starts with: 00:0a:f5.
To turn back to your back vendor mac address your last hope, as I know, is to use bluetooth mac. Considerading that you have a backup of it (it is located in /persist/bluetooth) and you have never touched it.
Click to expand...
Click to collapse
I was actually able to restore everything . I did a dd backup of my persist partition prior to messing with it. I simply restored that and got everything working normally after I re-registered my fingerprints.
Good to know that I can simply replace those files. I just checked those out after I extracted my backup. Good to know I can just use those.
Apart from WiFi, is there anything else that's damaged when flashing the persist.img from Fastboot?
P.S. You're right, it was showing the networks but it wasn't connecting.
Click to expand...
Click to collapse
I am currently in RR, I think the best way is to wait for the developers to solve the problem, with an update.
oreo27 said:
SevenSlevin said:
I was actually able to restore everything . I did a dd backup of my persist partition prior to messing with it. I simply restored that and got everything working normally after I re-registered my fingerprints.
Good to know that I can simply replace those files. I just checked those out after I extracted my backup. Good to know I can just use those.
Apart from WiFi, is there anything else that's damaged when flashing the persist.img from Fastboot?
P.S. You're right, it was showing the networks but it wasn't connecting.
Click to expand...
Click to collapse
But Attention on deleting files on /persist folder. If you delete one of this (or all them),
WCNSS_qcom_wlan_nv.bin
WCNSS_wlan_dictionary.dat
wlan_mac.bin
you will end in a costantly reboot of phone. For that I've advised only to delete lines with a text editor from "wlan_mac.bin", and as you have seen flashing "persist.img" need lots of knowledge and it is risky (in your case you have done the best thing of doing a backup of it) if you dont know what you are doing.
PS. you can send me in PM your /bluetooth/.bt_nv.bin file. Need an hexadecimal editor and if that file was never touched (as I think) you can restore back your old Xiaomi wifi mac address also.
Click to expand...
Click to collapse
Hi,
I'm having the same issue with WiFi. Connected to WiFi, accepted pw, but not working the wifi connection.
I've a fresh stock oreo, now I see the original BT MAC address.
How to do to make wifi work again without loosing original BT MAC?
speedunderx said:
You're wrong, you should read the tutorial, and with regard to the Mac I have the usual Mac, so you know a Mac is the physical code of the hardware, therefore you can not change it just read, the problem is that when you install RR you delete the WiFi module that uses the stock firmware, while the custom ROM uses drivers, persist.img helps to restore the Bluethoot module and wifi and sometimes the imei.
Click to expand...
Click to collapse
i dont know if u have tried it yourself and i dont know the technical details, but i have tried doing that after coming from RR and it didnt work. and more importantly i ended up having 30 sec reboots as someone pointed out here. This is what worked for me:
https://forum.xda-developers.com/mi-a1/help/wifi-issues-t3732798/page2
i havent tested the method described here but i am pretty sure it is no more worse than the one you advice
sachin273 said:
i dont know if u have tried it yourself and i dont know the technical details, but i have tried doing that after coming from RR and it didnt work. and more importantly i ended up having 30 sec reboots as someone pointed out here. This is what worked for me:
https://forum.xda-developers.com/mi-a1/help/wifi-issues-t3732798/page2
i havent tested the method described here but i am pretty sure it is no more worse than the one you advice
Click to expand...
Click to collapse
It works other users have tried, but as the author of this post says, leave a generic wifi and bluetooth mac for everyone, I'm RR, and I have the physical device mac bone the original, you can try all the methods there are but none will restore the original mac of your device, just wait for it to be corrected with the Custom ROM updates. If you try a lot there is the possibility that you will have a nice brick.
You have to take into consideration that the phone is quite economical, therefore it is not the same thing that you fail in this way a galaxy s8 for example.
If you are using Custom Rom enjoy it, there are many that work better than stock android.
OK, I confirm that now I tried OP's solution 2 minutes ago, and it's working. WiFi came back, and operating fine!
But is that OK, that before made the empty wlan_mac.bin file saved I saw different MAC addresses in the system info, and when
rebooted then I saw again different MAC addresses in system info??
Which is the original?
speedunderx said:
It works other users have tried, but as the author of this post says, leave a generic wifi and bluetooth mac for everyone, I'm RR, and I have the physical device mac bone the original, you can try all the methods there are but none will restore the original mac of your device, just wait for it to be corrected with the Custom ROM updates. If you try a lot there is the possibility that you will have a nice brick.
You have to take into consideration that the phone is quite economical, therefore it is not the same thing that you fail in this way a galaxy s8 for example.
If you are using Custom Rom enjoy it, there are many that work better than stock android.
Click to expand...
Click to collapse
Recently, I corrupted my /EFS partition when I tried to change my MAC address. I don't have any backups of the partition and now my wifi doesn't work. Basically, my last option is to flash someone else's /EFS and hope for the best. Can someone send me their TWRP backup of this partition? It would help a lot. Thank you.
DJsushi123 said:
Recently, I corrupted my /EFS partition when I tried to change my MAC address. I don't have any backups of the partition and now my wifi doesn't work. Basically, my last option is to flash someone else's /EFS and hope for the best. Can someone send me their TWRP backup of this partition? It would help a lot. Thank you.
Click to expand...
Click to collapse
You can't just use somebody else's EFS partition on your phone, as the data it holds is unique to each device. First, read what EFS actually is:
https://forum.xda-developers.com/oneplus-one/general/guide-efs-partitions-how-to-lost-t3307793
The only way (that I've found) of making your phone run properly again is to use a UMT dongle (do some research on how it works first) and input your IMEI back manually (it's written somewhere on the box the phone came in), but that dongle is a bit costly. If you do not want to deal with that, you should just reach out to OnePlus support.
I'm curious, why would you change your MAC address? Android 10 already has a MAC randomizer.
But yeah, EFS and Persist partitions are device specific and containing low level stuff that I don't think transferring it from one device to anther would work. First thing you could try is flashing stock ROM using MSM Download Tool.
McAwesomePL said:
You can't just use somebody else's EFS partition on your phone, as the data it holds is unique to each device. First, read what EFS actually is:
https://forum.xda-developers.com/oneplus-one/general/guide-efs-partitions-how-to-lost-t3307793
The only way (that I've found) of making your phone run properly again is to use a UMT dongle (do some research on how it works first) and input your IMEI back manually (it's written somewhere on the box the phone came in), but that dongle is a bit costly. If you do not want to deal with that, you should just reach out to OnePlus support.
Click to expand...
Click to collapse
I read somewhere that it could work... And thanks, I know what the EFS partition is... However, is it a problem if I end up with someone else's IMEI? Also, I already did a backup of the current corrupted EFS so if the EFS from another phone won't work then I can just flash my old EFS back.
Also, my IMEI is intact. I haven't lost it. Only the MAC address is probably changed and that creates the problem. But I can't restore the original MAC address because the wlan0 interface doesn't show up in custom OS's. Only in OOS.
Edit: lol I actually already read the exact same article you've sent a link to.
freezingfox said:
I'm curious, why would you change your MAC address? Android 10 already has a MAC randomizer.
But yeah, EFS and Persist partitions are device specific and containing low level stuff that I don't think transferring it from one device to anther would work. First thing you could try is flashing stock ROM using MSM Download Tool.
Click to expand...
Click to collapse
Does it? I couldn't find it there... I know that OOS has a MAC randomizer but i don't know if other custom OS's have it. Also, could you please verify if i'm using the right tool? This is the link: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Because it's OOS 5.1.5 and that's faaaar from the newest one...
DJsushi123 said:
Does it? I couldn't find it there... I know that OOS has a MAC randomizer but i don't know if other custom OS's have it. Also, could you please verify if i'm using the right tool? This is the link: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Because it's OOS 5.1.5 and that's faaaar from the newest one...
Click to expand...
Click to collapse
The latest one is here containing 10.3.5 https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Android has had MAC randomisation since Oreo.