I have Xperia S phone obviously and have used multiple different ROMs. I have been using the latest PAC for a couple weeks (update as they come), but have used all other major ROMs for the Xperia S (xtxperince 9, cm10, ka25 speria sspeed, etc) and for some reason my wifi will die on me and will not turn back on. I will reboot phone flash different kernels (for the right roms) and still cant ever get it to turn back on. The only possible way that I can get it to work again is flashing the stock ROM (inparticular LT26i_US_Generic.ftf). I flash this, let it cook for 5 min and the BAM the wifi works!! So I flash back to PAC (my fav right now) and the wifi will work wonderful for 1-2 days and then die on me again. I have to repeat this process a lot and really do not understand why I am having this issue. Are other people experiencing the same thing I am? Is there any possible thing I can do to take care of this?
Its fwustrating
Please help me!! Thanks!
-haryy
Anybody have any idea on what I can try besides selling this phone and getting a different one? I can't imagine the wifi module would just die like that. Please anything at all I will try.
-haryy
Related
ok, heres the deal. Ive played with just about every rom for this phone. Then one happy merry day, i decide to install miui (i loved it on my dinc 1) then after getting my fill of it i went back to stock (andybones stock rom i think it was). Now the 3g keeps cutting off so i have to use wifi whenever i get the chance or be stuck with 1x, and it wont send or recieve calls unless im outside. I tried flashing the latest radio, trying different roms, RUU then reroot, but its still having this issue. Anyone else having this issue? Anyone find a fix?
BTW its the miui rom from miui.us
SynysterSilence said:
ok, heres the deal. Ive played with just about every rom for this phone. Then one happy merry day, i decide to install miui (i loved it on my dinc 1) then after getting my fill of it i went back to stock (andybones stock rom i think it was). Now the 3g keeps cutting off so i have to use wifi whenever i get the chance or be stuck with 1x, and it wont send or recieve calls unless im outside. I tried flashing the latest radio, trying different roms, RUU then reroot, but its still having this issue. Anyone else having this issue? Anyone find a fix?
BTW its the miui rom from miui.us
Click to expand...
Click to collapse
Have you tried *228 option 1 then *228 option 2 from an OTA based ROM? If not I would suggest giving that a try.
CondemnedSoul said:
Have you tried *228 option 1 then *228 option 2 from an OTA based ROM? If not I would suggest giving that a try.
Click to expand...
Click to collapse
tried it didnt work tho. I even tried reinstalling the radio but it didnt help much. the way i see my best options are:
1) just call in for a replacement but ive already done that so much im sure verizon hates me xD
2) wait for the ics update to come out which i recently discovered is confermed by htc to come out soon this year
3) turbo charge the 3g i do have to get a better connection out of it and just stay on wifi when im at my house
unfortunatley i would really like to find a fix for this so if anyone wants to help out by finding a way or making one id appreciate it. Ive already googled the crap out of this but youre welcome to look around.
You could have a hardware issue, or you could be having the issue that just about everyone had on the Incredible 1 at some point.
http://forum.xda-developers.com/showthread.php?t=817487&highlight=3g+drops
Try that, but with files for our phone. Do NOT use the RUU for the Dinc1. Or, try flashing a stock based ROM like SkyraiderZeus. If none of this works, its probably a hardware issue.
since updating to 4.2.2 Liquid rom i am unable to downgrade to any version below that without my phone switching off after 5 secs and me having to reboot back in..
any idea?? seems like by upgrading to 4.2.2 something has been upgraded and anything below that, even 4.2.1 just refuses to work and switches itself off.
and doing it through odin with stock rom even fails to stop the phone switching off..it installs fine and then proceeds to promptly switch off, but the minute I put the custom 4.2.2 rom back on...its fine again and doesnt switch off, which makes me think something has been upgraded along the way and anything other than 4.2.2 now will not work correctly on my phone..
How can i get back down to 4.2.1 etc.. is it baseband or something? This makes me think that all others on here with their phones switching off have potentially done the same thing as me? If you have any feedback is welcome...
Also if you managed to fix your shutting down after 5 secs and having to reboot issue issue I would love to know how this was achieved
any help is greatly appreciated as always
Do a mega wipe. Then flash stock rom.
this is XXXDDDAAA
OK mega wipe?? can you explain this to me and how to do that??
I currently have the stock rom for the UK 4.1.1
N7100XXALJ3_N7100OXXALJ4_BTU
so even though I can install this it still switches itself off after 5 secs and I have to reboot.. i am now at my wits end and will try anything to get my phone back to stock and actually working...
so any help is greatly appreciated....
http://forum.xda-developers.com/showthread.php?t=1983489.
this is XXXDDDAAA
Thanks for that...however gutted..it didnt fix my problem...
Then flash stock rom and fully unroot it.
Then go to Samsung store.
this is XXXDDDAAA
Hi Guys really need help on this one.
As a brief background on the problem, from stock I have flashed a few custom roms mainly paranoid android, carbon, android revolution hd. Flashing was always successful. No problem with odin flash as well. My concern is this. I noticed that I was getting SODs after flashing a few custom roms. So in order to fix it, I tried to flash stock rom. No problem with flashing however SODs continue to exits. Have tried flashing quite a few stock roms but basically SOD problem still exists. By the way when flashing through ODIN I always just flashed with the PDA option never with the others. Getting really frustrated about this. I can get rid of the SODs temporarily by using SoftLocker. However, I wish to get back to a stable rom base before I try any new customizations. Hope you can help me. Thanks.
On an added note, when I connect my phone to the PC the phone is not automatically detected. I still have to input *#7284# change modem to pda in order for it to be detected. I think this is somehow related because this happened during my encounters with SODs.
Your help would be greatly appreciated.
By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.
t3kn1ks said:
By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.
Click to expand...
Click to collapse
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.
Fixed! and Solved!
t3kn1ks said:
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.
Click to expand...
Click to collapse
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.
t3kn1ks said:
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.
Click to expand...
Click to collapse
Thanks man i thumbs up ur account....i was changing my dead screen to a new one and i thought it was the new screen that kept turning off even after trying stock kernels and even pegasus but because of ur note2core recommendation and worked like a charm ....thanks man
so i try flashing back to lifeless v14 and stock zvb deodex to fix the gps and i come up with a problem, which is the reason im posting it here maybe someone might know. the problem is that when i flash the roms the phone keeps rebooting when it immediately connects to a network or wifi and wont let me get on the gps or do anything in the rom ,and weirdly enough the phone gets really hot. so far the only ROM that i can use is the cyanogen mod ones. anyone got any insight is not urgent but i would like to know what is happening.
jera27 said:
so i try flashing back to lifeless v14 and stock zvb deodex to fix the gps and i come up with a problem, which is the reason im posting it here maybe someone might know. the problem is that when i flash the roms the phone keeps rebooting when it immediately connects to a network or wifi and wont let me get on the gps or do anything in the rom ,and weirdly enough the phone gets really hot. so far the only ROM that i can use is the cyanogen mod ones. anyone got any insight is not urgent but i would like to know what is happening.
Click to expand...
Click to collapse
sounds like bad flashes. id LGNPST to stock and start over.
i will try that and let you guys know how it went
D851 here, When ever i switched from cloudy 2.5 to blisspop 4.0 and after wiping everything i flashed a various of radios bootstacks and etc to make it boot after many failed attempts to boot ( it boots up but after 4 or so seconds after the lg logo the screen turns black and doesnt turn back on until after i pull out the battery) it worked after i flashed the rom WITHOUT a custom kernel so naturally i booted up just fine and thought maybe now i set up everything on my phone and tweaks i should go back and flash a custom kernel i used to use (777 r16) but then it gave me the problem i faced before the black screen after the lg logo no kernal would work. THEN another problem arised similar to the freezing on the black screen randomly during a usage thru my day the phones screen would be unresponsive animations but touch wouldnt work and i know its not my screen cause when i flash back to cloudy it works fine the freezing happens at least every 5 mins. someone halp?
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
warrior420 said:
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
Click to expand...
Click to collapse
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
thelgog said:
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
Click to expand...
Click to collapse
Okay.
Well, when I was flashing I never flashed a kernel.
Ill be getting a brand new Anker Battery in the mail today. Ill report my findings.
I ended up going to a stock based rom and the issue never happened. So I stuck with it. Ill have to do some testing later and ill let you know how the battery works.
It's not the battery
I downgraded my T-Mo G3 since I couldn't root it with LP on it. Went back to 4.4.2., rooted it, TWRP'd it, and installed the latest CM12 Nightly, Gapps, SU, etc.
As long as the sim card was OUT the installation was great on wifi only, As soon as I put it in it shut off right after, or during boot up. Take the sim out and it works. And yes, the only way to get back into recovery was pulling the battery and doing the key press to recovery. Mystified.
If I find out anything, I'll post it here.
I'd say do a complete return to stock, upgrade via LG Mobile Support tool all the way to 20G, see how it works stock for a while. Then root ( http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 using the first method) and see what happens.