Develop Bugs

WIFI Router does NOT work with full root

Hey everyone. between my brothers and I, we have five Evo's. two of us are running full roots and nand unlocks, the other three are using unrevoked. those that unrevoked can use the wifi router without issue, but for my brother and myself, using the wifi router results in the app crashing and having to force close.
has anyone seen anything similar? can anyone offer me some solution?
and btw, this is my third rom. they all have the same results(full wipe, data and davik cache clear each time)

Delete wi fi tether from the phone and re-download it. This has worked for me everytime i change roms =)
Hope it helps.

Do you mean the wireless tether app? I am running my own rom but it seems that it worked for me when I was using fresh. But that is the only other rom I have tried. Have you tried re-installing the tether app?

I'm not sure i can remove the base wifi tether app. it's always cooked into the rom. and i have tried reinstalling the app. i've gone from the original version, to the newer version and finally the beta version with no luck

I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now

Hmmmmmm. I am sure someone else can offer better advice, but does the super user app come up to ask for permission or it fc's before that?

topdawgn8 said:
I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now
Click to expand...
Click to collapse
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests

I am not sure if your signature is correct but have you tried flashing the newest radio? I am not sure if that would fix it or not. And the same thing happens to the other phone? Puzzling indeed. I'm sure someone will drop in and tell you how to fix it soon. Worst case, start over. Even though I know you said you tried various roms, maybe you are accidentally skipping a step, I do that sometimes

SilverStone641 said:
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests
Click to expand...
Click to collapse
Ok, go back through the same process and try this one instead of what was in step 3.
http://code.google.com/p/android-wi...me=wireless_tether_2_0_2.apk&can=2&q=NexusOne
If that doesn't work, I've got nothing else. The first one was the beta you probably tried earlier. This is the stable one; however, I never tried it with this one. I always got it working using the 2_0_5 version.

Also, for ****s and giggles, have you tried updating you profile and prl?
- you didn't flash the wireless n patch over a 1.47 base Rom correct? Can you connect to a WiFi router or is it just the tether app?

elegantai said:
Also, for ****s and giggles, have you tried updating you profile and prl?
Click to expand...
Click to collapse
uh....what?? you got me there! i thought i knew what those were, but it escapes me now.
the only thing i can think of is that the rooting process screwed up somehow. but for it to screw up in the same way for two separate phones is odd, but it's the only thing that has remained constant since the very beginning.

Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this

elegantai said:
Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this
Click to expand...
Click to collapse
done. same results. "Unable to start tethering. Please try again!"

Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.

elegantai said:
Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.
Click to expand...
Click to collapse
i do have the wireless N enabled, but i do not have the new 1.47 yet. i'm waiting on OMJ to release an update

[Q] a different GPS problem

Ok, so I've searched on this and haven't been able to find anyone with the same problem. This is so annoying!
Phone specs:
HTC Evo, rooted
Cyanogen 7.0.3.1
PRL 01115
not sure what else you might need to diagnose this.
Around the time that Sprint released their stock gingerbread rom for the Evo, my GPS went on the fritz. All of a sudden, google maps would only get a fix maybe once every few minutes. Useless for navigation! Sometimes the GPS icon wouldn't even flash, like it wasn't even trying to get a fix, meanwhile, Maps is "waiting for location."
I tried the usual "fix" that you hear about, by flashing back to a sense rom and typing ##gpsclrx##, and then the MSL number when prompted. No success.
I finally figured out that if I go into recovery and clear the dalvik cache, and then run GPS Status after it reboots, the gps works again, but a few days later, I have to do that all over again.
Any idea what's causing this or how to fix it?

I get similar problems. I just started using Cyanogen when Sprint came out with their first Gingerbread update and broke everything. I love Cyanogen, and I have managed to get everything working except for the GPS.
A lot of times it takes a long time to turn on when I start up google maps, and then it will get a fix, and then after a minute it will loose the fix and won't be able to get gps lock again. I tried flashing back to a stock rom and doing the ##gpsclrx# thing, but it just clears the call screen and never even asks for a MSL number, so I don't know if that works or not. I love Cyanogen, but don't know if I can live without the GPS working.
Has anybody else figured anything out? Does anyone know if this is a know problem that is being worked on or not?

I get no fix on gps and no voice

a question for the OP since you dont make any mention of it.
Have you tried flashing the Galandy fix for GPS? Using the Vision GPS driver makes a world of difference.
the first one, at the top of the list.
found here in this thread - http://forum.xda-developers.com/showthread.php?t=1132412&highlight=gps+fix
use the flashable zip that corresponds to your recovery type. i've used the Fix_2 on several devices with CWM recovery.

