Hi, about 5 days ago my wifi stopped working. I'd turned it off a few days earlier since I didn't need it. When I try to turn it back on now though, it takes a few seconds and then says error. I'm not sure what's wrong with it.
Since then I've reflashed my phone rom (leedroid), factoryreset it, and updated the radio. nothing so far has fixed it. Mobile data still works so I wouldn't think it was hardware, but a software error shouldn't have survived the wipe and the radio update.
Does anyone have any suggestions?
blackied said:
Hi, about 5 days ago my wifi stopped working. I'd turned it off a few days earlier since I didn't need it. When I try to turn it back on now though, it takes a few seconds and then says error. I'm not sure what's wrong with it.
Since then I've reflashed my phone rom (leedroid), factoryreset it, and updated the radio. nothing so far has fixed it. Mobile data still works so I wouldn't think it was hardware, but a software error shouldn't have survived the wipe and the radio update.
Does anyone have any suggestions?
Click to expand...
Click to collapse
I had similar issue when flashing another kernel on my stock ROM. Maybe your kernel isn't compatible with the radio or the kernel modules haven't been applied correctly. Hardware error should be presumed after flashing original RUU.
The thing is that I hadn't played with my phone since last year. the wifi just randomly stopped working. It was still on 1.22ghz kernel 1.0.2. It got reset to stock kernel when I factory wiped it.
I've gotta go travelling again for work tomorrow so I'll try flashing the original ruu back next weekend. Would it just be a case of restoring the original nandroid backup I did before I first h-booted/rommed it?
blackied said:
The thing is that I hadn't played with my phone since last year. the wifi just randomly stopped working. It was still on 1.22ghz kernel 1.0.2. It got reset to stock kernel when I factory wiped it.
I've gotta go travelling again for work tomorrow so I'll try flashing the original ruu back next weekend. Would it just be a case of restoring the original nandroid backup I did before I first h-booted/rommed it?
Click to expand...
Click to collapse
As far as I know, factory wipe deletes just the user data. I might be wrong though, because this is my first android, so I'm still learning the basics on rooting, kernels, etc. But from your first post it seemed that you updated your radio in that period, so this might be the clue to what happened. I don't know if the nandroid backup would restore everything to stock, but I'm pretty sure that the original RUU would. Still, you should follow a procedure that would allow you to keep your root (I think if you have radio S-OFF, you'd be able to flash 1.32 RUU and just root it). Anyway, you can't return the phone for warranty services with a custom ROM, so you still need to flash a stock RUU.
Sorry, I should clarify: I did the radio update yesterday to see if it could fix it. It wasn't the cause.
Related
Hey guys, I am kind of a noob but have successfully been hacking with my Touch for a while now...or so I thought. I flashed to the 3.37.78 radio a while back and have been keeping up with NSFAN's ROM's for over a year now with no problems....until a few months ago. My phone locked up and I had to soft-reset but to no avail. It got stuck on the startup screen and would not do anything so I did a hard reset and all was good. Then it happened again weeks later. Now it has been happening a lot more recently. I will be texting or on the internet with it and then all of a sudden it will lock up, I do a soft reset and it will hang up either on the startup screen or seem to boot up but then contacts will be missing and there will be no signal. Sometimes the today screen will show but I cannot do anything on it.....all of this requires a hard reset to fix. This happened after I flashed NSFAN's latest ROM so I flashed back to some of his older ROM's that I had no problem with in the past and still the same problem. It has been happening every week or 2 now to the point that I can't even bother setting up the phone the way I want because I know it will happen again. Can any of you guys tell me what the problem is? I really need to get this resolved because I am losing information everytime. Please help!!!
Im a GSM Phone user... and as a general rule, if things start to go wrong.... Flash the OEM rom. That would be the stock ROM. And then flash back to your "custom" rom... Ive had to do that with my phone(s) as well.... It basicly puts things back to 'ground zero'. BUT. Use the phone with the stock rom for a day and see if you still have the same problems... it may be a problem in the phone. In which case you may need to replace and/or send the phone back for replacement to your carrier.
Hope this helps....
Thanks for the reply.....What I ended up doing is reflashing my radio to the 3.42.50 version and then reflashing my ROM to NSFFAN's again. So far so good. I am really hard on my phones and the fact that I drop my phone on a regular basis can't help either....I just need it to last me a few more weeks until I get a new one. Thanks again...
Okay, there is some misinformation going on.
If you are running a stock EVO, 3G works fine (I just did the 25MB speed test at testmy.net and averaged 1.1Mbps - when ROOTED, I can't get the 6MB test to finish).
When running a rooted EVO in Denver, for some reason, 3G cuts out constantly and won't last more than 2 minutes... generally about 30 seconds and then it dies for a few minutes or until you make a phone call, reboot, put it in airplane mode, etc.
I have tried literally EVERY ROM including the "stock rooted" ROM and they ALL exhibit this behavior.
The only thing I can think of is that something is amiss when flashing the new radio without using the official HTC update package but I'm not feeling like re-rooting my phone all over again with the old radio just to find out.
How many people are experiencing this?
I rooted my EVO and began having issues... Probably about the 13th as stated in the thread... Got really annoyed and flashed the stock RUU (had to take the rom.zip from the Temp folder and rename it to PC36IMG.zip in order to flash though because RUU would not find the phone)... Problem instantly was resolved. Ran the OTA update to get the new radio, thinking it was a radio problem, nope. Still works perfectly fine.
I decided I wanted to try EVOlution V8 today so I re-rooted. Right off the bat, 3G issues. I rooted manually, then NAND, then recovery, then flashed the new radio, REBOOTED, went back into recovery and flashed the ROM...
Now I just ran the RUU and flashed back to stock and everything is working fine. So there is something about the procedure to root that is causing the problem and I don't know if its Denver-specific or what...
I can tell you I didn't have any problems until I unlocked NAND and flashed the permanent recovery. Toast's original root gave me no issues... but that may just be coincidence.
If I decide to stop being lazy, I may re-root and skip updating the radio and see what that does... But for now, I have to conclude it is a rooting issue, NOT a network issue.
I've experimented today with the leaked XWKF1 build from samfirmware.com! After a few hours I realized that I've got a (for me serious) bug as well:
Every time I wanted to do a power off (shut down), the phone immediately restarts itself. Tried everything to get rid of this: Reflash with or without repartition, factory reset, rooting, using ZSKF1 kernel, CWM4.0.0.2, ...
Even after pulling the battery out: As soon as I put the battery back in the phone booted up immediately.
At this time I began to fear a hardware fault, luckily after going back to Liteningv1-3 power off works as intended again...
So, why I'm writing this here:
If anybody encounters the same: Just flash back your old rom and you will be fine again.
And: Can somebody explain this?
I do not have this problem with KF1
hg3atintin said:
I do not have this problem with KF1
Click to expand...
Click to collapse
Thx for your feedback!
I'm almost sure most people won't have that problem, otherwise there should be quite a few reports till now...
I've had that issue before, on KE7 and my o2 stock ROM. I never could figure out what caused it, but battery pulling usually fixed it (at least good for a few power downs)
Might be that you have an alarm set in the next days.
just flashed to the kf1 stock and don't have the problem
I think when you are on a custom rom and go to stock, you might encounter weird quirks like this. Since the stock roms are non-wipe, it may leave remnants of your custom rom. Might be better to try a full factory reset and wipe cache/dalvik from recovery before flashing if you are okay with losing all data to see if that stops the reboot issue. Its not always necessary but I have had some weird problems in the past.
Either that or just wait for Litepro to come out with a KF1 version or another version in the near future. I think thats what I'll do
+10 for a wipe .
jje
So.... I was stuck at the M logo after trying to update to a newer version of MIUI. I successfully SBF'd back to stock froyo and my phone won't activate. When the activation call tells me to press "1", it simply goes silent.
Now I somehow bypassed the activation screen, I don't think that was a good idea because it forced me to connect via wifi. I just said "screw it anyway" and went ahain to reroot. Then I installed CM7 (since I current don't have the MIUI zip I was previously running on my phone). Now I am stuck at the CM7 logo. Not sure if I should SBF again or what I should do. I'm kinda freaked.
Also, I have never had a problem SBFing before. This seems more serious than before.
Update: Wiping data allowed me to boot up in CM7. Still cannot activate my phone. Whenever it prompts me to press "1", all I get is complete silence.
I'm currently at UT Dallas, so I don't think location is a problem is it? Actually it shouldn't be because I bricked my phone here before. Had to reactivate it and it worked great.
Man, this is the first time my phone won't activate.
Yes I know I am posting a lot, but since no one is here to help currently I'm trying things out on my own.
I tried restoring a nandroid I had of CM7 previously. Man I thought this was always a failsafe....
Just thinking of things I did since the last time I activated my phone. I updated something (radio version, I don't really know much about it), it was supposed to make my 3G faster or whatever. But I mean I've SBF'd, factory reset and everything, so that shouldn't be an issue?
Gosh dang, I just want my phone back the way it was 2 hours ago.
One of the reasons nandroid might not be working is that I might have a different version of clockwork on my phone. I remember before having a version where the test was blue, but I forgot the version number. Now the one I get with rom manager is green (like the one I had before I got the blue one).
Man I am sooo confused here. I am completely at a loss. I am out of ideas. I need help.
So I realized I did not have the second init version of clockwork. I just flashed that, and I'm waiting to see if I will get any errors. If I get this to work I am going to flash the version of MIUI I had and try to restore my more recent nandroid (since Ive gotten MIUI).
Yup problem solved. Not sure what was causing the problem, but at least its solved. I'm gonna be extra careful next time I flash something.
Hi all,
I recently installed the newest build of Slimbean. I am having a few issues: I am unable to play any media... Music, videos (youtube). My phone app does not work. I cannot receive nor send any calls. And my phone produces no sounds at all.
I tried installing build 7 to see if it was an issue with the build I was using... didn't help.
Internet and wifi work without any problems.
Galaxy S4 i337m
Baseband: I337MUMUAMDL
Version: Slim-4.2.2.build.7-OFFICIAL
Build #: slim_jfltecan-userdebug 4.2.2 JDQ39E eng.blk_jack.20130706.15730 test-keys
Any ideas?
Thanks in advance
Update: Any ROM I install... Phone and sounds do not work.
Talabis said:
Update: Any ROM I install... Phone and sounds do not work.
Click to expand...
Click to collapse
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
jd1639 said:
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
Click to expand...
Click to collapse
I did just that... But it's a bit of a story.
I had just fixed another problem I was having yesterday. Was getting stuck at the S4 splash screen right after powering on the phone. The problem was caused by TWRP 2.6 and formatting /data partition. Long story short, I installed CWM and used it to do a full wipe/format of partitions and then was able to install ROMs, restore backups without issue.
So today, since everything was working, I decided to flash a new custom ROM (which I installed) and the MG1 radio. Wasn't having any luck with the radio. Finally, I was able to flash a radio via mobile odin, but then I soft bricked my phone. Got stuck at the S4 splash screen (same issue I had yesterday, but this time, a different cause). So was troubleshooting it all day. Tried to go back to stock, no luck. Tried to restore the stock backup I had, no luck. Only thing I could do was install custom ROMs at this point to get into my phone (i.e. Slimbean, FoxHound, etc...). But, at this point, although I could boot into Android, I had no sound at all and couldn't play video. So after hours of trial and error, I installed CWM again (replacing TWRP 2.5.0.2), did a full wipe/format and tried to install a stock ROM. No luck. Still was hanging at the S4 splash screen. Then I tried to install this ROM again which I had luck with in the past; |ROM| |★VLUAMG1★| |CANADIAN||i337M||STOCK||ROOTED||July.26.13|. But his instructions said to install a wifi fix or fear soft bricking my phone. So I installed the wifi fix, but selected the wrong file (I know, stupid. Done a lot of stupid **** in the past couple days with this phone). Now, after the phone rebooted, I would see the S4 splash screen for a split second, and it would auto load into download (odin) mode. Couldn't get into recovery at all. So then I decided to flash one of the stock ROMs I tried earlier that didn't work, but this time, SUCCESS!!!!! Phone was booting and all sounds worked. I could make/receive phone calls as well... Everything seems to be working fine now. I find it funny that flashing a wifi fix that I shouldn't have seems to have fixed my issue in a sense. Since it allowed me to successfully flash a stock ROM. So I am making a backup of the stock ROM and will decide what I'm going to do from here.
Holy goalie!!! It's been a very vexing couple of days.
Nice that you got it all worked out, I've found out that if your "status" is custom, it will sometimes give you problems when flashing a "stock" rom via odin.
So what I always do when reverting back to the stock rom, I use triangle away to clear the flash count and make my phone back to "Official". If you want the steps to do this, let me know, it's not hard, but there are crucial steps to get this right!
JP