Database Info

Bricked? And options?

I think I'm posting to the right place. I have been playing around with the various mods, tnt lite, vegan, cyanogen, and somewhere along the way it got stuck to the point it is giving me an error right when I start the tablet saying "magic value mismatch". First time it happened I was able to get back to recovery. And I tried to restore, and didn't work. Tried clearing cache and it hung there for over thirty minutes. Now I can't even get into recovery and error reads the magic value mismatch. So am I bricked or is there a way out of this? And anyone try returning a bricked tablet to Sears? I'm still within my 30 day window.
Sent from my Droid using XDA App

Here's a nice link:
http://forum.xda-developers.com/showthread.php?t=860493

Thanks for the link. This seems to work, as I did not know the low level capabilities. Hopefully, I'll be mod'ing again soon! And for anyone in my position between these two links I figured it out where to get the files:
forum.tegratab.com/viewtopic.php?f=6&t=8
forum.tegratab.com/viewtopic.php?f=13&t=18&p=170

Did you use a newer version of clockworkmod (.12 or higher) with the device, and attempted a firmeware update? If so, it's a known issue and it's why I'm still using .8, right now.
It's not bricked, btw. This device is virtually unbrickable - you will probably need nvflash to fix it, and I have a post that can point you in the right direction:
http://forum.xda-developers.com/showthread.php?t=861950
Hope this helps!

Thanks, but I'm now getting the issue some others had in the other forums, but I don't see a fix where every boot ends up in APX mode. How do I get out of that?
As a side note, I did try the latest updated Clockwork recovery last night, which I believe is 2.5.1.8, that seemed like they added support from ROM Manager.

Sorry, I take it back used, the right zip file and everything is fine. I grabbed the one dated 2010112600 thinking it was a later version. Thanks for the help and the great threads and ROM's!

jkpatel79 said:
Sorry, I take it back used, the right zip file and everything is fine. I grabbed the one dated 2010112600 thinking it was a later version. Thanks for the help and the great threads and ROM's!
Click to expand...
Click to collapse
You might one of the newer devices with the swapped partitions (thats the 11/26 one you used). We still don't know why this is - very bizarre as to why VS (or whatever vendor they use) did this.

roebeet said:
This device is virtually unbrickable
Click to expand...
Click to collapse
Virtually is right. I accidentally bricked mine because I hit one of the devkit .bats while trying to reflash to stock

[Q] Malata T2 (New)

Here's my question. Being new to this whole tablet scene, I bought a Malata Zpad T2 from China. Of course the first thing I do when I charge it up is to get all the Chinese stuff off of it, so I installed CWM and first installed TNT and it worked great. I couldn't leave well enough alone so i thought I would try another firmware and I think it was Vegan and ran into some problems. I tried again to install it but when I went into the files on the SDCard there was quite a bit of stuff missing. I'm thinking the whole Android 2.2 needs to be reloaded but I'm not sure? Also I tried doing a recovery when things started going screwy but CWM said there was no back-up to recover. (I know I did a back-up). Any advice would be appreciated. Thanks, Howie

meandg5 said:
Here's my question. Being new to this whole tablet scene, I bought a Malata Zpad T2 from China. Of course the first thing I do when I charge it up is to get all the Chinese stuff off of it, so I installed CWM and first installed TNT and it worked great. I couldn't leave well enough alone so i thought I would try another firmware and I think it was Vegan and ran into some problems. I tried again to install it but when I went into the files on the SDCard there was quite a bit of stuff missing. I'm thinking the whole Android 2.2 needs to be reloaded but I'm not sure? Also I tried doing a recovery when things started going screwy but CWM said there was no back-up to recover. (I know I did a back-up). Any advice would be appreciated. Thanks, Howie
Click to expand...
Click to collapse
I have one of these picked up in Guangzhou recently. Really like it a lot. Based on what you've said, you may have wiped out your backups in the process. If you are unable to boot into clockwork, or get a ROM to load on to the internal SDCard, you may have to use nvflash to restore bare metal.
This may help you: http://forum.xda-developers.com/showthread.php?t=861950
The only concern I would have with that is the ROM listed there is primarily for the Viewsonic version. It should still work. However, if you want to use bits more native to our tablet, you can go here: http://2.hot12.115cdn.com/pickdown/...gIdeas_XL_3.rar&key2=32342e3137392e39332e3536
I believe that you can use that package with the same instructions in the previous link. Let me know if this is over your head. You did say you were new to this.

Also look at this thread:
http://android.modaco.com/content/a...zpad-t2-development-should-also-work-on-vega/
zPad v2's are not the same as the GTAB (or the zPad v1's) in that they have 1GB of RAM. Using straight GTAB ROM's could cause issues.
That "Big Ideas 1222" is an nvflash image - I know this because I've actually used pieces of it in my own ROMs, for the performance enhancements.