I was able to solve it using the drivers here:
http://forum.xda-developers.com/showpost.php?p=14534313&postcount=2478
Not sure if this is the same thing as what drdrewdown posted... sounds like it is.

secretspy711 said:
I was able to solve it using the drivers here:
http://forum.xda-developers.com/showpost.php?p=14534313&postcount=2478
Not sure if this is the same thing as what drdrewdown posted... sounds like it is.
Click to expand...
Click to collapse
galandy made that post you are referring to lol... so yea its the same

Bumping this thread with a question: Will the Vision GPS driver (Galandy) work on a near-stock Sense ROM (GB)?
I'm running Jiminy, which is mostly a debloated stock ROM with a few changes made for ease of use on the Cricket network.
Currently my GPS is doing what the OP of this thread is describing- my current workaround is to do the following every single time I want to use nav:
1) Open GPS Status. Clear AGPS data. Download new AGPS data.
2) Open GPSFix. Hit "Start Fix", then hit the Map button.
3) Do my Navigation. It works fairly well after that.
This is an annoying procedure!!! I want to load the Vision driver but don't know if it will screw something up- it seems like most of the people running it are on CM7 or some other AOSP custom ROM.
Will it work with my setup?

mpsantiago said:
Bumping this thread with a question: Will the Vision GPS driver (Galandy) work on a near-stock Sense ROM (GB)?
Click to expand...
Click to collapse
In theory, they should work fine on Sense roms as well. However if your stock Sense GPS drivers are not working then the Vision drivers might not work either, but it doesn't hurt to try. Just backup your gps.supersonic.so file in /system/lib/hw/ folder before flashing the driver.
I posted new drivers HERE today btw

galandy said:
In theory, they should work fine on Sense roms as well. However if your stock Sense GPS drivers are not working then the Vision drivers might not work either, but it doesn't hurt to try. Just backup your gps.supersonic.so file in /system/lib/hw/ folder before flashing the driver.
I posted new drivers HERE today btw
Click to expand...
Click to collapse
Oddly enough, my phone does not have that file. And installing it seems to do nothing
The closest thing I have is /system/lib/libgps.so
Being the daring sort, I renamed that file and replaced it with the a renamed copy of the Vision gps.supersonic.so; my phone did not like that at all- no boot, had to reflash

drdrewdown said:
a question for the OP since you dont make any mention of it.
Have you tried flashing the Galandy fix for GPS? Using the Vision GPS driver makes a world of difference.
the first one, at the top of the list.
found here in this thread - http://forum.xda-developers.com/showthread.php?t=1132412&highlight=gps+fix
use the flashable zip that corresponds to your recovery type. i've used the Fix_2 on several devices with CWM recovery.
Click to expand...
Click to collapse
I flashed the vision driver and then the new one posted last night, and neither worked. my GPS is useless right now, for the first time ever...
Gonna try the GPSFix app now...
Another thing I notice is that I don't even get the GPS Icon when I'm trying to use GPS Status or navigator

HipKat said:
I flashed the vision driver and then the new one posted last night, and neither worked. my GPS is useless right now, for the first time ever...
Gonna try the GPSFix app now...
Another thing I notice is that I don't even get the GPS Icon when I'm trying to use GPS Status or navigator
Click to expand...
Click to collapse
you'd have to tell us a little more about your config if you want us to help diagnose it, as well as a little back history

galandy said:
In theory, they should work fine on Sense roms as well. However if your stock Sense GPS drivers are not working then the Vision drivers might not work either, but it doesn't hurt to try. Just backup your gps.supersonic.so file in /system/lib/hw/ folder before flashing the driver.
I posted new drivers HERE today btw
Click to expand...
Click to collapse
You are the frickin man!!!!
Before that driver I'd see 3 satellites and could rarely get a lock. Now I see 10 and it locks quick!!!
Thanks.
BTW, in case it helps anybody else, I used that latest Vision driver from galandy along with the PRI/Radio/NV combo found here: http://forum.xda-developers.com/showthread.php?t=1128135 and could not be happier with the results.

well, it worked great for a while, but now it's back to only working when it wants to (which is never when I need it)
Has anybody ever heard of undervolting breaking GPS? I ask because that's the only thing I've done aside from rooting/installing the ROM.

I had a problem with GPS. So I got off 28 nightly and went to the 100s lol works great.
World peace with no regard for human life.

mpsantiago said:
well, it worked great for a while, but now it's back to only working when it wants to (which is never when I need it)
Has anybody ever heard of undervolting breaking GPS? I ask because that's the only thing I've done aside from rooting/installing the ROM.
Click to expand...
Click to collapse
nope, i undervolt quite a bit & gps works great.

