[Miss Dragon]

My Gtab was based on 1.1bl and running VAGEn beta 5.1. So I decided to upgrade to FB rom based on 1.2 4349. When I finished the whole procedure, the Gtab will not turn on any more and it stays in APX mode, I tried nvflash many times back and forth from 1.1 to 1.2, it still won't turn on and stay in APX mode, i can still play with any roms as long as i don't shut down the Gtab. I'have tried many advises received from our Gtab members here on Slatedroid. I have to say, this was a great learning experience. and I would like to share my experience with others and hope it helps to many others whom has encountered this issue.

All credits goes to FB thread great helper Dave.S whom have been helping me all the way through and wrote this guide special for me based on boogiebear575's (Thanks) guide over XDA http://forum.xda-dev...&postcount=194.
Also thanks tlbardelljr found this link and tlb1961 , roebeet , Radon_22 giving me advises. As I said, Gtabbers Rocks !!!

A WARNING IN ADVANCE: NVFlash makes changes to the partition structure of your device. You should tread carefully and understand the risks. (MOD EDIT Note: It also has been noted a bunch of times that even NVFlashing your G-Tablet will not completely overwrite everything on it.)


Note: Me and Dave had went through the guide from XDA, which wasn't work for me, so he added some additional steps such as SD Card partition from 2048/0, then 4096/0 then 2048/0 again. ...etc

Warning: Some of the steps that I described here may be redundant. But do it to make sure that everything is taken care of properly.

I. Preparation:
1.1> Create a folder on your desktop, name it gTab_PowerOn_Repair. Download the followings files and place them in that folder. This is done so we have everything in one place, without clustering.
1.2> 1.2-4349 based image http://androidtablet...TA5OTM1NDA3MDQw ; After downloaded, extract it and you should have all the files as listed below:

Copy & override all above files into the nvflash folder that you've been using.
1.3> nvflash_bat_files.zip http://androidtablet...TA5OTM1NDA3MDQw ; Extract, copy and override all three files into the nvflash folder that you've been using.
1.4> Stock1.2.4349Recovery.zip http://androidtablet...TA5OTM1NDA3MDQw ; Extract it. You should have an 'update.zip' file and a 'recovery' folder with the 'command' file inside that folder. We will use these in step 2.5 later.
1.5> Remove the external SDcard from your tablet if you have one.

