Related
Hello i have a Rogers dream rooted. I used speedtest.net application here are my last 10 test result in kbps...
I have a clue can it be that is lsow my connection because it always roaming?
D/U
202/1553
5/1531
2/1605
24/1697
235/533
3/7
8/-0
561/1664
19/1806
Note:those numbers are not backward!
you get the picture the download speed is very very bad upload is good.
i tryed many differents roms and kernel mix.
here is my setup for those test above
radio: 3.22.26.17
spl: dangerspl
recovery: RA-dream-v1.7.0R
rom: MT3G-test2_S + MT3G-test2-market-fix_S
kernel: ez-BiffTest2Kern_ebi1_S
i dont know how can i fix my trouble i use this phone on telus network ans tested my sim in a telus htc desire and speed is fantastic!
if you have any idea to fix my trouble it would be very very appreciated since i need some internet for my work and if i cant fic it i need a new phone and its not a good option for me now!
thank for your help.
Look up ro.rill settings, the ota being a T-Mobile stock Tom is not optimized to other networks.
But you can from recovery modify your ro.ril settings to speed things up..
(Or copy the out of the desires build.prop)
thx for the info i will try the file from my firend desire he is on telus. i edited mine but im not sure if it worked yet!
pr0cess0r said:
thx for the info i will try the file from my firend desire he is on telus. i edited mine but im not sure if it worked yet!
Click to expand...
Click to collapse
You just want the ril settings, since the rest will impact the operation of the rom. Also not all settings will work so keep a backup.
Also in other threads it's noted it may take a few restarts for it to work.
Im not able to write to system i tryed some guide in terminal and one apllication from the marking but im notable to copy prop.buil to system.
Boot into recovery, atatch your USB wire and run the following adb comands from your computer:
To pull build.prop to your computer:
Code:
adb shell mount /system
adb pull /system/build.prop build.prop
Edit the file
Then to push back:
Code:
adb push build.prop /tmp/build.prop
adb shell dos2unix /tmp/build.prop
adb shell cat /tmp/build.prop /system/build.prop
adb shell sync
adb shell um
adb shell reboot
I finally managed to change the setting from 10 to 12 and its faster but not like the desire. i get 1000 kbps somes times and upload is still faster. Thx for the help whit this !! im still wondering if roaming can make the connection slower.
pr0cess0r said:
I finally managed to change the setting from 10 to 12 and its faster but not like the desire. i get 1000 kbps somes times and upload is still faster. Thx for the help whit this !! im still wondering if roaming can make the connection slower.
Click to expand...
Click to collapse
You have a telus sim on the telus network correct? [That combo is not roaming]
There are many factors in network speed. Personally for most things I use phone data for latency is more of a problem than speed.
One other note: if you are no longer with rogers you might try changing 3.22.26.17 -> 3.22.20.17 by fastboot. (not sure it will help speed but is know to solve some other gotchas without impacting the current rom)
do i need to flash a new recovery at the same time?
pr0cess0r said:
do i need to flash a new recovery at the same time?
Click to expand...
Click to collapse
No .. if you are just going between 3.22.* radios using fastboot to flash:
The current system (including recovery, boot, system, and userdata) ought to work without any modification..
In case of problems however: so long as you flash the radio via fastboot [AND NOT recovery] you can use fastboot to restore a -R recovery and wipe the rest of the system if something goes wrong.
ezterry said:
No .. if you are just going between 3.22.* radios using fastboot to flash:
The current system (including recovery, boot, system, and userdata) ought to work without any modification..
In case of problems however: so long as you flash the radio via fastboot [AND NOT recovery] you can use fastboot to restore a -R recovery and wipe the rest of the system if something goes wrong.
Click to expand...
Click to collapse
ok i flashed this older radio but i think froyo rom wont work whit it im not 100% sure about this.
i got good spped then checked 2g only by mistake and whas not able to change it back i wiped and now im not able to get good speed again
Finally i got some speed one of my trouble is that i cant test iut at home the signal is bad just here.I listened to internet radio for 100 KM today whit no trouble.Little cut when i whas changing tower i think!
hi all i got my tab for 3 days now and all of the roms i tried and used caused me problems! i tried cm9 and paranoid android cm10
cm9- sudden reboots and screeen rotate sometimes dont work forcing me to reboot
using paranoid now and here are the issues - wifi unable to detect for watever reason , can't enter storage option in settings and can't mount!
help please!
tohno said:
hi all i got my tab for 3 days now and all of the roms i tried and used caused me problems! i tried cm9 and paranoid android cm10
cm9- sudden reboots and screeen rotate sometimes dont work forcing me to reboot
using paranoid now and here are the issues - wifi unable to detect for watever reason , can't enter storage option in settings and can't mount!
help please!
Click to expand...
Click to collapse
Wifi is working in Paranoid android...just go to advanced menu in wifi and uncheck the temporary avoiding poor connection.....Wifi tether /hotspot doesn't work.....
Storage option Force closes
For mounting external sdcard do this:
1.Create a folder in sdcard and name it emmc......
2.Open notepad and paste these lines....(Thank alroger for these commands)
busybox mount -t vfat -o rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020 /dev/block/mmcblk1p1 /sdcard/emmc
3.save the notepad file with .sh extension.....like this....emmc.sh
4.Put it in your sdcard
5.open script manager(known as smanager).. you can download on playstore.....
6.In the file browser of smanager click on the emmc.sh file in your sdcard.......
7.activate these two things......
a)Superuser
b)Boot
8.then reboot your tab and voila its done......
Click to expand...
Click to collapse
I think you have a P1000.....try AOKP build#40 by stimpz0r....It hardly needs any progress......STABLE!!!!AWESOME!!!!!GREAT!!!!!
thanks but my real issue is wifi i can't connect to play store without it , anyways i can detect other wifis but not my wifi ...crap
Hello, I am very new to this forum. I searched everywhere but couldn't find an answer to my problem. I really appreciate it if you can help me as I am a total noob in android.
Previously my power button was a little buggy, it works on and off, and I solved it by wiping the partition cache in stock recovery <e3>.
My power button completely stopped working today for no reason that I know off.
Out of frustration, I tried what I did last time by booting into recovery mode (using quickboot this time) but then to realise that I can't choose anything/ get out of the recovery mode.
Nothing works by removing the battery. When the battery is reinserted, it boots back into recovery.
My phone is rooted, non CWM. Has a bad eMMC chip with a susceptible kernel. (latest update from KiES, no custom ROMs)
I got this phone as a prize, so there's no warranty that comes with it.
What can I do now? I have heard of this ADB thing but I have no idea how it works. Does it help? If so, how?
Thank you.
Edit: Service centre fixed it. Turns out its a pretty complex issue.
Click to expand...
Click to collapse
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
Hello, thank YOU very much! I got it to reboot properly and working. And I learnt a lot in the meantime.
Words cannot express my gratitude right now.
I have another question though, is it possible for me to wipe partition cache thru adb?
yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot
nokiamodeln91 said:
yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot
Click to expand...
Click to collapse
Okay, so I tried to do what you suggested, and got stuck at adb root. This is what I got in return:
"Adbd root cannot run as root in production builds"
So what I did was to skip to the second step,
"adb shell"
This is what I got in return:
[email protected]:/ $
I entered the command "su", granted su access on my phone using supersu (got a pop-up) and got this:
[email protected]:/ #
Moving on, I entered "cache /mount" and it repeatedly failed to mount.
I read up a bit of it and it seems like its because my bootloader is not unlocked.
But given the fact that my power button is malfunctioned, I cannot unlock it by normal means. I gave some thought onto PhilZ safe kernel but then the fact that my phone is susceptible to brick if I unlock the bootloader (there will be a data wipe right?) makes me stuck at where I am now.
What are your recommendations?
Additional info on eMMC:
[email protected]:/sys/class/block/mmcblk0/device # cat cid | cut -b 19,20
gives back: 19 (susceptible)
[email protected]:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid date type
gives:
Name: VYL00M
HwRev: 0x0
FwRev: 0x0 (not completely safe)
Manfid: 0x000015
Oemid: 0x0100
Date: 01/2012
Type: MMC
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
you saved me big time!!
I have almost the same problem
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?
FluffyBunneh said:
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?
Click to expand...
Click to collapse
Did you find a solution for this?
My Samsung j7 is stuck in recovery mode and power button is broken...and my USB debugging is also ON but phone is NOT detecting On PC...not even in DEVICE MANAGER...I checked in ADB deveices command but still nothing...help me....
FluffyBunneh said:
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?
Click to expand...
Click to collapse
I also have the same problem, my phone is now stuck in recovery, and without power button I am not able to bring it out of recovery mode, did you manage to find a fix for this? My phone is not getting listed in "adb devices"!
Phone:SM J200G
After installing stock rom via odin
I enter into recovery mode and forget to on USB debugging. Also my power button dead.
What to do? Now?
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
hey i got the same problem when i charged my phone after it turn of (low bat). Recovery mode suddenly showed up and i cant choose reboot system now because the lock button is stuck. So i tried the adb and installed it but when i tried to use it . it cant find my device the usb cord is 100% working and idk what to do anymore
I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
please help i have the same problem but my device is not recognized
bryll1022 said:
hey i got the same problem when i charged my phone after it turn of (low bat). Recovery mode suddenly showed up and i cant choose reboot system now because the lock button is stuck. So i tried the adb and installed it but when i tried to use it . it cant find my device the usb cord is 100% working and idk what to do anymore
Click to expand...
Click to collapse
please help i have the same problem
MaeButArt said:
I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.
Click to expand...
Click to collapse
did you find a solution i have the same problem
MaeButArt said:
I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.
Click to expand...
Click to collapse
same did anyone find solution for this?
nokiamodeln91 said:
yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot
Click to expand...
Click to collapse
when i plug my phone to pc its not connecting if i use commang adb reboot its say "error: no devices/emulators found"
Ive encounter that problem with j4 + what i did is just let the battery run out after that be ready to press button for download mode and insert charging cable to phone, hope this will help on your problem
x33eraser said:
Hello, I am very new to this forum. I searched everywhere but couldn't find an answer to my problem. I really appreciate it if you can help me as I am a total noob in android.
Previously my power button was a little buggy, it works on and off, and I solved it by wiping the partition cache in stock recovery <e3>.
My power button completely stopped working today for no reason that I know off.
Out of frustration, I tried what I did last time by booting into recovery mode (using quickboot this time) but then to realise that I can't choose anything/ get out of the recovery mode.
Nothing works by removing the battery. When the battery is reinserted, it boots back into recovery.
My phone is rooted, non CWM. Has a bad eMMC chip with a susceptible kernel. (latest update from KiES, no custom ROMs)
I got this phone as a prize, so there's no warranty that comes with it.
What can I do now? I have heard of this ADB thing but I have no idea how it works. Does it help? If so, how?
Thank you.
Click to expand...
Click to collapse
Sorry i hope i post this right first timer your guide didnt workt but i found a workaround:
usbc to usb adapter i tryed a mouse not working but my cheab truest cxt tastatur ACCEPTED THE ENTER BUTTON
and i came out of this because only repair loking cost 60 bucks .not with me i hope this help others too
i am doing a tiktok video on it(guide) PrestigeWorldWideUS
buy usbc to usb adapter i try your keybords sorry my english
Hi!! Yesterday i've triyed to flash cm12.1 in my i9070. It was not working good (fc in some apps), so i've decided to go back to cm11 with my NANDROID. Ok, just fine. BUT!! When i boot in recovery, TWRP shown me a EFS error ( E: unable to mount /efs). After several data, cahce and system wipes, I've managed to load de nandroid. The phone loaded great, except for WIFI! It can be turned on, and it shows wifi nets, but can´t conect to none of them. Problem? Mac address is 00:00:00:00:00:00 in About phone -> Status.
I´ve checked the nvram_net.txt and it has a macaddr inside.
What can i do? Why is my phone not "loading" the propper mac??
Thanks, and sorry about my english, i´m from argentina.
Abrazo a todos!:fingers-crossed:
solauciel said:
Hi!! Yesterday i've triyed to flash cm12.1 in my i9070. It was not working good (fc in some apps), so i've decided to go back to cm11 with my NANDROID. Ok, just fine. BUT!! When i boot in recovery, TWRP shown me a EFS error ( E: unable to mount /efs). After several data, cahce and system wipes, I've managed to load de nandroid. The phone loaded great, except for WIFI! It can be turned on, and it shows wifi nets, but can´t conect to none of them. Problem? Mac address is 00:00:00:00:00:00 in About phone -> Status.
I´ve checked the nvram_net.txt and it has a macaddr inside.
What can i do? Why is my phone not "loading" the propper mac??
Thanks, and sorry about my english, i´m from argentina.
Abrazo a todos!:fingers-crossed:
Click to expand...
Click to collapse
Hi, there.
Did you do a full wipe and flash a stock ROM using Odin? If not, try to.
Good luck!
solauciel said:
Hi!! Yesterday i've triyed to flash cm12.1 in my i9070. It was not working good (fc in some apps), so i've decided to go back to cm11 with my NANDROID. Ok, just fine. BUT!! When i boot in recovery, TWRP shown me a EFS error ( E: unable to mount /efs). After several data, cahce and system wipes, I've managed to load de nandroid. The phone loaded great, except for WIFI! It can be turned on, and it shows wifi nets, but can´t conect to none of them. Problem? Mac address is 00:00:00:00:00:00 in About phone -> Status.
I´ve checked the nvram_net.txt and it has a macaddr inside.
What can i do? Why is my phone not "loading" the propper mac??
Thanks, and sorry about my english, i´m from argentina.
Abrazo a todos!:fingers-crossed:
Click to expand...
Click to collapse
if you have /efs backup restore it and you will get mac no back..
if you don't have /efs backup and you still remember old mac no. then go to /efs/wifi/ open .mac_info file with text editor and type your mac no there in aa:bb:cc:dd:ee:ff format and save it
and reboot
you need rooted device & root explorer for this
( btw you can put any other no. for mac address as well but it's not recommended so you default if you still remember it )
hoping this'll help
MAC address can be whatever - it just needs to be propper format (characters in hex code: 0-9, a-f) and I wouldn't say it is not recommended to use this or that MAC - all are equally valid
even the one you posted as example is valid and can be used - obvious spoof as there is no vendor assigned to aa:bb:cc but it should work
all that matters is that there are no 2 exact same MAC addresses in single network
Sent from my TF300T using XDA Free mobile app
Me too...having the same problem. I was switching from MaxiCM to RR, all went great but the mac address went down to zeroes!! I tried everything - changed macaddr in nvram_mfg and nvram_net (i got 2 files) in /system/etc/wifi, but no use. i'm now using this "Wifi Mac Changer" but its temporary. PLzz Help!!
manaf_ek said:
Me too...having the same problem. I was switching from MaxiCM to RR, all went great but the mac address went down to zeroes!! I tried everything - changed macaddr in nvram_mfg and nvram_net (i got 2 files) in /system/etc/wifi, but no use. i'm now using this "Wifi Mac Changer" but its temporary. PLzz Help!!
Click to expand...
Click to collapse
reflash the stock firmware with saperate 5 files like pit pda csc bL cp try flashing them u can find them on google search and download them hope this work
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.