yashsingh1/xdaforums huggingface dataset:
[G Tablet Q&A, Help & Troubleshooting] Citi:
Your telling me, it is quite unique. Others have been trying to duplicate the issue as well with no luck. Not sure what I can tell you, I followed Roebeets guide exactly and it all seemed well. After I rebooted my Tab to apply the 3588 update I noticed it would not power on. Confused by the issue I plugged it into the computer only to hear the sound that it was connected. I was then informed that it was in APX mode.

I checked to ensure my (-) button was not stuck (it isn't) and then have tried every solution under the sea. Once I got CWM loaded onto it via NVFlash method my tension was eased quite a bit...but now I fear that this is a permanent brick.

Plus all these different methods I have tried have probably damaged my Tab even more...let's hope not.
[G Tablet Q&A, Help & Troubleshooting] Citi:
ClockworkMod Recovery v2.5.1.1-bekit-0.8

Partitioning SD Card... please wait...

(after a long wait)

Done!

-- Wiping data...

Formating DATA:...

Formating CACHE:...

Formating SDEXT:...

No app2sd partition found. Skipping format of /sd-ext.

Formatting SDCARD:/.android_secure...

Data wipe complete

-- Wiping cache...

Formatting CACHE...

Cache wipe complete.

E:Can't mount /dev/block/mmcb1k0p2

(File exists)

Dalvik Cache wiped.

Reboot Recovery

Still in APX mode, with a reboot unsuccessful. However, above is exactly what is seen when I partition, wipe data/cache and dalvik cache with CWM flashed using NVFlash.

I am going to try your above method now.

Edit* Couldn't get CWM on the MicroSD but used it the NVFlash way that I have been with no success after the wipes. I forgot to mention a few days ago I also used this format http://xdaforums.com/showthread.php?t=974422 at the recommendation of another forum poster.

I also noticed that my 'Internal tablet storage' is a mere 1.63GB, is this normal?
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
All of that sounds terribly normal except the APX loop. But I'm betting that's related to "System Space" being redefined by the repartitioning. A subsequent nvflashing of the stock ROM should take care of that.

That "format" method is actually just an nvflash with an image I haven't verified. It shouldn't matter at this point anyway since the method I outlined shouldn't care what the condition of the tablet is as long as there is enough room in "System Space" for the first nvflash of the image.

That sounds like the right amount of space for application storage which may be what that version of TnT reports. I'll have to flash it back on to check for sure.
[G Tablet Q&A, Help & Troubleshooting] ByByIpad:
SOLUTION

I had to NVFLASH to stock from 4349.

I had the same problem. I did the NVFLASH and could not install OTA 3588 and would reboot only into APX (the black screen).

I was convinced I bricked the unbrickable. I reread and reread and was certain I did everything right. Did the NVFLASH 3 times again with the same result.

A broken man. I took a break and drank a cool glass of red wine to calm me down. I was TRULY convinced I did everything correctly.

After reading the NVFLASH directions one more time, I noticed my blunder. I carelessly downloand the first file - "nvflash_gtablet_46_2010112600.zip" instead of "nvflash_gtablet_2010110500.zip".

Re-energized, I redid the the NVFLASH with correct file "nvflash_gtablet_2010110500.zip" and, this time, it worked per the instructions.

I did do one slight modifcation. Before I ran the nvflash_gtablet.bat file. I replaced part9.img with ClockworkMod. I unzipped cwmod_v08.zip. Unzipped update.zip. Renamed recovery.img to part9.img and copied the renamed part9.img to the NVFLASH folder. Rebooted with power/volume up and hello to ClockWord recovery.

This entire event took 1.5 hours to figure out.

When devs say the Viewsonic Gtablet is unbrickable, I'm now a true believer. Most errors result from a careless deviation from the written directions.
[G Tablet Q&A, Help & Troubleshooting] Citi:
I have used both zips, 46 and original with the same result. I have done everything correctly there is no doubt about it at this point. Glad your your problem was fixed though :)
[G Tablet Q&A, Help & Troubleshooting] Citi:
Bump, don't want this issue to be buried
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Haven't forgotten you. Haven't found anything that doesn't require direct access yet.
[G Tablet Q&A, Help & Troubleshooting] locnguyen1968:
i have the same problem here....... try every thing. still stuck at the tap ntap screen then power go out........
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
That is not the same symptom that Citi has. Try method I from this: http://xdaforums.com/showthread.php?t=1030915
[G Tablet Q&A, Help & Troubleshooting] oulu:
Citi

i dont know if this will help you or not but after two and half days trying to recover my tab i have finally got it back running. I was in the same boat as you APX boot or endless boot loop. I just got this back so let me try to run down what i did and see if it might help you.

I ran the format nvflash that I copied down from here:

http://xdaforums.com/showthread.php?t=974422

So basically turned the tab on and got into APX, mine was getting to the birds screen at this time and then looping. Once in APX I flashed it and was getting the bad magic on the screen.

***at this point after a power down and up I tried the standard NVflash with no luck, I would either do the power up and vol+ and get the triangle with the exclam. mark in it or it would just boot loop****

So I went back and did the format again, back to the bad magic, shut it off and took out the USB cable. Now i wanted to run NVflash again but this time I had moved the recovery.img from the CWM .8 into my NVflash dir, renamed the orig part9.img file to _old.img, renamed the extracted recovery.img to part9.img, I made no edits tot he CFG file at all, I powered up the tab with no buttons pushed and no USB cable in it, I had a black screen and then plugged in the cable, once i heard that my system saw it I flashed it, let it finished and powered down. Took the cable out turned on the tab while holding down the vol+ key and had CWM running! yeah I haven't seen that guy in days...so from that screen I did a wipe data and reset factory first, then a clear the cache, then did a reboot....wow even better up came the stock ROM it took a bit to boot but I'm back to the tab actually running...

I sure hope this helps I was frustrated trying to to get this guy back to life..
[G Tablet Q&A, Help & Troubleshooting] johnseidel:
Minor Victory

I have spent the last two days after returning from my trip, reading and trying everything that was posted during the five days I was gone. I was pleased that some had victories. But nothing worked for me.

My one success was getting into CWM. I saw a post in the developer section where it was suggested to hold power and V+ during the running of nvflash. http://xdaforums.com/showpost.php?p=12857382&postcount=157

Half the post I understood. Half, the part involving gparted and linux, was over my head.

I had a version of nvflash where I had replaced Part9.img with the CWM Recovery.img.

I set it up so that I only had to press Enter to start nvflash. Then I held down Power V+ with one hand, pressed enter with the other, and kept the Power V+ keys down until nvflash had finished.

The result was that recovery was detected and CWM was loaded. However, nothing I did with CWM made things better. I still ended up in the APX Boot Loop.

K J Rad, you had indicated in an earlier post you would like to get your hands on one of our misbehaving machines. PM me. I'd like to set that up. Otherwise I am going to squander more time and energy getting no where. Perhaps what you could learn would help some of us.

John
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
I'd love to get this nailed down and behind us. Message sent.
[G Tablet Q&A, Help & Troubleshooting] Citi:
Bump, any updates KJ?

I haven't touched my tablet as I am currently contained to the library for my last finals week ever
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Yes... sort of. johnseidel's machine is reporting a slightly smaller amount of internal storage than mine and several other working machines I've checked. I think that's what's preventing the images we're flashing to it from rebooting properly.

I need some information from another tablet to confirm this. To get that...

1) nvflash bekit's 1105 image

2) download and install a terminal emulator

3) run the emulator and type "su" without the quotes at the first prompt.

4) tap allow for superuser access

5) at the second prompt type:

busybox_fdisk fdisk /dev/block/mmcblk3 -l

(that is a lower case L)

6) post the results. Specifically we need to know total space, number of cylinders, heads and sectors.

Edit: I could also use your serial number (first eight characters should be sufficient), if you don't mind. I'm trying to rule out some change in manufacture.
[G Tablet Q&A, Help & Troubleshooting] fordmanck:
16.0 GB, 16097738752 bytes

Device Boot Start End Blocks Id System

/dev/block/mmcblk3p1 1 1709 13720703 c Win95 FAT32 (LBA)

/dev/block/mmcblk3p2 1709 1958 1999744+ 83 Linux

Serial Number = 1M2110480116330
[G Tablet Q&A, Help & Troubleshooting] chugger93:
I was stuck in APX mode too and bricked. I just sent it back. Whatda gonna do... next time...no clockwork from the market for me!
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Those were not the numbers I was hoping to see...

Are you using Bekit's 0.8 version of CWM? Have you used ROM Manager on that machine?
[G Tablet Q&A, Help & Troubleshooting] fordmanck:
Yeah, that's what got me here. :/
[G Tablet Q&A, Help & Troubleshooting] Citi:
I would love to send this back but w00t doesnt do returns, plus it is to late, and CWM = voided warranty so no VS support.

What did you do?
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
I think I've got a fix. I'm going to refine the instructions and do a little testing then post the results tomorrow. Very late. Very tired. Thanks for your patience.
[G Tablet Q&A, Help & Troubleshooting] fordmanck:
Whatever you need let me know. I appreciate the work you're doing. I have ways to get another one but I'd rather help you help the community find a fix. No more Rom Mangler for me....
[G Tablet Q&A, Help & Troubleshooting] fordmanck:
Still not working. I'm going to give it another whirl tonight. The updating to the 3588 worked but when I rebooted I still never saw the VS Birds splash screen.

For the record though, I live in Central Florida 5 minutes from the beach, not quite Key West but it'll have to do. I have an '88 Mustang Coupe in my driveway that isn't restored or a '34 Ford 3 window Coupe at my disposal, you make your pick. As for the bank account, as soon as my two girls are grown up maybe I'll have a pot to piss in to start that account. ;)
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
It's not a simple procedure by any means. Be happy to work through it with you over IM if necessary.

BTW... I live in NW Florida, '96 Mustang which I'm not allowed to park in the driveway and I've still got three of my five daughters at home... ;-)
[G Tablet Q&A, Help & Troubleshooting] fordmanck:
Sounds like we have a bit in common. Hit me up on gtalk. Same name as on here. Thanks again. :)
[G Tablet Q&A, Help & Troubleshooting] Citi:
Will be trying this in a few hours and I will let you know how it goes
[G Tablet Q&A, Help & Troubleshooting] fordmanck:
Still a no go for me. I'm never seeing the VS Birds splash screen. :/
[G Tablet Q&A, Help & Troubleshooting] xHVGx:
I just had this problem a couple hours ago and thought it had no fix since I nvflashed several times yesterday (would get stuck in APX or boot into stock rom but went into apx again after reboot) and I read this thread, but today I got it fixed and this is how I did it... maybe you already did it or you were told before but thought I'd share anyway.

1) Get the nvflash files from roebeet's post. Make sure you use	nvflash_gtablet_2010110500.zip instead of the one with the "46" in it. http://xdaforums.com/showthread.php?t=861950

2) Follow roebeets instructions but replace the part9.img with the one from cwmod_internal.zip version from this thread: http://xdaforums.com/showthread.php?t=865245

3) Continue with the regular nvflash process.

The difference in my process I think was that I used the image from that spefic version of cwm.

In my case it booted me into the stock version but it was rooted and with cwm running great, and all I did was rebooting it to see if it went through, then reboot into recovery wipe/factory reset and also wipe chache... then after that loaded a custom rom with no issues.

I know instructions might not be that detailed as I hope I could have written them, but I guess you have experience with nvflash so it wont be an issue. Hope it helps :)
[G Tablet Q&A, Help & Troubleshooting] Citi:
Unfortunately it was unsuccessful, after following the commands the tablet did indeed go to the 'Gtablet' screen. However, it did not restart and go to the birds but rather continued onto the N logo for TnT. It then loaded up fine with 3588 on it.

I restarted the tablet and continued to be in APX mode :(

I followed everything EXACTLY, not sure what happened but hopefully it can be resolved.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Citi, I'm still looking at it. There are others that are still having issues as well. It is possible that we'll need to do a hard reset on some of these to get them back on track.

xHVGx, We do appreciate your input but if you read back in the thread you'll see that method has been tried many times by these folks and hasn't been successful for them. In fact, I have one tablet in my hands right now that was fixed by the procedure I posted earlier but when I tested flashing back to stock again it failed and put it right back into an APX loop.
[G Tablet Q&A, Help & Troubleshooting] Citi:
Isn't the only way for a hard reset to open the device and push the button?
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Yes it is. I haven't given up on finding a software solution though. It was likely that software did the damage... it should be able to fix it.
[G Tablet Q&A, Help & Troubleshooting] Citi:
I always assumed that as long as you could load CWM then you should be ok, but I am unsure now.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
I'm sure it can be recovered. It's just very difficult to do without direct access to the tablet. One set of eyes may see something differently than another. Some small detail could be getting overlooked. It's very hard to say.

I just shipped one back to its owner and I have got to spend some time catching up with family this weekend but I will try to come up with some new ideas for you to try.
[G Tablet Q&A, Help & Troubleshooting] meltonch:
I'm having the same issues as many other people here. I've Nvflashed into an APX loop and have followed many different sets of instructions to try to get it working again. So far, no success.

I read in some other posts that some tablets have partitions 6 and 7 switched. If i'm correct, one of those is the boot image, right? If so, and if they did happen to be switched, would:

1)Following KJ's instructions above, except replacing "6 part6" with "7 part7"...

or

2)Switching partitions 6 and 7 in the Nvflash download file...

have any different results?
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
If you use Bekit's 1105 image it corrects the reversed partitions the first time you nvflash. Reversing them again manually probably won't help you but I'd be interested in knowing if it does.

Switch the filenames in the gtablet.cfg file.

The reason I nvflash that partition is simply because the command must perform some function or the --go switch won't cause it to reboot properly and I happened to have that command lying around to flash custom boot screens and it really doesn't matter what partition you use for this purpose.
[G Tablet Q&A, Help & Troubleshooting] meltonch:
As far as i know, switching the partitions was unsuccessful.

Every time i've tried to run your [K J] instructions above, I get the cardboard box and the status bar as the tablet attempts to update to 3588, but as i watch it, it always gets maybe 3/4 of the way through and then powered off before the status bar reached the end. I've assumed that maybe that was normal.

However, I just tried installing it by nvflashing JUST CWM and then manually navigating to update.zip on the sdcard. the same thing happened- the status bar got 3/4 of the way through then stopped. the tablet lingered for a second, then:

E: unknown command [bootloader]

E: unknown command [/tmp/bootloader.bin]

came up. I then got an install complete message. Is this significant?
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
It goes black because it rebooted into APX mode. You use the command I listed to reboot it and finish the process. You'll likely have to enter that command twice since it will need to reboot twice.

By putting CWM back in and installing the update that way you bypassed the reload that updates the bootloader and I believe the bct which is what fixes some of these and is what probably resulted in your error message. Stock recovery must be used to perform the update.
[G Tablet Q&A, Help & Troubleshooting] johnseidel:
My Brick has been unbricked. There are now blooming apps flowering in a garden of Vegan Ginger. Angry Birds are happily launching, Nook is nooking, TV Stream is streaming.

Thanks K J.

Citi and my fellow sufferers. There is hope. It doesn't appear that every solution works for everybody. K J wrestled mightily with my gtablet and the instructions posted above worked for it.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
My bank in the Caymans said they didn't receive your payment... ;-)

You're welcome. It was an interesting battle :-)
[G Tablet Q&A, Help & Troubleshooting] fordmanck:
I'm wrestling with opening it up. Will the reset button fix things for sure?
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
I wish I could say for sure but honestly it may only be one piece of the puzzle. There still may be some hoops to jump through.

That being said... I don't like to lose. I won't give up until you do ;-)
[G Tablet Q&A, Help & Troubleshooting] fordmanck:
Not giving up, just focusing on other things. I've got a Mustang in my driveway that needs some head gaskets. ;)
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
That sounds like a LOT more fun! Mine needs an AC compressor and a paint job.

Let me know when you want to get back to it or if you'd prefer to just send it up I'll PM you the address.
[G Tablet Q&A, Help & Troubleshooting] meltonch:
Using some updates to roebeet's nvflash instructions post on slatedroid, I've managed to load 3588. The only problem? It's still APX looping.

Also, stupid? question- should there be a "bootloader" somewhere in the system files?
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Ok... I think everyone is missing the point on the 3588 update. We already know that nvflashing doesn't fix the problem. It is the UPDATE PROCESS using STOCK RECOVERY that updates the bootloader and I believe some pointers in the BCT (perhaps even some other system information) that gets some of these tablets going again.

You cannot use nvflash or CWM to perform the update because they DO NOT update those pointers. You MUST use stock recovery. The method I posted earlier will help you reboot the tablet through the process. If you read it carefully and do it properly it will help some of you.

In addition... If ANY of your symptoms change or you don't get the expected results from a step in ANY procedure it may be an indicator as to what to try next. Patience is your ally here. Getting that information into the thread and waiting for us to look at it is much more likely to help you than blindly flashing yet another image.

Now... meltonch, did you go back and try the procedure as I wrote it? Your last post indicated that you didn't follow the steps correctly.
[G Tablet Q&A, Help & Troubleshooting] meltonch:
Several times. Like i said earlier, every time i try it, I get to entering the command line. I'll enter it while holding power + and it will run 3/4 of the way then shut off and load back into apx mode. I'll enter the command again and the tablet will turn on but it wont reboot to the birds- just the gtablet screen and then it continues into the rom. Try to reboot again without flashing and you're stuck back in apx mode.

Also, when I try clearing Dalvik, I get the E: can't mount (file exists) error. I don't remember what the exact code was but I believe some other people have posted that problem on this thread.

Fixing permissions, repartitioning, clearing data, cache, dalvik- none of it seems to work. So in the meantime, I read and try to find something that might work, and along the way, if i see something that i might not find logical (doesnt mean it isnt right), Ill ask a question.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
I apologize if I seemed short with you but it is very difficult to help on complex problems when you don't have access to the hardware and a good understanding of what is being done or has been done behind the scenes and I know that any deviation from the procedure will fail.

So... Then it's never actually executing the bootloader update. The file exists error is an indication that the partitioning, clearing and wiping (etc) was unsuccessful or at the very least not complete since that and the following nvflash should wipe out the entire structure and the system should rebuild it as necessary. This could be caused by corrupted or incorrect images (if you just downloaded them or have used them successfully in the past... not likely) or a problem with the utility we're using to do the work (if you have the correct version that shouldn't be a problem). Since those are unlikely we might be looking at a lower level problem.

I would try doing the data wipe with stock recovery and see if the indications change. You can do that by making a "command" file in the recovery folder with the following command in it:

--wipe_data

You can use the nvflash command in the procedure to force the reboot. Don't forget to hold down the Volume Up so it'll go into recovery. It isn't very good at reporting what it does but it is a relatively low level factory method. That rules out some potential CWM problems. I don't have an alternative partitioning method yet but am working on one.

I'd also be interested in seeing the partitioning table that CWM is setting up. You can view that by installing a terminal app or going into an adb shell and use the following command as superuser (type "su" at the first prompt and it should ask for permission):

./busybox_fdisk fdisk /dev/block/mmcblk3 -l

That last is a lower case L. You will need to have flashed a rooted ROM or install superuser for that to work. Might also have to navigate to the proper directory (/system/bin I think, I don't have my tablet right here to check).

I have a feeling you might be looking at a hardware reset to get going again but we can at least look at a couple other things first.
[G Tablet Q&A, Help & Troubleshooting] meltonch:
I have tried the --wipe_data command a few times with no success. I can always try again later. I have also downloaded the nvflash files 3 separate times to ensure that they were correct (they were from bekit's dropbox every time. Maybe i could try a different location, if you know of any?)

When you can, a little more instruction on the terminal emulator would be much appreciated. (no rush at all, seriously. :) )

We actually tried hitting the hard reset button last night. Nothing happened. Literally. ??