Database Users

Phone bricked?

So while i was at work today, I was just browsing through twitter on my phone and randomly it force closes, so I tried to reopen the app and it forces closes again and im like . So I thinking of just going to the market, uninstall and reinstall, when i opened market it force closed. Basically everything i opened force closed and so i was like ok ill just reboot.
After the phone turned off, it just stayed off, I cant turn it on, it won't charge(well it might but the led is not lighting up), nothing is working. Though when i do plug it into my computer my computer recognizes it but fails to install any drivers.
Any suggestions on what I could do from this point? Thanks in advance.

what rom were you on?

Try taking the battery out for like 10 minutes and put it back in. Never happened to me, but I have read posts where this has worked.

saranhai said:
what rom were you on?
Click to expand...
Click to collapse
Faux's AOSP Rom
lowandbehold said:
Try taking the battery out for like 10 minutes and put it back in. Never happened to me, but I have read posts where this has worked.
Click to expand...
Click to collapse
Ill try it.

what was the root method you used?
also.. if you do.. do you know what your eMMC chip was?
sorry for all the questions

saranhai said:
what was the root method you used?
also.. if you do.. do you know what your eMMC chip was?
sorry for all the questions
Click to expand...
Click to collapse
Tbh i forgot, I had this phone since it first came out, so whatever the first root method was, was the one i used. no idea what the emmc chip is.

Sounds like a failed emmc, if you can get adb to recognize it check it. But random fcs followed by no boot definitely sounds like a failed emmc.
Sent from my HTC Glacier

Nicgraner said:
Sounds like a failed emmc, if you can get adb to recognize it check it. But random fcs followed by no boot definitely sounds like a failed emmc.
Sent from my HTC Glacier
Click to expand...
Click to collapse
how exactly do i check an emmc?

tonyriceroni said:
how exactly do i check an emmc?
Click to expand...
Click to collapse
if you can't go into the OS, then go into recovery,
use adb and type
Code:
adb shell
cat /proc/kmsg | grep mmc0

I wouldn't worry so much about the emmc. I think that's a prob with newer phones(might be wrong on this). None the less this seems to have different symptoms. Your biggest concern is getting into recovery.
Can you boot into the bootloader?
If so do you have the Eng spl?
Use either that or adb to boot in to recovery
Adb reboot recovery
Fastboot reboot recovery
If neither of those work but you can boot into the bootlader try running the PD15IMG.zip
It will reset the phone and you will have to reroot but atleast you have your phone back. Let me know if any of this works please. If not we can go from there

He said his phone won't turn on at all. I don't recall that being a symptom of the failed eMMc chip. Probably a good thing though, will make getting a replacement less of a headache.

lowandbehold said:
He said his phone won't turn on at all. I don't recall that being a symptom of the failed eMMc chip. Probably a good thing though, will make getting a replacement less of a headache.
Click to expand...
Click to collapse
I know I'm hoping he just forgot about hboot
Sent from my HTC Glacier using XDA Premium App

Yeah I can't access recovery at all. I can't get my computer to recognize the phone through adb either. Im just going to call tmobile and see what i can do

So random update, I gave HTC a call and they gave me a RMA # to send to them to check the phone out. So sent it in(bout a week and a half ago) and they told me they would call me after they found out what the problem was and discuss cost of repairs. So today I wake up to find my phone at my door and everything is working again. No idea if they are going to charge me or not but this is how i fixed my problem lol.
I also purchased a SGS4G for the time being and am loving it. Now I don't which phone to keep X.X

If they sent it back without a call then your only out the shipping to them. Done 2 now, both were that way.
tonyriceroni said:
So random update, I gave HTC a call and they gave me a RMA # to send to them to check the phone out. So sent it in(bout a week and a half ago) and they told me they would call me after they found out what the problem was and discuss cost of repairs. So today I wake up to find my phone at my door and everything is working again. No idea if they are going to charge me or not but this is how i fixed my problem lol.
I also purchased a SGS4G for the time being and am loving it. Now I don't which phone to keep X.X
Click to expand...
Click to collapse

Hard bricked and possible hardware issue. I need advice please.

I recently received a used epic 4g when a friend replaced his phone, all was good but then yesterday the phone froze. I took the battery out and powered it back on it then took a long time to boot (2 minutes+) and once it finally did boot it was unusable and very unresponsive. I looked online and got into restore mode and then encountered a problem, my buttons at the bottom don't work therefore I could not hit the home button to select an option.
So I then used Odin to restore it (Used stock stuff). After I restored it it was working fine again. Then today i dropped it 2 feet off my bed and it went back to booting slow and then being unresponsive once booted. I then tried to restore it with Odin again but I made a mistake and didn't put the PDA file in and now my phone seems to be hard bricked (noob move I know).
I am considering sending it in for JTAG but I have some questions. Do you guys think the SLOW booting and unresponsive once booted issues were hardware issues? Will it just do that again eventually after I pay for it to be JTAG fixed? Also do you think they would be able to fix the buttons at the bottom? I would appreciate any advice.
Also please don't kick me when I am down, I know not double checking my Odin stuff was a dumb move, that's not what this thread is about.

So to just be sure, you can't power it on at all? The slow booting seems like a ROM problem. If you can get into Download mode you can fix it. If not, then you are definitely bricked and need to take it in.
If you could though, just reodin the proper files WITHOUT rushing.
I've dropped my phone everyday (I've even found out gorilla glass is ass since it cracked) but its always booted unless I did some dumb **** to it.
Sent from my SPH-D700 using xda premium