II. Procedure:
2.1> Hold down the volume + key then double click nvflash_CWM.bat. Continue to hold it for 10 seconds or so after nvflash starts doing it's work. When the nvflash finishes the tablet should start up into ClockworkMod 3.0.2.8 rev5
2.2> Repartition 2048 and 0, then 4096/0, then 2048/0. If you don't remember how to do this, refer to Bardell's installation instruction.
2.3> Data/Factory Reset, Clear Cache, Clear Dalvik Cache, Fix Permission in CWM. (This also described in Bardell's installation instruction). Then select 'Reboot System Now'. Tablet should turn off and again be in APX mode
2.4> Run nvflash_gtablet.bat. When nvflash completes, tablet should boot into stock 1.2.4349.
2.5> Mount the tablet to PC, then copy the 'update.zip' file and the 'recovery' folder into root of the SDcard. When done, unmount the tablet from PC, then turn it off.
2.6> Turn tablet back on. It should still be in APX mode even if you do not hold the volume + key. I am guessing this would happen according to the instruction.
2.7> Press and hold the Volume UP button and double click 'nvflash_part6.bat' to run. Continue to hold the Volume UP key for a few seconds after nvflash starts.
2.8> When the nvflash finishes, tablet should restart in recovery mode and install the update. The screen will go black and you will be back in APX mode. Again, I am guessing here according to the instruction.
2.9> Again, double click 'nvflash_part6.bat' to run WITHOUT holding the Volume key. When the flash finishes the tablet should boot to the "g Tablet" screen then restart to the "VS Birds" screen.


Yes, this guide works for me, and I saw the Birds!!!


Enjoy !

[bobg1231]

After doing all of this can you now use the standard nvflash or do you still have to use your modified version?

[Miss Dragon]

bobg1231, on 08 September 2011 - 10:24 PM, said:

After doing all of this can you now use the standard nvflash or do you still have to use your modified version?

after this, it was back on stock rom 1.2 4349. then I used cwm to flash to flashlight, no need to nvflash again.

[bobg1231]

I had this same problem a few months ago and fixed it doing basically the same thing you describe (had a few extra unecessary steps) but left it alone once I got the 3 birds up and going. I could flash different roms and everything OK. Just recently bought a new tab so I went back to see if I could condense my process and found out every time I use the regular nvflash (even tried the old depricated 46 2010112600 nvflash) I get stuck in the APX bootloop. I found that I can fix this everytime by basically doing what you have done but I can leave out the CWM portion. This does not take much extra time, but if I end up selling this at some point I would like to find a way that someone would be able to use the regular nvflash files. I have even thought about leaving it in the APX loop and sending it back to manufacturer (still under warranty) to see what happens. Just hoping that someone like roebeet, goodintentions, or tlbardelljr might have some insight on why this happens and how (or IF) this can be fixed. At the end of the day I have a way to make it work, just trying to understand what makes this gtab different than almost all of the others.

[Miss Dragon]

As far as I was told, i don't need nvflash again unless consider it as the last option.

[Tab_Modder]

I would not nvflash again unless absolutely necessary. I am curious how many users have experienced this.

[tlb1961]

bobg1231, on 09 September 2011 - 10:42 AM, said:

I had this same problem a few months ago and fixed it doing basically the same thing you describe (had a few extra unecessary steps) but left it alone once I got the 3 birds up and going. I could flash different roms and everything OK. Just recently bought a new tab so I went back to see if I could condense my process and found out every time I use the regular nvflash (even tried the old depricated 46 2010112600 nvflash) I get stuck in the APX bootloop. I found that I can fix this everytime by basically doing what you have done but I can leave out the CWM portion. This does not take much extra time, but if I end up selling this at some point I would like to find a way that someone would be able to use the regular nvflash files. I have even thought about leaving it in the APX loop and sending it back to manufacturer (still under warranty) to see what happens. Just hoping that someone like roebeet, goodintentions, or tlbardelljr might have some insight on why this happens and how (or IF) this can be fixed. At the end of the day I have a way to make it work, just trying to understand what makes this gtab different than almost all of the others.

There has been a few documented cases, and I have personally encountered, that the internal NAND flash has bad blocks which will not allow data to be written to areas of the media. I have researched this, and actually a lot of manufacturers have found a workaround which will allow the bad media blocks to be marked as bad so the data installation will use a different area. Something must happen along the life of the tablet which changes this, or possibly more bad blocks surface causing media degradation and the inability to successfully boot into a ROM. I have also read articles stating that there are areas of the media that are 'borderline' from the factory which aren't marked as bad, but there is no telling how many data 'flashes' it will accept before failing. I think the 'borderline' figure was something like 1000 flashes, but who knows what goes on behind the scenes.

My suggestion would be to try and RMA it, but realize that flashing anything over stock will void warranty, so it would optimal to be sure the gTab has a stock ROM and is exhibiting the no boot issue when returning. It's either that, or continue dealing with what you have right now.

Hope this helps.

[bobg1231]

Thanks. I really appreciate it. I hate it when something doesn't work and I can't find some sort of answer as to WHY. This happened to me on my first attempt at flashing the tab.

[CatherineNK]

cheers.rowwor.

[Miss Dragon]

CatherineNK, on 16 September 2011 - 09:01 PM, said:

cheers.rowwor.

Thanks. good to see you again.

[Commonplace]

I've only had my gTab a few days but already I've run into this problem. I was so happy to find this procedure, and it fixed my problem. However, it happened again today and I don't even know why. So I did this process again, and it fixed it... but then it did it again almost immediately after.

Is this likely to be a recurring issue? Since I'm still under warranty from Office Depot (where I purchased it), should I just exchange it and hope for a better one?

/Kevin

[sharpe351]

Commonplace, on 17 September 2011 - 05:43 PM, said:

I've only had my gTab a few days but already I've run into this problem. I was so happy to find this procedure, and it fixed my problem. However, it happened again today and I don't even know why. So I did this process again, and it fixed it... but then it did it again almost immediately after.

Is this likely to be a recurring issue? Since I'm still under warranty from Office Depot (where I purchased it), should I just exchange it and hope for a better one?

/Kevin

I would likely say yes to the return/exchange, due to tlb1961's reference to a possible major issue with some of the gtabs out there with big memory issues (bad blocks).

sent from my Brilliant Corners with Clemsyn Kernal Gtablet using Tapatalk

[Commonplace]

sharpe351, on 17 September 2011 - 05:54 PM, said:

I would likely say yes to the return/exchange, due to tlb1961's reference to a possible major issue with some of the gtabs out there with big memory issues (bad blocks).

sent from my Brilliant Corners with Clemsyn Kernal Gtablet using Tapatalk

Okay, thank you! I just didn't know if this was something "normal" or "expected" or at least somewhat common... but from what I'm reading/understanding, it's fairly rare and only affects a handful of gTabs. Guess I got a lemon! I'm going to return it and hope for better success. Thanks so much.

/Kevin

[Miss Dragon]

Commonplace, on 17 September 2011 - 06:10 PM, said:

Okay, thank you! I just didn't know if this was something "normal" or "expected" or at least somewhat common... but from what I'm reading/understanding, it's fairly rare and only affects a handful of gTabs. Guess I got a lemon! I'm going to return it and hope for better success. Thanks so much.

/Kevin

Oh, make sure you have stock FW on it when you return it.

[Commonplace]

rowwor, on 17 September 2011 - 06:11 PM, said:

Oh, make sure you have stock FW on it when you return it.

Definitely. I get the feeling the Office Depot people wouldn't know the difference but it's not worth the risk. (But when I bought it, they didn't even seem to know what this thing was, let alone what operating system was on it or what version of Android, etc.) But I've had to go back to stock on my Sprint phone for exchanges before, so I know the drill. Thanks for the reminder.

Addition: Just happened to think, I may just leave it stuck in APX mode -- maybe it'd do some good if ViewSonic got some of these back stuck like that. Guess it doesn't matter anymore since they've moved on to the ViewPad, but who knows. But at least Office Depot would just see a tablet that was "dead".

/Kevin

This post has been edited by Commonplace: 17 September 2011 - 06:23 PM

[Miss Dragon]

Commonplace, on 17 September 2011 - 06:21 PM, said:

Definitely. I get the feeling the Office Depot people wouldn't know the difference but it's not worth the risk. (But when I bought it, they didn't even seem to know what this thing was, let alone what operating system was on it or what version of Android, etc.) But I've had to go back to stock on my Sprint phone for exchanges before, so I know the drill. Thanks for the reminder.

/Kevin

lol..Guess you know better than them and can take their job there.

Good luck.

[LouieM]

Thanks, this helped me get my gtablet working again.

[NoLightsOn]

in step 2.9, when i'm done in 2.8 ... there's no VS Bird ... help me please

This post has been edited by NoLightsOn: 18 October 2011 - 09:28 AM

[NoLightsOn]

Yeahhhhhhhhhhhhhhh ... my tablet is alive thank you so much for your guide

[tincansailor]

Just wanted to say thanks for the effort. I tried a lot of different methods to get out of the
dreaded APX bootloop. This one was the most helpful. By far. Finally got the birds!!!!!

thanks again.