(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
Related
Just purchased a used G-Tablet from ebay.
Started it up for the first time, and on the initial device setup ( setting up the date ) I get the error: "android.process.acore has stopped"... and I forceclose it.
When I goto the next step ( wifi settings ) the same error message happens again... and again... and....
After the last step, it happens again, and then goes back to step 2, and repeats and I cant get past the set up screen....
Anyone have this problem? Know what to do... I tried the power button + volume up to reset and that didnt work. get the same error...
Any possible way to save it, if it is stock and has no mods (to my knowledge) ?
Thanks - G-Tab N00b...
It an issue with contacts data. You need to clear the data from contacts storage to stop this from happening. Easiest way to do this for you is to install CWM recovery and factory reset your gtab. Since you don't have any data to loose at this point wiping data and cash (factory reset) is an easy fix.
Check this link out for easy step by step instructions to get CWM installed.
http://viewsonic-gtablet-for-dummies.webs.com/
You can also search the forums with the search button for android.process.acore and find many threads detailing what causes this issue.
Thanks, that was going to be my next step, but Is there anyway to know which branch I have, since I cannot get into the system?
Thats tricky. I would say have nvflash ready just in case. There isn't really a way to tell that I know of unless you can get to system. Lucky for you the link above has nvflash instructions too.
If you hold power volume + at boot and it doesn't bring you to a recovery screen with selectable options for factory reset your most likely on bl1.1. As far as I remember 4349s stock recovery had a menu that had that and 3558 didn't.
There is no menu in recovery, so I guess I'll try 1.1...
Thanks for the help!
Hopefully I'll be up and running soon, and can officially join the community!
Good luck! Your already official, you got a good screen name, posted a valid question. Not only that but you were completely respectful in asking and graciously mashed the thanks button when helped. That's the way we roll here in the gtab forum
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.
Hello, after playing with a tablet I got boot loop so below is solution for this.
This is what I wrote first:
I purchased Chinese tablet called CyberNav, there is link to the website with specs http://www.dracotek.com/cybernav-7-...ps-navigator-ultra-slim-wifi-8gb-gps70yw.html It works great and is worth the money. I received- on request- firmware for it, but it is with .img extension and I have no idea how to get to the files. Attached application PhoenixCard should install it on sd card but it does nothing. So there is my question- can anyone help me with it? Possibly root it? Or update to newer firmware version? I'll post a link to, just need to upload it to my dropbox on my next break at work.
Sek
im pretty sure you need a 3rd party application to flash that firmware, i think you load the .img file into the software on your pc, connect tablet in flash/recovery mode then flash it that way, dont know which software you would need to use though , sorry i cant help further
There is link to rar package http://db.tt/jm7eHfbq
If there is someone who wants to spend some time... Please help.
Bump
Some new infos:
As far I found out tablet is detectable during boot in adb, but it stays in boot loop. I think I've got right usb drivers.
I tried unyaffs the .img file using C:/unyaffs/unyaffs pw08.img but it shows file corrupted (might be wrong method?).
Logcat attached.
Maybe there is someone who will find what it's missing...
I see there is nobody who can help me, so... If some of u have similar problem with chinese tablet- bootloop, can't flash it with LiveSuit our update from sdcard, I found solution which worked for me. Using adb, pulled catalog /dev/data/ to hard disk, then deleted all dalvik cache, installed by me apps and almost every other file from /data on my hard disk. Then typed adb remount, then adb shell rm -r /dev/data/* to delete all data catalog on tablet. Then pushed /data catalog from my hard disk to tablet, and finally adb reboot. And it WORKS! Booting without problems. I wasted 4 days on research how to turn it in flash mode etc. But it was very simple.
Cheers
Sek
Hi, sek111
It was necessary to use the LiveSuite to flash through usb.
Thank you very much, from your post, I found the firmware for my tablet.
An experience with another low cost tablet with Bootloop
I happen to got my tab (Wammy from WickedLeak.org) stuck in BootLoop and was struggling to get a way out for the past 3 days, checking almost all of the posts for this issue!
The tab would stuck on the android loading animation despite running for 2-3 hours and after several hard reboots, it throw-ed following error-
Encryption Unsuccessful
encrytion was interupted and cant complete. as a result the data on your tablet is no longer accessible
to resume using your tablet, you must perform a factory reset. when you set up your tab after the reset, u'll hav an opportunity to restore any data that was backed up to ur google account
Click to expand...
Click to collapse
Despite going for the factory reset, it still didn't workout as the reset activity never completed or proceeded. I happen to be a beginner/noob and was trying my luck with possible solution but was comfortable with ADB stuff and workaround. Well i checked the solution which sek111 offered in this post and it was most closely helped me out. So i would like to Thank him a ton for sharing his solution.
Another method for few others if you don't get through the technical stuff and handling all the flashing tools, i was successful in bringing up the setting window of my tab and chose to do Reset via GUI which worked. Actually my battery got drained out to 7% and a popup message for same displayed while i was on the above error page. I selected the "check battery" option from that pop up and got my way out via factory "Backup and Reset" option under settings.
I hope this might help few people if not all! But the XDA forum is great and everyone will find a solution here. Cheers!!!
So I got this wm8850 chinese generic tablet. The camera is in the front in the middle (wide). It was shipped to me with 4.0.3 in boot loop. I soon found out that it boots into safe mode when I usb to pc. This is the furthest I've gotten with it so far. I can adb into it and have already tried to wipe data. It seems like since its from factory screwed up that a may need to reload the firmware or the os or something. Im kind of a noob because I only have my droid x. I've gotten it out of a boot loop before but I also knew what I had done to cause it so I fixed it. I tried to follow seks adb commands but im too noob to do it I guess. I was able to wipe data and dalvik-cache. Issue still occurs . If anybody can give me some adb commands than can help I would greatly appreciate it. Im fairly sure that I found the firmware elsewhere on xda. I thank you guys for any help at all you can give. I don't wanna send it back without trying everything software related as I can, but ill send it back if I can't fix it or if I brick it
Sent from my DROIDX using xda app-developers app
i have same problem in my china mobile.. dupad k1 ... after in installed new boot screen, device stuck in boot... please help to recover my device in step by step....
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]
Hi there, i'm only really posting this out of desperation, I'm at my absolute wit's end with this tablet and i honestly can't suss out what's wrong with it anymore
I followed http://forum.xda-developers.com/showpost.php?p=20032494&postcount=2 to try and install CWM and it worked, CWM is running and uses 6.0.12 i believe the version is without looking.
UNFORTUNATELY now i can't access anything via CWM, i can't mount, open or format any of the internal stuff like system, cache, log, emmc ect. I've tried reflashing different versions of CWM with no success via ADB, they just quite simply don't seem to be taking hold no matter how many times i reboot or reflash and also i can't boot into the OS anymore, which really sucks since it won't accept anything i try flash to it.
Now here's the real slap in the testes, The original firmware recovery seems to be now gone meaning i can't put the device into software update or firmware recovery or anything to try flashing with Livesuit, i'm sure there's something i'm missing somewhere can anybody help? Livesuit definately detects SOMETHING is going on when i hold the volume buttons and hammer the power button, my system beeps and LiveSuit pops up, but it only displays a blank error message which i'll take a screenie of, from there it refuses to do anything else.
I've also tried using USBDeview or whatever it's called to remove every trace of a driver related to anything remotely Android and gone that route but no luck again.
I've looked into and read (and re-re-re-re-read) every single post i can find about this but the threads have either gone or died out
EDIT - Another quick think i forgot to mention was that if i try to view the partitions or hardware info via ADB i get extremely limited info back which i'll post in as well when i get chance