roebeet said:
Also look at this thread:
http://android.modaco.com/content/a...zpad-t2-development-should-also-work-on-vega/
zPad v2's are not the same as the GTAB (or the zPad v1's) in that they have 1GB of RAM. Using straight GTAB ROM's could cause issues.
That "Big Ideas 1222" is an nvflash image - I know this because I've actually used pieces of it in my own ROMs, for the performance enhancements.
Click to expand...
Click to collapse
Roebeet,
I am currently using a grab rom on the ztab... do you think that the performance would be much better if we moved to the bigideas rom? Also, got a weird issue with the dock status being backwards. Thinks it is docked when it isn't and vice versa.
Sent from my VEGAn-TAB-v1.0.0b5.1.1 using Tapatalk

Thanks
Thanks for the replies. Gonna give this a shot tomorrow and I'll let ya know how it works out. Howie

OK
meandg5 said:
Thanks for the replies. Gonna give this a shot tomorrow and I'll let ya know how it works out. Howie
Click to expand...
Click to collapse
Finally got BigIdeas installed. Not sure how, as the first time I installed it it came up Chinese? After a reboot it came up in English. Then USB through my laptop wouldn't work so I went into CWM and mounted or unmounted USB, rebooted and now that works. I think my next dilema is I don't think it's reading my 16GB INTERNAL card as being 16GB. I'm at work now but I'll be checkin when I get home. Thanks, Howie

meandg5 said:
Finally got BigIdeas installed. Not sure how, as the first time I installed it it came up Chinese? After a reboot it came up in English. Then USB through my laptop wouldn't work so I went into CWM and mounted or unmounted USB, rebooted and now that works. I think my next dilema is I don't think it's reading my 16GB INTERNAL card as being 16GB. I'm at work now but I'll be checkin when I get home. Thanks, Howie
Click to expand...
Click to collapse
Is it reading it at something like 14GB?

Nevermind
OK, Nevermind, I thought it was reading lower but it's actually saying 14.4Gb.

No worries

roebeet said:
Also look at this thread:
http://android.modaco.com/content/a...zpad-t2-development-should-also-work-on-vega/
zPad v2's are not the same as the GTAB (or the zPad v1's) in that they have 1GB of RAM. Using straight GTAB ROM's could cause issues.
That "Big Ideas 1222" is an nvflash image - I know this because I've actually used pieces of it in my own ROMs, for the performance enhancements.
Click to expand...
Click to collapse
Hello,
Many of us (Malata Zpad T2) still have problems implementing Gingerbread on their tablets.
All the builds i found here are based on the partition-structure of gtablet.
You were gone an other way with new FW TNT V5 based one big idea1222 ROM.
Is there a change to implement this new GB-ROM's on this base.
For Malata Zpad T2 it has the big advantage of having 1Gb RAM and better performance.

Received WOOT Tablet - Answering Version Questions

Just got my G-Tablet off of WOOT and wanted to let everyone know that it shipped with version 1.1-3389. Just thought I would ease everyones mind around here.

A few others have said the same - thanks! 3389 is a good baseline for mods, FYI.
3588 is what you'd get with the OTA updater, and I would actually recommend doing that first - 3588 came out in January and is a pretty rock-solid stock ROM. It's an even better baseline than 3389, imo. And the 3588 recovery is the only recovery that works with the 3991 UAT, so it might be a requirement for future stock ROMs. We don't know this for a fact yet, but better safe than sorry.

The first thing mine did was update to 1.1-3588. I'm off to figure out how to get the Market on it.

roebeet said:
A few others have said the same - thanks! 3389 is a good baseline for mods, FYI.
3588 is what you'd get with the OTA updater, and I would actually recommend doing that first - 3588 came out in January and is a pretty rock-solid stock ROM. It's an even better baseline than 3389, imo. And the 3588 recovery is the only recovery that works with the 3991 UAT, so it might be a requirement for future stock ROMs. We don't know this for a fact yet, but better safe than sorry.
Click to expand...
Click to collapse
Well apparently there will be a second batch, which I guess mine will be a part of, so there is still a chance for 3991 to still be used.

Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.

I'm guessing they are all 3389 - I'm sure they work off the same image.
However, I'd check it anyway - better safe than sorry, imo.

Tonydiv said:
Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.
Click to expand...
Click to collapse
Yeah I agree your tablet will be like the rest from woot!!!! So if we even see 3991 it will be a ota update!!!!

