Related
Everything was great.. did the update rebooted gtab worked great. Has always been stock. I shut it down and when I got home from work i hit the power button and I get the viewsonic birds then the tap n tap logo then the n just stays there and that is it has been stuck on the n for hours. I turn it off and back on and the same thing. Any advice would be appreciated.
Thank you
Have the same problem on stock Gtab.Mine gets to the birds and sticks.Tried holding power and volume up at the same time, but won't reset.Can't discharge the battery because it still goes into sleep mode after 10 min.Computer won't read when plugged into USB.Bought on Woot so a return will be a major p.i.t.a. I am new to Android devices
and was just getting enough balls to try rooting and flashing!!! FML
Yea bought mine from woot also... I liked the stock rom was also afraid to try to load a new rom. Looks like I will be sending it back
hvideo1 and sepder,
You have a choice to make. What both of you have is called a "boot loop".
Sometimes they happen because somebody does something wrong -- and
sometimes like in your case they just seem to happen.
You can return them if that is your desire -- or you can try to fix them.
Usually if one partitions the tablet and cleans it up, it can be fixed. But
that means you have to do some quick learning.
First, you have to get back to a fully stock, hopefully working version. Look
at the following procedure -- which we wrote hoping everyone would be able
to understand and use:
http://forum.xda-developers.com/showthread.php?t=861950
If you complete this procedure and the reflashed stock version works, then
we can load a program called CWM and do the partitioning and cleaning. If
the boot loops persist, then a second choice is to nvflash CWM and use it
to partition/clean up.
http://forum.xda-developers.com/showthread.php?t=865245
http://forum.xda-developers.com/showthread.php?t=1030042
The threads above give you more info on the various procedures.
Post back here what you decide to do or if you have questions.
Rev
I would try a simple data wipe first. Much easier and less invasive.
http://forum.xda-developers.com/showthread.php?t=1030915
Thanks for the replies. I don't want to send my gtab back so I'm reading both post and going to see what happens. I will reply back (hopefully with the gtab) Thanks again
I'm in the same boat as hvideo1 and sepde
Already tried the nvFlash first method mentioned by butchconner but can't get past the "Booting recovery kernel image" message, just sits there on the viewsonic splash.
Going to read and try the "CWM and do the partitioning and cleaning" next.
Appreciate everyone's help!
lrgche,
To NVFlash, you have to press Power/Volume - to activate APX. It will usually come
up with the white screen and then turn black.
"Booting recovery kernel image" indicates you may be pressing Power/Volume + , which
starts up Recovery -- a different process.
Go back through the procedure again and double check that everything is right and
it should work.
Rev
K J Rad said:
I would try a simple data wipe first. Much easier and less invasive.
http://forum.xda-developers.com/showthread.php?t=1030915
Click to expand...
Click to collapse
This worked for me. Thank you back up and working. the only reason I didn't go the other way was because I didn't understand alot of reading and just confused me (not hard to do)
Lol. Thanks to both of u
hvideo1 said:
This worked for me. Thank you back up and working. the only reason I didn't go the other way was because I didn't understand alot of reading and just confused me (not hard to do)
Lol. Thanks to both of u
Click to expand...
Click to collapse
Glad to help. You should learn that other procedure if you plan on doing any serious modding in the future though. It may become necessary next time.
(android.process.acore has stopped unexpectedly. Please try again. FC.) Seeing this message constantly, can't get into settings to reset g tab to factory settings, can't pull up keyboard, can't get into any of the recovery modes, etc...
Tried to nvflash g tab with no success, not sure what the problem is and I'm at my wits end, PLEASE HELP ME, ANYBODY!!!!!!!!!!!!
Not sure what ROM you're using but if you can get into recovery mode you can access Fix Permissions from there.
Advanced > Fix Permissions.
I tried pressing the power and volume+ at the same time, it goes to the recovery image, then directly to completeing the boot process, it won't let me into the recovery mode. Ant suggestions?
Have you got clockworkmod installed?
No sir. But I can't get into recovery mod at all, nor settings, keyboard, nothing.
http://forum.xda-developers.com/showthread.php?t=896395
You need clockworkmod first.http://forum.xda-developers.com/showthread.php?t=865245
I can't get into recovery mode to install clockworkmod with the tablet nor can I get into or access settings, contacts, calendar, keyboard, because each time I try to access the things listed, I get the same error message; the process android.process.acore has stopped unexpectedly.please try again.
Sent from my PC36100 using XDA App
duplaine1 said:
(android.process.acore has stopped unexpectedly. Please try again. FC.) Seeing this message constantly, can't get into settings to reset g tab to factory settings, can't pull up keyboard, can't get into any of the recovery modes, etc...
Tried to nvflash g tab with no success, not sure what the problem is and I'm at my wits end, PLEASE HELP ME, ANYBODY!!!!!!!!!!!!
Click to expand...
Click to collapse
You say: tried nvflash with no success, means you cannot nvflash your tablet or you did but this did not help? I assume you cannot finish nvflash...
Btw, what ROM is in your gtablet?
Im not sure, w/o being able to access the system of the tablet, Im really not sure. Everytime I try to access the system for things like settings, contacts, calendar, I continue to get the same message in the post above. The onscreen keyboard won't come up either.
Its your contacts. If you can wipe your contacts it will go away. Sometimes when syncing your contacts partial data gets sent and is displayed as unknown. This contact has no info and causes s the process.acore problem.
You can even just delete the corrupted contacts and it will go away.
If somehow you can get to settings,apps,manage apps, then select the contacts app and clear cash and data.
Good luck. You can do this, just take your time and use fast fingers.
you can try in adb:
adb shell rm /data/data/com.android.providers.contacts/databases/contacts2.db
Does anyone else know of a way to gain access to contacts, tablet settings, onscreen keyboard, or calendar, or for that matter, delete corrupted contacts?
A little bit more help Vald_z, what is adb?
ADB info is:
here
Info for newbies:
List of Important Links
duplaine1 said:
A little bit more help Vald_z, what is adb?
Click to expand...
Click to collapse
If you cannot get into settings or some kind other file manager normal way and delete this contact database then ADB might be your chance. ADB stands for Android Debug Bridge.
Basically you connect gtablet to your PC and if PC got SDK driver installed you can access your tablet file system through ADB command.
PS: I thought that since you were talking about nvflash then you already know about ADB. Well, also nvflash should recreate all partitions on your gtablet. When you run nvflash, you should see kind of progress messages and it should finish without errors then you might be sure you nvflashed your gtablet.
On other thought, nvflash doesn't touch partitions on SDCARD and I don't have my gtablet at a moment to verify where DATA partition is.
Could nvflash cwm and have cwm clear cash or factory reset data. It will take you about half an hour to read up on it and about 10 min to setup and flash.
Oh and in the future, checking the contacts and deletion of the unknowns should become part of the flashing a new rom process. If you have gotten it once you will get it again. Its corrupt data on Google's side so any time contacts is synced they could pop up. Turn of auto sync contacts and check your contacts first thing after you boot up a new rom.
You can install CWM via nvflash
http://forum.xda-developers.com/showthread.php?t=1058649
Ok, I did the pwr vol+ to get into recovery mode,( with the birds, gtablet, tapntap, n, ), I get the recovery image, then it reboots ( with the birds, gtablet, tapntap, n ) and directly to the classic home screen, never going to the actual recovery screen to manipulate the tablet, why is it doing this and what can I do to get it to go to the recovery screen? I can't do CWM, or know if I've loaded CWM on the tablet. I know I've asked alot of questions, and I apologize, but I'm really trying to follow all the instructions give by all of you, and I really do thank you all, but I'm really determined to get this tablet working properly and enjoy the benefits of this tablet and all it has to offer. I'm still getting the same FC message as I've stated at the beginning of my thread. The ROM I think that's on the tablet right now is TnT 3588, still no keyboard, settings, or contacts access. I've even tried starting from scratch, and will probably try it again before someone answers this post. Please don't give up on me guys, I'm determined to get this right just need some coaching from you. Thank you so much for all that you've already done.
duplaine1, it doesn't sound like you've tried installing CWM via nvflash.
http://forum.xda-developers.com/showthread.php?t=1058649
You will need to power on the tablet using POWER and Vol-. Either create a batch file with the command or run the command as in the post. If this doesn't work, based on your original post, you are wanting to do a factory reset, so you can use the following post to flash your tablet to stock ROM
http://forum.xda-developers.com/showthread.php?t=861950
From there you can load CWM and either stay at BL1.1 or upgrade to BL1.2.
Also, when you are doing this make sure you are installing the correct version of CWM to match the ROM you are installing (or have installed). I have 2 Viewsonic G tablets and I discovered the hard way I had to use the file in the nvflash deprecated folder on one of them.
Your recovery is borked. You need to nvflash. Its not hard just read the instructions on Gtablet for dummies.com
Update: Hallelujah, we have seen the birds!
Just for future reference to those of you who may be stuck in an "APX loop", where NVFlashing and even repartioning do not work for you. I tried many things, and only one thing worked.
Didn't work:
1) NVFlashing to anything
2) Repartioning or wiping
3) Wiping out all storage on the SD card
After doing many, many rinse and repeats on the above, the only thing that did work were these instructions:
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Click to expand...
Click to collapse
Now, I don't know of too many cases like mine where APX was the only thing that was working and that no amount of CWM or NVFlashing could bring back whatever was wrong with the bootloader, but this method forced a recovery image restore and got me back to the point where I can now power down and reboot. And for that, I thank this fine community!
I think we need a better guide somewhere on... Stages of recovery. If this doesn't work, here's the next deeper level. (Example: Level 1, wipe data/cache and reflash the rom. Level 2: Repartition and fix permissions. Level 3: NVFlash for 1.1 or 1.2 back to stock. Level 4: run the steps I have listed above. Level 5: fixing the bootloader. Level 6: Remove the case cover and short the back.)
Anyways, thanks again guys. Hopefully someone else will search with the same issue I had and get fixed as I have.
try this (not a developer here) when it boots up use your computer to delete all the files on the sd card so it looks blank- not sure if it will fix your issue but if there is a file on there messing your reboot into cwm that should will get rid of it. let me know how it goes. (standard at your own risk disclaimer) i have done this before just to see what would happen and nvflash brought it back up.
Hey, thanks for the reply. The sdcard was already blanked out through my various steps, so that doesn't appear to be the problem. Same things happen.
Now, that's just the app data and such on the sdcard, so I am guessing if I was able to see/delete all the system files instead via USB and delete it that way, I'd see something else.
just to bee clear i would delete everything on there not just the system files- so when you go to the drive from your computer it shows nothing at all.
here are the steps i would take start to finish.
1 nvflash rom
2 connect to computer, mount usb, then highlight and delete all files on gtab.
3 nv flash again (preferably with a stock rom with cmw pre loaded
4 reboot and pray that this fixed it.
OP - What size is the nvflash file you are using? I have run into a similar issue before with the larger nvflash.exe (like 152kb). It should be 140KB.
Just something else to check.
So to clarify, when you nvflash the 3588 stock image, it will automatically reboot at the end of the nvflash_gtablet.bat batch file?
pugsby said:
Hey all. Little frustrated since I've tried most of the tricks and still have a soft-bricked device. Not sure how it happened originally, but one way or another, I have a bad bootloader and no access to CWM.
APX works. I can NVFlash 1.1 or 1.2-based Stock or otherwise roms, and they boot (once, and only once...) . I can get USB mount. I've tried them with and without CWM pre-installed and see no differences.
But as soon as I reboot or power off, it just returns to APX mode. It is only a black screen, however. No birds, no logo, no nothing. The only way to make it boot again is to NVFlash it again.
All the instructions say to enter CWM to re-partition or to wipe data. That's great, but I have no access to CWM. Pressing the buttons during bootup does nothing because the device never makes it that far through bootup. And the format utility doesn't wipe enough data to return this back to a truly blank device, because when I nvflash, my apps still show to be there and I want it back to a blank slate.
I've tried pressing the buttons directly after a NVFlash to enter CWM that way, but it just goes straight into the rom.
Others have suggested popping off the back of the case and grounding out things to reset that way, but I thought that was just if APX didn't work, but APX is the only thing that DOES work, so not sure if it applies. (Let me know if I'm wrong there)
More things to try?
Click to expand...
Click to collapse
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
After you repartition, wipe data, clear cache, etc. it might still loop into APX. If it does you'll need to force it to install a new bootloader. I'll dig up a link to the procedure if you need it.
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
K J Rad said:
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
Click to expand...
Click to collapse
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Acidburn find out a solution for this problem
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
K J Rad said:
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
Click to expand...
Click to collapse
This got me into CWM (Yay!). This, however, did not fix the APX looping (boo).
I repartitioned, wiped, nvflashed, wiped, repeat. Even though I have more options now with CWM, the end outcome is still the same that after the initial boot, it won't boot again.
BUT, I did find a working method. See the original post.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I was hoping you'd respond, goodintentions, as I used your NVFlash files and instructions this last time around from your very handy site.
I'm not sure exactly what happened. I do know that Rom manager was involved somehow, trying to use that integration with recovery. (I know, not recommended, but at first it acted like it would work).
Also, I think a 1.2 Rom was mistakenly flashed on top of a 1.1 bootloader somehow.
The details are fuzzy. It's been so many things since then that who knows..
goodintentions said:
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Click to expand...
Click to collapse
I am a tech. Been working with/on/in electronics and computers for roughly 35 years. I had a hard time believing the problem was real until I had one in my hands that was doing it. I've tried doing it to my own tablet but a simple nvflash always got me going again.
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
Click to expand...
Click to collapse
This is successful in some cases but not all. In some cases the bootloader has to be updated using factory stock recovery. ClockworkMod and nvflash don't update the bootloader (and I suspect some other system related partitions/information) properly. For those cases the fix is a little more complex. This process...
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
has worked on all but one of the tablets I've recovered. The odd one out required an extra reboot (though I was doing the steps from memory and on an unfamiliar computer so I could be mistaken). However... as noted above... a subsequent nvflash of even the same image resulted in another APX loop. The end result was I had to craft a custom nvflash for each of those machines to avoid the problem in the future. That may or may not be necessary for all cases but since it's relatively easy I just do it out of habit now.
Keep in mind that serious APX looping issues are very rare in the grand scheme of things. Many times folks get confused and fail to follow directions properly and think they have a bigger problem than they really do. The overwhelming majority of times a simple nvflash and repartitioning will fix these things right up.
Added: BTW, the best way I've found to avoid the APX loop issue entirely... do a data wipe before you flash a new ROM and then again immediately after and before you boot it for the first time. I know... one should be enough... but if you make it a habit to do two... then you'll probably remember to do at least one of them ;-)
Great info. I shall try not to enter another painful APX loop. I was shocked how many things I had to try and places I had to go before I found a working method. I guess I really did a number on this thing somehow. But I'm happy that it's back.
I didn't have to do the more painful one you mentioned, but honestly I was ready to try about anything short of slaying a dragon.
I have a tf201 and it was fine until a week ago. My company forces me to have it encrypted (it's my own though). My kid has now rooted it but more importantly it turns out he had done the Asus unlock.
I don't know anything about rooting, unlocking or roms
What can I do to either keep getting that Asus updates - I'm happy to manual install as I've read OTA is no longer an option for me.
Alternatively, how can I reset it and apply a custom Tom that is exactly the same as the asus rom? Step by step total idiot guide needed - remember that it is encrypted.
Many thanks in advance
Anyone help? I can't even reset to factory default to unencrypt my device. it just goes back into CWM when it boots and gets stuck in a boot loop.
Any help please - I'm desperate
No, nothing you can do. Give it to your kid and buy another one.
Fixed It
adb shell
wipe all this wiped most stuff but not everything
Managed to do the "wipe" option at boot up (press down vol + power, leave go of power - etc...). then chose left icon. that did a wipe as well.
Hey presto - no more encryption.
into CWM recovery - all options working now - wipe data doesn't error anymore yippee
installed Virtuosa again and blow my socks off - everything is working - INCLUDING ,my WIFI.
Moral of the story - never give up, and never believe things cant be done just because people say they cant. Persevere and you shall overcome, or have a nice brick door stop that cost a lot of money - hehe
froodle said:
My kid has now rooted it but more importantly it turns out he had done the Asus unlock.
Click to expand...
Click to collapse
Aside from the obvious (to not let your kid have at your TP), the bootloader unlock requires your Google login. If you didn't share it with him/her, you may want to change your password or enable 2-factor auth
I have gotten a g tab from my father in law after he tried to fix it and ended up buying a new one saying "if u can fix it you can have it" I have tried for hours and days to fix it on my own and have now tried to reach out for help
Basic problem:
-When I got the device it would boot to birds and go to g-tablet screen and no further
-Found viewsonic gtablet for dummies tried nearly everything (i believe correctly)
-Called G Tablet Support and got the "send it in to us and we can add the correct software for $60 if there is no problems otherwise the $$ may go up"
-went back to trying to fix on my own
-failed
Basic info:
-able to NVFlash with 0 errors on any packet
-can boot to g-tablet screen but no further
-can boot power & Vol+/vol- no issue
-cannot partition
-cannot wipe data/ factory reset
-can install zip from SD
Help! any ideas are worth a shot when it means (possibly) a free tablet. Eager to fix and try most ideas to get this thing fixed!
Also, This seemed to me a repost but i have looked at, tried, and failed to fix with several different posts/ideas from this site
I've seen a number of posts suggesting that you power off, open the back, pull the battery, wait a few minutes, plug the battery back in and turn it back on. It seemed to work for a number of people.
There is also a reset switch under the back cover.
I honestly don't know if one of these will work, but it's worth a try.
Can't suggest which rom you might try, since there's no way to tell which bootloader you have (v1.1 or 1.2).
I'll have to try pulling the battery plug tomorrow I don't have small enough tools. But I do know that im running 1.2 got that much outta tech support before they went grabbing for mytwallet lol
Here's a thread that explains how to open the GTab. http://forum.xda-developers.com/showthread.php?t=994881
If you are on 1.2 (and are absolutely sure) you might want to start with http://forum.xda-developers.com/showthread.php?t=1525424 to get the latest recovery ClockWork. Do this after you "pull the plug".
If it doesn't work after that, come back and let me know and I'll try to do some more troubleshooting with you. Since you said you actually had NVFlash working before, this might actually get you up and running on the latest stock rom. From there, you can move up to just about anything you want, upto and including Ice Cream Sandwich (ICS). Just remember to check the forum information about what does not work. For example, if you move up to Gingerbread (3.x) or greater, there is a pretty good chance that you won't have camera or mic support at this time. Some roms don't support hardware acceleration at this point, but many do.
Anyway, come back and let me know how it went.
Awesome thanks. I'll be getting into that soon (after I finish cleaning) just wanted to thank you for your interest in helping me
Hey! finally got around to it but pulled the plug and grabbed that cwm recovery u had linked but i'm still hangin on the g-tablet screen. any other ideas?
I'm guessing that the tech support for GTab was wrong and you actually have a 1.1 boot loader.
Try following the thread here http://forum.xda-developers.com/showthread.php?t=974422 on formatting the gtablet and starting over from scratch.
Gregwa
what 1.1 should i use?
Cmdrbubbles said:
what 1.1 should i use?
Click to expand...
Click to collapse
There is no reason to go out of the way to figure out what Bootloader you have. the NVflash files that you found on the ViewSonic Gtablet for Dummies guide will be your best bet. If you can get grab the NVflash files that include CWM recovery those are the ones you need. After NVflash is complete and you see the Gtablet splash screen press and hold the power button till the tablet shuts down. Once shut down you need to reboot into recovery by pressing down the volume + and press the power button to boot up. That should get you into CWM where you need to do a wipe data fatory reset, wipe cache and also wipe dalvic cache under the advance menu. Once that is complete then you need to back out to the main menu in CWM and reboot. Make sure that you do not select Reboot Recovery. Give the device some time and it should boot into the Stock TapUI where you can mess around with it from there.
I would choose 1.2 build 4349 w/CWM preinstalled (Old) NVflash file found here http://viewsonic-gtablet-for-dummie...65610&fw_sig_premium=0&fb_sig_network=fw#2310
Many times in the past the wipe data/ factory reset and wipe dalvik and most anybody those options lock up the tablet. It will just hang on the screen (depending on the option chosen) and not move from there for hours on end... Thoughts on why? Hoping not a hard drive problem
Cmdrbubbles said:
Basic info:
-cannot partition
-cannot wipe data/ factory reset
-can install zip from SD
Help! any ideas are worth a shot when it means (possibly) a free tablet. Eager to fix and try most ideas to get this thing fixed!
Also, This seemed to me a repost but i have looked at, tried, and failed to fix with several different posts/ideas from this site
Click to expand...
Click to collapse
You will need to get your partitioning working. You can boot into recovery? And what happens when you attempt to partition.
If you are able to go past the 3 birds splash screen and see the gtablet screen, then you're on the stock ROM and the problem is most likely with the partitions on the internal SD card (or the card itself). In which case, nvflash will not help you.
Set up ADB and then run these 2 commands and post the output after you've tried one of those operations you mentioned in your 1st post:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
C:\SOME|PATH> [B]adb pull /tmp/recovery.log[/B]