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
Related
Hey guys,
quick question. I just picked up a G tab and used Z4 root app. My problem is, everytime I shut off the unit and power it on, for the next use, I lose root and app downloaded apps are gone. Is this a known issue or is there something specific I need to do?
Well maybe you did temporary root ?
I know for a certain fact that after JM6 the z4root wouldnt work well, you might wanna give a go at SuperOneClick.
sedde said:
Well maybe you did temporary root ?
I know for a certain fact that after JM6 the z4root wouldnt work well, you might wanna give a go at SuperOneClick.
Click to expand...
Click to collapse
I try the Z4 multiple times and it was the permanent root option.
Right now it's 100% stock. Where can I get the Super One click?
I just re-booted my VZW Tab and it was rooted with Z4 and it seems to be permanent here. Not sure why yours would not be. Mine is completely stock with root.
siafu said:
I just re-booted my VZW Tab and it was rooted with Z4 and it seems to be permanent here. Not sure why yours would not be. Mine is completely stock with root.
Click to expand...
Click to collapse
Yeah I don't get it at all. The Z4 root app disappear from my list and the new market I installed disappears as well. I have to reinstall both after every boot. Does anyone have any ideas what to do?
Breakthecycle2 said:
Yeah I don't get it at all. The Z4 root app disappear from my list and the new market I installed disappears as well. I have to reinstall both after every boot. Does anyone have any ideas what to do?
Click to expand...
Click to collapse
I would say you should try a hard reset and re-do it.
SuperOneClicker can be found here in xda.
I can also vouch for Z4 permanent root on the Verizon Tab.
I have a real problem I think. Before I go return it, does anyone have a system dump so I can try and reflash this tab and start fresh? I did a system wipe and now Im getting FC in masses. Nothing stays installed and it keeps asking me to log in after every boot as if I just bought it.
I had a similar problem - I couldn't remove anything I had installed to one point and couldn't install anything new. I ran 'dmesg | busybox grep error' in a terminal on it and had lots of errors on the device used for the /data partition. I had to bring it back to verizon and get it replaced. New tab had been fine since then.
-Dan
Problem With Verizon Galaxy Tab
i am having the exact same issue as well. Seams as anyhting you do, it just goes back to the way it was after a reboot.
dragonfire540 said:
i am having the exact same issue as well. Seams as anyhting you do, it just goes back to the way it was after a reboot.
Click to expand...
Click to collapse
So it seems to be a few of us. I guess I'm going back to best buy for a new one.
I ended up returning mine. Best Buy said they've never seen anything like this and there was def something wrong...lol. Really BB?
Editing,,,
Well, it worked flawlessly on my new tab so I guess it was just the defective one. Thanks guys.
OK. I rooted using Z4 I added Rom Manager and some other apps. I wanted to created a back and the tab when back to the original state, I unrooted and uninstall all the apps and rebooted the Gtab but now it bringing back to the with Rom manager FC.... any ideas?
I'm trying to do a hard reset by pressing vol up and power.... it goes into recovery and it stop about 20% I get the triangle imagen and reboots....
Can someone help me to do the right steps?
thanks
I had the issue where rebooting my tab caused everything to revert back to a previous state and giving me various force close messages. This was on a completely stock Verizon tab with no attempts at rooting. I did a full factory reset dozens of times, and every time it went back to a previous state. I posted on here about it a few weeks ago, and no one seemed familiar with the problem. I ended up returning the tab to Best Buy and exchanging it for a new one. No problems since then.
teardropcity said:
I had the issue where rebooting my tab caused everything to revert back to a previous state and giving me various force close messages. This was on a completely stock Verizon tab with no attempts at rooting. I did a full factory reset dozens of times, and every time it went back to a previous state. I posted on here about it a few weeks ago, and no one seemed familiar with the problem. I ended up returning the tab to Best Buy and exchanging it for a new one. No problems since then.
Click to expand...
Click to collapse
Exact same string of problems here. I too returned mine and no issues since.
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
My a7 was running well for about a week since it quit...but today when I booted up device, it failed to recognize sd card...same card used for updating to mod 1.4...same card I've been using to listen to my music, etc...but now won't recognize...I've tried two different micro sdhc cards..formatted, reformatted, but device continues to display mount sd card...all else works fine! Does anyone have any new ideas? I can't even reinstall mod since a7 can't read my cards. Thanks for any input that would be helpful. I understand these issues are ongoing for many out there...what to do?
deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Mine has hung on a black screen on me. Seemed that it didn't fully come out of sleep mode.
I was able to recover by holding the power button for 15 seconds to hard power down. No data loss.
deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Exact same thing happened to me this morning. Tried to reset - not happening. Hard powered down. Don't have time to try anything else right now. I'm new to the forums and new to android. Wish me luck! I've been loving my A7, and much appreciation to Dexter and all the other knowledgeable hackers/modders/posters.
hey the same thing happened 2 me twice. Once the first day after i got it, since i had only had it for 1 day i wiped it reinstalled dexter's mod 1.41 and it worked. First app i installed was backup root. Now, a week later the exact same thing is happening. This time i dont want to wipe it because of all of the apps i have installed, games ive played etc. Any ideas? Could we just try reinstalling dexter's md without wiping? Or wiping reinstalling and recover from a backup?
Also have you installed busybox? I had just installed it both times before it failed to turn on. Maybe its just coincidence but you never know..
-D
Thanks to anyone who can help! and also thanks Dexter for all your hard work as well as everyone else that has contributed to the elocity, im lovin it! (when it works )
success!!!!
I got it to work! I don't have a permanent fix but if it happens again just boot into recovery and reinstall the dexter's mod update 1.41 and it works again! No wiping required. This isn't a permanent fix but it will work until we find one
-Dylan
Hasn't happened to me (yet) but I didn't upgrade to the newest ROM. I'm still using 1.3and it has been very stable. Only issue I've had was when I tried to use Killswitch to go to sleep mode when the cover is shut (great idea) but it didn't work and froze all except the live wallpaper. Weird.
Good luck, guys.
in the event it does happen to you, you might want to check out my apx thread for reflashing the factory firmware if you can't get your tablet unstuck. theres alternatives if you don't want to get stuck again.
The method you outline seems so complex...way above my abilities, but makes me wish I had followed though on some early programming training opportunities. That was the road not travelled.
okantomi; while i wouldn't encourage others to follow thru with procedures they fear would cause more harm, i would mention that if you google up my nick you'll find i've been able to do much w/ android software and devices while not knowing anything about programming. if i can do it, anyone can. i just wanted some themes for my phone.
i'm just an android hobbyist by night (and when i get a chance during the day), and a computer tech by day. no programming expertise, but i can reasonably reverse engineer and port software and components using simple file managers like ztreewin(trialware).
don't be mistaken that the folks out there providing you solutions necessarily know anything about programming or software development. just how to chef up files at different levels. i understand this doesn't go for everybody.
Thanks for the encouragement. I'm impressed with what you've been able to do. It is also nice to read upbeat comments about the A7. There is something sort of special about a device that you really almost have to build yourself... putting so much into it... biting your fingernails to nubs with each ROM flashing. You don't get as attached to any device that is 100 percent complete right out of the box, though of course there would be a lot less aggravation.
I'm desparate, please help!!!!
I had to do a hard reset after failing to Root my A500, that's a long story.
After the Hard Reset it has come up with a APKInstaller (All pre-install processes complete). I click OK and then it has asked me to enter your password (with the Android logo on the left had side.
I have tried all the passwords I can think of, including my Gmail password, and it just says that it is wrong.
Can someone please put me out of my misery and help????
Feel free to mock me, as long as you come up with a solution that doesnt involve taking the device back to get fixed.
Thanks in advanced
had this happened before when i tried to do the factory reset through the method of HOLDING DOWN POWER + RIGHT VOLUME BUTTON (in landscape mode) + SWITCHING THE ROTATION LOCK BUTTON. easy solution to this would perform the factory reset one more time and it'll go away
Having this issue too..
Ok.. simplified version of long (2-wk) history:
1) Initially 3.0.1 device "bricked" attempting to do a direct 3.0.1 to 3.2.1 update.. bad move and stupid of me.
2) Successfully unbricked using EUUs_SBK_Acer_A500_1.016.05_COM_GEN1
3) 3.0.1 rooted, custom recovery, and updated to a 3.2.1 stock with root.. and stable for about 5 days.
4) I installed ES Task Manager and played with some settings. Shut down the device for the day (early afternoon).
5) Restarted device, boot, and was asked for a Password. -- One that I never set. None of the account (google) passwords that were on the device worked.
6) Being still somewhat fresh, I did the "unbrick" flash again and proceeded with root, recovery, and update again... stable for about 3 days.. before the Password prompt returned.
I'm now at the state that I've attempted multiple ROMs.. there is *something* not getting wiped. Now, even when I use the EUU "unbrick", the first boot is fine.. as soon as I restart though, Password.
Massive frustration.. but I'm hoping someone here might be of some help on this.
I figure the worst case.. I literally break the thing and have to use my "accident" warranty.. but I'd really rather not do that.
Any ideas?
MoonHowler said:
Ok.. simplified version of long (2-wk) history:
1) Initially 3.0.1 device "bricked" attempting to do a direct 3.0.1 to 3.2.1 update.. bad move and stupid of me.
2) Successfully unbricked using EUUs_SBK_Acer_A500_1.016.05_COM_GEN1
3) 3.0.1 rooted, custom recovery, and updated to a 3.2.1 stock with root.. and stable for about 5 days.
4) I installed ES Task Manager and played with some settings. Shut down the device for the day (early afternoon).
5) Restarted device, boot, and was asked for a Password. -- One that I never set. None of the account (google) passwords that were on the device worked.
6) Being still somewhat fresh, I did the "unbrick" flash again and proceeded with root, recovery, and update again... stable for about 3 days.. before the Password prompt returned.
I'm now at the state that I've attempted multiple ROMs.. there is *something* not getting wiped. Now, even when I use the EUU "unbrick", the first boot is fine.. as soon as I restart though, Password.
Massive frustration.. but I'm hoping someone here might be of some help on this.
I figure the worst case.. I literally break the thing and have to use my "accident" warranty.. but I'd really rather not do that.
Any ideas?
Click to expand...
Click to collapse
Do a clean flash directly to 3.2.1 rooted. Then don't install anything for a few days and see if your problem is gone. It should be fixed.
I've never had any problems like yours. I always use CWM to do full WIPES + FORMATS. I have used windows Directly to do about 3-4 Flashes that way. About 20-30 Flashed ROM's thru CWM Recovery (20-30 -not ever cuz of problems).
Best i can say is Next Time do it THRU CWM Recovery and WIPE (3) + FORMAT (4) = 7 commands to say "YES" to before Installing a CUSTOM ROM. I've messed arround a lot and have hard time BRICKING or having any messed up ROM INSTALLS.
amateurandroid said:
I'm desparate, please help!!!!
I had to do a hard reset after failing to Root my A500, that's a long story.
After the Hard Reset it has come up with a APKInstaller (All pre-install processes complete). I click OK and then it has asked me to enter your password (with the Android logo on the left had side.
I have tried all the passwords I can think of, including my Gmail password, and it just says that it is wrong.
Can someone please put me out of my misery and help????
Feel free to mock me, as long as you come up with a solution that doesnt involve taking the device back to get fixed.
Thanks in advanced
Click to expand...
Click to collapse
No problem, but, I have to "mock" you a little Because in over 350+ flashings for testings, etc, I have never had this happen, nor have I ever had to use the "pinhole" (knock on wood)
And that "password".... hint, there is no password that will work. The issue, is that you have a big mess internally when booting, and the OS doesn't know what else to do, so it gives you that dialog.
And you're not the first person to have this happen to.
My question, is WTH did you do to get yourself into this mess? And the reason I ask, is that others have done the same thing. So perhaps it would be best to give the "Long Story". This may be useful to others and serve as a reference point.
TimmyDean has a tool for unbricking devices. From what I've seen, it works well 90% of the time. So you should listen to him. There's also one other unbrick master, but haven't seen him around for awhile.
I got my ouya the day it launched. Set it up. Found out that it required a Credit Card, not happy. Blah blah i properly rooted it and installed superuser and busybox, nova and several apps. Worked fine. also set up wireless ADB. tried to set up CWM Recovery, both manual and one click. with adb over wifi and wired adb. noticed that adb would always revert to Wifi, causing it not to finish setup as ouya did not connect to wifi outside of being booted. did my best to get rid of wireless adb, taking it out of the build prop and pushing it back in, etc. Nothing worked. so i did a factory reset. added busy box and superuser. worked fine for a little. then su quit working and so i redid a factory reset, and now my Ouya wont go past the WiFi Setup, even after rebooting, making sure it was connected, still managed to connect through ADB -____- and if i click continue on the wifi setup, it says "controller connected, connect more later.. etc etc" and so i continue and it goes back to the wifi and does a loop!
Any Ideas? Any way to do a full reset like flashing a tar.gz on odin with stock firmware? Please help im not happy with my ouya already. almost ready to return it.
OreBoySwaggin said:
I got my ouya the day it launched. Set it up. Found out that it required a Credit Card, not happy. Blah blah i properly rooted it and installed superuser and busybox, nova and several apps. Worked fine. also set up wireless ADB. tried to set up CWM Recovery, both manual and one click. with adb over wifi and wired adb. noticed that adb would always revert to Wifi, causing it not to finish setup as ouya did not connect to wifi outside of being booted. did my best to get rid of wireless adb, taking it out of the build prop and pushing it back in, etc. Nothing worked. so i did a factory reset. added busy box and superuser. worked fine for a little. then su quit working and so i redid a factory reset, and now my Ouya wont go past the WiFi Setup, even after rebooting, making sure it was connected, still managed to connect through ADB -____- and if i click continue on the wifi setup, it says "controller connected, connect more later.. etc etc" and so i continue and it goes back to the wifi and does a loop!
Any Ideas? Any way to do a full reset like flashing a tar.gz on odin with stock firmware? Please help im not happy with my ouya already. almost ready to return it.
Click to expand...
Click to collapse
As far as I know right now there is no way to do a full reset. Try plugging it into ethernet before turning it on and see if it goes through everything. It sounds like you're having wifi issues, which was happening prior to the last 2 updates, and it's having a hard time connecting.
Right now trying to install CWM is very much experimental and advanced, so the fact that something messed up after trying that is not OUYA's fault. Why did you install CWM anyway? There is very little reason to do so right now unless you' like to try all the new stuff while it's still in Alpha. Plenty of people working with CWM have bricked their OUYA.
You can contact ouyasupport and get it fixed through them, I'm pretty sure, but it involves sending it into them.
It kind of sounds like you may have broken the OUYA recovery and when you tried to do the factory reset it didn't actually work. I can't know for sure without messing with it myself, though, and I"m not an advanced user when it comes to CWM, so maybe someone else can help you better.
Yes, there is a way to do a real reset and return it back to "like new" condition. The thing is, since Ouya doesnt have a way to enter recovery/bootloader mode in the event that the flashing goes wrong, there's a decent chance that you can make things worse by trying it. Having said that, here's how you can do it -
# go to bootloader
adb reboot bootloader
# launch cwm
fastboot boot clockworkmod.img
# use cwm's menu and select "install from sideload", then push a factory flashable zip with
adb sideload factory_ouya.zip
then wait 5 minutes, hope your power doesnt go out and make sure the dog doesnt trip over the cable. because 1 little mistake and its a brick.
ksd
JLCollier2005 said:
As far as I know right now there is no way to do a full reset. Try plugging it into ethernet before turning it on and see if it goes through everything. It sounds like you're having wifi issues, which was happening prior to the last 2 updates, and it's having a hard time connecting.
Right now trying to install CWM is very much experimental and advanced, so the fact that something messed up after trying that is not OUYA's fault. Why did you install CWM anyway? There is very little reason to do so right now unless you' like to try all the new stuff while it's still in Alpha. Plenty of people working with CWM have bricked their OUYA.
You can contact ouyasupport and get it fixed through them, I'm pretty sure, but it involves sending it into them.
It kind of sounds like you may have broken the OUYA recovery and when you tried to do the factory reset it didn't actually work. I can't know for sure without messing with it myself, though, and I"m not an advanced user when it comes to CWM, so maybe someone else can help you better.
Click to expand...
Click to collapse
Well when i do the factory reset it does go to recovery and goes through resetting, so i know that that works, i guess i will try Ethernet. i plan on installing CWM because i want to make my own ROM and Kernel as to the best of my ability, since there isn't really any options that work. if the Ethernet option doesn't work i might just return this and buy something else. I'm glad i haven't bought anything.
Ethernet?
gianptune said:
Yes, there is a way to do a real reset and return it back to "like new" condition. The thing is, since Ouya doesnt have a way to enter recovery/bootloader mode in the event that the flashing goes wrong, there's a decent chance that you can make things worse by trying it. Having said that, here's how you can do it -
# go to bootloader
adb reboot bootloader
# launch cwm
fastboot boot clockworkmod.img
# use cwm's menu and select "install from sideload", then push a factory flashable zip with
adb sideload factory_ouya.zip
then wait 5 minutes, hope your power doesnt go out and make sure the dog doesnt trip over the cable. because 1 little mistake and its a brick.
Click to expand...
Click to collapse
Well there is through adb, but adb will not work for me as unless i can turn off the network adb it will be network- only mode. So even in bootloader mode adb trys though the network.... wait maybe ethernet will help? Stupid 5 minutes between posts... well i plugged in the ethernet but it still goes to the WELCOME -Controller Connected screen
Broken?
Well it appears that Ouya Launcher and Ouya OOBE are not working, i started getting FC errors, and adb is still only working through wifi, i managed to reboot into the bootloader, but i couldnt control the Ouya, so no CWM if best buy will let me return this, here i go because i dont like this very much.
Returned it
Biked to Best Buy to return it. Had 3 minutes left til they closed, but hey! i got my $100 back! i'll just see what money ill get at my garage sale on friday and probably ill buy a new phone since my current Tmo S2 is a pos! What phone should i get from tmo or should i wait? I know the S4 is the best. Preferably a phone with LTE
Not sure if I'm the only one, and if I am that really sucks, but I got tired of waiting for the OTA and decided to install the update via the fastboot method, unlocked my bootloader installed without a problem.
However the issue now seems to stem from transferring media files to my tablet, which I never had a problem doing, a pop up window will tell me that android.media.storage has stopped, giving me an option to report and to simply tap okay.
Not sure reporting ever does anything, and if it does I've never seen it change a single thing at all, but after I tap okay or send the report, any files transferring will just exit out, then if I unplug my usb and plug it back in, it doesn't seem to recognize the tablet at all.
I've so far remedied this, not sure if it's a permanent fix or temporary, by going into settings>apps>all, then from there tapping the app, clearing data and cache, restarting my tablet with a hard reset and it seems to be working for the moment.
However transferring files since the update are sluggish at best, and taking a 356MB folder of images used to take maybe a few minutes, 5 or 7 at the most, now it's hanging there at times with the transfer time increasing.
As a matter of fact I'm transferring said 356MB folder right now and it's stuck at 10 minutes to finish and hasn't moved for about 10 minutes.
If anybody else is having these problems, can you suggest ways you've fixed it? Or do I simply need to either do a factory reset or straight up flash it again to fix the problem?
Also, I made another article detailing my problems with updating, which I've since fixed obviously, but Recovery Mode isn't anywhere to be found, I do the regular method and before it showed the android with the red triangle and below him it would say no command, now it just shows the android with the same triangle with no wording underneath at all.
I've also re-downloaded the official factory image 4.4 from google's developer site and tried to manually flash recovery onto it, and it says that it succeeded but then when it goes back to fastboot and I choose recovery it loads then shows me the android with the red triangle.
I've even tried downgrading back to 4.3 but it tells me during the rewrite of the bootloader that there's a signature mismatch.
In addition, this should be the last revision to my issue, I've even tried re-flashing 4.4 and now that's kicking back an error saying there's a signature mismatch, so I can't go into recovery, I can't downgrade, I can't flash a recovery image to my tablet, I think I screwed up in ever updating to 4.4.
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
StuMcBill said:
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
Click to expand...
Click to collapse
Nope no fix yet, I haven't tried transferring a large number of files since, oddly enough, I finally did get the OTA update and it installed 4.4 again.
It didn't take long and the file size was puny, only about 32MB, I assume it installed what was missing, but I haven't noticed anything out of the ordinary since the official updated kicked in.
Yeah I have the latest OTA also, but I am still having the same issue!!
StuMcBill said:
Yeah I have the latest OTA also, but I am still having the same issue!!
Click to expand...
Click to collapse
Not really sure why it's different for you, like I said I got tired of waiting for the OTA and manually flashed the factory image, that's when the problems started, but after a few days I got a notification that the new update was ready which really confused me.
But I installed the downloaded update without a hitch, booted like normal and I just finished transferring a 100MB folder of images to my N7 without an error popping up on my tablet saying something crashed, so I can only assume for the moment until I transfer a larger folder, that the DL'd update fixed the problem.
I've also heard people flashing it again, or side loading it, or even a factory reset would fix the problem, but there weren't many replies as to this actually fixing the data transfer problem.
Problem with downloading ota update kitkat 4.4
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
manow91 said:
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
Click to expand...
Click to collapse
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
JohnathanKatz said:
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
Click to expand...
Click to collapse
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
manow91 said:
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
Click to expand...
Click to collapse
That could be too, just thought I'd take a shot, hope it works out for you.:good: