Hey everyone I am getting a new phone and would like to use my Inc as a mp3 player. I'm looking for a Wifi only ROM not script. If any roms have a wifi only mode that you can choose when you first pick a Tom that would be great. Thanks for any suggestions
Sent from my ADR6300 using XDA
Bump
Sent from my ADR6300 using XDA
bmx5494 said:
Hey everyone I am getting a new phone and would like to use my Inc as a mp3 player. I'm looking for a Wifi only ROM not script. If any roms have a wifi only mode that you can choose when you first pick a Tom that would be great. Thanks for any suggestions
Click to expand...
Click to collapse
Is there a reason why you don't want the script? The beauty of the script is that you can use any ROM you want and use the script to make it wifi-only. Most people pick a ROM that they like and get good battery life with, and then just apply the script.
Aside from the couple of seconds it takes to flash the script, I cant envision any real benefit of having a ROM designed to be wifi-only vs. a ROM made to become wifi-only.
I'm also not sure what picking a "Tom" means... but it's probably not as important as my first question.
Really I did not know that. So when I flash the script what will change on the Rom? And do I need to wipe everything before I flash the script? Oh and spell correct changed Rom to tom and I didn't catch it...........
Sent from my ADR6300 using XDA
bmx5494 said:
Really I did not know that. So when I flash the script what will change on the Rom? And do I need to wipe everything before I flash the script? Oh and spell correct changed Rom to tom and I didn't catch it...........
Sent from my ADR6300 using XDA
Click to expand...
Click to collapse
As far as I know, it doesn't "change" anything... it just disables the radios (except wifi). Think of it like putting your phone in Airplane mode, but the wifi still works. As for wiping, I'm not sure. I've never used the script before.
demarcmj said:
As far as I know, it doesn't "change" anything... it just disables the radios (except wifi). Think of it like putting your phone in Airplane mode, but the wifi still works. As for wiping, I'm not sure. I've never used the script before.
Click to expand...
Click to collapse
Actually wifi works with airplane mode on you just have to turn wifi back on. However with sense you have to do that every boot, not on aosp though. Because of this and to avoid draining battery, the script sounds better for the op.
Sent from my Galaxy Nexus using Tapatalk 2
demarcmj said:
As far as I know, it doesn't "change" anything... it just disables the radios (except wifi). Think of it like putting your phone in Airplane mode, but the wifi still works. As for wiping, I'm not sure. I've never used the script before.
Click to expand...
Click to collapse
All the script does is install a startup script that runs another system script called "radio_options" in /system/bin with an option of 1, dissabling the radio. No wiping is required, and can be removed at any time.
Thanks this helped a lot!
Sent from my ADR6300 using XDA
does anyone have a link to such a script? I remember seeing one a while back but I can't find it anymore. I have turned my D2G into an mp3 player device so I was hoping for the same outcome. Plus it's cleaner to not have a radio attempting to connect all the time.
EDIT: Nevermind, I was under the impression it was a script one would flash, not something you could do yourself with script manager.
nschiwy said:
does anyone have a link to such a script? I remember seeing one a while back but I can't find it anymore. I have turned my D2G into an mp3 player device so I was hoping for the same outcome. Plus it's cleaner to not have a radio attempting to connect all the time.
EDIT: Nevermind, I was under the impression it was a script one would flash, not something you could do yourself with script manager.
Click to expand...
Click to collapse
You just make a file with no extension and then put this in it
Code:
#!/system/bin/sh
radiooptions 1
Then pop the file in your init.d folder if your rom/kernel supports it, or use an app like script manager or autostart root to run the file at boot. Note if using an app to run at startup, you must set the app to run it with root permission.
cmlusco said:
You just make a file with no extension and then put this in it
Code:
#!/system/bin/sh
radiooptions 1
Then pop the file in your init.d folder if your rom/kernel supports it, or use an app like script manager or autostart root to run the file at boot. Note if using an app to run at startup, you must set the app to run it with root permission.
Click to expand...
Click to collapse
I wrote this script using script manager and gave it root permissions and startup permissions and then ran it (also tried rebooting) and it didn't seem to do anything. Are there any visible changes that would take place when you do it?
nschiwy said:
I wrote this script using script manager and gave it root permissions and startup permissions and then ran it (also tried rebooting) and it didn't seem to do anything. Are there any visible changes that would take place when you do it?
Click to expand...
Click to collapse
Yes, the signal bars will grey out and have a white X over them.
Try using a terminal emulator app and type in
Code:
su - Hit Enter
radiooptions 1 - Hit Enter
You should see the signal bars X'd out.
cmlusco said:
Yes, the signal bars will grey out and have a white X over them.
Try using a terminal emulator app and type in
Code:
su - Hit Enter
radiooptions 1 - Hit Enter
You should see the signal bars X'd out.
Click to expand...
Click to collapse
this is what i got when I tried to do that, it didn't seem to change anything.
it's the same image that shows that it doesn't have any signal because there is no number attached to it anymore.
It looks like it worked, the bars are greyed out and has an X. Even if there is no telephone number associated with the phone, it will still show the signal bars as it will still communicate with verizon just not have service.
cmlusco said:
It looks like it worked, the bars are greyed out and has an X. Even if there is no telephone number associated with the phone, it will still show the signal bars as it will still communicate with verizon just not have service.
Click to expand...
Click to collapse
haha well in that case there might be something wrong with the phone because it has been like that since I flashed the ROM but it doesnt really matter since I don't need it.
Related
Hey I have a desire Z and my logcat says that the Wifi driver isnt loading. I want to replace it with one that works so my wifi actually turns on.
If you have a bcm4329.ko for the desire z could you please let me know?
Thanks
Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?
KCRic said:
Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?
Click to expand...
Click to collapse
Yeah I think it is normally part of a kernel but I cant seem to get this damn wifi to work no matter what I do, so I was thinking if anyone had one of the files kicking around I would just ADB overwrite the old one and see if it works.
Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.
theSpam said:
Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.
Click to expand...
Click to collapse
Still doesn't work
Really have no more ideas to fix my wifi.
you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one
ilostchild said:
you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one
Click to expand...
Click to collapse
I tried that too and it didn't do anything. Im really pulling at straws. Is there a program to test to make sure the hardware is actually good?
Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,
ilostchild said:
Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,
Click to expand...
Click to collapse
Yep, tried that twice. I even went back to stock between the reload.
One time I flashed it using the PC10IMG method and the other I used Clockwork (rom manager).
I really have no idea where to go at this point. I think I've exhausted all my ideas. Ive tried reflashing roms, kernels, and radios.
Was hoping someone had some diagnostic software that would test the hardware of the phone or something so at least then I would know if my actual hardware for the WiFi and Bluetooth was shot or not.
Thanks anyways.
Wow, I forgot about this thread over the weekend
Anyway, have you tried changing the permissions for the file? You can use 'fix permissions' in ROM Manager or clockwork or use Root Explorer to change the permissions. Of course if you're a terminal kind of guy you can chmod it.
Sometimes the permissions don't set correctly or, on some systems running linux, the permissions get changed for some reason. Maybe that's what's going no here, sounds like it anyway. Btw, make sure to reboot after changing the permissions because it won't work until you do.
has anyone fixed this issue where wifi stops working?
wifi not turning ON
Hello Everyone,
During the process of getting IP address from WiFi network, I received a "Error Massage" on my Alcatel OT-990. After this massage, WiFi started behaving abnormally. Sometimes it turned ON another time it did not. Now after a few weeks later, WiFi is not turning ON at all.
I have Tried following Solutions but nothing worked:
1. Did factory reset, erased system, cache etc and Flashed different ROMs (JB ot 990, ICS QME, QLTsar, 2.3.4, Telenor One touch 4.0.04) using Recovery many a times(From different Sources).>>Problem not solved
2. Updated my phone using alcatel update manager to 2.3.4>>> Problem not solved
3. Tried by changing permissions of BCM4329.KO, wpa_supplicant.confg etc every file related to wifi/wlan>>Problem not solved
4. Used WiFix Manager>>>Problem not solved.
Bluetooth and FM radio working all right.
If anybody knows about its solution ..please help me out.
When I first got my phone like many others, it vibrated when the phone first turned on and that's it. After flashing a few radios, I now have and have for awhile, the second vibrate about five seconds after the first. I think I read somewhere what it was, but can't seem to find it now. Did we ever figure out definitively what causes that?
I know in between flashing radios it stopped for awhile, and then came back and has been with me ever since. Not worried about it, just curious. Thank you.
Sent from my HTC Vision using XDA Premium App
Same here. What is the second vibration on startup all about?
I noticed this after flashing the 04.30 radio over stock.
I know someone knows or at least has an idea!
Sent from my HTC Vision using XDA Premium App
I think it only shows up when you flash radios. I haven't flashed a radio on my past two devices and I have only one vibrate.
Sent from my HTC Vision using XDA App
Shameless bump. I want an answer to this.
Sent from my HTC Vision using XDA Premium App
I think first vibration is when you push button and phone is "okay, got it, I'm booting up" and then second when "I'm ready, you can enter your pin code". I had the same on Spica and there it was useful because it booted about 1 minute.
Sent from my HTC Vision using Tapatalk
ciaastek said:
I think first vibration is when you push button and phone is "okay, got it, I'm booting up" and then second when "I'm ready, you can enter your pin code". I had the same on Spica and there it was useful because it booted about 1 minute.
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
That makes sense but none of our phones ever did that until we started changing radios. So it's obviously not part of the "normal" boot up process.
I have not changed radios on my phone yet. It is rooted. I get the second vibration also. I have been wondering why it does this also. It did not start doing this until I rooted my phone.
Bumpity..... I'm curious as to why myself
Sent from my shiny metal G2 w/ meXdroid V3
I know i saw an answer to this once. Damnit if i can find it again!!!
Not that im gonna try it lol, but i wonder if installing a pc10img that unroots, S-ON, and all that would make it go away?
xsteven77x said:
Not that im gonna try it lol, but i wonder if installing a pc10img that unroots, S-ON, and all that would make it go away?
Click to expand...
Click to collapse
I don't know what causes it but if you want to make it go away try this. Go to ROM Manager and select to download rom > virtuous > virtuous sense 1.0.2. Let it download all the way and then hit cancel, don't flash it. Then do a nandroid from within ROM Manager and it will be gone....back to just a single vibration at boot.
Ext3 vs ext4 ?
Ive Had This Issue A Few Times And After Trying To Fix It I Believe It Could Be Due To CWM Formatting The Devices Partitions As EXT3 When It Should Be EXT4.
Can Anyone With This Issue Please Confirm This By Posting The Result Of Typing "mount" In A Terminal.
Their Should Be A Line Which Says "/dev/block/mmcblk0p25 on /system type" And Then The Filesystem Type.
I Hope That This Is The Cause As If I Am Correct It Will Be An Easy Fix
EdKeys said:
I don't know what causes it but if you want to make it go away try this. Go to ROM Manager and select to download rom > virtuous > virtuous sense 1.0.2. Let it download all the way and then hit cancel, don't flash it. Then do a nandroid from within ROM Manager and it will be gone....back to just a single vibration at boot.
Click to expand...
Click to collapse
+1
Sent from my XDA premium App
That is seriously the craziest thing i ever heard Edkeys lmfao but going to try now! Will report back in the morning. Ty for the heads up. How the hell did you figure that out!?
And yes ollied there is, and it says ext4.
xsteven77x said:
That is seriously the craziest thing i ever heard Edkeys lmfao but going to try now! Will report back in the morning. Ty for the heads up. How the hell did you figure that out!?
And yes ollied there is, and it says ext4.
Click to expand...
Click to collapse
I noticed a few months ago that after I took virtuous froyo for a test run that my second vibration was gone. Since then I flashed a new radio and the second vibration came back. I thought I'd test what had happened before and low and behold just downloading it with rom manager and creating a backup got rid of the damned thing. One of those wtf moments...lol. It must have something to do with the old vs. new ext. as OllieD suggests.
Sent from my HTC Vision using XDA Premium App
OllieD said:
Ive Had This Issue A Few Times And After Trying To Fix It I Believe It Could Be Due To CWM Formatting The Devices Partitions As EXT3 When It Should Be EXT4.
Can Anyone With This Issue Please Confirm This By Posting The Result Of Typing "mount" In A Terminal.
Their Should Be A Line Which Says "/dev/block/mmcblk0p25 on /system type" And Then The Filesystem Type.
I Hope That This Is The Cause As If I Am Correct It Will Be An Easy Fix
Click to expand...
Click to collapse
Just ran that in an ADB shell. Here's what I got:
/dev/block/mmcblk0p25 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
Click to expand...
Click to collapse
So it's not the formatting. There's another reason why there's a second vibration, but that's really a minor bug.
Misc Partition?
Can Someone With The Bug Please Dump Their Misc Partition?
Run "dd if=/dev/block/mmcblk0p17 of=/sdcard/Misc.img" In A Terminal And Upload The "Misc.img" File From Their SD Card Somewhere ?
Based On The Previous Fix Mentioned I Believe It Could Be To Do With The Way Rom Manager Reboots Into Recovery.
A Command Is Stored Somewhere That Lets HBoot Know Which Mode To Reboot Into.
An Error With This Command Probably Causes The Second Vibrate And When Rom Manager Reboots Into Recovery It Clears This Flag. Although I Remember Flashing Various ROMs Via Rom Manager Without This Issue Being Fixed.
OllieD said:
Can Someone With The Bug Please Dump Their Misc Partition?
Run "dd if=/dev/block/mmcblk0p17 of=/sdcard/Misc.img" In A Terminal And Upload The "Misc.img" File From Their SD Card Somewhere ?
Based On The Previous Fix Mentioned I Believe It Could Be To Do With The Way Rom Manager Reboots Into Recovery.
A Command Is Stored Somewhere That Lets HBoot Know Which Mode To Reboot Into.
An Error With This Command Probably Causes The Second Vibrate And When Rom Manager Reboots Into Recovery It Clears This Flag. Although I Remember Flashing Various ROMs Via Rom Manager Without This Issue Being Fixed.
Click to expand...
Click to collapse
Gonna go take the dog for a walk and some other things, if someone has not done it by time i get back i will do it for us
When installing FXP113 to my phone, I found that on bootup I would get an error on the phone process and I had no service. After trying a few different things, I finally found the solution: Install FXP112 first, then install FXP113 over it without wiping data. Here is a step by step tutorial on installing FXP113 on the R800x. It probably would work the same for all Xperia Plays.
Required: Rooted Xperia Play and unlocked bootloader.
Needed Files: FXP112 as modified by Chevyowner
FXP113 as modified by Chevyowner
Replacement build.prop file for R800x
Fastboot - Fastboot+ADB+Fastboot_Drivers.zip
Sony Drivers
Recommended: Boot into recovery and make a Nandroid backup before continuing.
1. Copy the files for FXP112 and FXP113 to your sdcard. You will need to access these from recovery.
2. Install Fastboot. Unzip the file into C:\fastboot.
5. 2. Extract the boot.img of your choice to the fastboot directory. You may use the one in FXP113, or DarkForest3.img or DarkForest4.img (available here.)
5. Enter into Fastboot Mode. - Turn off phone. Hold search button down. Plug in USB cable. The power light should be blue The first time you do this, you will be prompted for the fastboot drivers. They will be in C:\fastboot\fastboot drivers.
6. To flash the new boot image, go to a command prompt and change to the c:\fastboot directory. Then use the following command:
fastboot -i 0x0fce flash boot boot.img <----- the name of your boot image.
7. When finished, remove the usb cable. Power on the phone and enter into Recovery. On some kernels, you will press repeatedly the volume down button; on others, you will press repeatedly on the back button or possibly the search button.
8. You MUST clear Data, Cache and Dalvik Cache. It is also recommended by some people to clear the battery stats.
9. Install zipfile from sdcard. Select the FXP112 file first. Allow it to install and then reboot the phone. (I usually clear data, cache and dalvik again just to be sure.)
10. Activate your phone on the Verizon network.
11. Now shut down and reboot into Recovery again.
12. This time, clear ONLY cache and dalvik cache. Do NOT clear data.
13. Install zipfile from sdcard. Select the FXP113 file this time. Allow it to install and then reboot the phone.
14. Copy the build.prop file into /system. You may want to rename the current one first.
15. Reboot and enjoy! You should be up and running with full data, wifi access now.
re
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this
FPlusPS3 said:
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this
Click to expand...
Click to collapse
#10 There is no charge to activate the phone if you already have service. It's like dialing *228 and choosing option 1, only the system does it for you.
#14 Yes, you can just copy it to \system, but don't forget to change access to RW before pasting. You may also want to rename the old file first as a backup, although I never have.
Sent from my R800x using XDA
my phone gets stuck at the android screen after i flash fxp112
johnboyjr said:
my phone gets stuck at the android screen after i flash fxp112
Click to expand...
Click to collapse
What kernel did you use?
Did you clear data, cache and dalvik cache before you installed FXP112?
If yes, just for kicks, go clear it again.
Also, remember, the first boot after a clean install takes longer than normal.
Sent from my R800x using XDA
yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing
johnboyjr said:
yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing
Click to expand...
Click to collapse
OK. Well, if it were me, the next thing I would do is to flash back to totally stock and get that working. Then try it again.
Sent from my R800x using XDA
What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.
crono141 said:
What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.
Click to expand...
Click to collapse
I think it was just edited to identify the phone properly as an R800x. PaxChristos told me to use it when he helped me install FXP111 and I have used it ever since. I haven't had any issues at all with it, so you might give it a try if you're on Verizon.
Sent from my R800x using XDA
That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA
*22899 is the shortcut for activating service in case anyone wanted to just store it for future reference
-and you can also use flashtool to flash back to stock or flash a new kernel
*228 worked fine for me. semcsuite.apk won't show up in my app drawer. I moved it to /system/app and fixed permissions. Still not there.
Sent from my R800x using XDA
Wallrunner said:
That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA
Click to expand...
Click to collapse
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA
re
Does Psxperia or XPERIA GAMEPAD games even work on cm9
For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.
FPlusPS3 said:
Does Psxperia or XPERIA GAMEPAD games even work on cm9
Click to expand...
Click to collapse
From what I have read... no. That is why I have not jumped ship to CM. Otherwise I would be there right now. So until they get the touchpads working I will wait, although I have also read they are working on creating from scrathc their own drivers for the touchpads as the current drivers now require SE framework...... so cross your fingers.
Nighty0 said:
For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.
Click to expand...
Click to collapse
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in
agraceful said:
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in
Click to expand...
Click to collapse
Yes, giving their release to us is amazing, but saying that camera works on changelog, and not even the basic apps like gtalk and camera works, this barely can be considered as working.
As a software engineer I label as a beta, not RC anything. beta is to fix stopper bug like this, RC is for the little annoyances lonely.
For example, my work friend installed another rom on their htc sensation, labeled as beta and all features works, with jagged areas here and there.
And yep, I know the Team FreeXperia is a one guy team
I'm happy with all this releases, only frustrated because the thing is being labeled as working, when not. So I made a report here to make sure another person doesn't make the same mistake as me.
netizenmt said:
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA
Click to expand...
Click to collapse
actually this build.prop works better it lets Plants Vs Zombies and Asphalt 6 RUN and work
How do install install the custom rom and set up fastboot?
I have the EVO 4g and I was able to put it into S-off....Once i did that i was getting wifi error when i tried to use the wifi. I'm stumped and have looked everywhere and have not gotten any clear answers. I have tried to install a rom (using digital karma now) but to no avail. Please help me out :laugh:
Try upgrading radios
death-by-soap said:
Try upgrading radios
Click to expand...
Click to collapse
that did not work =\
Could try reflashing the kernel and wiping cache and dalvik cache in recovery.
You tried switching your router off and on again?
note that some kernels need to have data and/or system mounted first in recovery before flashing the kernel otherwise wifi breaks. Just a thought.
also, you did sanity check your network by conforming that other devices still connect fine?
Sent from my PC36100 using xda app-developers app
Robobob1221 said:
Could try reflashing the kernel and wiping cache and dalvik cache in recovery.
You tried switching your router off and on again?
Click to expand...
Click to collapse
well i didn't do the router because its not even scanning for a router at all. This is a fairly new phone so it was never dropped (just some info).
NxNW said:
note that some kernels need to have data and/or system mounted first in recovery before flashing the kernel otherwise wifi breaks. Just a thought.
also, you did sanity check your network by conforming that other devices still connect fine?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
yeah the network is fine. I have another EVO that i use for wifi purposes, but the usb port broken. I have been charging my battery on one phone and using wifi on the other. It was fine while it lasted but now its a bit old. I want to flash one of these phones to pageplus and i prefer the one that the wifi works on.
Ok...let me search my memory banks to see if I can help. I have had this problem about 2 or 3 times, and I searched DILIGENTLY for an answer. After countless, and I mean countless pages, I found a solution. (Not saying you didn't search right...but it took me a while, and I had to change the words of my search about 20 times.)
You need a file explorer with root access. There are many good ones, and I use ES File Explorer. Not saying it's the best, not saying it's the worst, not saying anything except that it's the one I use. Period.
Anyway, you must access the root of your phone, and go to these folders.
System-->Etc-->Wifi.
In the Wifi folder, either rename the supplicant file to be safe, or delete it. I renamed mine the first time around to be safe, but I can confirm that deleting doesn't hurt anything. Restart your phone, and it will rebuild the file when the phone reboots. No need to wipe cached or anything. And fixing permissions doesn't work for this.
Try it, and let me know.
P.S.: I would give credit to the person who originally posted this solution, but I don't remember, since the answer was not on XDA, and I found it in a forum for a random Samsung phone.
______________________________
HTC Evo 4g
aarsyl said:
Ok...let me search my memory banks to see if I can help. I have had this problem about 2 or 3 times, and I searched DILIGENTLY for an answer. After countless, and I mean countless pages, I found a solution. (Not saying you didn't search right...but it took me a while, and I had to change the words of my search about 20 times.)
You need a file explorer with root access. There are many good ones, and I use ES File Explorer. Not saying it's the best, not saying it's the worst, not saying anything except that it's the one I use. Period.
Anyway, you must access the root of your phone, and go to these folders.
System-->Etc-->Wifi.
In the Wifi folder, either rename the supplicant file to be safe, or delete it. I renamed mine the first time around to be safe, but I can confirm that deleting doesn't hurt anything. Restart your phone, and it will rebuild the file when the phone reboots. No need to wipe cached or anything. And fixing permissions doesn't work for this.
Try it, and let me know.
P.S.: I would give credit to the person who originally posted this solution, but I don't remember, since the answer was not on XDA, and I found it in a forum for a random Samsung phone.
______________________________
HTC Evo 4g
Click to expand...
Click to collapse
nope did not work...I eeven tried taken wifi files out of my working evo to this one and still did not work
Do a Full Wipe of everything. Then Flash a Stock Rooted Rom. See if that corrects the issue. You may also want to check out THIS thread. Also the one HERE.
Hmmmm...I tried my best. I hope you find a solution soon.
But the way, does it simply say error, or does it behave strange, like turn off and on for a while, then give you the error message?
______________________________
HTC Evo 4g
aarsyl said:
Hmmmm...I tried my best. I hope you find a solution soon.
But the way, does it simply say error, or does it behave strange, like turn off and on for a while, then give you the error message?
______________________________
HTC Evo 4g
Click to expand...
Click to collapse
it say error
Since nothing else has seemed to work you could try this..http://forum.xda-developers.com/showthread.php?t=1982149 ..you have to be running an ics or jb rom for the app to work though. Just throwing it out there.
Can someone pls tell me why my Wifi is not working. I FLASHED the Synergy latest ROM and now I can't connect to wifi..I tried in other spots and it still tries but will not connect...help.. it gives me an "Saved"or "unable to authenticate error"...this happens anywhere that I try to connect to Wifi...and I actually have to turn WIFI off in order to download data from a file....any suggestions???
Did you chdck the md5 before flashing? Also did you clean flash the rom? One last thing, did you restore any system apps using titanium backup? Any of these three things can cause lots of headaches.
Sent from my SPH-L900 using Tapatalk 2
patrao_n said:
Did you chdck the md5 before flashing? Also did you clean flash the rom? One last thing, did you restore any system apps using titanium backup? Any of these three things can cause lots of headaches.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
I did not chk the md5..don't really understand what to do with that...I did a clean install and didn't restore apps from Titanium backup...
What do I look for in the md5 and what actually do I do with it..do I install like I am installing a custom ROM???
Usuall the websiye you download the rom from has an md5 or the original post(op) of the thread you got it from has it. It looks like just a bunch of random letters and numbers. Thr way you check the md5 of your file is to go to the playstore and download md5 checker. Also file explorers like root explorer have it. I find it easier though to use the md5 checker app. You open it and it has a box that says load file. You navigate the program to the file( your synergy rom) then you click the select file. It will calculate the md5. Then you just make sure that md5 matches the md5 on the page or thread.
Sent from my SPH-L900 using Tapatalk 2
I did not see a file for the mod5..so I used the ROM and this is what I got...how do I compare or find oit if it is correct.
Sent from my SPH-L900 using xda premium
I basically have the same issue for the international version.
This was my first time installing a custom rom, used the 'cm-10.1-20130708-NIGHTLY-n7100.zip ' latest nightly build.
Anyway everything seems to work fine, but WiFi gets stuck on authenticating / obtaining IP address.
I did the MDR5 thing, and when I check it turns red.
I believe I had a similar issue once when I only rooted it. I fixed it by placing the right WiFi file on my phone. But I can't recall the name nor method.
GVR1 said:
I basically have the same issue for the international version.
This was my first time installing a custom rom, used the 'cm-10.1-20130708-NIGHTLY-n7100.zip ' latest nightly build.
Anyway everything seems to work fine, but WiFi gets stuck on authenticating / obtaining IP address.
I did the MDR5 thing, and when I check it turns red.
I believe I had a similar issue once when I only rooted it. I fixed it by placing the right WiFi file on my phone. But I can't recall the name nor method.
Click to expand...
Click to collapse
Pls try to remember what u did..lol..I need my WIFI to work!!!
GVR1 said:
I basically have the same issue for the international version.
This was my first time installing a custom rom, used the 'cm-10.1-20130708-NIGHTLY-n7100.zip ' latest nightly build.
Anyway everything seems to work fine, but WiFi gets stuck on authenticating / obtaining IP address.
I did the MDR5 thing, and when I check it turns red.
I believe I had a similar issue once when I only rooted it. I fixed it by placing the right WiFi file on my phone. But I can't recall the name nor method.
Click to expand...
Click to collapse
Sorry nothing, not even a tiny hint in my mind. All I remember was I needed a file to fix it
Wait. I forgot something. I got a reply somewhere else telling the following:
'For your case go to the dial number screen and put *#0011# hit the menu then go to WiFi at the bottem. You will notice that the wifi is on eco mode, just get is disabled. There you go'.
I haven't tried it yet since I restored my phone to normal because I needed my WiFi working for apps and messaging.
Tell me if it works!:good:
It didn't work
Sent from my SPH-L900 using xda premium
I'm having the exact same problem, every time I try and flash an AOSP rom. Stock roms like All-Star and Whomp don't give me any issues, but paranoid, CM, anything along those lines at all, they all give me the same issue. I can't seem to find an answer anywhere.
Wanted to comment here again to a POSSIBLE fix. I backed up any internal files I needed to an outside source, then formatted my entire internal storage. Since then, I don't get the Authenticating/Obtaining IP issue as much. I sometimes have to turn the wifi off and back on just once if I restart my phone, but that's about it. Not sure if it'll work for anyone else, but it's helped me.