Database Info

[q] wifi "error"

No matter what ROM/Kernel I flash to i loose my WIFI access. When I go into settings/Wifi it just says ERROR. Anyone have any idea what I'm doing wrong?

With CM7.0.3.1, I have been using bcblends tinyrcu (available through kernel manager) and leave min/max as is (806max/245min) make sure you wipe cache/dalvik before installing the kernel...
Hope this works for you.
Sent from my PG06100 using XDA App

When it does that is your SD card not mounted anymore and requires a reboot for it to see it again? That happens to me smetimes
Sent from my NookColor using XDA Premium App

lilgrass71 said:
When it does that is your SD card not mounted anymore and requires a reboot for it to see it again? That happens to me smetimes
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
SD card should be mounted. It's only unmounted when I plug my phone to the computer to transfer files and such...

Same thing happens to me with kernels. Sometimes Wimax too. I'm using mik shift, works fine with stock kernel.
Sent from my Nexus S using XDA Premium App

Maybe its just my luck w cards... been running cm7 stables and had two 8 giggers die one me... one kingston class 4 and a sandisk class 6... its happening again on my last 8 gigger too!
Sent from my PG06100 using XDA Premium App

I have a regular evo with this same problem, tried 3 dif kernals, and upteen romflashes.... still have wifi error in settings

still no progress on this, i still have this problem... super gay

I too am getting an "Error" when trying to turn wifi, Logcat says " Wifi Driver missing" have tried rebooting, and flashing another rom. any help?

Well it's probably been said before, but here goes When you flash a new Rom make sure you do a FULL wipe. It's seems trivial, but not doing this can and usually does cause all kinds off issues. Also, you should check your WiFi settings, and make sure they're correct.

Full wipe has been done and what wifi settings are you talking about? phone settings can't be accessed because the phone can't turn wifi "on". is it possible to extract the wifi driver from another shift? i have another one at my disposal. BTW wifi was working a day ago no problem. i havn't flashed a new ROM in months and was on a stock rooted rom.

Have you tried to ruu back to stock to see if you have the same issue? Or nandroid back to a version where it worked?
Sent from my PG06100 using XDA App

yea ruu'd back to froyo, re-rooted and reinstalled updated radios, and am back to gb. any idea where the wifi drivers would be? thanks for the replies.

Have you just tried it from a stock froyo rom? RUU back to 2.2 and just try it from there. It should reflash all the proper radios. Maybe the wifi chip is defective in the phone too. It happened at work to a co-workers playbook.

lvpre said:
Have you just tried it from a stock froyo rom? RUU back to 2.2 and just try it from there. It should reflash all the proper radios. Maybe the wifi chip is defective in the phone.
Click to expand...
Click to collapse
+1 on that. Also if it was working then not. Something else might be up, are other devices able to connect to that WiFi spot with no issues? It is possible to extract the wifi driver from another SHift. But if you just RUU back to stock it should work. If not somethingelse is definately wrong. To get to the settings: Menu-Settings-Wireless & Networks-Wi-Fi settings-menu-Avanced.

yea went ruu'd back to stock, no dice. wifi just says "error" after "turning on", must be an internal problem. other devices work fine on this point. what would be the steps to extracting the driver from another shift, i have one ready to go.

If you RUU'd back to stock, and it's a still no good. Then you might want to consider getting a replacement if WiFi is really important to you. Especially if you know for sure that other devices can connect, and you cannot on a stock Rom. But you do risk getting an updated Shift. Not a risk worth taking in my eyes. Did you make sure and check all the settings?

Yea all the settings are good, it definitely seems to be an internal problem at this point. I'm weighing the options right now and came close to ruu'ing to gb to see if it solved the problem, but I just couldn't give up root.
only 2 things come to mind on what caused this, i attempted to update to the newest ota htc update over the stock rom, ( i know stupid, got the android + !) and i installed an app to transfer files over wifi.
Wifi isn't too important but I hate the feeling of not having my phone %100.

Same problem here. I just got a wifi-error running the latest shift-deck. The phone was brand new with a bad esn (planning to flash to a different carrier) and was first turned on 8/2/11. so basically 2 weeks turned on. This just happened 2 days ago. Cleared everything and flashed again. Don't know how to RUU or what it is. Anyone want to explain?

Ruu basically puts the phone back as if it were just out of the box. There is a thread somewhere here with the file. Just make sure you get the froyo version, otherwise you won't be able to root.
Sent from my PG06100 using XDA App

Freezing after flashing new rom

I know there is a thread similar to this already up, but my issue is a little different. I'm currently on Sasba Prime 3.0. Before that I was running a beta Jelly Time.
I've tried six different roms. Each freezes either in first boot or soon after. I know it is not the roms. I always do a full wipe. I have completely reformatted my sd. I've tried fixing permissions in 4ext and ROM manager.
Any suggestions? Because I am completely at a loss. Mainly because when I restore my backup of Sasba Prime, everything is perfectly fine with no issues.
Sent from my Inspire 4g using xda app-developers app