A_Flying_Fox said:
So to just be sure, you can't power it on at all? The slow booting seems like a ROM problem. If you can get into Download mode you can fix it. If not, then you are definitely bricked and need to take it in.
If you could though, just reodin the proper files WITHOUT rushing.
I've dropped my phone everyday (I've even found out gorilla glass is ass since it cracked) but its always booted unless I did some dumb **** to it.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Thanks for the reply
Correct I can't get it to power on at all. A second opinion on whether or not there was a hardware issue would nice, it just seems odd to me that the exact same thing would happen again a day later. When I bricked it I accidentally only used a pit file. When I did it right the first time I followed a guide and had a pit file and a PDA file, I assume one of those is(or includes) the ROM but I don't really know a lot about this stuff. I am considering just selling this one on ebay as-is if you guys think its a hardware issue and getting a new phone but if not I'll send it to be fixed.

JoeCow said:
Thanks for the reply
Correct I can't get it to power on at all. A second opinion on whether or not there was a hardware issue would nice, it just seems odd to me that the exact same thing would happen again a day later. When I bricked it I only had a pit file. When I did it right the first time I followed a guide and had a pit file and a PDA file, I assume one of those is(or includes) the ROM but I don't really know a lot about this stuff. I am considering just selling this one on ebay as-is if you guys think its a hardware issue and getting a new phone but if not I'll send it to be fixed.
Click to expand...
Click to collapse
try removing the battery. then try to get into download mode with it plugged into the computer only no battery also remove sd card.

tazfanatic said:
try removing the battery. then try to get into download mode with it plugged into the computer only no battery also remove sd card.
Click to expand...
Click to collapse
Thanks!! that did it. I had actually already tried that but tried it again when you suggested it I couldn't get it initially but kept trying and eventually tried unplugging it and plugging it back in while holding one and power the whole time and that got it. So was the slow boot thing happening twice just unlucky or is there something else I need to root or whatever?

JoeCow said:
Thanks!! that did it. I had actually already tried that but tried it again when you suggested it I couldn't get it initially but kept trying and eventually tried unplugging it and plugging it back in while holding one and power the whole time and that got it. So was the slow boot thing happening twice just unlucky or is there something else I need to root or whatever?
Click to expand...
Click to collapse
My guess is the slow booting was data corruption. A clean install should fix that. After Odining in the stock EL30 run it like that for a few days to see how it is working before looking into rooting it and a custom ROM.
Sent from my SPH-D700 using xda premium

kennyglass123 said:
My guess is the slow booting was data corruption. A clean install should fix that. After Odining in the stock EL30 run it like that for a few days to see how it is working before looking into rooting it and a custom ROM.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
what kenny said

Thanks guys, saved me $50s should i have sent it in. I appreciate it. I watched a few of the videos on rooting it and I saw the recovery program used to root things lets you use the camera button as apposed to the home button for selecting things. Think I should switch to that since my bottom buttons are broken? It looked like I probably wouldn't be able to navigate back in menus after selecting something but that would be better then not being able to select anything.

