I tried to flash the Calkulins rom and after i flashed, all it will do is power on to the white viewsonic screen with the birds and in red tiny letters at the top it says "magic value mismatch" ....and it will do nothing else, any suggestions?
vballrkc said:
I tried to flash the Calkulins rom and after i flashed, all it will do is power on to the white viewsonic screen with the birds and in red tiny letters at the top it says "magic value mismatch" ....and it will do nothing else, any suggestions?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=861950
x2 -- you need to nvflash. Did you use a newer version of clockworkmod, ie from ROM Manager? Then FYI that this is a known issue.
ok guys, thanks for the replies, i appreciate the help, and yes i used clockwork to flash, my bad i guess i didn't read enough, won't make that mistake again.
I'm trying to get the nvflash process to restore my gtab and i'm not getting it, i'm using windows 7 and the directions in the link i was given are not step by step enough for me, is there a post that has a really good step by step for newbs? or is there someone who wouldn't mind spending a couple posts with me to get it fixed? thanks alot guys.
vballrkc,
The following two threads are all you need:
http://forum.xda-developers.com/showthread.php?t=861950
http://forum.xda-developers.com/showthread.php?t=989320
The first one gives you two folders to download and extract. Put them in
an "NVFlash" directory. One is the nvflash files and the other is the
stock .img files.
The second gives detailed instructions -- my post on using the Advent Vega
USB Driver with APX.
Once you get all the files into the NVFlash directory,
all you have to do is run the .bat file -- it will flash your
G-Tablet with the stock bekit 1105 files -- and without
stopping will reboot all the way to the main screen if
things go right.
When you get there you are on update 2637 I think I
remember. When you get wifi up, it will automagically
ask you to update over the air (OTA) to Update
3588 -- which is the current stock level.
Stick with these two threads and you should do fine.
Rev
ok i know it's been about a week since i had this problem but work and family has been busy so i'm just now getting to to this but thank you all so much for the input, i've gotten farther with your help then anyones elses. after i do everything you told me, and then i put the tablet in apk mode, plug it in, my computer recognizes it, then i go to run that .bat file and it brings up the black window with white letters and says "nvflash configuration file error: file not found press enter to continue......
what now? again, thank you so much for your help so far
Did you extract both archves to the same directory?
vballrkc said:
ok guys, thanks for the replies, i appreciate the help, and yes i used clockwork to flash, .
Click to expand...
Click to collapse
There are several versions of CWM. Depending on the ROM you are flashing, you need to use the right one.
Rumbleweed,
He doesn't need CWM right now. We're working on getting the nvflash
recovery done.
vballrkc,
Never saw that problem before. My best guess would be that something is
wrong with the files nvflash loads.
I would:
1. Erase all the files in the NVFlash directory.
2. D/L the two .zip files again to make sure we have good copies.
3. Make sure you extract both .zip files into "NVFlash". (When you
look in the directory after the extract, you should have a bunch of lib* files and the nvflash.exe file. You should also have a group
of .img files with the images for the partitions. And you should have
the .bat file that runs it.)
4. If all of that checks out, I would try running it again and report
back.
Hope this helps,
Rev
If any Wooter has nvflash skills....
If any Wooter has nvflash skills, could you backup your partition info and post it? I'm curious if it's the same as our original devices.
We know that there are some GTABs with swapped partitions out there, so we honestly don't know if that's the case here or not. In hindsight, I almost wish that I had bought one just to rip it apart. Oh well, too late now....
roebeet said:
If any Wooter has nvflash skills, could you backup your partition info and post it? I'm curious if it's the same as our original devices.
We know that there are some GTABs with swapped partitions out there, so we honestly don't know if that's the case here or not. In hindsight, I almost wish that I had bought one just to rip it apart. Oh well, too late now....
Click to expand...
Click to collapse
What kind of skills are necessary? I haven't received mine yet, but I'm very computer literate and have flashed a phone or two in my day. I would be happy to help contribute to such a great community if I'm able.
ok wow, help please, i just tried to put it back into apk mode to give nvflash another go, and it freaking went into clockwork recovery, this is great right? what do i do i'm afraid to do anhything so i've just got it sitting here on my couch waiting to be told what to do....
update: ok i rememebred i had all my old roms on there still (vegan, tnt ligt) so i'm just flashing the vegan, should i do a wipe and restore just to be safe?
new update: Everything's fixed, i think, so far. Booted right up with a factory wipe and flash of vegan. Thank you all for your help and continued patience with a newb like me, it's people like ya'll that make it possible for people like me to have devices like this and trick it out. thank you guys again
vballrkc said:
then i go to run that .bat file and it brings up the black window with white letters and says "nvflash configuration file error: file not found press enter to continue......
Click to expand...
Click to collapse
ok, after experiencing the same error, and then about an hour of repeating the instructions over and over and freaking the f*** out, I found that the problem was that the instructions do not clearly state that all the files need to be in the same folder (strictly speaking). It says 'extract them to the same folder' or something like that.
Basically I ended up with the contents of nvflash_windows_20100500 in the NVFlash folder, and (most importantly) the contents of nvflash_gtablet_2010110500 in a subdirectory of NVFlash called nvflash_gtablet. It was this subdirectory that was screwing things up.
So the lesson is ..... all files in the same directory and no subdirectories.
But the rest of the instructions were top-notch, and thanks muchly. Now restored and can try to flash Cyanogen again
So I followed the instructions, and suprise suprise, I get an error -
Nvflash started
nvflash configuration file error: file not found
An error occured. Read above lines for details
Help please
Hybrid did u figure it out yet?
Sent from my Malata SMBA1002 using Tapatalk HD
Related
Hey xda forums, first time poster, long time reader. I rooted my Nook color from these forums and find them to be most informative. I just got back from hiking the Grand Canyon to find my G Tablet waiting for me from Woot.
As I did with my Nook, I immediately started to replace the stock rom with Cyanogenmod 7 beta. I followed the instructions on the Wiki, including installing Gapps, by putting them on the internal SD and using CWM to install from zip. After everything was done however I am now stuck at the Viewsonic splash screen. I tried to read thru the Googles and tried reflashing back to stock by way of some instructions on DroidPirate I think it was, to no avail. I can't even see my external SD card to load the update to recover. Please help. Anyone?
I would get nvflash set up with bekit's images and flash that to get yourself back to a working stock image. Follow the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=861950
After that, put Clockworkmod ( v .8, get it from development forum) on it and repartition your sdcard to 2048 and 0 then you should be ready to flash.
Then get a ROM from the development forum here, there are some based off cm7 (gingerbread builds).
I was hoping not to have to use NVflash cuz people report problems with the boot loop, however I havent found any other option so far so I guess i'm trying that. Thanks for the link.
Xxlgeek,
Every time I hear boot loop I think re-partition -- because most of the time that
seems to fix the problem.
I agree you should NVFlash to get a stock version working. Then install CWM so
you can partition -- and the do the Fix Permissions, Wipe Dalvik Cache, Wipe
Cache, Wipe Factory Data.
With that I would try to wind up with a stock machine and let it OTA up to 3588.
I wouldn't load another Alternate Rom until I knew my tablet is working good and
until I know a lot more about the roms and how to work with the G-Tablet.
IMHO.
Rev
I can actually boot into CWM right now. I already repartitioned and wiped all the caches. But when I try to flash Cyanogenmod 7 again, which is on the root of the internal memory, it just does the same thing, won't load past splash screen.
Xxlgeek,
If it didn't work, I would erase the Cyanogenmod 7 file -- and I would go back to a stock rom until I could make sure all the hardware is working right and the system
is stable.
When you know the tablet is good and stable, you can always download and re-do.
Rev
Xxlgeek said:
Hey xda forums, first time poster, long time reader. I rooted my Nook color from these forums and find them to be most informative. I just got back from hiking the Grand Canyon to find my G Tablet waiting for me from Woot.
As I did with my Nook, I immediately started to replace the stock rom with Cyanogenmod 7 beta. I followed the instructions on the Wiki, including installing Gapps, by putting them on the internal SD and using CWM to install from zip. After everything was done however I am now stuck at the Viewsonic splash screen. I tried to read thru the Googles and tried reflashing back to stock by way of some instructions on DroidPirate I think it was, to no avail. I can't even see my external SD card to load the update to recover. Please help. Anyone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1021978
you are not alone...
it may have to do with the boot loader .... further investigation needed. CW does not replace this but the stock does I have been running the old one since december on my personal tab. but most of these woot pads are updated .... hmmmmmm
Xxlgeek said:
I can actually boot into CWM right now. I already repartitioned and wiped all the caches. But when I try to flash Cyanogenmod 7 again, which is on the root of the internal memory, it just does the same thing, won't load past splash screen.
Click to expand...
Click to collapse
Which version of CM7 are you running?
jivy26 said:
Which version of CM7 are you running?
Click to expand...
Click to collapse
doesnt matter all the gbread roms do this when the error happens. thats why i am starting to think its the bootloader
Just throwing this out there. I bought 2 from Woot myself. On my first G-Tab I had the same issue with every single ROM I tried. I finally used NVFlash to go back to stock and everything was good again. I then flashed to the G-Harmony Gingerbread ROM and it worked and still runs like a CHAMP. Now, I finally get the other G-Tab out and start to go through the same routine as the first and it's been a no go repeatedly. I have mostly been trying with the Cyanogen 7 Final ROM to no avail and even with the G-Harmony. Going to try NVFlash on number 2 tab and see what the result is and will post back in a bit with updates.
Ok, I said I would reply and here it is. The downside is this.... The NVFlash worked great and put me back to stock. The bad part is that I am not sure that was what actually caused the problem to occur in the first place on the second tablet. I had read right before doing this that installing the Clockwork mod from the SD card instead can be a fix as well. I did that this time through. It also shows something different on the screen when you hold down the start and vol+ buttons than it was when CWM was installed wrong.
So basically this:
Run NV Flash (Detailed here: http://forum.xda-developers.com/showthread.php?t=861950 )
Run Clockwork Mod FROM THE SD CARD!!! (Detailed here: http://forum.xda-developers.com/showthread.php?t=865245 )
Then proceed to follow those exact instructions from the same thread.
Do not skip stuff, do not think you have a better path, just do it all as described. I now have a G-Tablet running the Cyanogen Mod 7 Final release SMOOTH as glass! Hope this helps someone else out.
tunez23 said:
Ok, I said I would reply and here it is. The downside is this.... The NVFlash worked great and put me back to stock. The bad part is that I am not sure that was what actually caused the problem to occur in the first place on the second tablet. I had read right before doing this that installing the Clockwork mod from the SD card instead can be a fix as well. I did that this time through. It also shows something different on the screen when you hold down the start and vol+ buttons than it was when CWM was installed wrong.
So basically this:
Run NV Flash (Detailed here: http://forum.xda-developers.com/showthread.php?t=861950 )
Run Clockwork Mod FROM THE SD CARD!!! (Detailed here: http://forum.xda-developers.com/showthread.php?t=865245 )
Then proceed to follow those exact instructions from the same thread.
Do not skip stuff, do not think you have a better path, just do it all as described. I now have a G-Tablet running the Cyanogen Mod 7 Final release SMOOTH as glass! Hope this helps someone else out.
Click to expand...
Click to collapse
I too am having the same problem but when I try to run NVFlash, I get the error "nvflash configuration file error: file not found Press enter to continue:"
The tablet doesn't restart or anything. I followed the steps to re-partition and install the ROM from "http://forum.xda-developers.com/showthread.php?t=865245." After that didn't work, I tried the steps from "http://forum.xda-developers.com/showthread.php?t=861950" and I get stuck at running the nvflash_gtablet.bat file.
Any help would be appreciated.
Did you extract both archives to the same directory on your computer?
akodoreign said:
doesnt matter all the gbread roms do this when the error happens. thats why i am starting to think its the bootloader
Click to expand...
Click to collapse
2 partitions are reversed and Gingerbread roms don't like it. Using bekits original nvflash files will fix the partitioning permanently as far as flashing between froyo and gingerbread.
Any official updates from viewsonic past 3588 have a locked bootloader and require viewsonics kernel so you must use Gojimis fix or nvflash to go back.
Edit.....This is not all tablets. I'm guessing around 30% or so have the 2 reversed partitions but it seems 50% of the woot tabs. Helped fix many of these on irc in the last 2 weeks
KrazyOne7 said:
I too am having the same problem but when I try to run NVFlash, I get the error "nvflash configuration file error: file not found Press enter to continue:"
The tablet doesn't restart or anything. I followed the steps to re-partition and install the ROM from "http://forum.xda-developers.com/showthread.php?t=865245." After that didn't work, I tried the steps from "http://forum.xda-developers.com/showthread.php?t=861950" and I get stuck at running the nvflash_gtablet.bat file.
Any help would be appreciated.
Click to expand...
Click to collapse
Having the same problem too!! Any help would be much appreciated.
Tried wiping everything with FORMAT.zip from another thread, and get and error for unknown device when running that *.bat file.
This newbie needs some serious help!
Locked bootloader??!
thebadfrog said:
Any official updates from viewsonic past 3588 have a locked bootloader and require viewsonics kernel so you must use Gojimis fix or nvflash to go back.
Click to expand...
Click to collapse
I think I must have the locked bootloader, but tried both Gojimis's fix and nvflash fix and get the error as mentioned above.
So I am getting nowhere, won't go past the "booting..." splash screen to install any of the update.zip files from the microSD card.
Help!
K J Rad said:
Did you extract both archives to the same directory on your computer?
Click to expand...
Click to collapse
Yes, I extracted both the gtablet and the windows zip files.
KrazyOne7 said:
Yes, I extracted both the gtablet and the windows zip files.
Click to expand...
Click to collapse
Me too, and still getting the error "nvflash configuration file error: file not found Press enter to continue:"
Are they in the same directory. If they are not then nvflash can not find the files to flash. Both zips have to be unzipped in the same directory and the driver has to work. You must be able to see the tablet from the computer when you boot into apx mode. APX mode is power/vol- NOT power/vol+
So, firstly, big thanks to the devs here. Gt ADB up and running and started the seemingly easy process f flashing ClockworkMod.
However, I'm not getting to ClockworkMod after resetting. If I try booting into recovery, it stays on the birdie splash screen with "Recvery key detected" and "Booting recovery kernel image" in the upper left.
Not finding any options for alternate recoveries or a fix for this.
I bought it used and the original owner had done some stuff to it so perhaps I was not meant to flash Clockwork from here.
Tap UI version is TnT Lite v5.0.0
Kernel version is 2.6.32.9-00001-g0e0c333-dirty
The standard ClockworkMod does not work properly with TnTLite 5.0. You need the one that was specifically compiled for that ROM.
Go here: http://forum.xda-developers.com/showthread.php?t=998663
and scroll down to the bottom of the first post for a link to the compatible version.
I thought that might be the case although I was told I could flash CLockworkmod once 5.0 was on there.
I'm normally a bit better at figuring all this out but starting in the middle of someone else's work has me at an awkward spot.
I've been searching with little luck. Any chance of pointing me in the right direction?
What about a complete factory reset? Would it be advised at this point?
I editted my previous post with a link to TwoTapsX (Experimental) which is identical to TnTLite 5.0. That should get you going but I'm not sure how much damage might be done at this point. I would try just installing the compatible version of CWM and see if that works. If not, we can look at other recovery options.
Just in case... Are you familiar with nvflash? http://forum.xda-developers.com/showthread.php?t=861950
Just started reading about nvFlash and paused to ask the questions before hacking away blindly at my new toy.
I really appreciate you pointing me in the right direction.
I enjoyed the ROM he put on here but, like the poster under me, my data suddenly got deleted and I like to try various ROMs anyway so I set to work.
I rarely leave my tablet running the same ROM for more than 12 hours ;-)
Be aware that switching away from this particular one can be a bit tricky. I find that doing a cache and data wipe before starting helps to boost the success rate. I also try to down grade to stock 1.1-3588 before loading anything else. If that fails it usually results in nvflashing back to factory stock.
Ack! Okay, in what is sure to be yet another Windows 7 issue, I'm having trouble running the .bat file for nvflash.
Are you sure it is the Bat file. Windoz7 64 need a different driver for NVFLASH.
The drivers I used appeared to work. I will try again.
Damn, I'm sorry. I swear I'm usually better at figuring all this crap out for myself. Once I'm back to stock, I can work from the beginning. This is like being dropped into the middle of a David Lynch flick with zero context.
When I run the batch command, it says that nvflash.exe is not recognized as an internal or external command. Weird.
Did you extract both archives to the same directory?
I sure did. I did take it to mean the gtab folder should remain intact within the nvflash folder instead of mixing the contents altogether in one folder. Right?
Everything else seems to be in order.
Putting any recovery zip on the sdcard produces the same results. Thankfully, everything seems to be working aside from the recovery. Maddening!
I think they need to be intermixed. Would have to check the original thread or look at the .bat and .cfg files to be sure... but if I recall properly they do.
All the files from both zips should be in the same folder, otherwise the batch file can't find nvflash and you get that error.
Good luck!
Wow. If that's what it was they need to put a dunce cap on my avi. Thanks for all the help. I shoulda had the guy put it to stock so I could start from scratch.
I'll try that when I get home.
Thanks again!
Sent from my HTC Vision using XDA Premium App
Sleef,
You are in a world of hurt -- and I say that not making any negative comment
toward the advice you already have been given.
TnT Lite 5.0.0 (which is now TwoTapsx) is a second generation ROM Roebeet did
based on the UAT 3991 update posted by VS in a kind of test mode.
The second generation ROM is not compatible in many respects with the original ROMS
up to 3588 -- some of the internals that normally are changed in an update have been modified.
So, as you have been properly warned by others, you cannot run stock CWM. You
also have to be careful downgrading to stock before moving to stock or another ROM.
To get out of 5.0.0 you need to:
1. Read Roebeet's TwoTapsX thread so you know what you are working with:
http://forum.xda-developers.com/showthread.php?t=998663
2. You need to NVFlash back down to stock. Normally we'd tell you to follow
the thread:
http://forum.xda-developers.com/showthread.php?t=861950
Since you already have been working with this, I'd step-by-step make
sure of your setup and that it is right.
My best suggestion would be for you to set up and follow the NVFlash thread above
exactly and see if you can get a good flash. If you do, it will take you down to what
we call bekit 1105, which is stock version 2638. If you get there and boot successfully,
then when you turn on wifi it will soon update you to OTA 3588. Then
you can carefully pretty much do what you want.
If you don't get a successful flash (because the tab has had so many different,
difficult to handle things on it), then all of us will have to help you find a successful
path.
Good luck,
Rev
P. S. -- What the other guys have been telling you is good -- I've just tried to
put it in perspective so you'd understand where you're at and be organized in
your approach.
Quick clarification... I think Rev meant to say "Is NOW TwoTapsX" rather than not which is why that thread is referenced later. The name change was necessary to differentiate the two development paths.
Thanks for popping in Rev. I've been meaning to pop in but I've been... practicing my recovery methods... don't ask...
Yep.
Fumblefingers strikes again. Thanks.
Rev
So I am just about at my wits end. I am fairly computer literate but an absolute noob when it comes to my gtab and flashing it.
I’ll try and give a step by step.
1. Got my Gtab today. I was sooooo excited!
2. Installed CWM and the latest TNT lite ROM.
3. All is well everything worked great.
4. Started up Android market…all hell starts breaking loose with “forced closes”.
5. Ok…so I shut down and restart
6. It starts what I have learned is called a “boot loop” going from the birds to the “G Tablet” screen to black to the birds…
7. I try to reflash TNT…nothin’.
8. I try NVflash, it *says* it completed successfully, but stays in the boot loop.
9. I’ve tried copying the CWM onto the microsd card (yes, command is pointing to the micro card). I then go through the Hold down the plus and start.
10. CWM *seems* to install, then HEY…right back into the boot loop.
11. I try something else and get (in little red text in the top left corner of the screen) something about “Magic” something missing.
Does anybody have any suggestions? I am a smart guy…I can read. The thing is, is that it seems like the mods and the CWM’s are completing successfully, but then I am right back in the flippin’ boot loop. I am afraid I’ve just wasted $300.
Sorry to be the dumb noob.
Pat
Did you change the partition when you installed the new rom? That was what fixed mine.
No...none of the instructions I saw mentioned that. Now I am seeing using CWM to do it but the problem is I can't get CWM to load!
if CWM is installed, you just need to hold V+ and power button when restarting. if not (and this happened to me) you should follow the instructions that were given to me by regalpimpin on this thread http://forum.xda-developers.com/showthread.php?t=1025128 to install CWM, and re partition (you will loose all the data on your internal SD card so be sure to back up) but repartition at 2048 and 0 unless the ROM specifically asks for a different partition.
You need to nvflash if you are getting the magic value mismatch. You could have gotten out of the boot loop originally by repartitioning. Only use bekit 0.8 recovery as any others will bork your tab. Dont use rom manager either.
mocheesehead,
First don't panic. We can fix this. It's REALLY hard to brick
a G-Tablet!
You have done all the right things from what you have written.
As Lisa said the one thing you haven't done is re-partition and
it seems that re-partitioning fixes boot loops most of the time.
Double check. Use your microSD with the CWM update.zip on it.
Since the command file is erased when you use it, you will need
to copy a new copy of the command file edited for /SDCARD2 back
into the recovery folder. Boot into recovery with power/volume +.
When all is finished shut down properly. The reboot as above and
see if you get CWM.
If you don't, you will have to try to load CWM by nvflash. If you
will try the above again, I will see if I can find directions for CWM
by nvflash. I know the process but will have to find the correct
command line.
*************
Just in case CWM loads: I will go ahead put the fix process here:
1. When CWM starts, go to the Advanced Menu and run the
Partition SDCARD, Fix Permissions, and Wipe Dalvik Cache options.
The re-partition takes a few minutes so
don't panic! Then go back to the Main Menu and Wipe Cache
and Wipe/Reset Factory Settings.
2. Once that is done, reboot and hopefully you will be fixed.
3. If not fixed, nvflash back to stock as per the thread:
http://forum.xda-developers.com/showthread.php?t=861950
Makes everything -- especially the files to load -- is correct.
Keep us posted on how you do. Meanwhile I will look for the
other procedure and post it.
Rev
Hi Lisa! Yes! That sounds like my problem. I'll give it a go.
Quick question...is there a preferred format (ie, FAT32, etc) for the micro SD card?
I'll let you know how it turns out!
Thanks...Pat
Pat,
Read this thread. This person had about the same kind of situation
you do and had to nvflash to load CWM.
http://forum.xda-developers.com/showthread.php?t=1026757
Rev
butchconner said:
Pat,
Read this thread. This person had about the same kind of situation
you do and had to nvflash to load CWM.
http://forum.xda-developers.com/showthread.php?t=1026757
Rev
Click to expand...
Click to collapse
Hey cheesehead! Absolutely follow Rev's advise! I was the Guy in the thread he references above. The fix worked like a champ.
You will get it fixed, just as I did. Same issue.
Mark
Thanks to everyone for the kind and informative responses. I probably won't get to a fix til Monday morning I as I have a soccer tourney (kids) all weekend, but I'll report back when I know something!
Thanks again,
Pat
As everybody said, it is almost brick proof, as long as you follow the correct procedures. Some people don't seem to understand missing one step can make things worse. Most of these post give you step by step instructions and by finding the right one to read you can't go wrong. I'm sure you will eventually have it worked out, learning what does what and why you did that will be a big help in the long run.
Ok! So I think I am breathing again! I partitioned the card and got back to the stock UI...man...it does really blow! So, a couple of questions...
1. I flashed TNT lite, and had force close issues. Would you recommend Vegan?
2. Now that I partitioned the card 2048 and 0 like everyone said, do I need to do this again before or after I flash a new rom?
Again, thanks for everyone's kind responses!
Pat
Glad to hear you made back to stock. Here in a bit I will write a step by step how to upgrade to TNTL 4.40 for you if some one doesn't beat me to it.
Thanks JH! I look forward to giving it another go! I appreciate your help!
Pat
Pat,
Remember that the bekit 1105 is about the oldest stock UI that exists!!! Most of us
started with 2967 on our first G-Tablets.
It WAS bad and there was no Flash and no replacement kernal and TnT was at about 2.x and VEGAn was at about .beta 3.
On the other hand, we didn't miss a lot of it because we were trying to keep them
running and find out what they would do and find apps we liked!!!
When I run the latest software I just can't believe how lucky we are.....IMHO.
Rev
Anybody could post an update.zip stock rom, please?
I got my gtab stuck on apx (like tccrews had it) and I need an stock rom update.zip to apply a fix that I found posted here.
Thanks in advance.
Here you go, there's a link to 3588 in this post:
EDIT: Correct me if I'm wrong but if it's stuck in APX mode wouldn't you have to use NVFLASH to get it back to stock? If so then just follow the directions in the post listed below to NVFLASH your G-Tablet back to stock.
http://forum.xda-developers.com/showthread.php?t=861950.
More specifically here is the exact link to the download:
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip.
Just make sure and rename it.
Just because you could have found what you were looking for faster with less threads. Did you try and search for "3389" or "3588" on xda. I do usually every other day to provide the link you were looking for so I know it exists.
Naysses,
I will try to help you, but you are going to have to do a couple of things:
1. Do not post for help in any other threads any more. I think everyone knows you
were upset and desparate -- but it still is bad netiquette and only upsets people and
makes them angry.
2. I have several things for you to do that we have used in the past. It may take us
a day or two of back and forth. But you've got to do them exactly as requested. From
what I have read your PC and tablet must be a mess of software, so I'm going to
start from scratch.
Here's what you need to do:
1. First we've go to make sure you are set up right and have the right software available
and are doing that right. Following is the thread on NVFlashing back to bekit 1105, which
is stock Version 2638. I want you to erase all the NVFlash setup on your PC and then go
in and do this procedure from end to end exactly as it requests. It's
been done a zillion times and will work if your tab is not to messed up to flash right -- and
that's a possibility we will deal with when we get there:
http://forum.xda-developers.com/showthread.php?t=861950
Double check everything as you go and note any exceptions that might happen.
If this does not give us a workable setup, then we will look at NVFlashing CWM to
repartition and clean up your internal drive -- but don't even worry about that until
we see if a repeated, good flash will work.
Good Luck,
Rev
P. S. -- I know I'm being demanding and hard on you, but lots of people I help don't
do what is requested and waste my time and theirs. If your problem is like I think it
is we need to get it right! I'll check this thread early tomorrow to see how you
are doing.
Ur a good man Rev
I got stuck in APX mode before when using the (newer?) 152KB nvflash.exe when trying to reflash the stock image. With the 140KB nvflash.exe I re-ran the nvflash_gtablet.bat and it worked successfully. You do need the 152kb version to pull and back up the BCT, but I use the 140kb one when using the batch file to restore stock (with stock recovery)and haven't had issues getting stuck in APX since that switch.
ramerco,
Thanks for the warning and update.
However, if he will just stick with what I give him I know that works.
A bunch of people have been messed up trying to install the SDK and
ADB and all on top of the original Procedure roebeet wrote. Drivers
get messed up. Makes it tough in times like this.
Rev
I have a G-tablet that belongs to a friend. When they first bought it, I used Clockworkmod and installed Vegantab. everything worked great for a few weeks and then she said apps started randomly force closing more and more till it got to the point it was unusable. She didn't use it at all for a few weeks and now it will not get past the Viewsonic flash screen (3 Birds).
I got it from her and have tried everything I can think of to get it into any kind of boot or recovery screen. I used a new SD card (formatted) and then copied several different recovery files on to it. Hold Volume + and Power up.. Nothing. Still will not go past Viewsonic screen. Another SD card (Formatted) Copied ClockWorkMod v8 (Unzipped, Command file and update folder to the root, Nothing else on the card). Hold Power and Volume +.. Still nothing.
Any suggestions?? Will gladly paypal enough to buy a few drinks for anyone that help me out here.
I had the same trouble, If your GTAB is not broken (hardware issue) then follow this basic procedure located at:
http://forum.xda-developers.com/showthread.php?t=892090
You will need an update.zip so you can download zip files from Viewsonic's TNT page and just rename them to update.zip.
If this process does not seem to work then you will have to setup what is called NVFLASH and you will need APX drivers to do it, you can use this link to find the instructions and pertinant links:
http://forum.xda-developers.com/showthread.php?t=861950 I have used this and followed exactly and was back on old stock rom. I ADVISE YOU TO READ AND REREAD this post then make sure you have all files and drivers before completing this, then you can go through the process and after that restore CWM recovery and go from there.
This is to restore the 1.1 BL along with stock 3588 image... if you like you can just get all stock updates to get you to the 1.2 BL as well then move on from there.
Basic instructions after the NVFLASH operation is succesfull to get back to CWM:
http://forum.xda-developers.com/showthread.php?t=865245
I hope this helps and props to roebeet, TeamSpeed, rr5678 and scsione889 for all the linked posts.
EDIT:
You may want to run this prior to any NVFLASH operation you do:
http://forum.xda-developers.com/showthread.php?t=974422
And only use this to format uSD cards. Time and again installs or fixes fail due to a bad format. Not saying that is the issue but always best to start with a good format.
Why don't you just nvflash it?
Google "nvflash for dummies" and follow those instructions, it might seems scary, but you just gotta follow the instructions correctly and everything will work out. This will return you to the stock tapntap rom.