sigvader said:
Yeah I agree your tablet will be like the rest from woot!!!! So if we even see 3991 it will be a ota update!!!!
Click to expand...
Click to collapse
If you see 3991 on your Woot tablet, please tell us immediately. I would very shocked at this point if that happened, but then again I didn't expect 3389 either. I really thought they were going to be 3588.

Tonydiv said:
Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.
Click to expand...
Click to collapse
One of the woot staffers gave an unofficial update the day after the purchasing ended and said that they were getting a rush shipment on Monday from the vendor to fulfill the second half of the orders. So they are physically a separate set from the first batch.

Just FYI, I got mine today and it was 3389.
Is there a point to doing the update?
Going to flash Vegan and the 5.1.1 add on now.
I copied the update.zip and all the files off the Gtab before I did anything. I'm betting that's a restore to 3389.
Edit: Updater-script says it's 3389.

theroblog.com said:
Just FYI, I got mine today and it was 3389.
Is there a point to doing the update?
Going to flash Vegan and the 5.1.1 add on now.
I copied the update.zip and all the files off the Gtab before I did anything. I'm betting that's a restore to 3389.
Edit: Updater-script says it's 3389.
Click to expand...
Click to collapse
It's not a requirement, but I think it's a good idea to flash to 3588 first. The reason is that you'll get the latest bootloader and recovery, which ROMs like VEGAn don't touch.
Recovery is the one that concerns me, as 3588 recovery seems to be a kind of "gateway" recovery that might (and I stress "might") be needed to get you to a future firmware level. So, imo, I would flash to 3588 first, THEN start using ROMs if you want. It's a safer bet, again imo.
Thanks for the confirm on that update.zip -- sounds like it's stock 3389, like you mentioned.

received my tablet from woot today. ill post back as soon as its charged and powered up with the version.

roebeet said:
It's not a requirement, but I think it's a good idea to flash to 3588 first. The reason is that you'll get the latest bootloader and recovery, which ROMs like VEGAn don't touch.
Recovery is the one that concerns me, as 3588 recovery seems to be a kind of "gateway" recovery that might (and I stress "might") be needed to get you to a future firmware level. So, imo, I would flash to 3588 first, THEN start using ROMs if you want. It's a safer bet, again imo.
Thanks for the confirm on that update.zip -- sounds like it's stock 3389, like you mentioned.
Click to expand...
Click to collapse
I am new to all this, so excuse me for some newbie questions.
Most of the walkthroughs to install a moded ROM, seem to install Clockworkmod first. How is that different from what you call "recovery" here. Will it replace the stock 3588 recovery? Or by the "3588 recovery" do you mean the bootloader part that calls the Clockworkmod. Is there a way to install a ROM without Clockworkmod? This is specifically for 3588.
I ask because I see some discussions about TNT Lite 5 where it seems to break with Clockworkmod. So if we want to get to TNT Lite 5 in the near future, should we now install Clockworkmod?
I am asking this specifically for the woot buyers who it looks like get 3389->3588
Any pointers would be very helpful.
thanks

cbay said:
I am new to all this, so excuse me for some newbie questions.
Most of the walkthroughs to install a moded ROM, seem to install Clockworkmod first. How is that different from what you call "recovery" here. Will it replace the stock 3588 recovery? Or by the "3588 recovery" do you mean the bootloader part that calls the Clockworkmod. Is there a way to install a ROM without Clockworkmod? This is specifically for 3588.
I ask because I see some discussions about TNT Lite 5 where it seems to break with Clockworkmod. So if we want to get to TNT Lite 5 in the near future, should we now install Clockworkmod?
I am asking this specifically for the woot buyers who it looks like get 3389->3588
Any pointers would be very helpful.
thanks
Click to expand...
Click to collapse
Clockworkmod is non-vendor third party recovery replacement, wheras "standard recovery" is stock recovery (this is what the vendor supplies).
TNT Lite 5 was pulled after about a week, due to more than a few issues where users were soft bricking their devices. Going on metrics I tried to compile, the majority of the problems stemmed from the use of clockworkmod, thus my reasoning for not recommending its use anymore. This is despite the fact that the update it was based on was a non-released firmware. I will explain further. Btw, we are seeing similar issues over in the Notion Ink Adam forums in notioninkhacks.com, for the same exact reasons (clockworkmod).
In the case of the GTAB, the vendor (Viewsonic) adds the bootloader.bin to its stock update firmware. And it has been updated at least twice tmk - once in a November firmware update, once in a December firmware update. And also with this 3991 UAT update, but for the sake of argument we won't count that one. But they have updated it in released firmware.
But clockworkmod users do not get that update, as the program doesn't support updating the bootloader.
3388 to 3588 seems to have the same bootloader so, for the short term, using clockworkmod is probably OK. But there is no guarantee that a future update will not require a bootloader change. Again, we have already seen this happen with the NI Adam, and also the Viewsonic non-released UAT. So, with all that being said, I cannot recommend Clockworkmod as a flashing tool.
I've actually kept TNT Lite 5 (which is now TwoTapsX) on ICE specifically because of the expected surge of new Woot users. The last thing I want to happen is for a large number of inexperienced users with mixed information to flash that firmware with the wrong tool (clockworkmod) and then soft-brick their device.
I actually require clockworkmod for my gADAM mod because that mod requires a user data wipe, which standard recovery does not support. But gADAM has a "Recovery Pack" built-in - what this does is allow the user to easily flip between standard recovery and clockworkmod, as needed. Since gADAM is a 1.1-based mod, the use of clockworkmod to flash it is low risk. But if you later flashed to a mod that might require a new bootloader, the Recovery Tool allows you to put standard recovery back before you flash again.
I know this is all very confusing - believe me, it is for me as well. Suffice is to say that modded ROMs are risky business and you should read the instructions very carefully before proceeding. I have started to add the firmware type in my own ROMs as a guide - "1.1" for example. So, a "1.1" to "1.1" firmware mod change should be a low risk, for example. Right now, most of the stock ROMs and probably all the modded ROMs are "1.1" based.

