Related
Latest and stable Wifi Driver for Android 2.1, Build SHOLS_U2_02.36.0
Build for the kernel "2.6.29-omap1"
** Stable and without any Wifi drop problem, which is compiled from the latest source from Google Android Repository. **
I recently found out that the Wifi driver of the latest Froyo 2.2.1 of Milestone that released by G.O.T. team is a new build and very stable. Therefore, I tried to pull the latest TIWLAN Wifi driver source code from the Google Android Source Repository (http://android.git.kernel.org/?p=platform/hardware/ti/wlan.git;a=summary), and compile it for the ROM build "SHOLS_U2_02.36.0", kernel "2.6.29-omap1".
I succeeded to compile as "tiwlan_drv.ko", and use it with the latest firmware "fw_wlan1271.bin" from the Froyo 2.2.1 build, and finally uses on the "SHOLS_U2_02.36.0", and the result is very stable wifi connection with the proprietary power saving feature .
I am using the ROM South Asia SHOLS_U2_02.36.0, I am not sure if it can be used with any other ROM, but normally should work on any kernel which have the version "2.6.29-omap1".
I did it because that the latest Froyo 2.2.1 beta ROM is not stable enough and the battery drain fast, but it have the stable wifi connection, so I compiled it for 2.1.
Enhancement:
Much more stable WIFI connection, no more connection drop within good signal environment.
No more WIFI freeze occur, will auto re-connect to AP if back to the signaled environment.
Much much much more battery saving (IT IS THE MOST IMPORTANT), can also feel that impressively in using "android-wireless-tether".
!!! Use it at YOUR OWN RISK !!!
Make a backup of "/system/lib/modules/tiwlan_drv.ko" and "/system/etc/wifi/fw_wl1271.bin".
Copy the file "tiwlan_drv.ko" to "/system/lib/modules/", and copy the file "fw_wl1271.bin" to "/system/etc/wifi/".
** WARNING **
Normally should work on any ROM which have the kernel version "2.6.29-omap1", BUT I didn't test it for any ROM other than SHOLS_U2.02.36.0, so USE IT AT YOUR OWN RISK!!!
It may result in bootloop in case if you did something wrong or not compatible with your ROM (need to revert back to the old driver with OpenRecovery + adb).
Therefore, it is only for advanced users, and ALWAYS MAKE FULL BACKUP of your milestone.
Download link:
http://www.sendspace.com/file/ln3xm7
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[EDIT]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
[EDIT2]Woo! Works!
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[Edit]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
Click to expand...
Click to collapse
"fw_tiwlan_ap.bin" is the firmware required for the Froyo 2.2.1 to use Wifi Hotspot, it did nothing on Android 2.1, so just simply ignore it.
and Thanks for pointing out the location of placing the "fw_wlan1271.bin" file, I will modify it.
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb
[EDIT2]Woo! Works!
Click to expand...
Click to collapse
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
How can I copy and paste to the system?
Thanks!
royshum said:
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
Click to expand...
Click to collapse
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
How can I copy and paste to the system?
Thanks!
Click to expand...
Click to collapse
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Lollipop_Lawlipop said:
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Click to expand...
Click to collapse
failed to copy - read only!
chungtau said:
failed to copy - read only!
Click to expand...
Click to collapse
You must have a rooted milestone in order to process.
Before you using adb push, try to remount your /system partition first.
Or you can try the following commands.
Ensure your wifi is turned off first.
*** Remember to make FULL BACKUP for your milestone before proceeding the following commands. ***
Code:
C:\android-sdk-windows\tools>adb push tiwlan_drv.ko /sdcard/tiwlan_drv.ko
C:\android-sdk-windows\tools>adb push fw_wl1271.bin /sdcard/fw_wl1271.bin
C:\android-sdk-windows\tools>adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock6 /system
# cd /system/lib/modules
# mv tiwlan_drv.ko tiwlan_drv.ko.bak
# cp /sdcard/tiwlan_drv.ko ./tiwlan_drv.ko
# chmod 644 tiwlan_drv.ko
# cd /system/etc/wifi
# mv fw_wl1271.bin fw_wl1271.bin.bak
# cp /sdcard/fw_wl1271.bin ./fw_wl1271.bin
# chmod 644 fw_wl1271.bin
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
And now, you can try turning on your wifi.
In case if there is any problem occurred, you may reboot into OpenRecovery, revert the drivers from "tiwlan_drv.ko.bak" and "fw_wl1271.bin.bak".
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Lollipop_Lawlipop said:
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
Click to expand...
Click to collapse
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network .
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
You haven't read the instructions carefully. It is the latest wifi driver for "2.1", not "2.2.1", as it is supposed to compile the driver from "2.2.1" down to "2.1".
So for 2.2.1, by default, you are already have the latest wifi driver (at least a stable wifi driver), it is no clue for using it.
royshum said:
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network :
Click to expand...
Click to collapse
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Btw, CM6 uses the file name fw_wlan1271.bin. I'm guessing stock Android from Moto looks for fw_wl1271.bin (just guessing... can't exactly prove it since I'm not running stock Android), which was why I was trying to correct you (although it seems to me both of us are right).
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
If you're running 2.2.1-CM6 you can extract the files from the update zip and adb push them into the phone. That is, if you're on CM6. If not, well... you can either upgrade to CM6 or go into fastboot and restore the sbf again.
Lollipop_Lawlipop said:
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Click to expand...
Click to collapse
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
MenoDev said:
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Click to expand...
Click to collapse
Yes, I have the same suspicion as well.
MenoDev said:
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
Click to expand...
Click to collapse
Can you go into a bit of detail on that? I'm interested
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
works flawless, extreme improvement, thank you very much!
Lollipop_Lawlipop said:
Yes, I have the same suspicion as well.
Can you go into a bit of detail on that? I'm interested
Well, I use to code similar stuff but I am complete new to android so i have to read the dev guide, if I had no guide I'd probably create a dump, see according the file descriptor where the tables and storage are are located, then set a "write" flag on the file system and flush it to avoid a manual battery pull. but i'm sure there's more elegant ways.
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
Click to expand...
Click to collapse
I made a little research and found a working solution, tested it myself.
Apparently it can happen that the resolved DNS can not be stored under certain circumstances, (in order to trace those, i try to avoid the "out of the box" mods, even though the guys make a tremendous job, but i feel more secure and have a higher learning curve by doing stuff myself).
In order to avoid random disconnects from network or wifi, or worst case both, add the following lines of code to /system/default.prop
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
These are the google dns, most probably the best choice. You can find this out if you fire up the "getprop" command.
I've seen that most Recovery tools such as the G.O.T one, have implemented the DNS fix, but personally I prefer to just fire up a terminal from the phone and add these lines manually with some comment, so i know what and why I'm doing stuff.
Hope this helps, let me know.
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it didn'tsolve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
b787 said:
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it solve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
Click to expand...
Click to collapse
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
MenoDev said:
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
Click to expand...
Click to collapse
I did turn off wifi before copying any files. However, I didn't rebooted before I tried to start wifi, only after I noticed it doesn't work.
Fix for 2.2.1 Possible?
I have the same issue with my home WIFI network on 2.1 and 2.2.1: namely the connection drops during large transfers (such as a Market app download) and I have to turn WIFI off and on again to have connectivity again.
I wonder if 2.2.1 really has the latest firmware baked in...how would I compile the TI firmware for 2.2.1?
Hi ,
I was using JP6 (via Reg. Hack...), as we know that, Samsung has released official Froyo update... I downgraded to Eclair i.e., (DDJG4) ... Now, i can use all functions of Galaxy S , except Mobile Network.
My Phone application is not working anymore...it just shows me, Not available icon for network signal.... More over, i cannot do Factory Reset from Settings menu...its doing nothing....
Please help !
No idea what you did but it sounds like you screwed up your IMEI, do a search for fixes but unless you have a backup file you might be out of luck
Virtualsk said:
Hi ,
I was using JP6 (via Reg. Hack...), as we know that, Samsung has released official Froyo update... I downgraded to Eclair i.e., (DDJG4) ... Now, i can use all functions of Galaxy S , except Mobile Network.
My Phone application is not working anymore...it just shows me, Not available icon for network signal.... More over, i cannot do Factory Reset from Settings menu...its doing nothing....
Please help !
Click to expand...
Click to collapse
I also faced the same problem see this thread. It will solve your problem
**IF YOUR SIMCARD DOESN'T WORK AFTER THIS, EXECUTE THE FOLLOWING**
- adb shell
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot
You can also do this from the Terminal Emulator if you don't have ADB on your PC! Like this:
-su
-chown 1001:1001 /efs/nv_data.bin
-reboot
I hope it's easy to follow my steps, it works guaranteed.
http://forum.xda-developers.com/showthread.php?t=780509
Solved ... using same link...
seking said:
I also faced the same problem see this thread. It will solve your problem
**IF YOUR SIMCARD DOESN'T WORK AFTER THIS, EXECUTE THE FOLLOWING**
- adb shell
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot
You can also do this from the Terminal Emulator if you don't have ADB on your PC! Like this:
-su
-chown 1001:1001 /efs/nv_data.bin
-reboot
I hope it's easy to follow my steps, it works guaranteed.
http://forum.xda-developers.com/showthread.php?t=780509
Click to expand...
Click to collapse
Last friday, i fixed it using the same command...Actually, few weeks back I also restored by Product code refering to this thread.... Now i am waiting for official Froyo....
When I try "chown" I get "no such user" .
seking said:
I also faced the same problem see this thread. It will solve your problem
**IF YOUR SIMCARD DOESN'T WORK AFTER THIS, EXECUTE THE FOLLOWING**
- adb shell
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot
You can also do this from the Terminal Emulator if you don't have ADB on your PC! Like this:
-su
-chown 1001:1001 /efs/nv_data.bin
-reboot
I hope it's easy to follow my steps, it works guaranteed.
http://forum.xda-developers.com/showthread.php?t=780509
Click to expand...
Click to collapse
Hi, I tried using this and I got this error:
Permission denied
$ busybox chown 1001:1001 /efs/nv_data.bin
chown: /efs/nv_data.bin: Read-only file system
$
Click to expand...
Click to collapse
Any idea how to remove the read-only for the files in the efs folder?
xCruciaLx said:
Hi, I tried using this and I got this error:
Any idea how to remove the read-only for the files in the efs folder?
Click to expand...
Click to collapse
You have to rooted....
sori to disturb but....no option.
I am not a techie guy like u...so..please help me out. I am using my samsung i9000 which is bought from Ireland and now I am using in India. Its smifree and unlocked so using it nisely. But unfortunately...i lost ime imei and network when I tried to upgrade my firmware or something. I dont know what is the base version and i dont know what to do now....?
please help me guys.....as my phone not ringing due to missing imei or some other problem.
Thanks & Regards,
Ravi
raviakumarin said:
sori to disturb but....no option.
I am not a techie guy like u...so..please help me out. I am using my samsung i9000 which is bought from Ireland and now I am using in India. Its smifree and unlocked so using it nisely. But unfortunately...i lost ime imei and network when I tried to upgrade my firmware or something. I dont know what is the base version and i dont know what to do now....?
please help me guys.....as my phone not ringing due to missing imei or some other problem.
Thanks & Regards,
Ravi
Click to expand...
Click to collapse
Try to follow the thread and see if that helps. If not than there is one thread in sgs ii section check that out.
Sent from my GT-I9100 using xda premium
Hi everyone! I have updated two days ago my ROM from gingerDX v28 to v28b, and since then I have noticed my phone has started to reboot too often, most of the times when trying to change the network configuration between 2g and 3g through the buttons on the status bar, but also when opening heavy apps. It sometimes reboots from the alfs kernel screen and other times from the gingerDX animation. I have latest alfs kernel, and the alfs addon pack installed. It started also with reboots on the "insert pin code" screen, but that was solved with a full wipe. Does anyone know why can this be happening? May it be an overclock issue? I have the cpu set between 122 and 729 Mhz, and I don't think it's too much because i have had that configuration for a long time and it has never caused reboots. Anyone can help? Thanks in advance.
Edit: solved. It was finally a problem of too many apps installed and running in background causing many low memory situations and lots of errors. B.Jay adviced me to do a full wipe, and now i have installed just the apps I need. Now there are no reboots and the user experience has been improved a lot.
Yes...overclock problem.. disable overclock!
Sent from my E15i using xda premium
maybe low ram is causing the problem..
Try swapping ur SD card..it might help u.
harshitgroup said:
maybe low ram is causing the problem..
Try swapping ur SD card..it might help u.
Click to expand...
Click to collapse
No, in alfs no problem with ram..only for stock
danygarss said:
most of the times when trying to change the network configuration between 2g and 3g through the buttons on the status bar
Click to expand...
Click to collapse
Yes, there is some weird "crash-and-burn" problem when the phone runs 2G ... yarik2720 reported it already (he has a single "blind spot" in the city where he lives where the phone reboots when it falls back to 2G).
Now, to solve the problem it would be insanely helpful to have a logcat from when it happens so I can try and help eagleeyetom to fix it up ... no logcat, nothing we can really do to track down the root of the problem (can't replicate it as I only have 3G (HSDSP, HSUPA, HSPA) all around me - no old-fashioned 2G anymore).
Get a logcat from when it happens it, post it to pastebin, put the link here or PM it eagleeyetom so it can be investigated.
B.Jay said:
Yes, there is some weird "crash-and-burn" problem when the phone runs 2G ... yarik2720 reported it already (he has a single "blind spot" in the city where he lives where the phone reboots when it falls back to 2G).
Now, to solve the problem it would be insanely helpful to have a logcat from when it happens so I can try and help eagleeyetom to fix it up ... no logcat, nothing we can really do to track down the root of the problem (can't replicate it as I only have 3G (HSDSP, HSUPA, HSPA) all around me - no old-fashioned 2G anymore).
Get a logcat from when it happens it, post it to pastebin, put the link here or PM it eagleeyetom so it can be investigated.
Click to expand...
Click to collapse
Thanks for the fast response! I really would like to help with the feedback since gingerDX is a ROM I have been using for 8 months or more, and somehow I have a debt with doixanh and of course the whole new gingerDX team wich has improved it's ROM so much. Sorry for the noob question, how can I have that logcat you talk about? I will try to give feedback next time it reboots. Thanks again!
danygarss said:
Sorry for the noob question, how can I have that logcat you talk about? I will try to give feedback next time it reboots. Thanks again!
Click to expand...
Click to collapse
Get yourself adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll (if you haven't installed the SDK) and put the three files into, for example, C:\Windows. You can obtain the files by downloading the Platform Tools ZIP directly from Google.
Enable USB-Debugging on the phone and connect it to your computer (you need the SEMC drivers installed apparently).
Open the command prompt, type:
adb logcat > C:\Users\<your username>\Downloads\logcat.log
Force the error.
Once it crashed let it boot up ... then press CTRL+C to terminate adb.
Copy/Paste the WHOLE contents of logcat.log to pastebin.com and paste the link here or PM it.
B.Jay said:
Get yourself adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll (if you haven't installed the SDK) and put the three files into, for example, C:\Windows. You can obtain the files by downloading the Platform Tools ZIP directly from Google.
Enable USB-Debugging on the phone and connect it to your computer (you need the SEMC drivers installed apparently).
Open the command prompt, type:
adb logcat > C:\Users\<your username>\Downloads\logcat.log
Force the error.
Once it crashed let it boot up ... then press CTRL+C to terminate adb.
Copy/Paste the WHOLE contents of logcat.log to pastebin.com and paste the link here or PM it.
Click to expand...
Click to collapse
Thanks! Now I know how to get logcats! I have tried it, but today it didn't reboot, bad luck... i have tried changing the network configuration lots of times and forcing to send-receive data by using self messages through whatsapp in both 2g and 3g mode but everything worked fine... maybe it was something related to a network incidence that my carrier (movistar) had here in madrid last days (2g data EDGE network wasnt working), I reported it and they called me this morning to advise everything is now fixed, I tried and now 2g data works. I didn't think that a disconnection from the carrier was related to reboots on my phone's system, so i dindn't mention it in the thread, but since the reboots have stopped the same time as the connection is fixed from the carrier I don't know what to think... Thanks anyway! If this happens again I will try to get another logcat and send to you. I am sending you anyway the logcat of this non-rebooting sesion for if it helps you anyway. Thanks for the hard work and your wonderfull ROM!
Cool, it has solved my problem thanks!:laugh:
I have problem with WIFI keeps turning on but it never turn on like usual, i tried flash stock rom neswest build and do factory reset it with no luck.
Searching around internet and found that there are some Nexus5 user can fix it by delete folder of mac address (they said it is in /persist/wifi folder) buti cant find that folder in my Marshmallow. Anyone knows how to fix this i think it is something wrong with corrupted MAC address it quite weird that my MAC Address is 20:00:00:00:00:00
Got EXACTLY the same issue...I tried to flash all available roms, right from 5.0.0 to the latest 6.0 and no luck...Wifi and Bluetooth are non existent now! Is your bluetooth ok?? And its not 20.00.....its 02.00.00.....pls check again...
pradipsoman said:
Got EXACTLY the same issue...I tried to flash all available roms, right from 5.0.0 to the latest 6.0 and no luck...Wifi and Bluetooth are non existent now! Is your bluetooth ok?? And its not 20.00.....its 02.00.00.....pls check again...
Click to expand...
Click to collapse
Messed up EFS partition? If you don't have a backup i *think* the device is hard bricked > repair
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Droidphilev said:
Messed up EFS partition? If you don't have a backup i *think* the device is hard bricked > repair
Click to expand...
Click to collapse
How can a messed up EFS prevent the WIFI and Bluetooth from working? All other features work well. And if the partition is messed up and device is hard bricked, how does it work and all the other features work...Could you explain please...and if you have the knowledge could you give any tips to get it right?
pradipsoman said:
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
How can a messed up EFS prevent the WIFI and Bluetooth from working? All other features work well. And if the partition is messed up and device is hard bricked, how does it work and all the other features work...Could you explain please...and if you have the knowledge could you give any tips to get it right?
Click to expand...
Click to collapse
AFAIK the factory puts files in that partition that includes the wifi MAC, BT MAC, IMEI etc etc. From there the rom reads the mac addresses. If it cannot find these then wifi won't turn on. I may be wrong that this is the case though. I had a problem with a tablet before. Flashing something caused that the permissions of that file became wrong, i had no wifi either. Luckily for me the file was still there and changing permissions fixed it. Is you IMEI still shown correctly in "about"?
Droidphilev said:
AFAIK the factory puts files in that partition that includes the wifi MAC, BT MAC, IMEI etc etc. From there the rom reads the mac addresses. If it cannot find these then wifi won't turn on. I may be wrong that this is the case though. I had a problem with a tablet before. Flashing something caused that the permissions of that file became wrong, i had no wifi either. Luckily for me the file was still there and changing permissions fixed it. Is you IMEI still shown correctly in "about"?
Click to expand...
Click to collapse
Yes, my IMEI is shown correctly but wifi mac id shown as a bogus number i.e 02.00:00:00:00:00
pradipsoman said:
Yes, my IMEI is shown correctly but wifi mac id shown as a bogus number i.e 02.00:00:00:00:00
Click to expand...
Click to collapse
That's something i guess. Otherwise you wouldn't be able to make calls any further. Hopefully you will find a way to fix. Please report here.
Droidphilev said:
That's something i guess. Otherwise you wouldn't be able to make calls any further. Hopefully you will find a way to fix. Please report here.
Click to expand...
Click to collapse
Could it be related to the /persist folder
pradipsoman said:
Could it be related to the /persist folder
Click to expand...
Click to collapse
check PM.
Can you tell us exactly what you were doing when this happened? you flashed a rom or something like that? Would be good to know.
Droidphilev said:
check PM.
Can you tell us exactly what you were doing when this happened? you flashed a rom or something like that? Would be good to know.
Click to expand...
Click to collapse
I was on 5.1.1 and then everything was working fine...I installed the 6.0 OTA and then this happened....
Went ahead and did the hard brick repair method to see if that would help, but even after that the problem persists!
pradipsoman said:
Went ahead and did the hard brick repair method to see if that would help, but even after that the problem persists!
Click to expand...
Click to collapse
the unbrick thing or the persist thing?
you guys do realize that google is using the wifi to figure out your location, right? even if you never ever turn wifi on. you have to disable scanning in the location settings for google not to use the wifi.
none
If you had a hard bricked device you would know it because your phone would have a black screen and you would have a paperweight
I did everything...including the persist wipe etc....No use...seems the wifi/bluetooth chip is dead after the 6.00 OTA update
pradipsoman said:
I did everything...including the persist wipe etc....No use...seems the wifi/bluetooth chip is dead after the 6.00 OTA update
Click to expand...
Click to collapse
Have you tried setting a custom MAC yet?
Had this for my old N5:
Code:
cd /persist
rm -rf bluetooth
mkdir bluetooth
chown bluetooth:system ./bluetooth
chmod 770 ./bluetooth
echo -ne '\xBC\xF5\xAC\x70\xA9\x5F' > ./bluetooth/.macaddr
chown bluetooth:system ./bluetooth/.macaddr
chmod 660 ./bluetooth/.macaddr
rm -rf wifi
mkdir wifi
chown wifi:system ./wifi
chmod 770 ./wifi
echo -ne '\x8c\x3a\xe3\x41\x8d\x79' > ./wifi/.macaddr
chown wifi:system ./wifi/.macaddr
chmod 660 ./wifi/.macaddr
Reboot afterwards. Of course you'll need root.
Some things to keep in mind:
1. Not all MAC addresses worked for me. setting 1234567890 would cause wifi to get stuck at turning on. Some MACs work, some don't. Didn't bother to find out why.
2. The addresses above are for my old N5, you're free to try them if you want. That motherboard is toast.
3. My N5 died due to a wifi/bt chip burn out. Manufacturing defect. Hence my investigation into the issue and whatnot.
I have the exact same problem but with a completely stock, never-rooted Nexus 6. Marshmallow 6.0 OTA arrived a week after the 1 year Motorola warranty expired, and problems with screencasting started immediately. But yesterday, the wifi quit, and the phone rebooted itself moments later. The wifi has never come back on since. I also noticed the bogus 02:00:00:00:00:00 mac address, suggesting that something got corrupted. For reference, this phone was purchased directly from Motorola, and is using a VZW sim.
Of course there's nothing Motorola will do, since it's 2 weeks out of warranty. But I'm hopeful that the hardware is still alright since I can still turn bluetooth on and off. Can someone confirm that this phone's BT and Wifi are on the same chip? I suppose there is no reason not to root it now...
I'd like to try to set the mac address using the above code. Can anyone suggest a way to retrieve the old mac? Thanks...
Not working..
toastgodsupreme said:
Have you tried setting a custom MAC yet?
Had this for my old N5:
Code:
cd /persist
rm -rf bluetooth
mkdir bluetooth
chown bluetooth:system ./bluetooth
chmod 770 ./bluetooth
echo -ne '\xBC\xF5\xAC\x70\xA9\x5F' > ./bluetooth/.macaddr
chown bluetooth:system ./bluetooth/.macaddr
chmod 660 ./bluetooth/.macaddr
rm -rf wifi
mkdir wifi
chown wifi:system ./wifi
chmod 770 ./wifi
echo -ne '\x8c\x3a\xe3\x41\x8d\x79' > ./wifi/.macaddr
chown wifi:system ./wifi/.macaddr
chmod 660 ./wifi/.macaddr
Reboot afterwards. Of course you'll need root.
Some things to keep in mind:
1. Not all MAC addresses worked for me. setting 1234567890 would cause wifi to get stuck at turning on. Some MACs work, some don't. Didn't bother to find out why.
2. The addresses above are for my old N5, you're free to try them if you want. That motherboard is toast.
3. My N5 died due to a wifi/bt chip burn out. Manufacturing defect. Hence my investigation into the issue and whatnot.
Click to expand...
Click to collapse
Tried changing the mac id as per this method...Does not work..After reboot still shows the bogus id 02:00:00:00:00:00
Thanks for all supported here, seems so many people got tge same problem as mine.
I never unlock bootloader on this device, im at 5.1.1 and it happens with my wifi shows wrong mac address so i just tried to ota to 6.0 and the issue is still there? Anybody find the cause pf problem here?
pradipsoman said:
Tried changing the mac id as per this method...Does not work..After reboot still shows the bogus id 02:00:00:00:00:00
Click to expand...
Click to collapse
Did you happen to try setting it to its original mac, or to some other valid broadcom mac? Or did it fail after setting a random mac. I ask because I am about to root my wife's phone just to attempt this same procedure...
If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).
Just so others know, TWRP under the "Advanced" menu item has a "File Manager" which allows you to remove each of these files. That's important for those who can't get to a PC with a working adb to mount the shell. I used OTG external storage to access the OTA and Magisk zips for flashing and storage of my nandroid backup.
Personally I would need the File Manger as I have a fully functioning PC fastboot but for some reason can't see my OP5 using adb. Not a big deal but there is a user-friendly built right into TWRP which always has "root" privileges to "/data".
zdimension said:
If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).
Click to expand...
Click to collapse
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".
Dchoi229 said:
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".
Click to expand...
Click to collapse
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.
zdimension said:
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.
Click to expand...
Click to collapse
Thanks for the response Z! I just tried it and my wifi isn't stable at all when trying to connect to wifi. It's my workplace wifi that I usually have to sign into to access. It'll connnect and disconnect constantly. Is there anything you'd advise me to do?
Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.
buzzfuzz1 said:
Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.
Click to expand...
Click to collapse
Nah, the command is supposed to be run when the phone is in TWRP.
First, you use adb shell to open a terminal from your PC (ignore this step if you want to use TWRP's integrated terminal directly on the phone).
Then, when you're in the shell, run the rm command.
Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?
buzzfuzz1 said:
Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?
Click to expand...
Click to collapse
The file the command deletes is basically the "Wi-Fi" settings file, which contain identification settings for the network card amongst other things. If you keep the Nougat one while you're on Oreo, you can't turn on Wi-Fi, or use anything related to the Wi-Fi antenna; Thus, we delete it. That solves the problem "Wi-Fi doesn't turn on". Here, you've got another problem: "Wi-Fi can't connect". I have no clue of what could be causing this, this issue never happened to me. I'm gonna search a bit and update here if I find anything.