[Q] Wlan broken, any fixes? - G2 and Desire Z Q&A, Help & Troubleshooting

Hey guys, searched for a while now but couldn't find a similar thread to this related to our phone.
Suddenly,
my Wlan stopped working.
The issue is well known, it starts up, says "unable to scan for networks" and shuts down.
Same goes for setting up a W-Lan hotspot, starts up and immediately after it stops trying.
Both worked flawlessly before.
Since then, i tried cache wipes, reboots etc.
I am on the newest dz radio, using Virtuous Sense 2.0.0 for sum time now.
I found a workaround for a galaxy s that implied deleting the configuration file. This file seems to be at a different location on the desire z. Additionally, it probably has a different filename.
I was only able to find the file with the information of my saved wlan connections (WTF, why are the passkeys writting in clear text, not crypted in any way??) - this was the only file in the /data/misc/wlan directory.
I actually only want to full wipe as a last consequence,
since my phone's a bit shaky. Last year I had a severe issue with my sd-card slot (maybe someone remembers), which somehow disappeared month later without any interaction - pure magic. I even replaced the slot before with no improvement - suddenly the functionality returned.
I actually don't want to lose sd-card functionality again, so i even fear flashing a new rom.
I hope there is someone who can give me some input - maybe some config files are missing or stuff - i only hope its not hardware related.
In the meantime I also tried reflashing my rom and flashing the radio again,
no success
EDIT:
Okay screw it, I wiped and flashed my rom again - same issues,
Sounds like a hardware issue...
any ideas?
Greetings

Related

[Q] Device hangup - what is the reason for

I have very strange behavior of my Desire. Several weeks ago I have installed InsertIcon v1.0.8 non-CM version. Everything was fine, run quite smothly. But last week I had the first device hangup. Without any critical operation it's just stop working - locked, no program running, only hard reset help (battery take out). Then it was running for several days without any problems and hanged again and again after reboot. And then again... in several minutes.
I thought it was just because of some new software - I delete it (2x battery and some device monitoring software). But problem became worse and worse - finally I got lost all my widgets from the screens, except application links. The problem is wiered - device can run for several hours without any problems and then hangup because of ... nothing. Just frozen in Screen On or Off ... What is the reason for it? Is it device, SD card or software related? How could I fix it?

[Help] A Myriad of Problems

Disclaimer: I am extremely illiterate when it comes to Android terminology, so you will most likely have to talk to me like I'm a child. I will try to explain my problems as best as I can, and will of course answer any questions. I also might over-explain, so I apologize for any length/redundancy issues.
Phone: XPERIA Play R800at, Android 2.3.3, Rooted with su and rom manager
My previous Play's touch screen stopped working, so the warranty granted me this new one. It's only two or three weeks old. The first problem I noticed was that I tried and could not delete anything off of my SD card. I tried formatting it a number of times, both in-phone (In Settings, as well as ES File Manager) and on Windows (both default formatter and a specific SD card formatter), but it would always revert back to what it's previous state would be. After researching a bit, I concluded it's probably faulty or failing, so I've ordered a new one that should get here within the week.
The second problem rose out of the first, I'm sure: My computer now doesn't recognize the sd card anymore. In SMC or MTP mode, it will not pop up on my computer and could not be recognized in PC Companion. On phone, the usual options you get in the notification bar (*dis*connect phone, etc.) do not show up. When connecting, the MTP USB Device driver attempts to install, but never succeeds. This is with USB debugging off and on, and every permutation I could think of.
Now, the most recent problem has been that the Home button doesn't work and there is no lock screen. Using the Terminal Emulator, I've attempted the popular fix (su -> echo -n ON > /efs/imei/keystr -> sync -> reboot) but I get the message /efs/imei/keystr directory nonexistent. I've factory reset my phone a number of times, reset settings, gone into recovery mode and reset things there, as well as caches, but all to no avail.
This could probably easily be remedied by just reflashing Android, or an older version or something, I'm sure, but given that my SD card is currently unreachable, I was wondering if anyone would know of a way I can fix these problems, or at least one of them. Thanks in advance.
If I've left anything out, please tell me and I will expound as best I can.
Other notes that might be of importance:
- It seems my *system* or whatever it would be is read-only, which seems like it could definitely be a problem. How do I fix this or do I even need to?
- I don't have the Setup Guide on my phone; I saw a thread that posited that this was a cause of the no lock screen problem.
Thanks again.
Driver install issue
Hello!
I'm not sure how to fix all of your problems. However, I have the same issue with my MTP drivers not installing when I connect the device. I've tried installing with various tools and the standard sony ericsson software. I believe I have the problem with the driver sorted out. I noticed that the drivers are, for some unknown reason, attempting to install to a TEMP folder. I would assume they are then being dumped from the TEMP folder after only a few seconds because when I install the driver it continues to ask me to install even when I click "finished."
You might try making sure the drivers are installing to the proper location if you haven't already. That might help with some of the issues.
On the same topic, do you know where the drivers are SUPPOSED to go in Windows XP? I'm fairly new to all of this stuff so I'm not sure exactly which folder in C:/WINDOWS the MTP driver for the Experia Play is supposed to go.
I hope this helps!
-Zot-

Wi-Fi completely broken.

What happened/is happening:
Wi-Fi won't turn on. This includes anything that uses it. (Tethering, normal connection to routers)
The settings application will try to turn it on, but it just sits there until I enter another menu or back out and re-enter, at which point it shows it as off. Built-in wifi tethering menu in the same place says 'Error' and the checkbox is disabled.
USB tethering still works.
OpenVPN and its tun0 device still works.
Bluetooth... I don't use it, so I don't know.
What I've done:
I tried getting a logcat but I don't have any computers that I have administrative access to install the HTC drivers on, I wasn't able to.
I did some searching, and some frantic listing of directories, and comparing them to a friend's G2, and I found something.
`ls /proc/sys/net/ipv6/conf/` (same with /proc/sys/net/ipv4/conf/) gives me a list of directories corresponding to devices from `iwconfig`, but none with the names of eth0, wlan0, or wl10. List of devices from iwconfig:
lo, gannet0, dummy0, ifb0 ifb1, rmnet0, rmnet1, rmnet2, usb0, sit0, and ip6tnl0
Roughly the same list in /proc/sys/net/ipv6/conf/ (and /proc/sys/net/ipv4/conf/)
I've also flashed CM10.1 (Flinny's Andromadus build 25) and CyanogenMod 7.2.0 stable from their wiki. I started from 10.1, reflashed it, then flashed 7.2.0. No change.
I used CWM Recovery to format my /system partition and restore CM7.2.0 Stable, no change.
I have searched for about two weeks, and I've come up with nothing, short of getting a new phone, or getting some kind of backup of the files. I need a solution, because having Wi-Fi working is pretty important right now.
Had an issue like this way back when once and a clean wipe (including efs partition) and reinstalling ROM fixed it. Toward the top of this thread you'll find a link to the superwipe tool I'm talking about
http://forum.xda-developers.com/showthread.php?p=43195539
If this doesn't work then digging through the old threads for a fix should turn something up as I've seen many WiFi error threads over the years.
Oh and a logcat should help, just get an app from play store if you have no PC to use
Sent from my Nexus 4 using Tapatalk 2
Worked!
demkantor said:
Had an issue like this way back when once and a clean wipe (including efs partition) and reinstalling ROM fixed it.
Click to expand...
Click to collapse
Worked great! Thanks! It kinda wiped my data partition though, so I had to spend an hour queuing downloads on the Play Store. Better than having broken Wi-Fi.
I was wrong.
ArghArgh200 said:
Worked great! Thanks! It kinda wiped my data partition though, so I had to spend an hour queuing downloads on the Play Store. Better than having broken Wi-Fi.
Click to expand...
Click to collapse
Not fixed, actually. I thought it had worked, but last night when I decided to power on my computer and start tethering to it, it was broken again. I'm getting kinda tired of putting up with this phone.