If it is possible, maybe some admin could update the last message in the thread (http://forum.xda-developers.com/showthread.php?t=1006571) you had posted on woot's discussion page. Either link here, or just update and say: hey, people got some woot gTabs in already and they are the 3389 version.
I read this above post, but have not received my woot gTab (so no idea what version I'm getting). Good thing I searched first and found this post. Just to put my mind at ease

eak0703 said:
If it is possible, maybe some admin could update the last message in the thread (http://forum.xda-developers.com/showthread.php?t=1006571) you had posted on woot's discussion page. Either link here, or just update and say: hey, people got some woot gTabs in already and they are the 3389 version.
I read this above post, but have not received my woot gTab (so no idea what version I'm getting). Good thing I searched first and found this post. Just to put my mind at ease
Click to expand...
Click to collapse
i can't update it as the moderators locked it (trust me, I want to update it). I already PM'd jerdog to either open it up or delete it, as I don't think it's needed anymore. I'm not a moderator so I cannot do this, myself.
EDIT: It's been unstickied and updated. TheImpaler handled the unsticky / unlock.

roebeet said:
Clockworkmod is non-vendor third party recovery replacement, wheras "standard recovery" is stock recovery (this is what the vendor supplies).
But clockworkmod users do not get that update, as the program doesn't support updating the bootloader.
Click to expand...
Click to collapse
Thanks for the detailed answer Roebeet!
CWM not updating the bootloader is the main problem isnt it?
Also that it overwrites stock recovery.(True?)
If CWM overwites stock recovery, reverting to 3588 using CWM, might still not enable things like OTA update, right?
So, I see that CWM will work with current ROMS (except TNT Lite 5) and everyone will be happy till the newer ROMS come along based on 3991 or later. At that point, it will become a lot harder for people to get to the new ROM as the new bootloader will have certainly changed.
Alternatively, if people wait for a Viewsonic 3991 or later OTA update from Viewsonic, CWM will work again for some time until the bootloader changes significantly. (possibly).
So how does one get a new ROM without CWM?
I have searched some on the forums and I see
1. Use CWM, but comment out some "assert". This was used by people reverting to stock, and seems sketchy.
2. Use nvflash. Is there a walkthrough for this for Vegan/TNT Lite? I see one for going to bekit 's original image but not to any arbitrary ROM. Also this repartitions the SD, has this caused problems with OTA updates?
3.Using adb. Maybe 2 and 3 are related, but I think did see somewhere to get back to stock recovery using adb. Can we do a new rom update through adb, without risking breaking stock recovery?
I wish I had bought 2 gtablets, one to enjoy and one to tinker with

cbay said:
Thanks for the detailed answer Roebeet!
CWM not updating the bootloader is the main problem isnt it?
Click to expand...
Click to collapse
Correct.
cbay said:
Also that it overwrites stock recovery.(True?)
Click to expand...
Click to collapse
Yes, they cannot co-exist. Stock recovery (specifically 3588) will update the bootloader, I've tested this repeatedly. clockworkmod .8 does not.
cbay said:
If CWM overwites stock recovery, reverting to 3588 using CWM, might still not enable things like OTA update, right?
Click to expand...
Click to collapse
Not exactly. If you have cwm and revert to stock 3588, you might not have the latest bootloader (since clockworkmod doesn't touch that) but everything else should be reverted back to stock. But an important note: I've heard stories from users who used clockworkmod to revert to 3588 stock and, although it worked, recovery was actually broken. This happened to a lot of users who were trying to get back to 3588 stock before they upgraded to my later-pulled TNT Lite 5. This is actually the reason why I created the 3588 Recovery Pack.
cbay said:
So, I see that CWM will work with current ROMS (except TNT Lite 5) and everyone will be happy till the newer ROMS come along based on 3991 or later. At that point, it will become a lot harder for people to get to the new ROM as the new bootloader will have certainly changed.
Alternatively, if people wait for a Viewsonic 3991 or later OTA update from Viewsonic, CWM will work again for some time until the bootloader changes significantly. (possibly).
Click to expand...
Click to collapse
Possibly. Lets assume for a moment that the new firmware is a released "1.2" with a new bootloader. Once everyone moves off the "1.1" to "1.2", the issues with the bootloader will probably stabilize. Until there's a "1.3", of course.
And yes, this is all speculation. Viewsonic could throw us a curve balll with their next firmware.
cbay said:
So how does one get a new ROM without CWM?
I have searched some on the forums and I see
1. Use CWM, but comment out some "assert". This was used by people reverting to stock, and seems sketchy.
2. Use nvflash. Is there a walkthrough for this for Vegan/TNT Lite? I see one for going to bekit 's original image but not to any arbitrary ROM. Also this repartitions the SD, has this caused problems with OTA updates?
3.Using adb. Maybe 2 and 3 are related, but I think did see somewhere to get back to stock recovery using adb. Can we do a new rom update through adb, without risking breaking stock recovery?
I wish I had bought 2 gtablets, one to enjoy and one to tinker with
Click to expand...
Click to collapse
Right as the Wooters were buying their GTABs, I did a few things to help users out with recovery options.
1) I created a "3588 Recovery Pack". This is a flash update.zip that will add few sripts to your rooted 1.1-based ROM and will allow you to flip between clockworkmod and 3588 stock recovery with a minimum of fuss.
2) I added the Recovery Pack to TNT Lite 4.3.0 and gADAM 1.3.0, the two active mods that I support. So it's built-in there.
nvflash is a different animal. Think of it as a low-level format tool for when your device is messed up and cannot boot anymore. It's good to know about it and learn how to use it, imo - some devices like the Advent VEGA and even Viewsonic's Viewpad10s offer nvflash updates, only. nvflash is a tool specifically for Tegra 2 devices.
adb is a generic "remote shell" tool that is part of the Android SDK. You can find information about adb here or on other Android sites, and that would apply to the GTAB as well. you can make changes via adb, including flash updates, but you need to know what you're doing.

roebeet said:
2) I added the Recovery Pack to TNT Lite 4.3.0 and gADAM 1.3.0, the two active mods that I support. So it's built-in there.
Click to expand...
Click to collapse
That is great! I dont think I will have the patience to wait for Viewsonic to release an update beyond a few weeks.
I was debating between Vegan and TNT Lite, the Recovery Pack will push me towards TNT Lite, at least till I can get a 1.2 bootloader.
Thanks for all the help
--

Recently received G tablet from woot
I'm new to this and would like to know what the best thing to do to my viewsonic g tablet purchased from woot that makes it run the best way. I'm not sure how many and what mod's are recommneded. I've read alot of the posts here and figure TNT Lite (version?) is highly recommended. It is 3588, build frf91. Please give me the best mod's to do, what versions, and where I can find the step-by-step to make it all happen. thanks

Roebeet's new 1.2firmware "Brilliant Colors"

http://www.youtube.com/watch?v=cWtM7xyHtQs
Roebeet has made a very stable build on the 1.2firmware. Itwasnt hard at all to get there. I think if and when VS brings out new codes, it will only be 1.2 compatible. My thoughts only, not gospel
Anyway, this is how I was able to get this working the first time without any issues.
1) NVflash to base build
2) CWM to clear all data, cache. I used Calkulin's FORMAT ALL. boot to the os.
3) usb to the comp and slip in 3588 and recovery folder. rename 3588 to "update"
3) reboot with power and vol pressed. automatically installs 3588.
4) once insalled, boot to os.
5)usb to the comp and slip in 4349 and recovery folder. rename 3588 to "update"
6) reboot with power and vol pressed. automatically installs 4349.
7) once insalled, boot to os.
8) now find Roebeets Brilliant Ccolors ROM in another forum and repeat step 5 and 6 for this ROM. you shuold be good from there!

