Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
uncledavek said:
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
Click to expand...
Click to collapse
If you can get to the factory reset in the settings menu that would the first thing to do. And then check for an update. Make sure you set the wifi to not turn off and I would keep the screen from shutting off while downloading the update. Check in settings "about Device". If your not 3389 or higher then you need to update
I had this problem back in November when I first got my tab. Even though nothing seemed to work right, I was able to connect it to my desktop and push across clockworkmod v .08 and a custom rom. So, I never used the original rom more than 10 minutes.
If you can't get it connected while booted in original rom, then Bekit's NVFLash full restore procedure works really well. Just follow the steps carefully and it's a quick and painless factory reset to a known working rom.
These things are virtually unbrickable (is that a word?).
uncledavek said:
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
Click to expand...
Click to collapse
badfrog is correct. If you factory reset the device it should be fine from there - then you set up your wifi and get the update.
Go into your app drawer and choose Settings. I don't remember if you can do it from the menu button as I'm on a different launcher.
Inside Settings go to Security and select Factory Data Reset. Do this, the unit will reboot and come back up at which point you'll be asked to set it up. It may take some time. Set your Date and Time correctly and set up your Wifi and such.
Once that's done you'll likely get a prompt to update very soon after Wifi connects. DO NOT DO IT, yet.
Within Settings, go into Display and set the Display Timeout to Never.
This ensures that the tablet doesn't sleep or turn off your wifi while it's downloading the update. It's not likely to happen but if your connection is on the slow side and the timeout is set too low, it can mess things up.
Once you've done that, proceed to let the tablet update itself. Again, it may take a bit of time.
Once it's done, make sure you take not of what you have. You'll find this information under Settings in the About section. The last version I got was 3389 - but something newer MAY be there for you. If you get anything less than 3389 then you will have to wait until you get another notification for an update. I don't remember how they work - but I THINK you should get the newest one there.
Once you've confirmed you're on the most current build, It may not be absolutely necessary to do it, but I would factory reset again just to clear the 'gunk' of the older TnT out in case there is actually any.
When I got mine and powered it on the 1st time, I got a bunch of FCs. I powered off and then on, and no more FCs, and it was fine after that. I think I posted asking about that, and someone (roebeet, I think) said it was a known problem. I don't remember the TNT version, but it was the one before 3389, or one before the one before 3389.
Jim
It is a known problem, especially with the older firmware. Sometimes the FC's are so bad that you can't even get into the settings to do a data wipe.
I've actually called CS about this, as an example of why they need an offline updater of some kind to get around issues like these. Suggestion: if you don't want to install clockworkmod, at least try to update the firmware to the latest and greatest, via one of the newer stock ROMs we're retrieved:
http://forum.xda-developers.com/showthread.php?t=842000
That might get you enough access to get into the Settings menu and do the factory restore.
Related
after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42
Oh. Ok. Thanks for telling us.
nabzilla1990 said:
after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42
Click to expand...
Click to collapse
First of all... let me address this before someone rips you apart here. Your question (if it is one) is a bit difficult to read. I am certainly not an english teacher but maybe a period here and there would make it easier to understand. Because I honestly don't know if you are asking a question, stating that you're having a problem with reflashing, going back to factory settings or other. I mean I had to read it 5 times!
Secondly... if you do a factory restore from the settings and you get the flashing android on boot you should let it keep flashing for a few minutes. You need to be patient because it is wiping all of your previous data/settings and restoring them to default.
Third. If it stays on the flashing android for longer then say three to five minutes (depending on how much you need to wipe) then go ahead and boot up in recovery mode and do a wipe from there. If you still get stuck on the flashing android then yes... reflash.
Fourth. Do not assume it is an app that causes this problem unless you are CERTAIN of it. Hundreds if not thousands of people have downloaded this app (including myself) and have not had a similar problem. Maybe do a search for the app name and read what people are saying about it. If it is the app then believe me you won't be the only one commenting. If you're lucky there will be a fix so you won't have to wipe or reflash.
Finally... every so often (especially before making a major change like apps to sd, themes, etc) it'll be a good idea to do a backup with Nand so even if you do end up messing something up (by app or user error) you can always reflash your image to your phone.
Good luck!
EDIT: Whoops! Wrong thread!
I'm very sorry for my poor English but my story is after installing ahome
everything was fine until I rebooted my phone. After rebooting the phone I
tried dialing a number and when I pressed a number once the it would dial
the number twice for example when dialing 7 instead of only dialing the
number 7 it would dial 77, or when using useful switchers turning off the wifi I
would try to check the wifi on but with one push it would check and uncheck
the wifi. Later I did a factory data reset and rebooted the phone I couldn't get
past the flashing android. I reverted back to stock rc33 just in case its a
hardware problem I can let t-mobile know thanks for the replies
i doubt it's a hardware problem.
i had the same problem, coincidentally after installing aHome; i was unable to get past the "flashing android" screen. The first reboot that i did, though, was after using the JF auto-updater app, so i'm not entirely sure where the problem lies.
long story short, i wiped my system, and am now in the process of installing Windows and the Android SDK to my system so i can do a restore.
thanks im gonna go back to root then
yeah, aHome still has lots of thigns to be fixed specially that force close issue every time u return to home :/ i liek dxtop better dont feel like scrolling tru 10 pages like the iphone..
I used designgears' jh7_ota.zip to update my phone to JH7. It worked fine. The one reason why I used it was because the OTA update had gone through to 100% and then crashed. In the "About phone" menu it had the right kernel version and the right baseband version, but the Build number was stuck on ECLAIR and not showing ECLAIR.UCJH7 like it should. So after using the JH7_OTA.zip it showed the right build number and the PC Internet option was gone from USB options like it should have been. Also, the GPS started working pretty well.
The one thing that sucked was it completely wiped my phone. So after reloading all my apps and redoing all the customizations I finally got it back to how I like it. Then I happened to notice that the "Build number" had somehow reverted back to just "ECLAIR". I also noticed that "PC Internet" was back as an option when USB was plugged in. I have no idea how it reverted back after I had successfully installed JH7. I never used ROM Manager or Titanium Backup to restore anything, I just went and redownloaded everything and reinstalled everything.
Has anyone else seen or had this happen to them? I had to reinstall JH7_OTA.zip again. And again it wiped my phone out completely. Having to go back through and reinstall everything all over again. How annoying.
You could always master clear, flash stock JF6 and then use Mini Kies to get the update. That way you know you have a fresh install.
I just did that coming of Cognition, loved it but didn't use any of the useful features (mobile AP, tethering) to make it worthwhile. I still bought DG a beer, dude works hard.
That was what I did to get the JH7 update. Although, I did use designgears' zip file rather than mini kies. Mini Kies wasnt out at that time. I used odin one click to revert to stock JF6, then the first thing I did was install clockwork recovery, then I installed designgears' zip file. Everything worked great for weeks. Cant see how or why it reverted back to build number "ECLAIR" from "ECLAIR.UCJH7".
I reinstalled JH7 with DG's zip file again since I still had it on my sdcard. Its back to the right version, build number says the right thing and pc internet is not an option and gps seems to work good and battery life seems to be better again. If it monks up again I will flash back to JF6, then use mini kies to get the JH7 update and try that.
I dont know whether its android or its just this galaxy S, but I've never had such a glitchy phone before. Random software crashes, random shutdowns, half-baked gps, updates that dont work and even brick phones. Just seems like I cant go more than a day or two without something on this phone F'ing up. Is this how it is with android all the time? This feels like the microsoft windows world a la 1995-2000. I thought we moved past all these crashes and glitches with plug and play and with Windows XP.
May or may not be the same thing ... but ... my wife updated to the current release OTA and said it worked. However I noticed the other day that she still has the PC Internet option that shouldn't be there.
jahfry said:
May or may not be the same thing ... but ... my wife updated to the current release OTA and said it worked. However I noticed the other day that she still has the PC Internet option that shouldn't be there.
Click to expand...
Click to collapse
Go to About Phone and look at the build number on her phone. If it really took the full update it will say "ECLAIR.UCJH7". If it didnt it will still say "ECLAIR".
The very first time I tried to get the update OTA, it downloaded, then installed and it went to 100% on the install screen, but once it reached 100%, it then said "Update is failed". And when I rebooted it, the build number was still at "ECLAIR". and I still had PC Internet option and Quick Office wasnt installed and it acted kind of "glitchy".
When I downloaded and installed the zip file from Designgears, I could tell right away the the update was truly installed. Build number was "ECLAIR.UCJH7". PC Internet option was removed from usb options. Quick Office was installed. It ran a little smoother. GPS performance was somewhat better, and I did notice improved battery life.
Well, I've gotten my tablet for 5 days now and have been playing with it a lot, tried all the different ROMS, anyways, upon receiving the tablet, pretty much nothing worked, e-mail app wont launch at all, a lot of the stuff in the settings crashed when I try to change them, just figured something out today after going back to stock rom, I formatted the internal storage and did a factory reset. Upon startup, I notice that it went through a TnT wizzard which I never got when I first received the tablet, and e-mail and all other apps are now working, and no more FC (still crappy, but atleast it works). I really think this is the problem viewsonic has, the devices didn't come factory reset, or atleast mine didn't anyone else's tablet didn't run the setup wizzard when you first received it, or is it just me? Because I really think they would have a lot less returns if all tablets came and started the setup wizzard on boot up as mine didn't have any problems at all after the reset/format. I tried the 3361 update and wow, its actually decent now, VS is definitely listening to the community when they added the ability to use the regular launcher.
Original Rom
Where can I get the Original Rom?
da-slicksta said:
Where can I get the Original Rom?
Click to expand...
Click to collapse
FAQs are your friend
http://forum.xda-developers.com/showthread.php?t=842899
For the latest version of the stock fw, check out the thread whose title ends with 3316. The first post has a link to it, and if you read through the thread you'll find posts with instructions on how to load it with or w/o clockwork mod.
http://forum.xda-developers.com/showthread.php?t=879534
For the original fw, check in the dev forum, there should be a thread with instructions on how to revert to stock fw.
http://forum.xda-developers.com/showthread.php?t=861950
http://forum.xda-developers.com/showthread.php?t=842000
Mine did not perform setup wizard as the manual said it would on first boot. As others have reported, about 20+ FC on first boot. I will try the factory reset to see if that helps like it did for you.
UnRoot
Do we need to unroot to get OTAs
eviltuna said:
I formatted the internal storage and did a factory reset. Upon startup, I notice that it went through a TnT wizzard which I never got when I first received the tablet, and e-mail and all other apps are now working, and no more FC (still crappy, but atleast it works). I really think this is the problem viewsonic has, the devices didn't come factory reset, or atleast mine didn't anyone else's tablet didn't run the setup wizzard when you first received it, or is it just me? Because I really think they would have a lot less returns if all tablets came and started the setup wizzard on boot up as mine didn't have any problems at all after the reset/format.
Click to expand...
Click to collapse
When I returned my first GTab to Sears I did a factory reset. When the person at the store opened the the box and turned it on it didn't go to the wizard. I believe that the power button can activate during shipping and after a certain amount of time it skips the wizard and then shuts off. VS should put a piece of paper inside the box with instructions on doing a factory reset FIRST. This could solve a ton of problems for new customers
There's a new one out - just see the vanilla ROM's section in the faq, in my sig. I'm going to post a link to the new ROM, shortly.
roebeet said:
There's a new one out - just see the vanilla ROM's section in the faq, in my sig. I'm going to post a link to the new ROM, shortly.
Click to expand...
Click to collapse
I already gave them links to the FAQ, new stock fw, and two threads for flashing original stock fw...
To get the setup Wizzard you must first Format you Internal Storage (Settings -> Storage), then do a factory reset (Security -> Reset to Factory). Once you do this the gTablet will shut itself down, then when you start it up you will get the wizzard, just doing a factory reset alone will not do this, you must format the storage + factory reset. Anyways, all the FC I had prior to doing this are now gone, I really think that after doing Quality control at the factory, they never did these steps and so the tablet comes borked with bad softare which can easily be fixed with this 30 second format/reset.
Hey Guys -
I hope this is the correct forum to post this in - its the closest I could find...
After owning an Nvidia Shield (now "Portable") and loving it, I went ahead and purchased an Nvidia Tablet which came in 3-4 days ago. It's great except for that without the Controller (which is on Backorder ), you really can't do anything a standard tablet doesn't do.
Once updated, I rooted it and proceeded to install all the tools and apps I use. One thing I had always wanted to try out was the Modded Google Play. I saw that it had an installer so installed it and applied the modded version. Once back up, I had some difficulty with stability so went back to the original version installed (4.8.20.)
Since then, sometimes when I boot up, WiFi doesn't work and is disabled. I'm not saying I can't connect, but that it's in the "Off" position and greyed out to where I cannot turn it on! After a 2nd reboot, it would work again.
Yesterday, I rebooted and it was disabled again. This time, though, no matter how many times I restarted, it was still disabled!! I tried uninstalling / reinstalling Google Play a few more times as well as a few other reboots with no luck.
I will also say that I tried one more thing which may be the cause. I tried out Freedom to check it out, but it crashed when opening plus I found out it takes away functionality so uninstalled it. After uninstall, I found out the hard way that I had to rename my hosts file to get online working. At that point, though, WiFi would at least be enabled.
Any suggestions for what I can do? If I need to restore to OEM, I will - I just need to know the correct process as I am rooted. I'm on build KOT49H.20258_426.6902.
Thanks!
I had this happen when I first booted mine up. Then again when I unlocked the bootloader. I didn't do anything other then keep trying and it came on. It hasn't done it since.
Sent from my XT1060 using Tapatalk
Thanks for the reply. I ended up just performing a full reset and starting from scratch. At least I know what I want installed on it, now. That resolved the issue and it retained the root.
Thanks Guys
I was really worried about it, I chatted with nvidia support and they said to return it to the store. For whatever reason it started working, and hasn't done it since. I've seen a couple posts on it, so it might be a software bug.
Sent from my SHIELD Tablet using Tapatalk
I have a Pixel and recently received the 7.1.1 OTA update. This morning my phone restarted and failed to boot properly. It does boot, and I get to the home screen where all apps seem to be functional. But there are several problems, including 1) I can't turn on cellular data, 2) the home button and the task switcher button do not work. Also, when I press the back, home or task switcher buttons, I get vibration feedback which is not how I had the phone set. Another odd thing is that when I check settings, it shows that the phone is on Android version 7.1 It is as if the phone tried to revert back to 7.1, but did not do so fully. Another anomaly is that when I got to the Play Store, all my apps appear as if they are not updated, even though I just installed available updates yesterday.
When I go to System Update, it shows a 261.9 MB update available to download. I assume that's 7.1.1 OTA update. I could try downloading and re-installing it, but before doing so, I wanted to see if anyone thinks that could cause more problems. Or, does anyone have another suggested step I could take. I would like to avoid a factory reset, if possible. Hopefully, there's another simple, quick solution.
Most likely it is easily fixable by just flashing the full stock 7.1.1 image from Google. Unfortunately it will wipe your device, but it is basically a surefire way to fix whatever went wrong.
It sounds like what happened is the OTA failed somewhere, bad download etc. As the pixel has the dual partitions if an OTA fails it will revert back to the last known working system. As @renegadeone8 mentioned, flashing the full 7.1.1 zip should cure your issues. You will have to unlock the bootloader to do so. (No a bad idea anyway imho Incase you have errors)
No harm in trying the OTA again. If it fails you won't be any further behind than you are now.
I'm having very similar issues, I also have no notifications and cannot pull down the full drop down menu or turn my data back on.
Thanks, k.s.deviate. I wish I had read your response earlier. It probably would have been good for me to at least try re-installing 7.1.1 again. However, I read from users on a different forum that they had experienced odd behavior very similar to what I experienced. In their case they didn't realize, at first, that the problem was associated with the 7.1.1 update. So, they re-installed it. Unfortunately, they had the same problems re-occur. For them the only solution was a factory reset and then not downloading 7.1.1 again.
That's what I've done. Everything is working great now. Android shows the 7.1.1 update available. Based on your assessment, I'm partially tempted to try installing it again. However, if it does end up with problems again, like it did the first time, I don't feel like I have the time to go through the whole factory re-install process again. So, I'm just going to stick with 7.1 for now and wait until either 1) I feel I have more time or 2) Google releases another update (7.1.2 ?) that might fix this problem. Thanks, again, though for your feedback.
exactly same here, so bad download could be ruled out. Also I've seen discussion on reddit and google forum, but unfortunely no solution was presented