Try a different SD card...

ai6908 said:
Try a different SD card...
Click to expand...
Click to collapse
Tried it also.

Well, I finally got IceColdSandwich to flash okay. No force closes or anything. I'm never using Sabsa Prime again(No offense to the dev. It works great). It seemed like it was causing my issues. Someone had mentioned to me that some ROMs can take over a phone. I have no idea if this is true, but better safe then sorry I guess.

Random, constant SODs with any ROM or kernel

I having big issues with my SR lately. I was on chimera 2.2 and things were great. Popped cm10 alpha 3 on there with investgator Xs kernel on there and started getting SODs, one time it was locked for a while before I got to it. Was pretty warm. After that I've wiped the SD cards clean, odin'd back to stock, tried SEVERAL ROMs, cm 9 official, skyics, cm 10 super lite, and others... no matter what ROM (all with the kernel they come with) I get a SOD every 15 to 45 minutes. Even weirder is no last_kmsg is being produced!
With or without any CPU apps. No under volting. Tried 3 different batteries. Tried all I/O Schedulers.
I have exhausted everything I know about this to fix it and I don't know what to do.
I've tried wiping and flashing ROMs with all existing recovery options (twrp, cwm, cwm touch, custom cwm touch) and with or without dark side scripts. I've wiped 3 times or more....restored very old nandroids that never had that problem too, and they get it.
Is it possible there is ANYTHING left in my files that normally won't get wiped that could cause this? Is there anyway to figure this out or does it sound like my SR is going bad? I'm up for any solution. Today using one of the nandroids it didn't get a SOD all day, but it was stuck from going into deep sleep due to a wake lock from chrome which I have since fixed... its getting SODs again now...
I realize you may benefit helping me with a log cat which I'm trying to get with lumberjack. Oh and a dmesg right?
Thanks in advance to anyone who can help. I'll answer any questions I can I may have forgotten.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Forgot to mention I know a repatriation in Odin should help but there is no pit file for this phone... any other ways around that?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Try a fresh new revert back to stock on odin. If you still get sod, you are sol. Your phone hardware has gone bad. I'm guessing your internal sdcard developed corruption and is ireparably damaged.
Try to get it repaired or replaced under warranty.
Sent from my SGH-I727 using xda premium

jamesc760 said:
Try a fresh new revert back to stock on odin. If you still get sod, you are sol. Your phone hardware has gone bad. I'm guessing your internal sdcard developed corruption and is ireparably damaged.
Try to get it repaired or replaced under warranty.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
Wanted to give an update... I sent the phone to Samsung for warranty repairs last week. It is labeled as fixed and on its way home today. The repair tracker they let me see said it was a "Side Button Failure" and the repair was a "S/W Updated"... Now I know there has been talk of a power button issue with this phone.. but I was leaning more towards what the above poster stated.. a corrupt internal SD or something along those lines...
I guess my confusion is, did they really duplicate my problem before throwing a fix at it and then VERIFY it was indeed, fixed? I don't know how shotty Samsung warranty repairs have been for others but I hope they did indeed fix my problem. I guess we'll see.

VRBLK1 Full Wipe vs No Wipe in Odin

Since the New TouchWiz JellyBean leak dropped, we quickly found out that the Rootdebug method no longer works for rooting...Not a big deal as developers rolled back to our grass roots and used the original Odin method to achieve root. My only issue is with the suggestion to flash a modified No Wipe image of the stock K1 leak...Im not sure if I agree with this. I have dirty flashed with Odin in the past and things appeared to work fine on ICS, but stepping up to JellyBean seems to be different!
Point is since the leak has dropped many folks complain of media server causing battery drain, I was one of them. So I decided to odin back to stock using the rooted FULL WIPE VRBLK1 version by Mr. Robinson...and I have had substantially less battery drain!!! Battery life is currently at 15hrs with 65% left...2 hrs screen on.
I would suggest to anybody that flashed a no wipe image in odin and is having issues with media server draining the battery, and/or any other issues appear, try flashing the FULL WIPE version! As others have said, I believe the problem is a corrupted file on the internal sd causing the issue. Also a few other small issues I was having appears to be fixed, such as touch screen being unresponsive at times...also gps seems to lock faster. Anybody else noticing the same??

This is interesting. I did the no wipe to the newest leak and I felt it was horrible. Battery for me was not as good and the phone was always hotter. So I went back to J1 leak. If I get time I might try the full wipe version of the newest leak. Try the theory out.
As an addition, my CPU was always acting crazy. Random low frequency locks (would not ramp up). Sometimes it would stay high, probably the cause of the warm phone. And weird battery drain from the system I just could not explain.
Thanks for this and as I said I'll try fresh after the weekend. Holiday weekend is my family time.
Sent from my SCH-I535 using Tapatalk 2