Internal SDcard Busted, Can't Format or Write (Forever Locked as Read-only)

HI,
I used to be more active in this forum, but honestly nowadays I can't found any reason to since everything has been smooth sailing for me without any problems—until this day, at least. Somehow I got my internal sdcard busted, it was pretty spontaneous, all I can recall is suddenly the system starts to reboot itself. Nothing much, I thought to myself, problem is the system keeps rebooting, it doesn't even last a minute. Naturally when faced with this problem one would do the usual procedure, namely completely format the thing to stock the rule out any possibility on the user side of things, but then this is the part when it starts to get interesting...
The thing refused to be formatted, seriously, it baffles me at first but it does
Things I've tried:
Fastboot, it hangs at writing system, whether I was doing it line per line manually or via the flash_all.sh script, I haven't tried the toolkit but I think it's safe to assume that It'll do the same thing. Even if it does go on (which it did, once) it doesn't do any sort of changes whatsoever to the system.
ADB, nope, not this one either. And since the system reboots faster before I can do anything worthwhile it's pretty much out of the question.
Recovery, multiple times I've tried nuking everything via CWM, nada. I've tried TWRP too, I have to boot it from fastboot since it apparently doesn't allow me to flash a new recovery either, it reverts back to CWM every time. Also tried to flash a different ROM (CM), that didn't work, it spits out an error message regarding some failure in changing metadata, thought it was a corrupted file or something, so I re-downloaded it, that doesn't work. Still convinced that it's corrupted I tried 4 different version of it without any luck. Even the one I had successfully flashed before. Interestingly enough, flashing the exact same ROM I'm currently using (ShinyROM) works, not that it seems to do anything.
Built-in data format from settings, now this doesn't work because I assume that it needs the stock recovery to work, which I couldn't flash because it wouldn't let me—in a sense that it flashes just fine on the command line—fastboot doesn't show up any error or anything—but it defaults back to CWM as soon as I reboot it.
Manually via terminal emulator/file manager, still nothing, curiously enough, Terminal Emulator indicates that the whole system is read-only (I tried making a file with it, it shows that exact message).
Grit my teeth, clench my fist and screams out every curse word that I know of, this somewhat reduced my stress levels, but ultimately yields nothing.
Which led to be believe that either my phone was either a) Haunted or b) Has a serious hardware problem, I'm leaning on the latter. A few quick lookup with my limited amount of Google-fu and I've found several threads that described the exact same issue:
http://forums.androidcentral.com/go...-factory-settings-no-matter-method-i-try.html
http://forums.androidcentral.com/go...eset-nexus-7-2102-using-multiple-methods.html
Both of which hints at it being a hardware problem. Which was my biggest fear since I can't really revert the phone back to stock now can I? Locking the bootloader doesn't seem to work either (the 'fastboot oem lock' command works just fine but just like every single thing I've tried, reverts back to my previous setup as soon as I did a reboot), plus this means I have to send it back with my private data still on it, and I can't say I trust Samsung, Google (or anyone really) with my private data. Not to mention some of the stories I've heard/read about Samsung and their policy regarding rooted devices (much less ones with an unlocked bootloader).
In case it helps, here's a few more details:
What state the device is currently in:
It boots up just fine, but nor for long, apps starts to hang and ends up with a cold reboot (sorry if it's not the right jargon, but it starts right from the Google screen).
Everything that doesn't require you to access the filesystem works fine.
Apps doesn't seem to be able to write anything to the filesystem, I tried backing it up with Titanium Backup, much to my surprise the backup files weren't made (although TiBu seems to indicate that they were).
What the device is running:
Variant: Maguro 16GB
ROM: ShinyROM 4.4.2
Kernel: franco.Kernel r395
Baseband: XXLJ1
Bootloader: PRIMED04
Also I don't know if this will affect things but for the record I'm running the latest Ubuntu and Debian.
So this post is pretty much a shot in the dark, since I think I know what I'm dealing with already; if anyone had this problem before in the past, or has it now and somehow managed to fixed it, please do tell. Or if anyone has any experiences RMA-ing your device with a condition like this I'd love to know.
Yep your EMMC is fried. Sorry man.. But you can go to warranty. They *should* accept it since it is a developers phone but they could make a lot of hassle about it being rooted..
Sent from my Galaxy Nexus using XDA Premium HD app

Stuck in setup wizard after factory reset

Alright, hello everyone,
I'm having a pretty weird issue here. I've flashed my DUK-L09 and the C432B183 EU Firmware, everything was running fine.
I couldn't make a backup of the /data/ partition though, someone told me to wipe the data to decrypt it, but nothing came good after this.
So I tried to flash back the old recovery image by extracting it, flashing it via fastboot, as I would normally do; enter the factory reset, run it.
Everything is good, it goes up to 100% pretty fast, less than 2 minutes. I then enter the setup wizard the NFC is acting weird. It keeps activating
and deactivating illogically. So, ignoring this issue, I kept up configuring the phone then once I'm logged in Google and sync'd, pops a Huawei ID
logging page really really fast then goes back to the EMUI menu at the beginning of the Setup, in an infinite loop.
Useful information to let you help me better:
- Many firmwares. Currently trying to flash back to B120a and NoCheck from OldDroid and Morph. (Edit: Didn't work)
- Phone unlocked, TWRP accessible.
- Getting a weird "Error 9" when trying to run Update.zip from TWRP.
- Sideload working, but not transferring anything.
- Cannot find any B182 or B130 stock firmware. Everything seems to be gone from Huawei's servers.
- The loading logo isn't Honor anymore but Android, for a reason I can't yet understand.
- Restoring a clean backup (without /data/, since I couldn't back it up) did not fix the problem.
- Trying to update with the 3 buttons do not work, even with the right firmware (C432B183) (Software install failed)
- Factory reset works with the right ROM, but gets me to the setup loop issue.
- The loop occurs when I am supposed to see the Huawei ID setup page. If I do not put any SIM card, or WiFi
I am prompted to choose which way to restore data; if I skip this step, it blinks and doesn't do anything.
- I tried to restore via WiFi (Google's cloud stored data from my account), but it does the same thing as mentioned
earlier. It blinks multiple times rapidly the "Huawei ID" setup page then goes back to the first Setup screen w/o
me being able to do anything about that.
I'll be glad if you knew the answer to this, because I'm all lost right now.
Greetings, Kameyuu.
UP !
After many tries and a LOT of hard work, and spent an entire night (was about to spend the second night on this), I found the culprit and now I know what the issue is, it sounds completely legitimate.
So here are the reason and the solution to this issue:
Actually, my CUST was somehow broken. I never flashed it back because no one told me to flash the CUST.img back. They told me to flash BOOT, SYSTEM, and RECOVERY only.
So, after I downloaded a software called HUAWEI Multi-Tool (From hwmt.ru) I noticed they were also asking for the CUST.img and USERDATA.img (<- this one was apparently optional)
So, trying my luck I flashed it. Did a factory reset, and all, it acted weird and failed, then I tried again and it succeeded. So, with all my hope I booted the phone to the system, started configuring... And it worked !
I was able to set up the phone. For a -yet- unknown reason, some apps look missing and the NFC is still blinking on and off repeatedly and randomly, but I'm investigating that.
If you have any question on the precise steps feel free to send me a PM or ask in the thread directly I'll be glad to sort your issue out.
[EDIT]
Sorry, double post I don't know why my message was posted twice. Feel free to delete this message @moderators

Categories

Resources