While I definitely respect the dev's work, I think I'm going to stay away from 1.2-based ROMs until VS gets its firmware upgrade situation sorted out once and for all.

Did you mean ... rename 4349 to "update" in this step?
5)usb to the comp and slip in 4349 and recovery folder. rename 3588 to "update"

g0t0 said:
http://www.youtube.com/watch?v=cWtM7xyHtQs
Roebeet has made a very stable build on the 1.2firmware. Itwasnt hard at all to get there. I think if and when VS brings out new codes, it will only be 1.2 compatible. My thoughts only, not gospel
Anyway, this is how I was able to get this working the first time without any issues.
1) NVflash to base build
2) CWM to clear all data, cache. I used Calkulin's FORMAT ALL. boot to the os.
3) usb to the comp and slip in 3588 and recovery folder. rename 3588 to "update"
3) reboot with power and vol pressed. automatically installs 3588.
4) once insalled, boot to os.
5)usb to the comp and slip in 4349 and recovery folder. rename 3588 to "update"
6) reboot with power and vol pressed. automatically installs 4349.
7) once insalled, boot to os.
8) now find Roebeets Brilliant Ccolors ROM in another forum and repeat step 5 and 6 for this ROM. you shuold be good from there!
Click to expand...
Click to collapse
I agree
The firmware is running real stable.. I installed it last night and i am loving it.