I know this is somewhat off topic so I apologize for derailing....are you guys having any issues with NFC on AOSP ROMs after flashing the leak via Odin?
Sent from my SCH-I535 using Tapatalk 2

Marcismo55 said:
I know this is somewhat off topic so I apologize for derailing....are you guys having any issues with NFC on AOSP ROMs after flashing the leak via Odin?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I've only flashed an AOSP once. That was the last time. Too choppy, and i like my TW features. So, to answer your question, I don't know.
Sent from my SCH-I535 using Tapatalk 2

I did full wipe and everything is great except gps.

I did a no wipe version moving from J1 to K1, what I saw was the RAM footprint increase by 50%...
I did the full and footprint went back to what I recognized on J1...Barry seems as good or better than J1 too
Sent from my SCH-I535 using xda app-developers app

I did Robinson's no error via Odin and don't have any apparent issues. what should I be looking for?

lexluthor said:
I did Robinson's no error via Odin and don't have any apparent issues. what should I be looking for?
Click to expand...
Click to collapse
Did you use the full wipe or no wipe version in odin? Thats the point of this thread...no wipe seems to be causing a foul odor with media drain and random issues for folks. The full wipe leaves you so fresh and so clean!!

Sorry for sounding like a noob, but what exactly is media drain? Battery use by "media server?"
Sent from my Galaxy S III using Tapatalk 2

US Marine said:
Sorry for sounding like a noob, but what exactly is media drain? Battery use by "media server?"
Sent from my Galaxy S III using Tapatalk 2
Click to expand...
Click to collapse
yes

Hmm...I did the no-wipe flash, and I haven't had any issues whatsoever.
Sent from my Galaxy S III using Tapatalk 2

US Marine said:
Hmm...I did the no-wipe flash, and I haven't had any issues whatsoever.
Sent from my Galaxy S III using Tapatalk 2
Click to expand...
Click to collapse
Thats good! Im not saying everybody is going to have issues with the no wipe version...most likely its going to be folks that have flashed a bunch of roms and accumulated alot of folders/files on the internal SD. The point is if you are one of the unfortunate folks thats having issues, try the FULL WIPE version.

droidstyle said:
Thats good! Im not saying everybody is going to have issues with the no wipe version...most likely its going to be folks that have flashed a bunch of roms and accumulated alot of folders/files on the internal SD. The point is if you are one of the unfortunate folks thats having issues, try the FULL WIPE version.
Click to expand...
Click to collapse
Yeah, I flashed from bone stock the day I got the phone.
Sent from my Galaxy S III using Tapatalk 2

My phone seems a little laggy which I did not experience on the first leak. I don't not have the typical problems people have with flashing the no wipe version... That's what I flashed. Thinking of trying a factory reset but this thread makes me wonder if flashing the wipe version might be better? What's the difference though? Both wipe and no wipe are from the same file, right?
Sent from my SCH-I535 using xda premium

Question, I did the no wipe version on odin from the stock samsung s3, and now my RAM usage is almost always close to 1 gb. Before on ICS it was like 600 or 700 mb. Is this normal for jelly bean?

Ryno77 said:
My phone seems a little laggy which I did not experience on the first leak. I don't not have the typical problems people have with flashing the no wipe version... That's what I flashed. Thinking of trying a factory reset but this thread makes me wonder if flashing the wipe version might be better? What's the difference though? Both wipe and no wipe are from the same file, right?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Full Wipe will repartition the Internal SD and wipe rom data...this will get rid of any corrupted files that reside on the internal. Its the same principal as reformatting and installing windows. Dirty Flashing writes your data over the top of data and nothing else in the internal sd is touched...not saying dirty flashing is bad, I do it alot, but when wierd issues arise, 90% of the time a Full Wipe with Odin fixes things.

VigilanteM2 said:
Question, I did the no wipe version on odin from the stock samsung s3, and now my RAM usage is almost always close to 1 gb. Before on ICS it was like 600 or 700 mb. Is this normal for jelly bean?
Click to expand...
Click to collapse
I believe touchwiz jellybean uses more ram.

Is the full wipe version included everything like the original Verizon release version? (radio, rom, kernel, bootloader etc...)Thanks.

buhohitr said:
Is the full wipe version included everything like the original Verizon release version? (radio, rom, kernel, bootloader etc...)Thanks.
Click to expand...
Click to collapse
Yep

I have just realized that the hotspot is broken. Every time I try to turn it on, it force closes Settings. Anyone else having this problem?
EDIT: So I downloaded a hotspot toggle widget, and it works fine. I only have a problem if I try to enable hotspot via Settings. Interesting.
Sent from my Galaxy S III using Tapatalk 2

vzw s3 random reboots when downloading a file or moving files.

For the last 2 months or so my s3 has been having random reboots when acceding the internal or external storage. It happens when downloading files from web or transferring files over wifi. Happens when connected to home network or cell network. Also happens when moving or unzipping files that are already on my device. Generally files about 100mb or larger, but has happened with smaller files. May reboot once and I can finish downloading or transferring, or it may reboot repeatedly when I try to redownload or move files. I have Googled this and can only find older threads about freeze ups that occur when accessing storage but were for the GSM models of s3, and aging the threads were over a year old. Device info is 16gig with 16gig external card. Running aokp (8/20 build currently). BMS kernel (7/30 build). Happens on last few releases of aokp with stock (aokp) kernel or others (BMS). (Lean). Any one experience this or have any input on this issue?

Try going back to stock with stock kernel. If it still happens you have a faulty device or hardware is failing.
Sent from my SCH-I535 using Tapatalk 4

Sandman-007 said:
Try going back to stock with stock kernel. If it still happens you have a faulty device or hardware is failing.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Would it be ok to restore my stock nandroid? Or should I just use odin?

No use odin
Sent from my SCH-I535 using Tapatalk 4

Sandman-007 said:
No use odin
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
thank you, i will give it a go when i have a chance. just flashed beanstalk 4.3 to see if that helps. ill restock if i have any issues.

tdawgg777 said:
thank you, i will give it a go when i have a chance. just flashed beanstalk 4.3 to see if that helps. ill restock if i have any issues.
Click to expand...
Click to collapse
Going back to stock would only be necessary if you have a soft brick. You're already rooted, and there is no other reason to go through the entire process again until you've tried everything else.
Lots of things can go wrong with Odin that could put you in a predicament, such as accidentally putting the file in the wrong slot, a faulty connection, a bad flash, all of which would put you in a much worse situation.
Random reboots occur from many factors, but a lot of it can be boiled down to the phone not playing nice with the current rom you are on, these are the steps I would take.
1. Try a different rom, 4.2 aosp roms or touchwiz roms might fix it. Restoring your stock android would be a great step, just make sure you don't ota because you'll lose root.
2. If it's similar on all roms, then try a different kernel.
3. If it's still occurring, try to use a kernel that allows you to apply voltages such as ktoonsez, and raise the minimum voltage for each cpu step a tiny bit for each step.
4. If it's still rebooting, try formatting your internal SD card and reflashing a stock based rom through a custom recovery, such as cleanrom or a stock rooted rom.
5. Odin back to stock at a last resort.
If all of those steps don't work, then you have a hardware problem.
Sent from my SCH-I535 using Tapatalk 2

If he just went back to official Firmware ie Stock he wouldn't have to screw around with different ROMs and kernels and voltages. No offense but you need to learn better troubleshooting skills. If he went to stock it would pretty much eliminate all things u suggested (ie low voltage). Odining back to stock would format his internal for him thus eliminating that step u suggested as well. I this this will save him time and frustration.
Sent from my SCH-I535 using Tapatalk 4

Sandman-007 said:
If he just went back to official Firmware ie Stock he wouldn't have to screw around with different ROMs and kernels and voltages. No offense but you need to learn better troubleshooting skills. If he went to stock it would pretty much eliminate all things u suggested (ie low voltage). Odining back to stock would format his internal for him thus eliminating that step u suggested as well. I this this will save him time and frustration.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
What you're suggesting is basically a cure all for everything, but don't you think it would be better to troubleshoot the problem systematically than simply go back to stock everytime you have an issue you can't figure out? If that was the case, then I would have used Odin to go back to stock at least a dozen times by now.
It's a better learning experience to understand what a specific phone can run and can't run. It's a pita to have to flash back to stock and reroot when you don't troubleshoot the actual problem. Especially when it's a rom or kernel related issue that can be easily remedied.
Sent from my SCH-I535 using Tapatalk 2

OK I can see where you r coming from.
Sent from my SCH-I535 using Tapatalk 4

Ok so its been 10 or so hours now that I've been running beanstalk 4.3 (8/27 build) with bms kernel (8/15 build). I've transfered files around, made app back ups and downloaded latest update for beanstalk (200+ MB) and no reboots.

What advice is there when I have random reboots across roms. no matter which I try oi always get random reboots. is it tthe battery?
Sent from my SCH-I535 using Tapatalk 4

0331 said:
What advice is there when I have random reboots across roms. no matter which I try oi always get random reboots. is it tthe battery?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Odin back to stock and run it completely stock and see if you can repeat the problem.
If you're completely stock and your phone keeps rebooting, it's likely a hardware problem.
Sent from my SCH-I535 using Tapatalk 2

will do thank you!
Sent from my SCH-I535 using Tapatalk 4