mpsantiago said:
Bumping this thread with a question: Will the Vision GPS driver (Galandy) work on a near-stock Sense ROM (GB)?
I'm running Jiminy, which is mostly a debloated stock ROM with a few changes made for ease of use on the Cricket network.
Currently my GPS is doing what the OP of this thread is describing- my current workaround is to do the following every single time I want to use nav:
1) Open GPS Status. Clear AGPS data. Download new AGPS data.
2) Open GPSFix. Hit "Start Fix", then hit the Map button.
3) Do my Navigation. It works fairly well after that.
This is an annoying procedure!!! I want to load the Vision driver but don't know if it will screw something up- it seems like most of the people running it are on CM7 or some other AOSP custom ROM.
Will it work with my setup?
Click to expand...
Click to collapse
Thank you a lot
It works for me @ Cyanogen 9 on my Nexus S !

Wifi Error

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.

Constant Reboots!! PLEASE HELP!!!!

Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!

i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does

First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before

have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay

Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.

XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion

Needs a trip to the Service Centre then by the sounds of it.

XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?

Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium

tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?

plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium

i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always

plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.

lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes

Wifi Broke xperia s Was Fixed now Broke again

I am trying to get my WiFi working on .96 stock rom and optino to turn on is faded out., Tried resetting many times tried re installing software and moving everything on to stock rom kernel and firmware etc still does not work.
Was originally it was working on .96 firmware but done some updates went on a custom rom and found wifi not working. So reverted back to stock again and now to only find WiFi is not working on it again.
Any one here know how to fix this problem.

mentalghost said:
I am trying to get my wifi working on .96 stock rom and optino to turn on is faded out., Tried resetting many tiems tried re installing software and moving everything on to stock rom kernel and firmware etc still does not work.
Was originally it was working on .96 firmware but done some updates went on a custom rom and found wifi not working. So reverted back to stock again and now to only find wifi is not working on it again.
Any one here know how to fix this problem.
Click to expand...
Click to collapse
Try flash the wifi modules http://forum.xda-developers.com/showthread.php?p=46145682&highlight=module#post46145682 this will happen when you come from custom kermel like trinity kernel, you must flash back stock wifi modules to make the wifi working

chrissiong said:
Try flash the wifi modules http://forum.xda-developers.com/showthread.php?p=46145682&highlight=module#post46145682 this will happen when you come from custom kermel like trinity kernel, you must flash back stock wifi modules to make the wifi working
Click to expand...
Click to collapse
Thanks for the link. Do I just add them to my phone somewhere and then flash with recovery program?
Also will these work on other roms?
Flashed to phone however didn't work still no wifi after flashing with recovery program. Is it meant to say android devices updating as i didn't see that happen this time

mentalghost said:
Thanks for the link. Do I just add them to my phone somewhere and then flash with recovery program?
Also will these work on other roms?
Flashed to phone however didn't work still no wifi after flashing with recovery program. Is it meant to say android devices updating as i didn't see that happen this time
Click to expand...
Click to collapse
you are on .96 firmware right? Try flash the baseband from the original .96 ftf with flashtool, make sure exclude all the option except the baseband. Hope it helps

chrissiong said:
you are on .96 firmware right? Try flash the baseband from the original .96 ftf with flashtool, make sure exclude all the option except the baseband. Hope it helps
Click to expand...
Click to collapse
Just tried as advised and still the same working between 2 threads 5 people in different places and trying so many things lol its crazy. Am sure ill get to the bottom of this sooner rather than later I hope.

mentalghost said:
Just tried as advised and still the same working between 2 threads 5 people in different places and trying so many things lol its crazy. Am sure ill get to the bottom of this sooner rather than later I hope.
Click to expand...
Click to collapse
Just take it easy dude sometimes i wasted a couple hours just to search for solutions and i often get mad but i didnt give up since flashing baseband didnt work, i suggest you to flash back to original ftf since this is the last option

chrissiong said:
Just take it easy dude sometimes i wasted a couple hours just to search for solutions and i often get mad but i didnt give up since flashing baseband didnt work, i suggest you to flash back to original ftf since this is the last option
Click to expand...
Click to collapse
Where would I look at getting the original one that was gingerbread or first releases as ftf i have is .96 baseband
XperiaS_LT26i_6.2.B.1.96_1257-6919.ftf
Also took phone to shop and they even advised it is some software glitch bug hes had a few people with the same sort of problem and its sony that needs to fix it he was on about some part of the software when flashing is not being wiped out and re applied with new stuff and have to remove the files he even checked to see if the files where their and he said well its not that as plugged phone into a reader and shows the files being removed and re applied from new flash.
What other onces besides the XperiaS_LT26i_6.2.B.1.96_1257-6919.ftf I have is their ? might jsut get every single one of them starting from oldest to new n seeing if any work.

