Hi
I picked up a t959w off craigslist. The guys said he couldn't connect to wifi or anything, but I guessed he just screwed something up. However, after flashing AOKP or CM9 I can't get any data, wifi etc..
Is there any way of diagnosing this?
Thanks in advance for the advice.
Kentt
First goto, setting, about phone, what does it says for baseband? Sometimes too network drivers don't flash fully, trying flashing something like Hefe's 0.81 kernel and flash it twice if needed.
Baseband is T959WUQLB6. I'll try hefe.
Ok. There is some command to get logs of the wifi and what its trying to do, but I can't recall them off hand, but if reflashing a new kernel, then reflashing again doesn't do it, might be hardware somehow. You did get the phone with capacative buttons DOA, so who knows what this person did to the poor phone. lol. I assume calling/messaging works with the modem flashed.
Related
Can someone explain the nature of the reboots that they are experiencing? I had a reboot on Friday but it was much more then just a reboot, after the phone was finishing powering back up I had no ability to call out as if there was no service. I tried numerous battery pulls and even had Verizon do a reset on there end, nothing helped yet I was still able to receive and send data. Finally after about an hour my service was back. Then the same thing happened again yesterday, I went through the same processes with no success yet. I have tried all the different radio choices and nothing is working, does anyone have any suggestions?
Thanks!!!
Also I am rooted and using the stock rom
Bump..........
Did you do any radio flashes? I know mine rebooted on me when I was trying to flash the GB leak from yesterday and there wasn't even a signal bar...just blank space. I reflashed my radio and everything was ok.
Edit: read the last line that I missed before. I am assuming if you are on a stock rom that you didn't flash any radios (otherwise it would have been noted). Thats the only thing that I have run across causing issues. SMH
Yes, I had similar problem
I was running the Stripped Das BAMF with the new radio (same as the one that recently came out OTA) and had this no service problem twice. Since I'm in a 3G only area, I have been using CDMA auto(PRL) and use the Phoneinfo app to change it. I tried to change the network type to something else but couldn't change it. (I presume the network type is for data, but I was trying to see if changing it would affect the service). The other options were there, but I couldn't select anything other than the CDMA auto. A battery pull fixed my problem both times.
Now I'm running BAMF Remix 1.6.3 with the new radio and everything is fine. I don't change the voltages or overclock. Yesterday as I was driving around town the phone rang, but I didn't answer it. When I got home, the phone had powered down and did a reboot.
Just an additional thought. You might try doing a data wipe/factory reset to see if that helps. Of course, you lose your settings that way, so back up first.
Sorry in advance for starting a new thread; I looked around for someone who already had this problem, but haven't come across it yet.
As title states, my phone started getting stuck in a loop of restarting after I updated my phone to Gingerbread, then used drhonk's kernel to root it.
I have a t-mobile Galaxy S 4G.
Don't know what numbers you need, so here's all I can grab
Model #: SGH-T959V
Firmware: 2.3.3
baseband version: Y959VUVKF1
Kernel version: 2.6.35.7-t959VUVKJ1-CL611444
build number; GINGERBREAD.VUVKF1
Everything was working well, and using my data connection, I downloaded the apps I wanted on my phone from the market, including root uninstaller, to get rid of some bloatware.
Afterwards, I decided to turn on my wifi to see if the signal stregnth was any better after updating to GB.
Since then, my phone has been in a constant state of restarting, running media scanner, finishing media scanning, and then restarting.
I managed to get it into airplane mode, and that keeps the phone on, but as soon as I turn airplane mode off, the wifi starts back up and the phone begins the restarting cycle again. When I can get far enough into the phone to see the wifi settings, I have to deactivate airplane mode, and my phone freezes up when it tries to turn the wifi on, and I touch to turn it back off. Every try I've done, it restarts before it can actually turn wifi off.
Any ideas on what I can do to fix things? I would really like to have a working phone. >_<
(Also, the only bloatware I uninstalled that I can think would have anything to do with connectivity, was media hub. Beyond that, I just removed inception (This was an insurance phone, so the sd card didn't have any info on it), amazon kindle, amazon mp3, and t-mobile tv)
I am pretty new to rooting and flashing. I've been doing my research before actually doing anything, but I won't even pretend to be very smart on the subject. So please, help would be appreciated. Help, in newbie terms, even more so.
Thank you.
KF1 is really old. Try following my GB starter pack guide to make sure you're on a good ROM, and try flashing some of the newer roms, mainly ICBINB, Audiophile, Valhalla or Beautiful SGS4G. They're all based off of recent builds and you can even try all of them by putting them on your sd card and flashing each to see which one you like best.
If you're thinking you'd prefer to stay on a KF1 rom, I'd strongly recommend against it, since it's an early GB leak that still had a lot of bugs. Generally, the KH#+ builds have been a lot more stable. The latest is KJ2 now by the way.
Thank you so much for the advice, I'll go ahead and do so later today.
ok, so weird issue for me.. and idk if anyone else is experiencing it cause it doesn't seem like it.. I'm getting wifi error (and before anyone says anything about my router, it's already configured). It just won't turn on no matter what. I hit it, it says a grayed out "Turning On..." and then error again. No attempt or anything. I go into wifi settings and everything under Wi-Fi is grayed out, that's the network notification at&t wifi hot spot setting and wifi networks. I've been trying hard and absolutely no resolution. A google search only affords me more "fixes" for my router and that's not the issue. If i can get a referral somewhere else that doesn't talk about the router being the issue then i'd greatly appreciate it.
**update**
sorry for the "vote for.." whatever it says, i didn't mean to i was trying to subscribe so please don't get upset about it. kthksgb
Vahnyyz said:
ok, so weird issue for me.. and idk if anyone else is experiencing it cause it doesn't seem like it.. I'm getting wifi error (and before anyone says anything about my router, it's already configured). It just won't turn on no matter what. I hit it, it says a grayed out "Turning On..." and then error again. No attempt or anything. I go into wifi settings and everything under Wi-Fi is grayed out, that's the network notification at&t wifi hot spot setting and wifi networks. I've been trying hard and absolutely no resolution. A google search only affords me more "fixes" for my router and that's not the issue. If i can get a referral somewhere else that doesn't talk about the router being the issue then i'd greatly appreciate it.
**update**
sorry for the "vote for.." whatever it says, i didn't mean to i was trying to subscribe so please don't get upset about it. kthksgb
Click to expand...
Click to collapse
I've never heard of that error before so I don't know. Are you rooted? What version of Android are you running? What I'd do is backup all your apps, text messgs, contacts, etc., and do a factory reset and see if that fixes it. Worst case scenario you could flash a fresh new version of 2.3.5 via RSD Lite and you'd almost surely have the problem fixed, unless it's a hardware issue.
I actually started off on 2.3.5 with the issue, and then i started having problems with my ability to actually get past FB, so i had to do a the rsd fix where i force stock on there again. From that point since it still wasn't working I went and pushed ota which took forever and got onto blaze hoping/praying that it would finally work after that. ultimately nothing worked so I'm here now at the mercy of the forum hoping some guru might have something that I could try.
Vahnyyz said:
I actually started off on 2.3.5 with the issue, and then i started having problems with my ability to actually get past FB, so i had to do a the rsd fix where i force stock on there again. From that point since it still wasn't working I went and pushed ota which took forever and got onto blaze hoping/praying that it would finally work after that. ultimately nothing worked so I'm here now at the mercy of the forum hoping some guru might have something that I could try.
Click to expand...
Click to collapse
Wow brother, if you flashed the 2.3.5 fxz to it and still had the problem, i'm thinking there's a hardware issue.
yea, i figured. so i've already contacted motorola and since i'm still under warranty i can return it and they'll send me another one. them's the break, but i got 2 weeks before i even have to decide on that so its not something i'm rushing towards lol
Try going to adb shell
su
ifconfig tiwlan0 down
(toggle airplane on then off)
ifconfig tiwlan0 up
(toggle airplane on then off)
Maybe that will bring your adapter back up. Hope that helps.
hope this doesn't mean anything bad, but it says error no such device
i did adb shell in cmd prompt, it started up went [email protected] then i did su and it changed to [email protected] and i did what you said.. and it gave me that error
Had the same error problem a few ago using blaze v3 rom. After reboot, it was solved and I could connect to my wifi again.
Have no idea what caused the problem, as I didn't do anything out of the ordinary with the device since the update from blaze 2.5.
Sent from my MB865 using XDA
I am facing same issue on Droid 3. it does not work with Stock ROM, but works with CM9 or AOKP based rom.
wifi error afterusing motofast fast script 2.3.5
i am having the same problem also. it just started right after i did the "flash back to 2.3.5 moto fast script" the first time i used it everything was fine but this time ..which i did the same process....i am getting that same error.and when i try to ota to 2.3.6 it says that i need to turn on wifi ????since then i have tried factory reset and still had the issue.then i rooted 2.3.5 and using cwm i was able to restore a backup.so now i am back on 2.3.6 and i am still having the same problem.i have tried a few wifi fixer apps from the playstore but nothing seems to work. and i still dosnt want to OTA without wifi working :confused........so it seems like there is something nthat went wrong with the motofast script or something got erased ???i hope this will help to try and figure out a solution ......btw im new to this somewhat so please bare with me
trev1134 said:
i am having the same problem also. it just started right after i did the "flash back to 2.3.5 moto fast script" the first time i used it everything was fine but this time ..which i did the same process....i am getting that same error.and when i try to ota to 2.3.6 it says that i need to turn on wifi ????since then i have tried factory reset and still had the issue.then i rooted 2.3.5 and using cwm i was able to restore a backup.so now i am back on 2.3.6 and i am still having the same problem.i have tried a few wifi fixer apps from the playstore but nothing seems to work. and i still dosnt want to OTA without wifi working :confused........so it seems like there is something nthat went wrong with the motofast script or something got erased ???i hope this will help to try and figure out a solution ......btw im new to this somewhat so please bare with me
Click to expand...
Click to collapse
only once did i have problem with wifi on this phone and i never fixed it on 2.3 ...
after a lot of trial and error though, i got it fixed with upgrading to ics.
other than that, does your bluetooth do the same? because symptoms like these usually mean water damage. you might want to check the indicators, (if the a2 has any) --- if you broke your wifi by updating rom, this probably isnt the case.
I noticed that the description for the wlan interface is different in the build.prop between GB and ICS. So you might check your /system/build.prop.
Look for this towards the top of your build.prop
Code:
# wlan interface
wifi.interface = tiwlan0
softap.interface = tiap0
In GB wifi.interface = tiwlan0
In ICS wifi.interace = wlan0
So make sure the value is correct, if the value is wrong it will show your wifi "greyed out" in the settings. Anyway, it's something to try, and I hope that helps. If you change the value, make sure you reboot then check to see if it is fixed.
Since I don't know if anyone is still looking into this at all because I haven't seen many updates to this thread, I'm wondering if anyone has checked the kernal information. I was able to do some searching (btw I haven't sent in my atrix 2 in yet because of work) and I found that there was some issues in regards to the Kernal. I don't know if thats true or not but I would like to see someone test it out or try it out or what have you and see if they can shed some light on the situation because the situation is rather bleek, and i'd rather not have to send in a perfectly good phone that was working just fine before the flash, and still wouldn't work after reflashing the AT&T rom.
I have read all the post on this and let me say I have done everything (that I know). Factory reset. Wiped everything through rom manager and through bootloader. Loaded several custom roms. Even updated the radio. Took battery out for 5 mins. My router is working fine. wifi turns on like it is looking but then says "error". Also bluetooth doesnt work. Turns on then turns off. No "error" or anything. Try to use the up sound button and it no longer works. Everything was working fine then all of a sudden they quit. Is there something I am missing? I though maybe hardware problem but cannot get info on where they are. Have read that wifi antenna is in the battery cover. Checked and all contacts are clean and making contact. Really frustrated. All help is appreciated. Thanks in advance.
Were you s-off or s-on ?
Sent from my Inspire 4G using xda premium
Phatomwarrior6 said:
I have read all the post on this and let me say I have done everything (that I know). Factory reset. Wiped everything through rom manager and through bootloader. Loaded several custom roms. Even updated the radio. Took battery out for 5 mins. My router is working fine. wifi turns on like it is looking but then says "error". Also bluetooth doesnt work. Turns on then turns off. No "error" or anything. Try to use the up sound button and it no longer works. Everything was working fine then all of a sudden they quit. Is there something I am missing? I though maybe hardware problem but cannot get info on where they are. Have read that wifi antenna is in the battery cover. Checked and all contacts are clean and making contact. Really frustrated. All help is appreciated. Thanks in advance.
Click to expand...
Click to collapse
When was the last time the phone worked completely and what state was it in (ROM, S-Off or S-On unlocked bootloader, etc.)? What radio did you have, what radio did you flash, and what radio do you have now?
So here's my issue, my Galaxy S Blaze has been switched from ROM to ROM constantly, I have seen ROMS with modified build.props, other added features, and a bunch of other tweaks, you name it! I don't know what all those tweaks mean, I have no idea if it could affect the way my phone receives the signal but it got me so frustrated that I kept switching roms until finally then I went back to stock and am no longer am switching to another ROM.
Here's a history of the ROM switching I've made in the past couple of months:
1st - MIUI
2nd- Cyanogenmod
3rd- Gummy ROM
4th- Liquidsmooth ROM
5th- Cyanogenmod
6th- Dirty Unicorns (problems with signal started occurring right about here, and onwards)
7th- Stock ROM (hmm... nope nothing fixed.)
8th- Validus (still no, I didn't like the constant force-closing of many apps)
9th- Gummy ROM (nope, what's worse is my screen kept freezing if I had atleast 2 apps open and I slid down the notification drawer)
10th- Cyanogenmod (well, maybe switching to cyanogenmod will fix it)
11th- Gummy ROM (*sigh* switching back? Nope, still didn't help my signal)
12th- Stock ROM (you would expect it to be fixed right about here, but nope)
So what's up what is the exact problem with my signal? Here's the thing: My signal works! That's a start atleast. However, if I turn on my Wi-Fi while I'm home, I can still call/text people, all of that works. But after maybe 2 hours or so, the signal bar is still there, it's telling me it has signal and it's connected, SOMETIMES it will be empty meaning I have no signal(when I really do). But in reality, I can't receive texts, nor calls, none of that. So how do I fix it? By restarting my phone sadly, that has been the only solution for me for these past 2 months. People have complained to me because I don't answer my phone anymore, well I'm sorry my phone can't receive those calls due to this messed up signal. There are 3 other T-Mobile phones in the house that have no problem! The problem here is with my Blaze phone.
So what if I turn the Wi-Fi off for the whole day and see if it's the main thing causing the issue? Well, I did this. Turns out that the signal stays on longer than when I'm on Wi-Fi but it still goes out. I have switched SIM Cards, I have tried switching my APN: from "epc.tmobile.com" to "fast.t-mobile.com" but the problem appears to happen more quickly on the "epc" one than the "fast" one. Please help me with this, this has been frustrating me a lot lately. I'm not sure if anyone has even had the same exact problem that I'm having, I've searched online but haven't seen a similar problem.
Some of you might say, wow that is a lot of ROMS you've switched to, I'm sure there were more that I missed but that's as of recent. I can install ROMS correctly, I know how to use CWM when installing a .zip and using Odin when it's a .tar(or other supported file extensions). I've factory reset, wiped the cache, the dalvik cache, all before installing a new rom. After installing each rom, I've also factory reset and wiped the cache to make sure no other problems could affect the way the rom would work. Hopefully I did the procedure right, thanks for anyone who's willing to help me!
Right now I am running:
Baseband Version:
T769UVLH5
Kernel Version:
3.0.8-perf-T769UVLH5-CL990184
[email protected] #1
SMP PREEMPT Fri Aug 17 15:12:14 KST 2012
Android Version:
4.0.4
Another Issue is that I can't even transfer files to and from my phone when connected to my computer! This is another big issue, here are some images:
http :// i.imgur.com/xx699ss.png
http :// i.imgur.com/1wRzJpX.png
Here's what happens when I turn Wi-Fi Calling on but maybe it's just a built-in function that I forgot it had and it's probably normal:
http :// i.imgur.com/cTSqRci.png
By the way, sorry for the links just copy and paste them in a browser to and remove the spaces between the http :// and i.imgur, thanks! Unfortunately, I can't post links until I reach 10 posts. If the links don't work for you, I've also provided attachments.
Many thanks!!!
That last picture does show the proper function of Wi-Fi calling however I don't know what to say about the rest of your problems.
Sent from my SAMSUNG-SGH-T769 using XDA Free mobile app
There are two things I would recommend trying...
1. Use Blackhole System Wipe
I know you've been following all the proper steps in CWM (and I would say to keep doing so), but I've added using Blackhole, in addition to the first steps, and I always get great system performance on my phone, and my parent's phones (I put them on ProvisionMod after stock was being stupid). It works well for pre installation for ANY ROM and helps prevent pesky issues. However, chances are, your issue is baseband related and this probably won't solve it... But still! You never know! It's worth a shot!
2. Reroot your phone
I know this will be annoying and pesky... but sometimes the process goes wrong from the beginning and starts giving issues later on... When I first rooted my mom's blaze, something went wrong, despite my following all the directions, and one of her partitions was completely disabled, no matter the ROM. I redid the process of rooting her phone (not from GB though... From the ICS stock) and fixed the issue instantly! I would try these two steps first and see if they do anything! Good luck!
Sent from The Doctor's Blaze