Database Users

Wifi Problem on 3.1 FIX

Hello all;
I hope that this post is in the right place. The fix are for a problem that's been happening after you update to 3.1 when your tablet gets stuck in a connecting loop and never actually gets connected.
I searched for a while for the wifi loop fix and couldnt find anything (its probably somewhere already here but this should make it easier for noobs to find), so I called Acer and the lady was helpful and got me the solution, unfortunately she told me that this might happen again but the fix is not much of a headache and hopefully a patch will come soon.
Here is the Fix (By the way, you will not lose any data):
1) Once the tab is on, press that tiny reset button (I used a staple) and let it restart.
2) Once your tab starts up again, simply repeat step 1, apparently you have to do it TWICE in a roll.
That's it, reset your device twice through that tiny reset button and should work most of the time. No need for a factory reset.
My tablet is rooted and encrypted and it worked fine.
Im up and running again and hope you will be too!
EDIT: If it works for you, feel free to post here and let others know.
ZuzOnline

If that doesn't work try this (Some people said it did the trick)
lostsoul3471 said:
So after running into this problem myself i was going to start looking for said file and realized, no root explorer and no super manager installed (also has root level file managment) i had no way to easily pull the file out.
If nothing else, always and i mean always pick up terminal and busybox for any android device. You don't have to be a linux geek to use it, you just need to know a couple to get by.
Code:
$ su
# cd /data/misc/dhcp
# rm dhcpd-wlan0.lease
(Also works in adb shell)
That should clear the offending file to get you up and running. I would love to know if the permission fix does the trick as i travel alot and run into this more times than not between phone tethering, hotel and restaurant wifi spots. My list of saved available connections starts rivaling a teen's ipod at times.
Click to expand...
Click to collapse

This did not work on my A500. Nothing worked except a factory reset. Now re-installing all my apps. I'm NOT happy. But Acer gave me a choice between factory reset and shipping the damn thing to TX.
I'm going on vacation in a week. I want my tablet with me, so the reset was the only option. My tab is not rooted, and worked for six days after the 3.1 update. Then suddenly (maybe because I power off) the wifi got into the endless loop.
You would think that Acer TESTED this before rolling it out????
P.S. The 2nd level Acer support admitted that this double reset only works for some. They don't have any idea why.

Worked for me.

I had to do a triple reset, but it got me up and running! Thanks!

Thanks for the information. The reset twice worked perfect for me.

zuzonline said:
If that doesn't work try this (Some people said it did the trick)
Click to expand...
Click to collapse
The instruction in post #2 has worked everytime for me.. i've done it at least a dozen times.. no reboot required. Just have to go back to wifi settings and click connect again.

Soft reset did not work for me. Im not rooted so I could not del file. Had to do factory reset. Pretty messed up.
Sent from my A500 using XDA Premium App

I have deleted the dhcp.lease file and it works great now
Official but rooted 3.1

[CLOSED] Need to remove encryption, but factory reset borked - help!

I've got a bit of a problem with my Nexus 10, I want to do a factory reset to remove encryption, but the factory reset fails every time. I've tried the stock one via the menus, and the clockwork one via recovery, but neither works. I thought I'd have a go at re-rooting it to see if I could force the issue, but the recovery isn't able to mount the SD, so I can't get to the file to flash. The unit is spoofing a Galaxy Nexus for SkyGo purposes, which seems to be causing the adb drivers to not work on my PC, as it's obviously not seeing it as a Nexus 10 when I connect. I can't remove the spoofing, as it needs to be rooted, which brings me full circle.
It's a right pickle!
Any ideas what I might be able to do to get the unit rooted again?