mentalghost said:
Where would I look at getting the original one that was gingerbread or first releases as ftf i have is .96 baseband
XperiaS_LT26i_6.2.B.1.96_1257-6919.ftf
Also took phone to shop and they even advised it is some software glitch bug hes had a few people with the same sort of problem and its sony that needs to fix it he was on about some part of the software when flashing is not being wiped out and re applied with new stuff and have to remove the files he even checked to see if the files where their and he said well its not that as plugged phone into a reader and shows the files being removed and re applied from new flash.
What other onces besides the XperiaS_LT26i_6.2.B.1.96_1257-6919.ftf I have is their ? might jsut get every single one of them starting from oldest to new n seeing if any work.
Click to expand...
Click to collapse
Just use the latest .96 ftf, make sure do the clean install

chrissiong said:
Just use the latest .96 ftf, make sure do the clean install
Click to expand...
Click to collapse
Well still not working. Solely beginning to give upon this.

mentalghost said:
Well still not working. Solely beginning to give upon this.
Click to expand...
Click to collapse
Hmm... Try to reflash to your previous ROM and kernel that has working WiFi. If this also doesn't helps, then I think is hardware related

chrissiong said:
Hmm... Try to reflash to your previous ROM and kernel that has working WiFi. If this also doesn't helps, then I think is hardware related
Click to expand...
Click to collapse
I know its not hardware related as I see my wifi option it comes on and goes out and fades away sometimes when hard resetting settings it will light up but then get stuck again, I been reading more about it and found it to be some bug within it and sony have yet to fix the bug that many devices have. tried reverting back to backed up firmware and kernel and no joy still

chrissiong said:
Hmm... Try to reflash to your previous ROM and kernel that has working WiFi. If this also doesn't helps, then I think is hardware related
Click to expand...
Click to collapse
Tried going right back to jingerbread on this it turns on starts scanning and then says error. When using wifi tools I get the error wifi stuck and have looked at sonys database and seems many are reporting the same sort of bugs on the xperia s and other devices with stuck wifi and cant turn on not matter what is done or they have tried.

Well I look and looked and looked.
RESOLVED after 4 bloody days.
After a shocking discovery this actually worked. But think it might be some bug that is within Sky WiFi thats resolved the problem
1 went to https://play.google.com/store/apps/details?id=com.bskyb.cloudwifi
Downloaded installed. Next logged into my account and shortly after I seen devices available to connect to but their cloud. Shortly after saving my settings phone locked up froze and restarted on me n rebooted and then noticed that my ? option was on for saying WiFi available clicked on it and wifi on powered phone down and back on and still on.

mentalghost said:
Well I look and looked and looked.
RESOLVED after 4 bloody days.
After a shocking discovery this actually worked. But think it might be some bug that is within Sky WiFi thats resolved the problem
1 went to https://play.google.com/store/apps/details?id=com.bskyb.cloudwifi
Downloaded installed. Next logged into my account and shortly after I seen devices available to connect to but their cloud. Shortly after saving my settings phone locked up froze and restarted on me n rebooted and then noticed that my ? option was on for saying WiFi available clicked on it and wifi on powered phone down and back on and still on.
Click to expand...
Click to collapse
Glad to know that your wifi is fixed:good::good:

chrissiong said:
Glad to know that your wifi is fixed:good::good:
Click to expand...
Click to collapse
Me to but guess what...... Its stopped working again. the rom I went on is bugy and it crashed n didn't come back on. Booted recovery back up i made and no wifi so this has goto be rom related somewhere or a problem in the builds

mentalghost said:
Me to but guess what...... Its stopped working again. the rom I went on is bugy and it crashed n didn't come back on. Booted recovery back up i made and no wifi so this has goto be rom related somewhere or a problem in the builds
Click to expand...
Click to collapse
Did you format system before flashing a rom? when doing major update, this step is optional

chrissiong said:
Did you format system before flashing a rom? when doing major update, this step is optional
Click to expand...
Click to collapse
I always do to make sure stuff is working like flashing rom wiping data cash etc n then flash and start up.

mentalghost said:
I always do to make sure stuff is working like flashing rom wiping data cash etc n then flash and start up.
Click to expand...
Click to collapse
Emm, i mean format system, it is under mount and storage in recovery. It shouldn't have any problem if you wipe the system before flashing

chrissiong said:
Emm, i mean format system, it is under mount and storage in recovery. It shouldn't have any problem if you wipe the system before flashing
Click to expand...
Click to collapse
Will give it a go now and see if this resolves the problem by wiping everything on it then flashing

Still no joy on this. Looks like something is totally messed up in the software firmware or rom not doing as it is meant to.