ps - if you search for Brilliant Corners, it will be easier to find

cd112 said:
I agree
The firmware is running real stable.. I installed it last night and i am loving it.
Click to expand...
Click to collapse
Any points on what you like on it, better than TNT Lite 4.4 (or any 1.1 ROM ). Things you could not do/were not as good in the older ROMs.
thanks
--

i installed it when it was released. heads up make sure to install the 1.0.1 supp so that you can have flash support back up and rollin.

This rom is the only one that makes the tab seem like a tab and not a giant phone I've seen so far. Assume and market has no issues for me every other rom I couldn't get market to work.
Just my opinion!
I believe the new update that was pulled should have been more like this .
Would be better with a kernel but definitely a step in the right direction.
Dale

notsob2002 said:
This rom is the only one that makes the tab seem like a tab and not a giant phone I've seen so far. Assume and market has no issues for me every other rom I couldn't get market to work.
Just my opinion!
I believe the new update that was pulled should have been more like this .
Would be better with a kernel but definitely a step in the right direction.
Dale
Click to expand...
Click to collapse
Keep in mind this is not a TnTLite-based mod, but it's based on VEGAn-Tab from GoJimi - it's a MOD to an existing ROM repackaged with a locked bootloader from Viewsonic. The theme applied looks cool!
EDIT: After a nice PM from roebeet, I am clarifying for those who don't know the following:
VEGAn-Tab, in it's original state, was a collaboration between GoJimi, rothnic and roebeet
as already stated in this post, this new Mod is based on VEGAn-Tab and will over time take on a different form, but it's base is VEGAn-Tab
there is no insinuation that roebeet lifted anything from GoJimi, only a correct statement that the base for this Mod came from VEGAn-Tab
There. That should hopefully clear up any misperception or misunderstanding as to what I was stating above. This mod looks great roebeet.

dannyboy22 said:
Did you mean ... rename 4349 to "update" in this step?
5)usb to the comp and slip in 4349 and recovery folder. rename 3588 to "update"
Click to expand...
Click to collapse
sorry. Yes rename to " update". Make sure you reinput another recovery folder. While the folder would still be there, the system deletes the command file so it doesn't loop back to installing the same file on a reboot.

notsob2002 said:
This rom is the only one that makes the tab seem like a tab and not a giant phone I've seen so far. Assume and market has no issues for me every other rom I couldn't get market to work.
Just my opinion!
I believe the new update that was pulled should have been more like this .
Would be better with a kernel but definitely a step in the right direction.
Dale
Click to expand...
Click to collapse
hopefully when the new upload from VS turns up, it will correct the minor issues it has now. Very minor issues I should stress.

I must have missed it but did Robert stop posting here?
Sent from my VEGAn-TAB using XDA Premium App

shadowhawk2020 said:
I must have missed it but did Robert stop posting here?
Sent from my VEGAn-TAB using XDA Premium App
Click to expand...
Click to collapse
yeah, unfortunately. Google "Roebeet and XDA" and you will find some tidbits. It seems a real shame, especially for a site like this, to lose someone who really turned out great work and genuinely cared for and responded to questions about his work.

Thanks for the heads up on this rom. Definitely have to check this out.

cbay said:
Any points on what you like on it, better than TNT Lite 4.4 (or any 1.1 ROM ). Things you could not do/were not as good in the older ROMs.
thanks
--
Click to expand...
Click to collapse
hi cbay,
First of all this rom is based off the 1.2 (4349) bootloader. Also it has the feel of the Vegan-tab outlook. It is pretty responsive and the FC are almost to none. So far it has been stable and running like a champ.. I know roebeet has removed the phone apk to improve the battery life as well so that a big plus. Once i play with it more i will know more about this rom.
The HD videos are working really good as well as the tegra games.
Let us know how u make out.

So what's the benefit, if any, of installing this as opposed to VEGAn 5 with the supplement?
I am currently running 5 and it is VERY stable for me. Love it. It's my Daily Driver.
Any improvements on installing this? They look they same for the most part.

I have vegan 5 on one tablet and brilliant corners on my other tablet. I honestly can't really tell a big difference. BC may be slightly more stable. I still take the vegantab with me to work everyday but that is more because i have it setup perfectly than any particular problem with BC.
Both are very good.

pitamakan said:
While I definitely respect the dev's work, I think I'm going to stay away from 1.2-based ROMs until VS gets its firmware upgrade situation sorted out once and for all.
Click to expand...
Click to collapse
Your lost then

jasco13 said:
I have vegan 5 on one tablet and brilliant corners on my other tablet. I honestly can't really tell a big difference. BC may be slightly more stable. I still take the vegantab with me to work everyday but that is more because i have it setup perfectly than any particular problem with BC.
Both are very good.
Click to expand...
Click to collapse
I think hardware acceleration for vids work on BC but not vegan. Dun quote me, i haven had time to flash but ill do BC this weekend for sure. Nv tried vegan, always been on TNT Lite.

amusedkid said:
Your lost then
Click to expand...
Click to collapse
Nah ... the current Vegan ROMS work great, without the uncertainty.

Firmware 5699 Released OTA

Viewsonic has finally released a update OTA for the GTablet:
http://www.viewsonic.com/gtablet/support.htm

Guess what this one bricks
Just like the one we had last April, this new one bricks as well. Mine doesn't even want to read the external sd card. I tried nvflash and it doesn't recognize it. Save this one and try it later.

Installed the Firmware 5699 OTA this morning. Upgraded with no problem.
After 10 months of no support from VS, I wonder why now? I wish there was a changelog for this...

No changelog. Wow. Never update firmware without at least reading the changelog....esp if system is stable

Great. Now give us official ICS or source code

Pawnty said:
Great. Now give us official ICS or source code
Click to expand...
Click to collapse
That would be very interesting.
EDIT: not going to happen though.

Your cool Viewsonic, STILLLLLLLLL android 2.2...

I feel like this is a more of a low blow than anything. Us as users ***** for literally an entire year and Viewsonic labels the gTablet as an archived product on their website basically fully dropping support for it. Now 2012 rolls around and ICS is finally making its way onto a slew of devices and Viewsonic drops another update to a Froyo rom? Really? That was 2 generations ago... Like the hardware is still there to do something with this device. Team Drh has been proving this as we continue development with ICS. Now if Viewsonic wants to help us push ahead with this mission, by all means please help us out. But dropping updates to Froyo is BS if you ask me. But hey, what do I know...I'm just a user with an "outdated" tablet.

fosser2 said:
But hey, what do I know...I'm just a user with an "outdated" tablet.
Click to expand...
Click to collapse
LOL! That's funny!

Changelog is up. Looks like everyone is being pushed to BL 1.2 now.
http://www.viewsonic.com/gtablet/support.htm

Ok I NVflashed my Gtab just for shticks and smiggles to see what this 5699 update was really all about...
Conclusion...GARBAGE! Plus it tells you to restart your Gtab and ends up having a broken android icon with an exclamation mark on the screen!!
Oh well...now Imma flash my PreAlpha ICS rom again! YEY!

ml_boston said:
Changelog is up. Looks like everyone is being pushed to BL 1.2 now.
http://www.viewsonic.com/gtablet/support.htm
Click to expand...
Click to collapse
Not much of a change log. They state over 40 enhancements, but then only list four.

arveeee said:
Ok I NVflashed my Gtab just for shticks and smiggles to see what this 5699 update was really all about...
Conclusion...GARBAGE! Plus it tells you to restart your Gtab and ends up having a broken android icon with an exclamation mark on the screen!!
Oh well...now Imma flash my PreAlpha ICS rom again! YEY!
Click to expand...
Click to collapse
Sounds like your GTab didn't take the update. It sounds a lot like the OTA update failures on Xoom's and TF's when its been rooted or modded.
Honestly though I do not see any visible changes. All code enhancements is my guess.

I am new and have only had the gtab for two months. I thought this is an update and I should download. Now my gtab doesn't work. I am not a techy by and stretch of the imagination.
I have done the power and +volume and it said recovery and had a wrench/screwdriver on it. Then it was coming on but stuck in the tap n tap screen and then turning off.
I only use to read and play games and will be nice to have on vacations or when away from home/work but now it doesn't work. I could use help.
Any help is appreciated. Wish I could take a class. Looked at viewsonic for dummies but even that is over my head.
Thanks for any help.

dleem said:
I am new and have only had the gtab for two months. I thought this is an update and I should download. Now my gtab doesn't work. I am not a techy by and stretch of the imagination.
I have done the power and +volume and it said recovery and had a wrench/screwdriver on it. Then it was coming on but stuck in the tap n tap screen and then turning off.
I only use to read and play games and will be nice to have on vacations or when away from home/work but now it doesn't work. I could use help.
Any help is appreciated. Wish I could take a class. Looked at viewsonic for dummies but even that is over my head.
Thanks for any help.
Click to expand...
Click to collapse
Do you know if your tablet was modified (custom rom, rooted, etc.) when you took the update? People with modified stock roms and recovery seem to be having this issue on another forum.
I would say the easiest fix to try would be to drain the battery completely (might take a while) if you can boot into recovery (power) + (volume+) or apx (power) + (volume-) and leave it on till it dies (edit - if you can boot into recovery try the wipe data/factory reset option if there is one, then try to reboot. That might fix it also). Keep doing that till the tablet won't turn on anymore. Then charge it and try turning it on again. If you are lucky it will reset your tablet to stock without any complicated fixing or flashing.
Remove your SD card if you have one before you do this. You will also loose any data not stored on your SD if you do reset it but hopefully it will work again.

Same Problem
I had this same problem yesterday after downloading the OTA update. I was able to restore the bricked device by holding the power for 5 seconds (figured it was shutting down in that amount of time) restarting in APX mode (power button and volume - simultaneously) and I did not see a screen response, I plugged in the USB cord and checked the safely remove hardware widget on the bottom right of windows system tray and could see NIVIDIA device. Therefore, I knew the GTAB was on and in APX mode. I then went to the rom of choice (stock tapntap) and double clicked the batch file for the ROM and watched as it went to the CMD prompt screen and transferred the file. I did have to run the batch file several times to get it to work...but it did. I downloaded the OTA again, and discovered the same results with the same fix. I will not download the OTA update a third time. Good Luck.

I had just put my VS GTab back to complete stock 1.2 4349 in anticipation of the ICS Rom release coming soon. My GTab showed a OTA update was available and I accepted the update. It downloaded and ran through the process with no issues at all. Some of the people having issues must have modified or rooted devices.
---------- Post added at 08:36 AM ---------- Previous post was at 08:34 AM ----------
dleem said:
I am new and have only had the gtab for two months. I thought this is an update and I should download. Now my gtab doesn't work. I am not a techy by and stretch of the imagination.
I have done the power and +volume and it said recovery and had a wrench/screwdriver on it. Then it was coming on but stuck in the tap n tap screen and then turning off.
I only use to read and play games and will be nice to have on vacations or when away from home/work but now it doesn't work. I could use help.
Any help is appreciated. Wish I could take a class. Looked at viewsonic for dummies but even that is over my head.
Thanks for any help.
Click to expand...
Click to collapse
http://viewsonic-gtablet-for-dummies.webs.com/
dleem this is not difficult. Sit down, focus and read. It has step-by-step instructions. Go to Code Red.

ml_boston said:
Changelog is up. Looks like everyone is being pushed to BL 1.2 now.
http://www.viewsonic.com/gtablet/support.htm
Click to expand...
Click to collapse
Yes. I can confirm this on my old device ( was running 1.1.3588 ). I went ahead and updated the tablet, and found out the exact upgrade path.
I'm for devices using firmwares older than mine, the first update will probably be to version 1.1.3588, and then from there, the rest of the updates.
The first update after 1.1.3588 is 1.1.3588+. After installing this update, the tablet will have be able to update to 1.2.5699 using the update program, or waiting for the notification.

yup.. downloaded find and dies on the install....I wonder if I take CWM off and do a factory restore if it would work.

Clear data/cache
To upgrade, you have to use stock recovery with 1.2 bootloader. Not rooted. No CWM.
In stock recovery clear data/factory reset, clear cache; otherwise, you'll get stuck. You will lose everything so backup with Titanium Backup.
I keep a copy of Titanium Backup and Amazon Appstore Apps on my SDCARD and SDCARD2 to install after installation and restore apps.
Plants vs Zombies crashes on this.
Pixel Rider on Slatedroid will eventually mod this with market and root to be named Detonator.
If you like stock, stability and camera, this ROM has a niche.