mcwildcard said:
I've got a bit of a problem with my Nexus 10, I want to do a factory reset to remove encryption, but the factory reset fails every time. I've tried the stock one via the menus, and the clockwork one via recovery, but neither works. I thought I'd have a go at re-rooting it to see if I could force the issue, but the recovery isn't able to mount the SD, so I can't get to the file to flash. The unit is spoofing a Galaxy Nexus for SkyGo purposes, which seems to be causing the adb drivers to not work on my PC, as it's obviously not seeing it as a Nexus 10 when I connect. I can't remove the spoofing, as it needs to be rooted, which brings me full circle.
It's a right pickle!
Any ideas what I might be able to do to get the unit rooted again?
Click to expand...
Click to collapse
Custom recoveries don't deal with encryption, if I'm remembering things correctly. If your stock recovery's not working either, then that's a serious cause for concern (and is likely why factory reset isn't working for you). To be honest, you may be kind of hosed on this install around. I'd recommend that you boot up, back up your data using Titanium Backup, offload it (connect it to a PC/cloud service while device is on), then plonk into fastboot and just reinstall (or RUU).

Rirere said:
Custom recoveries don't deal with encryption, if I'm remembering things correctly. If your stock recovery's not working either, then that's a serious cause for concern (and is likely why factory reset isn't working for you). To be honest, you may be kind of hosed on this install around. I'd recommend that you boot up, back up your data using Titanium Backup, offload it (connect it to a PC/cloud service while device is on), then plonk into fastboot and just reinstall (or RUU).
Click to expand...
Click to collapse
Therein lies the problem though, for whatever reason my PC won't recognise the nexus 10, despite the drivers being installed from the ADK etc.
Because of that, I can't use fastboot or anything PC based. I suspect it's because the device is spoofed as a Galaxy Nexus.
The device is currently unrooted too, so that also limits my options.
My data isn't really a problem, I'm happy to wipe everything, it's all backed up on my NAS anyway.
Isn't there any sort of physical reset button anywhere that will force a factory reset?

Managed to get the drivers working on my gf's laptop, not sure why my PC wasn't playing ball, but this is all fixed now.
Ta!

[SOLVED] Suddenly G2 boots only into recovery mode (loop)

Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.

Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.

I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.

[Q] Galaxy S4 won't boot past recovery (urgent)

This is somewhat urgent because I am leaving the country for two weeks on Friday, and need a working phone. I am not sure what happened today, but my Sprint Galaxy S4 (SPHL720TBK) wouldn't connect to WIFI at my house. My tablet would, so I know it was a phone issue. I rebooted then was going through settings, and just checking things. The phone rebooted itself, and when it came back up, it went through a couple of screens, one of which asked about activation. It seemed like it was installing an update from Sprint, which it had been trying to do for a week or so. But it kept failing, saying it didn't have enough space for the download, despite there being several GB free internally and on the SD card. (I figured it must be because it was rooted). After a couple of additional screens on which I could only answer OK, the phone rebooted again, and that was it. It would not boot again. I decided to power off the phone and deal with it tonight. I can boot into recovery, and connect with Odin. I can boot to recovery and connect with ADB (in sideload mode). I know I could just do a factory reset, but unfortunately, I do not have a full backup since the end of January, and I would rather not lose everything. The phone was running v 4.4.2. I had rooted the phone several months ago with CF Auto Root using CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5, so it was essentially stock, but rooted. Is there anything I can do to get the phone back on its feet that will not lose everything? Or anyway to copy data from the phone with it in this state? Any assistance will be VERY much appreciated! Thanks!

Fixed it myself
andrewt2323 said:
This is somewhat urgent because I am leaving the country for two weeks on Friday, and need a working phone. I am not sure what happened today, but my Sprint Galaxy S4 (SPHL720TBK) wouldn't connect to WIFI at my house. My tablet would, so I know it was a phone issue. I rebooted then was going through settings, and just checking things. The phone rebooted itself, and when it came back up, it went through a couple of screens, one of which asked about activation. It seemed like it was installing an update from Sprint, which it had been trying to do for a week or so. But it kept failing, saying it didn't have enough space for the download, despite there being several GB free internally and on the SD card. (I figured it must be because it was rooted). After a couple of additional screens on which I could only answer OK, the phone rebooted again, and that was it. It would not boot again. I decided to power off the phone and deal with it tonight. I can boot into recovery, and connect with Odin. I can boot to recovery and connect with ADB (in sideload mode). I know I could just do a factory reset, but unfortunately, I do not have a full backup since the end of January, and I would rather not lose everything. The phone was running v 4.4.2. I had rooted the phone several months ago with CF Auto Root using CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5, so it was essentially stock, but rooted. Is there anything I can do to get the phone back on its feet that will not lose everything? Or anyway to copy data from the phone with it in this state? Any assistance will be VERY much appreciated! Thanks!
Click to expand...
Click to collapse
Since I didn't spark enough interest for anyone to offer advice, had to spend most of the afternoon/evening fixing these problems myself. Everything seems to be working, so I thought I would pass along key parts of this hard-learned lesson in case anyone else finds himself in such a situation.
First I booted into adb sideload mode, which is all I could do anyway. I installed philz_touch_6.23.9-jflte.zip and the aromafm.zip. I was then able to boot into a "normal" recovery mode. Aromafm was troublesome, and I eventually had to manually put the zip into place for it to work consistently. These are both WONDERFUL , and I highly recommend them both. Thanks very much to the creators! I used the file manager to find the files that I didn't want to lose, and used ADB to pull the files over to my PC. (ADB pull <source> <target>) Then I did a full wipe and factory reset. That did little other than delete all my data, which I had already copied anyway. The phone still would not boot past recovery.
I tried to use ADB to install a new ROM, but got a variety of errors. My phone being an L720T, there are not many ROM's available, at least not for which I could find functioning links. I finally found a TAR, L720TVPUBNG5_L720TSPTBNG5_L720TVPUBNG5_HOME.tar.md5, and used ODIN v3.09 to install that.
I still need to go back and re-root the phone, and install lots of APPS and restore data, but at least I have a functioning phone, and I can do the rest on my plane ride tomorrow.
I found the information I needed in a variety of posts here on xda developers, and would not have been able to get through this without all the helpful advice posted to other threads. So thanks to all of you for the wealth of information available here!

Normal (rooted) phone, went full retard all of a sudden. Need help extracting data

Hello all,
I have a Nexus 6P, stock, rooted, with Xposed installed. The phone is completely functional for the better part of its life time since I bought it at release -probably first or second batch- (except for random reboots once daily on average, deemed by my investigation and exhausting all options to be a hardware issue or Xposed related).
Today, out of nowhere, the phone randomly rebooted itself and surprisingly it launched the "Android is starting..." dialogue which, if I'm not mistaken, optimize apps for ART. The battery was at 19% before it randomly rebooted, so when it started that optimize apps it went down to 0 (I assume) and it turned off. The charger wasn't connected correctly so that happened. Now the phone keeps restarting itself up to before it gives me the boot up decryption phase of the Data partition and reboots again. I assumed it can't decrypt Data for some reason, so I launched TWRP recovery to try and decrypt data and take a backup copy of my Titanium Backup folder on storage... Unfortunately, TWRP reports "failed to decrypt data" even though I'm 100% positive that the pattern is correct because I'm literally inputting it almost 10-20 times a day for the past two years...
Note: there seems to be a red blinking LED in the top left corner of the the phone. I never even knew this existed.
WHAT I WILL DO
I'll reflash everything system-wise.. I'm ok with that. I'll reflash the factory images, root it, install Xposed, no problem.
WHAT I NEED HELP WITH
I need to extract some folders from my phone storage, namely the Titanium Backup folder. I know the pattern protection of the encryption.
How do I go about doing this?
UPDATE:
Help is urgently needed now indeed: The phone doesn't even turn on to bootloader mode anymore now. It was able to, just half an hour ago. Now all I see it the red blinking LED.
UPDATE2: https://support.google.com/nexus/troubleshooter/3337561?hl=en-GB#ts=3337942
I'll try in 30 minutes.
Meanwhile, please help me with my original problem; extracting data.
I was thinking, if I boot into bootloader mode, can I use adb to pull any folder? If so, will that work in my case with decryption fails or Data partition doesn't seem to mount correctly?
Relevent:
Reviewing some other threads:
TWRP: 3.0.2-2
Bootloader: UNLOCKED
I did NOT upgrade to Android 7.0 nor was I planning to, until Xposed is available.
I did NOT flash anything **new** recently. However, Installed an Xposed module yesterday which caused a bootloop. I rebooted into TWRP, uninstalled Xposed, rebooted into system (which looped once, out of the ordinary) and I uninstalled that module, back to TWRP installed Xposed, and rebooted back into system. It worked for 12 hours and then what I wrote this post for happened as stated above.
UPDATE3:
15 minutes into charging... NOT EVEN A RED BLINKING LED ANYMORE.
Last? UPDATE:
Almost 1 and a half hour into charging and there is no longer ANYTHING. Is it hard-bricked now?
How the **** is this possible? I'm very much capable of solving any sof-brick but not a hard-brick...

Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck

KLit75 said:
Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck
Click to expand...
Click to collapse
I was indeed able to connect to a PC after I saw the problem (the bootloop essentially)... But I didn't at the time as I didn't have a plan of action as to how to get my data, so I turned it off. After sometime, I couldn't do anything with the phone... Not able to boot into bootloader, not recovery, the phone is essentially not turning on to anything, not even the splash screen; like a hard-brick. I'm not sure if this indeed is a hard brick as I've never seen any.. and don't currently know what to try next.

Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.

TnT_ said:
Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.
Click to expand...
Click to collapse
I honestly declared it hard-bricked.
Will Fastboot show any devices if the phone didn't show bootloader screen?
I'll try again today.
Update:
Didn't work.

check out my post
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311