JoeCow said:
Thanks guys, saved me $50s should i have sent it in. I appreciate it. I watched a few of the videos on rooting it and I saw the recovery program used to root things lets you use the camera button as apposed to the home button for selecting things. Think I should switch to that since my bottom buttons are broken? It looked like I probably wouldn't be able to navigate back in menus after selecting something but that would be better then not being able to select anything.
Click to expand...
Click to collapse
If they are still broken after a fresh Odin then yes the newer CWM will work fine for you. There are widgets somewhere (don't remember) to add those buttions to your screen once you get it working right.

If the buttons really are toasted there are two fairly good onscreen button apps available. One is called Zmooth and the other is called Button Savior.

Lines across screen/ Hardware problem

My Asus TF300T has been starting to act up lately. When I access the settings menu faint grey lines start to appear which run across the screen. When I change to portrait the lines disappear for a split-second and then reappear black. When accessing Google Play I see the same thing. The power menu and other menus appear to have a pixelated background and are 'blocky'. It also happens in the ASUS File Manager on the white background (faint lines).
I am confused as to what's causing them. It appears to me to be a graphics-related issue as I have taken screenshots and viewed them on my computer and they appear pixelated on the TF300T but not on my computer. I have cold booted and performed a full factory reset. I have also switched to Safe Mode with no change (lines still appearing). I am using the Jelly Bean 4.2 launcher and am stock. The tablet hasn't been dropped and has been protected. It's only 4 months old and I bought it from Argos in the UK.
It's a shame because I like this tablet
Thanks.

mr.fast said:
My Asus TF300T has been starting to act up lately. When I access the settings menu faint grey lines start to appear which run across the screen. When I change to portrait the lines disappear for a split-second and then reappear black. When accessing Google Play I see the same thing. The power menu and other menus appear to have a pixelated background and are 'blocky'. It also happens in the ASUS File Manager on the white background (faint lines).
I am confused as to what's causing them. It appears to me to be a graphics-related issue as I have taken screenshots and viewed them on my computer and they appear pixelated on the TF300T but not on my computer. I have cold booted and performed a full factory reset. I have also switched to Safe Mode with no change (lines still appearing). I am using the Jelly Bean 4.2 launcher and am stock. The tablet hasn't been dropped and has been protected. It's only 4 months old and I bought it from Argos in the UK.
It's a shame because I like this tablet
Thanks.
Click to expand...
Click to collapse
If it were mine I would use App Backup. Be sure to check apps and data and when presented check copy to external sdcard.
Download stock firmware 4.2(10.6.1.8), unzip once and place on internal sdcard. If you don't receive the update notice in three minutes reboot tablet and wait another three. When you get the update notice accept and wait for completion as usual.
Good Luck!
Note: This should help decide whether it is hardware or software.

tobdaryl said:
If it were mine I would use App Backup. Be sure to check apps and data and when presented check copy to external sdcard.
Download stock firmware 4.2(10.6.1.8), unzip once and place on internal sdcard. If you don't receive the update notice in three minutes reboot tablet and wait another three. When you get the update notice accept and wait for completion as usual.
Good Luck!
Note: This should help decide whether it is hardware or software.
Click to expand...
Click to collapse
I am already using that firmware version so it won't work.
Thanks anyway.

mr.fast said:
I am already using that firmware version so it won't work.
Thanks anyway.
Click to expand...
Click to collapse
You can rename it US_epad-user-10.4.4.20 or what ever that previous version of firmware was pretty sure it was that. When update comes up it will say if want to downgrade and accept but it will just reinstall you're current version. Now not sure if your unlocked as when i did this for a random reboot issue i was unlocked but worked for me and acts just like an update everything else should be the same but do backups just to be safe.
Correction thats US_epad-epad-user-10.4.2.20 and us as doesnt have to be that if WW then use that or etc. Hope that works
And as for unlocking may not want to do that as it will void warranty if need to send it in but sure everyone know that.

aerdely said:
You can rename it US_epad-user-10.4.4.20 or what ever that previous version of firmware was pretty sure it was that. When update comes up it will say if want to downgrade and accept but it will just reinstall you're current version. Now not sure if your unlocked as when i did this for a random reboot issue i was unlocked but worked for me and acts just like an update everything else should be the same but do backups just to be safe.
Correction thats US_epad-epad-user-10.4.2.20 and us as doesnt have to be that if WW then use that or etc. Hope that works
And as for unlocking may not want to do that as it will void warranty if need to send it in but sure everyone know that.
Click to expand...
Click to collapse
OK, thanks. Will post back if it works or not. Thanks to the poster above too.

mr.fast said:
OK, thanks. Will post back if it works or not. Thanks to the poster above too.
Click to expand...
Click to collapse
Ok and if nothing else can refer to this thread for touch screen and pcb issues not sure if anyone has had same issue but can read through and ask question because alot seem experience with some of this. Good luck.
http://forum.xda-developers.com/showthread.php?t=2091233

mr.fast said:
I am already using that firmware version so it won't work.
Thanks anyway.
Click to expand...
Click to collapse
It works for me, I have used that method several times including 10.6.1.8 and 10.4.2.20. You can also upgrade and downgrade this way if you have Asus stock recovery.

tobdaryl said:
It works for me, I have used that method several times including 10.6.1.8 and 10.4.2.20. You can also upgrade and downgrade this way if you have Asus stock recovery.
Click to expand...
Click to collapse
I've placed the blob file in the latest firmware's zip folder from the (4.1 )10.4.2.20 firmware in another zip folder on the tablets root storage and nothing. I called the file WW_epaduser_10_4_2_20_UpdateLauncher.zip - any suggestions?

mr.fast said:
I've placed the blob file in the latest firmware's zip folder from the (4.1 )10.4.2.20 firmware in another zip folder on the tablets root storage and nothing. I called the file WW_epaduser_10_4_2_20_UpdateLauncher.zip - any suggestions?
Click to expand...
Click to collapse
Exactly what are you trying to do. All you have to do is raname the latest update zip after download and unzipping once from the 10.6.1.8.zip or cant remember exactly but what ever it is to WW_epad-user-10.4.2.20.zip
That the way most use and seems to work. No need to replace the blob file or etc just renaming the latest update zip to that should work and after maybe sometime either rebooting or waiting couple mins for it to show up in notfication bar. Replaceing the file inside the update zip its self may affect the signature or etc and may not work even if option does come up. Another way after placing on root of sdcard or internal storage which is what i do is just remove and replace the sdcard should pop up right away.
Yea just placing the blob file into a zip folder and naming it that wouldnt work as it checks for signatures atleast unless unlocked but not totally sure on that. Try what i had stated if your trying to downgrade take the 4.1.1 update file and name it WW_epad-user-10.4.2.20.zip or just rename the latest update zip to that works every time for me.
Tell you the truth it does sound more like a hardware problem just reflashing the update is a way to be sure. I'd more in the way of thinking of sending it in for service in your case atleast if you still have warranty i would. I've been through 2 seperat device still get random reboot with this new update tried reflashing couple times etc fixes temporarly but seems to come back almost considering sending to asus my self at this point since have warranty. Usually the best bet.

aerdely said:
Exactly what are you trying to do. All you have to do is raname the latest update zip after download and unzipping once from the 10.6.1.8.zip or cant remember exactly but what ever it is to WW_epad-user-10.4.2.20.zip
That the way most use and seems to work. No need to replace the blob file or etc just renaming the latest update zip to that should work and after maybe sometime either rebooting or waiting couple mins for it to show up in notfication bar. Replaceing the file inside the update zip its self may affect the signature or etc and may not work even if option does come up. Another way after placing on root of sdcard or internal storage which is what i do is just remove and replace the sdcard should pop up right away.
Yea just placing the blob file into a zip folder and naming it that wouldnt work as it checks for signatures atleast unless unlocked but not totally sure on that. Try what i had stated if your trying to downgrade take the 4.1.1 update file and name it WW_epad-user-10.4.2.20.zip or just rename the latest update zip to that works every time for me.
Tell you the truth it does sound more like a hardware problem just reflashing the update is a way to be sure. I'd more in the way of thinking of sending it in for service in your case atleast if you still have warranty i would. I've been through 2 seperat device still get random reboot with this new update tried reflashing couple times etc fixes temporarly but seems to come back almost considering sending to asus my self at this point since have warranty. Usually the best bet.
Click to expand...
Click to collapse
Thanks - It also sounds like a hardware problem to me but it's worth a try. In the UK if you return it within 6 months you may receive a replacement. I could also RMA the tablet.
I'll post back soon.

mr.fast said:
Thanks - It also sounds like a hardware problem to me but it's worth a try. In the UK if you return it within 6 months you may receive a replacement. I could also RMA the tablet.
I'll post back soon.
Click to expand...
Click to collapse
Ok if flashing doesnt work then yes i'd just do a replacement what i did with my original that had problems and only has 30 days but got lucky. Good luck it's worth a try there are some other threads on here on how to do it if can't figure it out but i've used i method i stated couple times and it work for flashing atleast but fix my problem temporarily. If anything else don't be affraid to ask just don't unlock or would most def mess up your chancefor rma atleast if not exchange too.

aerdely said:
Ok if flashing doesnt work then yes i'd just do a replacement what i did with my original that had problems and only has 30 days but got lucky. Good luck it's worth a try there are some other threads on here on how to do it if can't figure it out but i've used i method i stated couple times and it work for flashing atleast but fix my problem temporarily. If anything else don't be affraid to ask just don't unlock or would most def mess up your chancefor rma atleast if not exchange too.
Click to expand...
Click to collapse
Thanks. I'm in the middle of downgrading now.
Hope it works :fingers-crossed:

mr.fast said:
Thanks. I'm in the middle of downgrading now.
Hope it works :fingers-crossed:
Click to expand...
Click to collapse
Good luck also hope it works like said method should just not sure if would fix the problem could be something with your nvidia chip that process' your video sort of what it sounds like to me or something atleast is affecting your video. Like said i posted a link for you with people experiencing these types of problems just give it a read through most replace there lcds and mainboard or digitizers depending on what it is because they have no warranty but they probably would know what the problem is if you asked. As you said you can exchange it i'd just go for that my self.

aerdely said:
Good luck also hope it works like said method should just not sure if would fix the problem could be something with your nvidia chip that process' your video sort of what it sounds like to me or something atleast is affecting your video. Like said i posted a link for you with people experiencing these types of problems just give it a read through most replace there lcds and mainboard or digitizers depending on what it is because they have no warranty but they probably would know what the problem is if you asked. As you said you can exchange it i'd just go for that my self.
Click to expand...
Click to collapse
It didn't fix the problem. Still lines and graphics glitches appearing.
I'll exchange.
Thanks.
I also performed a factory reset after downgrading the tablet which did'nt work...

mr.fast said:
It didn't fix the problem. Still lines and graphics glitches appearing.
I'll exchange.
Thanks.
I also performed a factory reset after downgrading the tablet which did'nt work...
Click to expand...
Click to collapse
Well like said atleast you know now sucks i didn't fix it but didn't sound like it would. Was worth a try. Hope the new one turns up no problems should i was ok after.

Just before I return it to the store tomorrow I am still questioning the cause of the problem. The strange thing is that it doesn't appear on everything. Just on some gradients and backgrounds. Also, Google Now force closes and so does Email. I downgraded but my data was left intact, so I reset the device but the problem still persists.
Just a last final try before it goes back

mr.fast said:
Just before I return it to the store tomorrow I am still questioning the cause of the problem. The strange thing is that it doesn't appear on everything. Just on some gradients and backgrounds. Also, Google Now force closes and so does Email. I downgraded but my data was left intact, so I reset the device but the problem still persists.
Just a last final try before it goes back
Click to expand...
Click to collapse
Tell you the truth I'm not totally sure what the issue can be. It could be a number of thing but in the case of my old tf300 before i exchanged I had what looked like a finger print under the screen. Just sort of a smudge about the size of an eraser head. On black screens where screen was on like as when it starts up or loading an app it would show but since it was light colored It wouldn't show on most others. Not sure if that's the case for you but when I sent it back to Newegg they determined it was a problem with the lcd screen, maybe dead pixels they said.
In your case if you have option to just go to store I'd just do that and save your self the trouble. If other wise bought it online then maybe worth trying to figure out because also in my case Newegg took about a week of testing it before approving the exchange also I should mention there couple other problems with it. Not sure what else you can try if you had already downgraded which in most cases erases everything not sure whynit didn't for you I'm not sure what else to do. One other thing is to try ,aybe holding down the reset butoon on left side of tablet in the hole under the volume buttons. I posted a link earlier on lcd and pcb problem thread maybe you can try to ask some one there, they probably would know more most of them are fermiliar with hardware issues so might be able to tell you if it is or not but as i said might just he easier returning it and start fresh. Good luck and sorry I can't help more.
Just in case theres the harware issues thread again.
http://forum.xda-developers.com/showthread.php?t=2091233

aerdely said:
Tell you the truth I'm not totally sure what the issue can be. It could be a number of thing but in the case of my old tf300 before i exchanged I had what looked like a finger print under the screen. Just sort of a smudge about the size of an eraser head. On black screens where screen was on like as when it starts up or loading an app it would show but since it was light colored It wouldn't show on most others. Not sure if that's the case for you but when I sent it back to Newegg they determined it was a problem with the lcd screen, maybe dead pixels they said.
In your case if you have option to just go to store I'd just do that and save your self the trouble. If other wise bought it online then maybe worth trying to figure out because also in my case Newegg took about a week of testing it before approving the exchange also I should mention there couple other problems with it. Not sure what else you can try if you had already downgraded which in most cases erases everything not sure whynit didn't for you I'm not sure what else to do. One other thing is to try ,aybe holding down the reset butoon on left side of tablet in the hole under the volume buttons. I posted a link earlier on lcd and pcb problem thread maybe you can try to ask some one there, they probably would know more most of them are fermiliar with hardware issues so might be able to tell you if it is or not but as i said might just he easier returning it and start fresh. Good luck and sorry I can't help more.
Just in case theres the harware issues thread again.
http://forum.xda-developers.com/showthread.php?t=2091233
Click to expand...
Click to collapse
Thanks again
I tried the reset hole but the paper clip just goes straight in?

I've just downgraded to 4.1 and the lines disappeared. I then downloaded an OTA for Android 4.2 for the lines to then reappear.
I am about to downgrade again the then download the 4.2 firmware file instead of downloading the update OTA (in case the update file is corrupted).

mr.fast said:
My Asus TF300T has been starting to act up lately. When I access the settings menu faint grey lines start to appear which run across the screen. When I change to portrait the lines disappear for a split-second and then reappear black. When accessing Google Play I see the same thing. The power menu and other menus appear to have a pixelated background and are 'blocky'. It also happens in the ASUS File Manager on the white background (faint lines).
I am confused as to what's causing them. It appears to me to be a graphics-related issue as I have taken screenshots and viewed them on my computer and they appear pixelated on the TF300T but not on my computer. I have cold booted and performed a full factory reset. I have also switched to Safe Mode with no change (lines still appearing). I am using the Jelly Bean 4.2 launcher and am stock. The tablet hasn't been dropped and has been protected. It's only 4 months old and I bought it from Argos in the UK.
It's a shame because I like this tablet
Thanks.
Click to expand...
Click to collapse
You might try hitting it with some circuit cooler (with the cover removed of course) to see if its heat related - an upside down can of liquid air would do it. Problem is, if it is heat related, you need to provide better heat sinking, which likely means ripping your warranty sticker to get access to the IC's underneath the copper heat sink in attempt to provide better heat dissipation with thermal compound or something.
Reseating the video connector to see if its a bad connection is another viable option without creating evidence of tampering and potentially voiding warranty.
Hope this helps.

WiFi wont work...

Hey xda, i just got this used Mytouch 4G and rooted and flashed, etc... but know i notice that my wifi does not turn on at all, it just says turning on..... but it never does, when i was on 2.3.4 it would turn on but would say cannot scan. is there any fix for this? is the wifi just dead? throw the phone away?

symbiiote said:
Hey xda, i just got this used Mytouch 4G and rooted and flashed, etc... but know i notice that my wifi does not turn on at all, it just says turning on..... but it never does, when i was on 2.3.4 it would turn on but would say cannot scan. is there any fix for this? is the wifi just dead? throw the phone away?
Click to expand...
Click to collapse
What ROM are you using. Sometimes its just a kernel problem, I've been testing different kernels with different ROMS, and some of them wont let you turn on wifi. Try a different ROM then.

Hey thanks for the replie, ive used pac rom 4.2.2 and cfx rom 4.2.2

symbiiote said:
Hey thanks for the replie, ive used pac rom 4.2.2 and cfx rom 4.2.2
Click to expand...
Click to collapse
Try a stable-ish rom. Like Dark Unicorn Resurrected --->http://forum.xda-developers.com/showthread.php?t=1716558 (Second Post). Or Synthetic.Nightmare's AOSPX -----> http://forum.xda-developers.com/showthread.php?t=1684835
If that doesn't work try going to a stable GB rom (Like CyanogenMod 7.2.0) If that doesn't work then just donate your phone to someone that could use the parts

I tried cm7 and no go, click on turn wifi on and it reboots... x(
Sent from my A500 using Tapatalk HD

Awwwww man. That sucks. If it won't work on cm7. Then try a GB sense rom. If it doesn't work there. Revert to stock all over again. If it won't work there. Then your screwed man. Hope it works though.
Sent from my myTouch 4g using xda app-developers app

N_otori0us_ said:
What ROM are you using. Sometimes its just a kernel problem, I've been testing different kernels with different ROMS, and some of them wont let you turn on wifi. Try a different ROM then.
Click to expand...
Click to collapse
symbiiote said:
Hey xda, i just got this used Mytouch 4G and rooted and flashed, etc... but know i notice that my wifi does not turn on at all, it just says turning on..... but it never does, when i was on 2.3.4 it would turn on but would say cannot scan. is there any fix for this? is the wifi just dead? throw the phone away?
Click to expand...
Click to collapse
N_otori0us_ said:
Awwwww man. That sucks. If it won't work on cm7. Then try a GB sense rom. If it doesn't work there. Revert to stock all over again. If it won't work there. Then your screwed man. Hope it works though.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
It's not an issue with the ROM, it's an issue stemming from the kernel modules. You'll see this most commonly when a kernel and the subsequent modules weren't compiled together or the modules were compiled against a different kernel version or configuration. If it's always done this out of the box, however, you may have a problem on your hands but that doesn't necessarily mean it isn't still software related; it just makes that likelihood far less.. likely. You said it was used, so it's possible the previous owner screwed up the kernel modules and the kernel. It's not a hard issue to test for, you just need a known working kernel with known working modules. If you'd like, I'll build you a kernel that's mostly stock just so you can eliminate a majority of the suspects but I am only prepared to build kernels for Jellybean based ROMs, which isn't a big deal because most of the ROMs are already 4.2.2. LiquidSmooth is also a good ROM to try, it worked very well off the jump for me. In the event that you find that you still have an issue, certainly don't throw it in the trash. I happen to need a MT4G because my camera button, volume rocker, and the connector on the side with the three contacts that I assume is some sort of dock connector err.. fell off.. I'd advise against disassembling it unless you pay very close attention to the instructions because those three items are attached to the outer casing and if you aren't careful when you remove it then I'll have to make space in the boat because you'll be in the same one I am, haha. If you have any other questions, by all means ask and if I'm incorrect in any of my statements then someone please correct me so that I don't go around giving out bad information out of ignorance, but I'm fairly confident in my statements. You'll find the modules in /system/lib/modules if you care to look but just because it's empty doesn't mean that they aren't simply compiled directly into the kernel as there isn't much reason not to unless it's something that not everyone would use or someone might see fit to change. The firmware for the WLAN, however, will be in /system/firmware/ no matter what and will be something along the lines of bcmdhd.bin or bcm4329.bin

zygh0st said:
It's not an issue with the ROM, it's an issue stemming from the kernel modules. You'll see this most commonly when a kernel and the subsequent modules weren't compiled together or the modules were compiled against a different kernel version or configuration. If it's always done this out of the box, however, you may have a problem on your hands but that doesn't necessarily mean it isn't still software related; it just makes that likelihood far less.. likely. You said it was used, so it's possible the previous owner screwed up the kernel modules and the kernel. It's not a hard issue to test for, you just need a known working kernel with known working modules. If you'd like, I'll build you a kernel that's mostly stock just so you can eliminate a majority of the suspects but I am only prepared to build kernels for Jellybean based ROMs, which isn't a big deal because most of the ROMs are already 4.2.2. LiquidSmooth is also a good ROM to try, it worked very well off the jump for me. In the event that you find that you still have an issue, certainly don't throw it in the trash. I happen to need a MT4G because my camera button, volume rocker, and the connector on the side with the three contacts that I assume is some sort of dock connector err.. fell off.. I'd advise against disassembling it unless you pay very close attention to the instructions because those three items are attached to the outer casing and if you aren't careful when you remove it then I'll have to make space in the boat because you'll be in the same one I am, haha. If you have any other questions, by all means ask and if I'm incorrect in any of my statements then someone please correct me so that I don't go around giving out bad information out of ignorance, but I'm fairly confident in my statements. You'll find the modules in /system/lib/modules if you care to look but just because it's empty doesn't mean that they aren't simply compiled directly into the kernel as there isn't much reason not to unless it's something that not everyone would use or someone might see fit to change. The firmware for the WLAN, however, will be in /system/firmware/ no matter what and will be something along the lines of bcmdhd.bin or bcm4329.bin
Click to expand...
Click to collapse
Wow, thanks for the detailed reply. ill defiantly try this out, ill get back to you. [Update] ive checked and theres no firmware folder in system, and in system/lib/modules there is a bcm4329.ko file. (im on CM7)

Are you interested in a trade? I cant use phone with no Wi-Fi
Sent from my A500 using Tapatalk HD

Fixed my wifi!
symbiiote said:
Are you interested in a trade? I cant use phone with no Wi-Fi
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
Just FYI, I was in the same boat. I bought a used and heavily abused Mytouch 4g just to pull the motherboard and use it to fix my wife's hard bricked (no power whatsover) mytouch. It worked fine for a day or so, then started having random reboots and wifi failure (i.e. on the stock ROM it would cycle on & off repeatedly, then reboot, and on CM7 it would just not turn on, or occasionally show 'error' if I forced the driver to load.
I tried everything: rooting and installing multiple ROMs, multiple kernels, flashing to stock unrooted, flashing to stock Froyo unrooted, and it never resolved. In the dmesg I would get an error "dhsdsio_probe_attach: si_attach failed!" every time I tried to enable wifi. I even tried different radios, not really expecting much, but just to cover my bases. I took the phone apart multiple times looking for loose cables, damaged ribbons, etc, but never found anything, although occasionally wifi would return for a few hours, then disappear again. Often it came back right after flashing a new rom or factory reset, but even without installing any apps, it would eventually fail, so it wasn't an app issue.
Then... I discovered another thread where people with the Motorola Atrix discovered that a well placed piece of plastic would resolve their failing wifi by applying pressure in just the right spot - most likely due to a loose or failing solder connection. I dug around online and found a photo showing exactly where the Broadcom 4329 chip is in our phones (it is right behind the microphone on the underside of the motherboard), and discovered that by squeezing hard with one finger just to the left of the trackpad, and the other directly behind on the back of the phone, I could get wifi to enable and scan. Letting go would drop the scan. Give that a shot and see if it makes a difference. If so, read on...
I found that people with iPhones with a failed Broadcom 4329 module (same chip) had had some success in reflowing the motherboard. Not having any expertise in that area, I was surprised to find that a common solution was to use an oven to heat the motherboard up in order to soften the solder and do a poor-man's "reflow". I can't post links yet, but if you google "iphone WiFi Repair: Oven Fix" you'll find a great video describing how to to it and why it works.
So I went for it. I took it apart one last time (plenty of take apart videos online to show how this is done), pulled out just the motherboard, stripped everything off that wasn't permanently attached (including removing/unlatching the metal covers on front & back & all ribbons), got a cookie sheet and some aluminum foil, put the foil loosely around the rest of the motherboard (shiny side out) and ripped an opening just around the chip. Then raised the mother board off of the cookie sheet with little foil balls (per instructions online for laptop reflowing) and baked at 360 for 8 minutes, shutting off the heat and cracking the oven door slightly for 20 minutes to cool it slowly, then open all the way for another 20 minutes, out, reassembled, and now I have a working wifi chip.
Crazy, yes, but if you are about to toss the phone, it might be worth a shot as a last resort. Not a 100% success rate when you search online for people trying this, some people have destroyed their phones, but it worked for me!
Keep in mind, I just did this about 2 hours ago, so there's still the possibility it was a short-lived solution. I will try to check back in here in a week or two to confirm that it 'took'.
UPDATE 1: One day later, and zero reboots, 100% reliable wifi. It has never been so stable.

zygh0st said:
It's not an issue with the ROM, it's an issue stemming from the kernel modules. You'll see this most commonly when a kernel and the subsequent modules weren't compiled together or the modules were compiled against a different kernel version or configuration. If it's always done this out of the box, however, you may have a problem on your hands but that doesn't necessarily mean it isn't still software related; it just makes that likelihood far less.. likely. You said it was used, so it's possible the previous owner screwed up the kernel modules and the kernel. It's not a hard issue to test for, you just need a known working kernel with known working modules. If you'd like, I'll build you a kernel that's mostly stock just so you can eliminate a majority of the suspects but I am only prepared to build kernels for Jellybean based ROMs, which isn't a big deal because most of the ROMs are already 4.2.2. LiquidSmooth is also a good ROM to try, it worked very well off the jump for me. In the event that you find that you still have an issue, certainly don't throw it in the trash. I happen to need a MT4G because my camera button, volume rocker, and the connector on the side with the three contacts that I assume is some sort of dock connector err.. fell off.. I'd advise against disassembling it unless you pay very close attention to the instructions because those three items are attached to the outer casing and if you aren't careful when you remove it then I'll have to make space in the boat because you'll be in the same one I am, haha. If you have any other questions, by all means ask and if I'm incorrect in any of my statements then someone please correct me so that I don't go around giving out bad information out of ignorance, but I'm fairly confident in my statements. You'll find the modules in /system/lib/modules if you care to look but just because it's empty doesn't mean that they aren't simply compiled directly into the kernel as there isn't much reason not to unless it's something that not everyone would use or someone might see fit to change. The firmware for the WLAN, however, will be in /system/firmware/ no matter what and will be something along the lines of bcmdhd.bin or bcm4329.bin
Click to expand...
Click to collapse
I think WiFi should have worked on cyanogen7 or a sense Rom....
That's why I figured it was a hardware problems.
Also can you compile kernels for me? I don't know How to properly. :'(
Sent from my HTC Glacier

A little more info in case it helps anyone diagnose a different issue, below were some handy-dandy commands I used to check the driver situation:
Try to turn on wifi (obviously it will fail)
Then in terminal emulator (download one from the play store if not installed), type
$ lsmod
if nothing is returned, the driver isn't loaded. If you get "bcm4329" listed as 'live', then your driver is loaded. Its probably not a driver compatibility problem (not 100% on that, since I'm new to all of this).
If your driver isn't loading, it still might not be a bad driver. It might just have been because the chip wasn't detected. Type the following to give permissions and manually load the bcm4329 driver:
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
# insmod /system/lib/modules/bcm4329.ko
if it returns an error/fail, you've got the wrong bcm4329.ko file/driver installed or maybe a corrupted file. Try reflashing the ROM, or replacing the bcm4329.ko file with one that is compatible with the ROM/kernel you are using.
If not, then
# exit
then check again with
$ lsmod
If the driver shows up now, then at least you know it can load. Then try connecting again. If it still doesn't connect, this might help the process of elimination.
go back to terminal emulator immediately after trying to connect
type in dmesg
scroll up a little ways and look for the a series of phrases 'wifi_set_power: 1', etc. If you see it trying to connect, then a few lines down, see the error "dhdsdio_probe_attach: si_attach failed!" shortly after it loads the Dongle Host Driver, then it isn't finding the chip. You probably have the same loose connection problem I had (above), and may have to do something physically to your phone if you want wifi back. I'd try the 'squeeze test' first to confirm before taking it apart.
I hope that is helpful. I spent way too much time figuring this out, and would have loved to have found this info somewhere in one spot online.

its def a kernel problem because i rely on wifi everyday since i tether to my pc and once i tried a kernel that should fix headphone heat up. didnt know if it did but it broke the wifi. would not switch on so i switch back to a next kernel n wifi works. roms like carbon, cm10.2 everlov gives kernel with wifi working. hope this help if someone end up in this boat again

http://forum.xda-developers.com/showpost.php?p=41652708&postcount=3
Just a quick link to N_otori0us_'s posts on kernels if you wanted to try other ones.

tonyMEGAphone said:
http://forum.xda-developers.com/showpost.php?p=41652708&postcount=3
Just a quick link to N_otori0us_'s posts on kernels if you wanted to try other ones.
Click to expand...
Click to collapse
There's more kernels for Gingerbread in the second post too. The one's in the 3rd post were just common things I've seen people asking for,

my friend just gave me a new motherboard, works fine now.

followup on the oven solution
After a week - wifi still working, but not without some intervention. It crapped out again after 2 days, and I re-baked it (the first time I chickened out and didn't keep it at 385 for the full 8 minutes). It has stayed fairly consistent, but started acting up again over the weekend, so I grabbed a tiny square of some sort of soft compressable insulation material from a tablet I was fixing, and placed it right over the broadcom chip to keep it compressed and applying a little pressure. So far that has held and worked well.
I have a feeling its a matter of time before this eventually fails again, too. I don't think there is anything that can be done to permanently fix lead-free solder paste that has started to develop micro 'whiskers', according to what I've dug up online. Reflowing and pressure seem to work temporarily to re-establish a connection. If I knew how to remove the solder and re-apply a solder paste with some lead content, I'd do it. That would probably be a permanent fix. That or a new motherboard ala simbiiote.
[UPDATE 2] Killed it. Apparently re-baking every few days at slightly hotter temperatures eventually will fry your motherboard. Don't go past 400 degrees, and use an oven thermometer to get an accurate idea of what the real temp is. Now back hunting for broken ebay phones to replace the motherboard. Oh well, it was good while it lasted.

Super damage- HELP!

Hello people, today I come here requesting for help.
Last night as I was getting out of a bus my phone fell to the street and got ran over by cars.
Lcd was kaput, battery punctured by a small rock, and the most strange thing happened, the Home button became black!!!! (I own a white L5).
Anyway, just as I was getting off the bus, I got a phone number from certain person I was trying to contact since 4 years ago.
I did not save the number, just dialed it and thought on saving it once I was off the bus.
Now, I´m well-aware google backs up everything, Is there any chance to get a hold of the call log from them?
Or is there a way I can recover this data from the battered basterd?
Thanks in advance guys, any help will be, well, helpful.

donlloreda said:
Hello people, today I come here requesting for help.
Last night as I was getting out of a bus my phone fell to the street and got ran over by cars.
Lcd was kaput, battery punctured by a small rock, and the most strange thing happened, the Home button became black!!!! (I own a white L5).
Anyway, just as I was getting off the bus, I got a phone number from certain person I was trying to contact since 4 years ago.
I did not save the number, just dialed it and thought on saving it once I was off the bus.
Now, I´m well-aware google backs up everything, Is there any chance to get a hold of the call log from them?
Or is there a way I can recover this data from the battered basterd?
Thanks in advance guys, any help will be, well, helpful.
Click to expand...
Click to collapse
Google never backup call log. You can only get your contacts.

george brown said:
Google never backup phone log. You can only get your contacts.
Click to expand...
Click to collapse
Thank you mate, I had my hopes high on google creeping around my call log
Well, to wait some other 5 years now....

I'm so sorry to hear that, mate.

There MUST BE A WAY
donlloreda said:
Thank you mate, I had my hopes high on google creeping around my call log
Well, to wait some other 5 years now....
Click to expand...
Click to collapse
Download These tools
extract to folder
plug your phone using usb cable
wait for drivers to install if you don't have drivers google it or if you lost google search >>>CLICK ME<<<
press shift on pc keyboard and right click mouse button inside folder you extracted toolkit and select "open command prompt here"
then copy and paste following
Code:
adb devices
and post back result
then copy and paste following
Code:
fastboot devices
and post back results
if any of them will return some outcome there is 99% chance you will get your number back

IGGYVIP my clever friend!
Will try this ASAP, problem is I need another computer, Windows 8.1 for me, has never got along with either ADB nor the LG drivers..
Will download a copy of 7 to try and report.
I took apart the phone, and noticed that though the screen, camera and battery were busted, the main board was all OK:
i.e., no cracked chips nor any visible damage.
Will report back soon.

No problem
donlloreda said:
IGGYVIP my clever friend!
Will try this ASAP, problem is I need another computer, Windows 8.1 for me, has never got along with either ADB nor the LG drivers..
Will download a copy of 7 to try and report.
I took apart the phone, and noticed that though the screen, camera and battery were busted, the main board was all OK:
i.e., no cracked chips nor any visible damage.
Will report back soon.
Click to expand...
Click to collapse
Lets hope the board will respond
download vm and slim windows xp copy (only about 500 mb )
it will be faster and easier also less wasted space
and has all the support