A little while ago, I'm not really sure when but my Wifi stopped working. If I tried to enable it, it would just grey out and look like it was enabling but eventually just returned to not on. I've tried flashing new kernals, new roms, new modems, and currently sitting on stock 2.3.4. I've factory reset, (without wiping sdcard data) on stock. Tried to see if there was an update (saw a post that had said if you update to 2.3.6 over the air it will fix wifi, however no such update exists) I've searched and searched and searched and I cannot seem to find any information regarding whats wrong or how to fix this.
Any input would be greatly appreciated, thank you.
It may be hardware failure. The normal test for hardware/firmware issues is to flash back to stock. You have tried everything that I would suggest for such an issue, except perhaps flashing the latest stock. However, wifi works on all stock versions, so... your troubleshooting steps point to likely hardware failure.
Actually, there is one more step I can suggest. Install a custom kernel, and re-format everything, including USB memory (internal sd card- be sure to back up anything you don't want to lose) and remove any external card. Mr-cook has some scripts that can make the process easier. This is a little more thorough than just erasing the data from the partitions. Then install the stock firmware, preferably the latest stock UCMD8.
creepyncrawly said:
It may be hardware failure. The normal test for hardware/firmware issues is to flash back to stock. You have tried everything that I would suggest for such an issue, except perhaps flashing the latest stock. However, wifi works on all stock versions, so... your troubleshooting steps point to likely hardware failure.
Actually, there is one more step I can suggest. Install a custom kernel, and re-format everything, including USB memory (internal sd card- be sure to back up anything you don't want to lose) and remove any external card. Mr-cook has some scripts that can make the process easier. This is a little more thorough than just erasing the data from the partitions. Then install the stock firmware, preferably the latest stock UCMD8.
Click to expand...
Click to collapse
Which of those scripts do you suggest using?
killerxtreme said:
Which of those scripts do you suggest using?
Click to expand...
Click to collapse
Hopefully, you have a basic understanding of memory partitioning. It is best to understand what you are doing, and not just follow someone else's recipe. That being said, you can use the first one, cook's rom wipe, which will format the system, preload, data, and cache partitions. If you also want to format the USB memory, you will need to do that from within recovery of the custom kernel: from the "mounts and storage" option, select "format /sdcard".
For installing the stock firmware, Odin3 v1.85 is recommended. Download the file from the Download Repository, extract the .tar.md5 file, and put that in the pda slot.
I actually have narrowed it down to a hardware issue, apparently I have the battery leaking issue. I've removed the corroded battery, and cleaned up the area which was effected. The phone still operates, however I still do not have Wifi. Is there something I can do to further fix the issue? I am missing a few tiny resistors in that area could they missing be the issue? I heard they just filtered the signal or something along those lines. What can I check or do before finally just needing a new mainboard.
killerxtreme said:
I actually have narrowed it down to a hardware issue, apparently I have the battery leaking issue. I've removed the corroded battery, and cleaned up the area which was effected. The phone still operates, however I still do not have Wifi. Is there something I can do to further fix the issue? I am missing a few tiny resistors in that area could they missing be the issue? I heard they just filtered the signal or something along those lines. What can I check or do before finally just needing a new mainboard.
Click to expand...
Click to collapse
I bought a phone cheap from the Swappa boneyard with a good screen but with the wifi not working to go with another phone I acquired which had a cracked screen but fully working main board. I combined the two into a fully working phone, and a phone with cracked screen and no wifi. The second phone sat in a box for a long time. Not too long ago, I read about the battery leaking issue, so I pulled that second phone apart and looked at the main board. Sure enough, the battery and the area around it was corroded. The phone was fully functioning except for the wifi.
I didn't play with it too much, but it looked to me like the battery was soldered onto the main board. Did you have to de-solder it to get it off? I believe that the battery is necessary for the wifi to work. I build electronics, but not on the miniature scale of a phone pcb. I have a professional soldering station, but I wouldn't attempt to work on a board like that myself. Unless you have the right equipment, and the experience to go with it...
I think you would need to replace the main board. You could try buying a phone with a broken screen that is otherwise working. It might be fairly cheap. But the I777 is getting old enough that it will be experiencing various kinds of failure, so it is a crap shoot.
I gave my original I777 to my wife, and bought one for myself on swappa over a year ago. The one I bought just went dark one day a few months ago. I don't know what part failed, but it was completely non-responsive, a true brick. My son had an I777 also, and he had cracked the screen, so I bought him an S4 for Christmas. I got his i777 and combined the main board with the good screen from my dead phone, to make a fully functioning phone. After setting that phone up and using it for a couple of weeks, one day the power switch failed. I'm still using that phone as my main phone, with gravity screen to overcome the failed power button, since I don't want to spend another $40 on it to get the power button replaced. The point of relating this is just to show how likely failures are.
Actually I just pulled it off, and cleaned the area. I've been reading that its suppose to keep the date and time, and I've also read that people don't actually know what its for. However I do know that since i pulled it my phone seems to heat up less. (It was getting rather hot) However wifi still does not work.
Related
Okay I am looking at getting an HD2 used from a gentleman who says he's been having problems with it sticking on the "T-Mobile screen," which I'm assuming is the infamous "Stick Together" screen. From my knowledge he hasn't unlocked or rooted the phone or anything. Would flashing Android on it resolve the issue? I've dug through all the Q&A threads and used the search engine too but I didn't find any threads that were very helpful. Please help?
depends what he did, if he was playing around and task 29'd for instance, that would cause such symptoms, and can be resolved easily, but there are a ton of other, far less fixable causes too.
best thing, get the 3,14 t mobile rom from t-mobile.com, and flash it from sd card, (4gb or smaller, look up sd card flashing) if the flash takes and the phone boots, lovely, if it doesnt, stay away.
Okay I'll keep that in mind, he said something along the lines of it been stuck there. Like it doesn't progress at all. So if that's the case (I'm not a noob with roms and the like only with the HD2) would it still be flashable because I will have to set it up to be flashable period.
heh, theres the rub, you wont know till you try, it could be a corrupted flash that a new flash solves, it could be task29 left an empty OS, it could be a corrupted radio (more severe, not always fixable) it could be a hardware fault (overheating can cause same symptoms) stuck/unchangeable spl/radio will do this too, where flashing appears to happen but the phone sticks there, amd teh radio/spl didnt change, again, not always (very rarely, in fact,) fixable, its not an easy one to diagnose without seeing the results of a few flashes.
If you can, flash its stock rom from sd card(4gb or smaller, bigger cards wont work), that will be the big test, until that happens its all guesswork. You deff shouldnt hand over a fat wad of bills until such time.
So, I've been jumping back and forth between Atrix CM9 and CM7 roms and running the .36p radio. Yesterday on CM9, i started getting a large amounts of random reboots and finally got things settled by doing a factory reset in CWM and flashing a clean cm9 rom. However, whenever I turned on wifi, the phone would crash and reboot to the Dual Core logo. I tried flashing another CM9 rom and it didn't crash, but the wifi radio would never seem to pick up any AP's (i'm at home).
I've gone as far as changing to the .37p radio and going back to cm7 to no avail... I'm a bit worried I might have "fried" the wifi radio on the phone.
Did you do a full wipe? Use fastboot to wipe properly before flashing any ROM. Plenty of threads with instructions.
Sent from my MB860 using xda premium
Looking at the fast boot command, I'm not sure how that does anything different then the clockwork mod wipe... but I will give it a shot.
Sent from my NookColor using xda premium
Sorry, but your wifi/bluetooth card is dead. My Atrix got the exact same symptoms a few days ago. Both WiFi and bluetooth are on the same chip. When the system tries to reference them, it fails to locate the hardware and crashes/reboots.
In fact, in researching this topic, I found dozens of threads about this. We should make a sticky about it at this point. Best Buy was kind enough to take back my phone (unlocked bootloader, rooted, cwm, custom fonts, startup, etc.) if I restored it all to stock. If you want Motorola/AT&T/the store you purchased it at to not void your warranty, you should flash the 2.3.6 SBF. Just be cautious and read all about it. But that is the only way that Motorola will service a modded phone
xandr115 said:
Looking at the fast boot command, I'm not sure how that does anything different then the clockwork mod wipe... but I will give it a shot.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Nothing like the same. Clockwork wipe only does data and cache. You erase boot, system, preinstall, cache, user, webtop, etc., via fastboot. I've posted the procedure probably more than 20 times before.
Sent from my MB860 using xda premium
Yeah unfortunately even after a fastboot wipe, the phone's bluetooth and wifi were gone. I was also over the year warranty. Luckily, I picked up a barely used one on Craigslist and restored my backup to it. Now i've got an expensive battery charger (and spare phone should i need it).
If there were any tips you'd have on restoring to a new phone? I've restored my phone a lot and worked on a lot of android phones (I work at a repair shop), but I've never restored data/settings from one phone to another. Of course its the same model, but I can only imagine the issues that could arise out of such an operation
Thanks!
I just made sure I did a fastboot full wipe of the new phone, then placed my clockworkmod directory on the internal (external should be ok too) storage and did a restore. After the restore, I re-flashed the latest version of the rom I was running on top of it with Google apps and it booted fine. Afterwards, I made sure to do a permissions repair and reboot.
Yeah, it seems like a lot of people are having this problem. Like me for example :[
So far there is no solution that I'm aware of, after trying practically everything I could think of and find on the internet... I'm pretty sure it's hardware related. I bet the phone just isn't very high quality. How much did it cost again? $600? + all of the dumb accessories for it. Normally when you see a pattern of failures you would call it a design flaw, but apparently when it comes to expensive electronics they call it out of warranty.
xandr115 said:
So, I've been jumping back and forth between Atrix CM9 and CM7 roms and running the .36p radio. Yesterday on CM9, i started getting a large amounts of random reboots and finally got things settled by doing a factory reset in CWM and flashing a clean cm9 rom. However, whenever I turned on wifi, the phone would crash and reboot to the Dual Core logo. I tried flashing another CM9 rom and it didn't crash, but the wifi radio would never seem to pick up any AP's (i'm at home).
I've gone as far as changing to the .37p radio and going back to cm7 to no avail... I'm a bit worried I might have "fried" the wifi radio on the phone.
Click to expand...
Click to collapse
did your wifi
For anyone interested, here is a supposed solution to the problem:
http://www.youtube.com/watch?v=SYz_RiuFVRk
It will require you to open the phone up, and solder the "wifi battery" into place. I'm not sure what the hell that thing is, but that guy in the video called it a battery. Voids warranty etc. Good luck.
cafe. said:
For anyone interested, here is a supposed solution to the problem:
http://www.youtube.com/watch?v=SYz_RiuFVRk
It will require you to open the phone up, and solder the "wifi battery" into place. I'm not sure what the hell that thing is, but that guy in the video called it a battery. Voids warranty etc. Good luck.
Click to expand...
Click to collapse
I'd give it a try, if I could understand what exactly he does. It looks like he just pries it up with a screwdriver and then pushes it back down.
Meursau|t said:
I'd give it a try, if I could understand what exactly he does. It looks like he just pries it up with a screwdriver and then pushes it back down.
Click to expand...
Click to collapse
If I ha some solder I might try it
Sent from my NookColor using xda premium
Hi all,
I recently bought an i9100 GS2 from a friend for a really cheap price. $100AU. He works for a telco and hence gets phones given to him to trial. The phone was not previously used often as he used his iPhone instead. So essentially it has been sitting around unused for close to 2 years.
My issue is: The phone tends to shut down and become totally unresponsive at random times. When this occurs, it requires the battery to be pulled in order to restart the device. The phone is also really hot at this point in time. It generally occurs when the device is on charge, however it has also happened when the device has simply been left on standby.
I have purchased a new battery (2013 stock) in order to replace the original (2011 stock) however this has not fixed the problem. The phone is also rooted with ThinkingBridge ROM (Stable 1) installed.
Does anyone have any ideas? Is there an app to track and pinpoint the cause?
Thanks.
Sent from my GT-I9100 using xda app-developers app
Clean the battery contacts in the phone with isopropyl alcohol on a cotton bud, could also be symptomatic of the USB/charging circuitry (which the battery/connections is part of) on the way out as well. Is it an original Samsung battery (Tho many people have no problems with 'el cheapo' batteries, a lot do) ?
After cleaning the contacts, do a clean install of stock to see if the issue persists to rule in/out a rom/firmware issue.
If it does persist on stock, it's probably the 2nd thing I mentioned. If that's the case, you may be able to swap the relevant board out with one from a donor phone with a broken screen (this is what you'd do to replace a motherboard, I'm assuming you can do the same with the USB board), or you can send it to a service centre. Or even a local mobile shop may be able to diagnose & repair.
But if that problem persists on a clean stock install w/new genuine battery, my money is on a hardware issue.
MistahBungle said:
Clean the battery contacts in the phone with isopropyl alcohol on a cotton bud, could also be symptomatic of the USB/charging circuitry (which the battery/connections is part of) on the way out as well. Is it an original Samsung battery (Tho many people have no problems with 'el cheapo' batteries, a lot do) ?
After cleaning the contacts, do a clean install of stock to see if the issue persists to rule in/out a rom/firmware issue.
If it does persist on stock, it's probably the 2nd thing I mentioned. If that's the case, you may be able to swap the relevant board out with one from a donor phone with a broken screen (this is what you'd do to replace a motherboard, I'm assuming you can do the same with the USB board), or you can send it to a service centre. Or even a local mobile shop may be able to diagnose & repair.
But if that problem persists on a clean stock install w/new genuine battery, my money is on a hardware issue.
Click to expand...
Click to collapse
Thanks for such a prompt and thorough reply!
I've cleaned the battery contacts on the phone, and the battery to be sure. It is an original Samsung battery so should be no problems there.
With an install of the stock ROM, am I able to root the phone to allow myself the freedom to restore data for apps etc etc...? Would you recommend doing a clean install of the latest stock ROM found here?
Not too keen on trying to fix it if it's broken. May just sell up and get a GS3.
Cheers!
Yep a rom from that thread will be fine. Yes, reinstall/restore your apps & what not; just trying to ascertain if there's something funky in the rom/kernel you're currently using causing the issue or not.
You're welcome Let us know how you get on after you've done that.
MistahBungle said:
Yep a rom from that thread will be fine. Yes, reinstall/restore your apps & what not; just trying to ascertain if there's something funky in the rom/kernel you're currently using causing the issue or not.
You're welcome Let us know how you get on after you've done that.
Click to expand...
Click to collapse
If it makes any difference, it has occurred on multiple custom ROM/kernel combinations...Hopefully the clean with isopropyl alcohol solves the situation!
That sounds ominous (and not in a good way) in that case.
Hello every-xdadeveloper-one~ here i would like to ask questions about my S2 GT-i9100g
My phone is dead. No download mode, recovery mode, usb connection, odin recognition, kies detection, charging, turning on, nada. Meaning in whatever it is, it is not responding to anything.
I would like to ask some professional help here in xda; what has happened to my phone? Is it the emmc? power supply failure? or anything related to it? i really need to know any related things that i'll be dealing with before going to the last step, service repair. it is working fine, i have rooted, unrooted, cyanogenmod and stock, cwm and stock, but none of this has given any problems until one day when it is charging, it suddenly turned off forever.
Please tell me any related things of what has happened.
note: i used a few PIT files when flashing before this, and i'm not sure which is which for the mobo. and few months back before the s2 is totally dead, it keeps on turning off by itself even when full battery, but still workable.
Probably the EMMC, but without having the phone in front of us with the tools to diagnose it, nobody here can tell you this for certain. Fix will be motherboard replacement (assuming you intend to keep this phone & not get a new one).
Take it to a Samsung service centre (more expensive option), or source a 2nd hand motherboard online & either swap the boards yourself, or pay a local mobile repair shop to do it (cheaper option).
Well i just bought a phone from amazon and got it monday it had half battery when i got it so i put it on the charger A hour later it was dead so dead that it wont even charge i tryed diffeent plugs different chargers still nothing what could it be ???
^^^
What model; I.E sticker on the phone chassis under the battery, what does it say ?
I guess it is :crying: Heard there is a workaround that maybe the balls beneath the emmc is like problematic? Maybe i need to reheat it a few seconds and cool it instantly to MAYBE get it able to turn back on? Changing a new board is not an option as important work flowcharts are in the internal storage. I guess service repair of the emmc is needed. Hmmm.
Is it possible that wrong PIT files be the culprit that made all this?
You won't be recovering any data regardless of how you proceed.
You can't 'repair' the EMMC, and it's not feasible to just replace the EMMC (and even if it was, your stuff is on there which means you lose it anyway), replacement of the board is how you proceed. Even if it was possible to replace just the EMMC, you'd probably end up paying 3-4 times the cost of having the entire board replaced due to the cost of labour (swapping a board takes 10 minutes).
If a PIT was the problem, the problem would have occurred immediately after the PIT flash I.E you would have flashed the PIT, and the phone wouldn't have booted immediately after. It's a simple case of component failure, which happens with all electronics all the time. I'm always surprised by how people on here seem to find this incredible. Stuff breaks, simple really.
The only possible very rough chance you have of recovering any data is a company who specialises in recovery of data from dead HDD's, they may be able to help, though very unlikely. If they are able to help, expect this to be very expensive. I have not seen a single post from anyone who has contacted one of these companies & been able to recover data from a phone in this state in the over 2 yrs I've been here.
Thank you for the info. Now i guess the only choice to do, is to repair(replace the mobo), or go buy a brand new s2(or higher models). I will check if there is any way to retrieve the data inside, and i dont mind the cost. :good:
My Amaze was connected via USB to my Ubuntu laptop and I was testing a game I was working on. Suddenly, my computer could not recognize my device and, my device and charging light was off (the battery was at ~94%). I have 3 batteries, and none of them work when trying to power on the device. My device was S-OFF, SuperCID, rooted, and running Android Revolution ROM HD. I was using a Samsung cable if that makes a difference. I tried booting with Power+Vol. Down but that did not work. I figure it is a hardware problem, but it seems odd that it would do this all of a sudden. Can anybody confirm what is wrong with it, and maybe a possible fix? Thanks!
Edit: I get the QHUSB_DLOAD driver message.
Anyone? Please help!
Sorry, your phone is almost bricked. Flash chip bug makes large chunks of the entire flash unreadable. It's more likely to happen if you issue a trim command or format a partition in the wrong way. (Well, it's the right way for flash, but our chip can get borked.) Mine just happened when I was copying a bunch of data over.
You corrupted something fairly early in the boot process but not the earliest thing. Search for fixes for the qhusb and you'll find a couple things. They didn't work for me, but might for you. Even if you fix it, it might re-brick itself after a bit of usage.
ezdi said:
Sorry, your phone is almost bricked. Flash chip bug makes large chunks of the entire flash unreadable. It's more likely to happen if you issue a trim command or format a partition in the wrong way. (Well, it's the right way for flash, but our chip can get borked.) Mine just happened when I was copying a bunch of data over.
You corrupted something fairly early in the boot process but not the earliest thing. Search for fixes for the qhusb and you'll find a couple things. They didn't work for me, but might for you. Even if you fix it, it might re-brick itself after a bit of usage.
Click to expand...
Click to collapse
Thank you for your response! You logic seems to be correct as I wasn't messing with any critical files. Please update your post if you find a solution!
Did you find the post(s) I was talking about? They may work for you. It basically involves trying to rewrite the bootloader.
I ended up punting and trying to desolder the MMC chip so I could try to get my data off it. Unfortunately, it's epoxied on so it got very damaged even though I was using a pretty good hot-air reflow station, so I haven't tried soldering it to a SD-card reader.
ezdi said:
Did you find the post(s) I was talking about? They may work for you. It basically involves trying to rewrite the bootloader.
I ended up punting and trying to desolder the MMC chip so I could try to get my data off it. Unfortunately, it's epoxied on so it got very damaged even though I was using a pretty good hot-air reflow station, so I haven't tried soldering it to a SD-card reader.
Click to expand...
Click to collapse
I have tried that numerous times to rewrite the bootloader, but to no avail. Can you post a picture, and do you think a JTAG would work?
cowboy1995 said:
I have tried that numerous times to rewrite the bootloader, but to no avail. Can you post a picture, and do you think a JTAG would work?
Click to expand...
Click to collapse
Picture of the board? I think I have it around somewhere. If I can find it, sure.
In theory it should work, but I don't think anyone has publicly mapped out the pins for it and I didn't feel like trying to figure out the software side of things to connect it to the generic JTAG adapters I have access to. It's possible that one of the phone-centric JTAG makers has an adapter board, but I'm not willing to spend $bank on a phone worth barely anything.