First of all, forgive my noobness.
Second of all, I have read for days multiple threads of people having problems with their TF101 with Wi-Fi issues, I have tried multiple, multiple methods of instruction on how to root, unroot, flash custom, flash stock, using custom recoveries to wipe data, etc. (At one point I was in TWRP recovery with no OS installed, and flashed stock firmware from ASUS.
All to no avail.
I even tried to put Ubuntu on it, and succeeded but I still could not get the Wi-Fi to work.
What I have learned from this experience, is that I am either very very bad at following instructions, since everyone seemed to fix their problem but me, or that there is something wrong with the Wi-Fi chip itself. I cannot confirm that it worked before, but the previous owner claims that it did before they shipped it to me.
Just to be complete, I received the item with a cracked digitizer which I replaced myself.
Obviously sending it back to ASUS to repair will be too pricey to be worth it.
Any help is much appreciated!
I would really like to get this tablet working.
Update*** Tried flashing custom rom and custom kernel 9.2.1.27 still no results
Any ideas?
Related
I've looked at multiple forums, not just galaxy 3, and I can't find an answer to this problem. I keep getting the "symlinks: some symlinks fail - status 7" error when I try to flash certain roms. First of all, I'm rooted and unlocked. I have flashed CM10 and Synergy before (couple weeks ago,) but now I can't install any of the synergy nightlies or JB roms. I've tried to install from internal and external sd, and failed on both. I've flashed CWM touch and non touch 6.0.1.2 as well as twrp with the same error message. I've flashed the cwm recoveries through Rom Manager and Odin with no change. I loaded the latest Modem through Odin to see if that would fix the problem somehow, and that didn't work either. (Wasn't expecting it too.) Has anyone run into this issue and come out with a fix? I think I've done some pretty in depth research on this, but maybe I've missed something. I don't want to create a brick if someone has a fix. Thanks for the help.
I just bought a S3 last night. I immediately went through all of the steps for root,unlock,and tried to load a custom rom. After about 5 hours worth of research and trial and error I gave up and am probably going to return it for something different. No one has answers for this issue, but it seems a decent amount of people are getting this. I believe it has something to do with the phones memory / storage. Be sure to share anything that might fix this issue.
Motorola XOOM Z604 32GB IHDT56MT1
Sorry if there was another thread about this, but i looked and didn't find any
Anyway friend of mine flashed some kinda rom he says official 4.1.1 JRO03H, but i'm not sure
anyway as he said after OTA tab is freezing randomly and gives android keyboard error
so i assumed i can unlock/root and flash some custom rom that will resolve the problem
after using AIO tool and unlocking/rooting/flashing various roms problems persists
sometimes tab is crashing during start up (android loading) sometimes just randomly by touching/using absolutely random
using tiamat recovery 3.2.2 and TWRP, it's rock stable in recovery
so i assume it's hardware related
any ideas, cause i'm out of any
p.s. it does have a sim card slot, but judging by FCC code it's wifi only
p.s. i tried to flash stock rom and lock it, still freezing and crashing randomly, first at wifi menu then at internet browser, guess something is really hardware related, possibly memory got corrupted or something like that
p.p.s now i'm not even sure which xoom this one is, is it a wifi only or 3g and maybe it needs some different stock rom? most confusing tab i've seen so far, there is just so many variation of this
thnx in advance
Mortibus said:
Motorola XOOM Z604 32GB IHDT56MT1
Sorry if there was another thread about this, but i looked and didn't find any
Anyway friend of mine flashed some kinda rom he says official 4.1.1 JRO03H, but i'm not sure
anyway as he said after OTA tab is freezing randomly and gives android keyboard error
so i assumed i can unlock/root and flash some custom rom that will resolve the problem
after using AIO tool and unlocking/rooting/flashing various roms problems persists
sometimes tab is crashing during start up (android loading) sometimes just randomly by touching/using absolutely random
using tiamat recovery 3.2.2 and TWRP, it's rock stable in recovery
so i assume it's hardware related
any ideas, cause i'm out of any
p.s. it does have a sim card slot, but judging by FCC code it's wifi only
p.s. i tried to flash stock rom and lock it, still freezing and crashing randomly, first at wifi menu then at internet browser, guess something is really hardware related, possibly memory got corrupted or something like that
p.p.s now i'm not even sure which xoom this one is, is it a wifi only or 3g and maybe it needs some different stock rom? most confusing tab i've seen so far, there is just so many variation of this
thnx in advance
Click to expand...
Click to collapse
The wifi xoom also has a sim card slot but it does not work( missing the radios).
Can you get into recovery and which one is it (custom CWR or stock)? With the xoom off press power until the moto dual core logo appears then press volume down after 3 seconds. You will see android recovery written on top press volume up. If you still have a custom recovery you can then install 4.1.1 JRO03H again but do a factory wipe (very important to get rid of any possible corruption) before and a cache dalvik cache wipe before.
If you are still having issues you can fastboot the stock honeycomb wifi images and allow the updates to happen automatically but this will wipe all of your data. I can walk you through this.
i did mentioned recovery in my post, otherwise how the hek would i be able to flash it in the first place duhh
i did all that, i even tried stock image 3.01 let it update it all the way up to the 4.1.1 which kept giving me weird android keyboard stopped working error and same random freezes
most stable was honeycomb though, i could stay in the system sometimes longer before touching anything, i even let it on lock screen for an hour or two and wouldn't freeze, in ics and jb it froze on lock screen, sometimes wouldn't even let me pass welcome/choose language
i just don't understand how can it install without any problems and stock/custom recoveries being stable while in OS it's just freezing for no apparent reason, my theory is something wrong with video part of the chipset, then again i simply dunno anymore
i tried several times factory defaults and wiping cache before and after flashing didn't helped
Good luck
I'd like to get the feedback from XDA masters on this issue I had.
Here's the steps that led to the problem.
Flashed ROM(Dr No V2), Decide i didn't like it after a day, the wifi was orking.
Entered 4ext recovery did a full wipe.
Used restore to flash my previous fully functioning ROM (EnergyROM-RCMIX)
Rebooted.
After reboot received the message in settings>...>Wifi "error"
I went through a bunch of steps, lots of reboots.
Try restore of an earlier backup - no fix
Reflashed from Zip the original RCMIX ROM, and fastboot flashed boot.img - no fix
Went into recovery and factory reset only. - no fix
Restored the last working ROM (RCMIX) and just fastboot reflashed boot.img
Still not fixed
More reading tried rename of the wpa_supplicant file. nope
One more fastboot flash of boot.img --
Then... turned on "Airplane Mode" for a few minutes. After turning it off Wi-fi "error" was gone and was able to turn it on.
The error changed to "unable to scan for networks"
Rebooted
Went back in and renamed wpa_supplicant.conf 1 more time.
reboot
When I enable wifi this time it scanned and connected.
I left some steps out, but they were just repeats of the ones I listed.
My question after all that is what went wrong?
Lots of threads about the problem but solutions seem to vary.
Is there something in there that I did incorrectly?
Aren't the drivers for the hardware located in the boot.img (as it contains kernel)?
Is there a better way to do this?
trying to get better at this; Insights, advice, comments appreciated.
I do need to get familiar with logcat.
Clean flash a stock-ish ROM like Android Revolution HD. Is the problem still there?
bananagranola said:
Clean flash a stock-ish ROM like Android Revolution HD. Is the problem still there?
Click to expand...
Click to collapse
Wifi seems to be stable now. Running the restored RCmix. Rebooted a couple times and no issues. I'm interested in gaining some insight into the source and solution of the problem. My next step was to run a stock RUU I have, but your suggesting something close to stock might have worked?
Why didn't a re-flash of the previously functioning ROM (RCmix, zip on sdcard & fastboot boot.img) fix the issue? I did full wipes each and every time. Even full wipes before doing Restores from recovery. Restore should be a straight forward process from recovery, right?
The problem started right after a restore, and I'm not sure what step it was that fixed it. The last thing was renaming the wpa_supplicant.conf file. I left out the part where my restored ROM got stuck in the boot animation. There was something going on with the boot loader. Re-flashing boot.img fixed it.
But the wifi...? Any thoughts.
I'm a little hesitant to flash another ROM for fear of losing wifi again. I use it a lot.
Cremnomaniac said:
I'm looking for some intelligent feedback. Any thoughts on my OP?
Click to expand...
Click to collapse
I already answered you...and also, why are you renaming wpa_supplicant.conf? Are you making any other changes?
bananagranola said:
I already answered you...and also, why are you renaming wpa_supplicant.conf? Are you making any other changes?
Click to expand...
Click to collapse
Thanks, but your first comment offered a possible solution, and solutions are important, but as indicated in the title it had been solved. There aren't any comments on the questions I specifically asked. At the least, I was hoping that someone with greater experience could provide insight into the possible causes of loss of wifi (steps, incompatibility of ROM, freak thing, etc.) so I can avoid it in the future.
The renaming of wpa_supplicant.conf came from threads in the XDA forums where similar wifi problems had been encountered. It was a solution with zero risk.
Here: http://forum.xda-developers.com/showthread.php?t=1965812&page=3
Here: http://forum.xda-developers.com/showthread.php?t=1662805
Here: http://forum.xda-developers.com/showthread.php?t=1988190&highlight=wifi+error
Here: http://forum.xda-developers.com/showthread.php?t=703105
If I made any other changes I would mention it. I can see that you may be the only one monitoring this forum, which is unfortunate. You exhibit a lot of patience, but unlike some of the questions posted, I do the research and read directions carefully. The reason I ask questions is to learn, not to have my hand held. And someone posting "ddpo" is a waist of bandwidth. If no one has any comments to my questions, we'll leave it at that.
Because stock is most stable, flashing a stock-ish ROM will reveal whether the problem is a hardware one or a software one. If the problem still exists on stock, your hardware is probably messed up. If the problem doesn't exist on stock, something is up with your ROM. That is why flashing stock is still relevant: for the first step in diagnosis. Other than that, you can look into getting S-Off and flashing an updated radio, but that's up to you.
And I already reported the "ddpo."
This has happened to me several times and I am seeing that other people are running into this problem with no fix found.
Everytime I try to install CM10.2 onto my xt926 I can never get past the unlocked bootloader warning screen after a reboot. I can still access CWM which is the recovery I'm using. I have tried clearing cache, data, factory reset, fixing permissions, reflashing the rom. The only way to get a working phone again is to flash stock 4.1.2 using RSD.
Then I remembered seeing an article a while ago saying that their were two versions of an OTA update for Razr HDs because for some reason their were slight differences between some phones, hardware wise.
Could this be the reason for these random phones not accepting CM10.2 installs?
Also if anyone has any ideas to get past this. I read someone had luck toggling bluetooth on and off for some reason but it didn't help me. I'm at a loss here and would love to play with Android 4.3 but I guess its just not in the cards...
ive got the same problem to i finally decided to get rid of safestrap and unlock my phone. now im stuck on stock rom because no roms will work after a reboot. theres two diferent stock 4.1.2 firmware files. one says mr4 the other one says mr2 anyone know the diference?
Not sure. I just use the RazrHD Utility 1.21 for that, its a lot easier. Also I have heard that 10.1 may work for us, just not 10.2 for whatever reason
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive: