On mine no the sound or the video was working. I had to revert to GB Rom. Going on vacation and I need netflix for my daughter
Sent from my Desire HD using Tapatalk 2
[ROM - 1.2] BETA ICS 4.0.X - Team DRH (Update 07/02/12)
- Thread starter fosser2
- Start date
-
- Tags
- ap10a1 ics hcl me ap10a1
On mine no the sound or the video was working. I had to revert to GB Rom. Going on vacation and I need netflix for my daughter
Sent from my Desire HD using Tapatalk 2
Were you on our newest rom (1.3) because in the rom the hdmi port on the dock is working with video but does not have sound yet. Keep in mind this is for the hdmi on the dock the hdmi cable for the gtablet is not working yet.
Probably i might be lost , but i will need some help on making my pc recognize the mtp file , or how can i make the tablet work with the to transfer a file via usb?
if anyone knows i will appreciate the help.
From the OP
HOW TO INSTALL MTP DRIVERS
Open Device Manager and find the offending TeamDRH MTP device.
Right-Click and choose Update Driver Software
Then choose Browse My Computer for Driver Software
Then click Let Me Pick From a List of Device Drivers on My Computer
Then choose All Devices
When that list populates choose Standard MTP Device followed by MTP USB Device
Click Yes to the warning and VIOLA!
Also if you have issues like that, boot into recovery and access usb mount there.
Also, uncheck android debugging under settings/developer options/ android debugging. Pc will install drives.Probably i might be lost , but i will need some help on making my pc recognize the mtp file , or how can i make the tablet work with the to transfer a file via usb?
Last edited:
JUGOMAN said:
Thx guys i will try that tonight , at least last night i went by recovery mode and uploaded some files, but will test those two options .
The rom has been working fantastic so far since installing it last saturday. All my sounds work.
Today all of a sudden I get a pop up screen and an error " Unfortunately, System UI has Stopped". I click OK and it goes away for 15sec. and comes back again. What can I do to fix that??
Sent from my TeamDRH ICS for GTablet using XDA Premium App
Today all of a sudden I get a pop up screen and an error " Unfortunately, System UI has Stopped". I click OK and it goes away for 15sec. and comes back again. What can I do to fix that??
Sent from my TeamDRH ICS for GTablet using XDA Premium App
Did you do a re-boot? That usually fixes a lot of stuff.
If not, there are three things that you can do in CWM that do not cause you to loose any settings or data: you could do a "fix permissions" ; you can wipe the cache; & (in advanced) wipe the dalvik. The only negative is that the next boot will be a little longer than normal.
Last edited:
Sounds like you changed DPI (change it back to 120). Also try resetting permissions.
Great ROM
Great ROM guys. Thanks as always.
Quick question (and I see its been discussed):
HDMI out through dock did not work at all for me. Some posts stated video should work but not audio. My question is will any other compatible kernel work with this ROM for video / audio out through HDMI?
Thanks again.
Great ROM guys. Thanks as always.
Quick question (and I see its been discussed):
HDMI out through dock did not work at all for me. Some posts stated video should work but not audio. My question is will any other compatible kernel work with this ROM for video / audio out through HDMI?
Thanks again.
I changed it to 240 dpi cause I can't stand how small every thing is. And I did do the cache & d. cache wipe + fix permissions and that still didn't fix it.
I'll changing dpi again and see that fixes it. Thanks.
Sent from my SGH-T989 using XDA Premium App
That is weird, it is working fine here. You are using a g-tablet correct (just have to check we sometimes get posts from hannspad users too)?
As far as kernels there are none other than ours for ICS that work with the dock as far as I know. Have you tried a different hdmi cable? Or maybe the port on the dock is not functioning correct?
Ok guys I just flashed over to the latest AOKP rom and had issues with sound, but I like the option of changing the theme in it So I ripped apart the system apps looking for the app theme and found it. If you haven't done it yet it does work with DRH ICS. Attached below is the apk that needs to be placed into the system/app folder then reboot. After reboot go into system setting and under themes apply new theme and reboot into CWM and fix permissions and enjoy. Hopefully this will be applied in the nested release or to OP.
Will do screenshots in a bit.
Also uploaded font.zip to change the fonts in the UI if anyone would like them.
Instructions for this.
1. Using root explorer or ES file with root access and allow to write system. Unzip file and open folder.
2. Copy the 3 images over to ./system/fonts and except it to merge over existing files.
3. Hold power button down to force power down and reboot and enjoy.
Will do screenshots in a bit.
Also uploaded font.zip to change the fonts in the UI if anyone would like them.
Instructions for this.
1. Using root explorer or ES file with root access and allow to write system. Unzip file and open folder.
2. Copy the 3 images over to ./system/fonts and except it to merge over existing files.
3. Hold power button down to force power down and reboot and enjoy.
Attachments
Last edited:
I'm having the same issue. Tried to upgrade to 1.3 using the DRH app update, then normal dl. Clearing cache and factory reset every time. just did the 300mb nvflash with the same results.
Just trying to pass on what I did in hopes it would help. In the mean time 1.2 works great! You guys are setting the bar HIGH!
Thanks for all your hard work!
Try NvFlashing back to the older 1.1 bootloader and then flashing the rom, we have found that this works for some people.
No I was not, I was using the prior version. Anyway without sound still a no go for me. It is a shame my tablet run super smooth with this rom.
Sent from my Desire HD using Tapatalk 2
I was just about to suggest that. I used that same path after restoring back to 1.2 stock and taking a OTA update on TapUI. When I did the update I tryed loading different 1.2 Roms and only a few would load up using the CWM 5504 beta 15. Everything loaded up fine using 3028 though. So I NvFlashed back to 1.1 using the guide from the great roebeet found here http://xdaforums.com/showthread.php?t=861950 . Then after that I NvFlashed 1.1 with CWM 08 to clear out the internal storage with a partition 0/2048, a wipe data factory reset, cache wipe. Then NvFlashed 1.2 w/ CWM 3028 where I performed the same steps, but I also did a full complete format of data, system, cache and boot. Forced a power down to perform the last NvFlash the CWM 5504 package from the OP with following the in instructions to the "T".
I was trying to update from cm 7.2
I followed the op instructions to the letter white data system cache dalvic, the works.
I kept getting the 3 birds boot loop.
I've then tried the 300 megabytes system partition nvflash.
Still did not work.
I tried the troubleshooting method of installing 1.1 then 1.2 then the drh 1.2 with clockworkmod 5504
I still can't get past either the 3 bird boot loop or birds just sitting there.
Sent from my Dream/Sapphire using Tapatalk 2
I followed the op instructions to the letter white data system cache dalvic, the works.
I kept getting the 3 birds boot loop.
I've then tried the 300 megabytes system partition nvflash.
Still did not work.
I tried the troubleshooting method of installing 1.1 then 1.2 then the drh 1.2 with clockworkmod 5504
I still can't get past either the 3 bird boot loop or birds just sitting there.
Sent from my Dream/Sapphire using Tapatalk 2
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
46
CLICK PIC FOR TEAM HOMEPAGE
Now for the moment you all have been waiting for...
Team DRH (Dirty Reset Hole) is proud to announce the public beta for Ice Cream Sandwich. The name "DRH" came from the hole that all of the developers had to drill into the back of their tablet to access the on-board reset button. As you all probably know, development for this project started back in August and has finally developed into a mostly stable release. Ice Cream Sandwich is a huge jump for the G-Tablet community because along with the building of ICS specifically for SMBA1002 (G-Tablet), the Linux kernel backbone had to be reworked from the ground up.
DISCLAIMER
Attention commuters of the intertubes! The group of individuals known as Team DRH take absolutely NO RESPONSIBILITY for any DAMAGE that YOU cause to YOUR device! This "labor of love" we call and Android ROM comes AS IS and is not an official release by any means. If you have not already SOILED your device by flashing a custom ROM then to do so will VOID any WARRANTY you may have left. Team DRH and its affiliates are not responsible if your G-Tablet does any of the following: Explodes, Flies off to space to battle the Flying Spaghetti Monster, Is generally awesome, solves world hunger or explodes... again. (OK We take responsibility for you Tablet becoming Awesomesauce.) So in essence... Flash this totally rad ROM at your own RISK and prepare to Spontaneously Combust with AWESOMENESS!
WHAT WORKS
- WIFI
- Hardware Acceleration
- Sleep!
- WiFi
- Bluetooth
- Sensors
- Sound
- USB/MTP (If you plug in USB while your tablet is asleep you will have a SOD)
- Capacitive Buttons
- Hardware Buttons
- USB Flash Drives
- Proper SD Card Mounts
- HD Videos
- More to come...
WHAT'S NOT WORKING
- Camera
- Microphone (Works but drops after 6-8secs)
- Possible ROM Slowdowns
- HDMI Audio
- More to come...
List of Common ICS Problems
http://xdaforums.com/showthread.php?p=23146434
HOW TO INSTALL
- Boot into current version of CWM and "Wipe data/factory reset"
- Partition Internal SD Card (2048M/0)
- Turn tablet off
- Download the following file <--- Seriously don't skip this step unless you are 100% positive that you have a 250M system partition
- NVFLASH the file following the instructions that are included for Windows/Linux users
- Upon reboot of tablet let T&T fully boot and then shut it down
- Reboot into recovery
- Flash the Rom/Gapps
- Enjoy
HOW TO INSTALL VIA DRH NEWS APP
1. Open DRH News App (You Will be notified that you have an update)
2. Download Update
3: Reboot into CWM
4: Wipe Data and Cache
5: Flash Update.zip
6: Flash Your Gapps
7: Reboot
8: Enjoy
FINAL THOUGHTS
This build has been tested but not to the extreme. It is called a "beta" test for a reason. Sleep is properly working and I have not had to use my reset button in weeks. I'm not trying to scare anyone but the possibility of a kernel panic is still there. This build is very stable and deserves the beta tag but if you find yourself in a snag you might have to press the internal reset button. Here is a picture of where to find the button if you are really in a bind. PICTURE If you have the balls to open your tablet, just drill the reset hole while you're in there. You already voided your warranty
DOWNLOAD LINK
ROM/GAPPZ Package: TeamDRH ROM
ROM (Includes GPS Mod): TeamDRH GPS ROM <-- Only use if you physically installed the internal GPS mod as documented here. This rom is not updated to 1.3 yet.
Remember this is a beta build. It will run nicely for the most part but I'm sure that there will be glitches a quarks that we have not seen. I will keep the what works/doesn't work section updated so we don't have tons of posts cluttering the thread. Also these links will be updated pretty regularly when we have new builds to release.
CHANGE-LOG
The ROM's system folder was very close to the max size our system partition could handle on the G-Tablet and with any bad blocks, it was more than the G-Tablet could handle and installing GApps made it even worse. So on initial boot everything was fine, because all the apps that make temporary files don't make them until after initial boot, but in the process of making those temp files it corrupts system files that are already loaded and running, so on a reboot the system fails because the files are now corrupted. This also effected the overall speed of the ROM. This should be fixed with the increased system partition from 200M to 250M.
TeamDRH-ICS-Beta-1.3.zip 07/02/12
- Kernel changes to help stability
- Wifi Updates (latest bcmdhd android code)
- Changes to sound (should reduce audio lag)
- Mic Partially Working (Will record for roughly 6 - 8 seconds)
- Dock Support with HDMI and Ethernet (No Sound over HDMI yet) This includes a dock clock mode
- "Blinkies" Have been fixed
- Updates to CM9 code. Now includes lots of the CM9 features
- Overall stability improvement
- New Boot Animation
- Added Sound to Boot Animation (Optional)
- New Default Wallpaper (created by annel)
- Installer Updated
- Gappz Changes
- Updated Google Plus
- Updated Google Books
- Updated Google Chrome Browser
- YouTube Updated
- Google Drive Updated
- Google Play Updated
- Google Currents Updated
- Added Google Magazines (From JellyBean)
- Added Google Ears (From JellyBean)
- Probably more changes too this is just all I could remember
HOW TO INSTALL MTP DRIVERS
Open Device Manager and find the offending TeamDRH MTP device.
Right-Click and choose Update Driver Software
Then choose Browse My Computer for Driver Software
Then click Let Me Pick From a List of Device Drivers on My Computer
Then choose All Devices
When that list populates choose Standard MTP Device followed by MTP USB Device
Click Yes to the warning and VIOLA!
Hope you all enjoy the TeamDRH gTablet ICS preview!!
POSSIBLE MARKET ERROR
Upon start up Android Market may give you an error when you try to download an app. The fix for this is to go into settings/applications and force close market. Upon doing that clear app data and you should be good to go.
IF ALL ELSE FAILS (Only do this If I tell you too)
Try doing what is posted here
If you like this project and appreciate the extreme amount of time that the devs put into this please donate:
Donate to TeamDRH: LINK
If you would like to donate to single people:
Ch3vr0n5: LINK
Treznorx: LINK
Fosser2: LINK
The3dman: LINK
Plastikman: LINK
Mayday_jay: LINK
Dwagner:
Tlb1961: LINK
Busa_blade:
Jaybob413:
Clemsyn: LINK
(This is not a complete list yet changes are still being made)
Information on G-Tablet Camera!!!
http://www.slatedroid.com/topic/290...update-040112/page__view__findpost__p__346429
Video (courtesy of pagantek):
Pictures:7TeamDRH Change-log:
TeamDRH-AOSP-Preview-1e-LDPI.zip 02/08/12
- USB/MTP
- Vold.fstab
- USB Flash Drives work if plugged in when tablet is off, then booted
- SystemUI notification toggle bug
- TeamDRH Welcome in Trebuchet
- 3g Icon
- Few other little adjustments...
- Few extra added apps
- Google Maps
- Google Chrome Beta
TeamDRH-AOSP-Preview-1F-LDPI.zip 02/16/12
- USB/MTP Now works even if plugged in on boot. If your tablet is asleep and you plug in USB your tablet will get SOD!!!
- USB Flash Drives work should work if plugged whenever
- New Touchscreen driver (should be more responsive)
- New Battery Driver (should perform better. Has a charging icon issue.)
- Capacitive keys should now fully work
- Bluetooth now works
- Few other little adjustments...
- Few apps added/deleted
- Tweaked Permissions
- Should perform faster
TeamDRH-ICS-Preview-2A.zip 02/29/12
- Added ROM control in settings.
- Adjusted Dalvik Cache sizes for better performance (thanks community)
- Much faster Read/write speeds (probably better than Froyo)
- Many i2c/clock changes to the kernel to improve stability
- Amount of system ram increased from 295M to 359M!
- Other various tweaks and speedups built into the ROM
- Games should play better in this release
- Few apps added/deleted
- Tweaked Permissions
- Should perform faster
TeamDRH-ICS-Preview-2B.zip 03/01/12
- Moved some apps to the /data folder to reduce the size of the /system folder
- New Boot Img - Fixes cache size
- Added FakeIMEI to the framework so some apps that request one don't crash (ex. XDA App)
- Moved some apps to the /data folder to reduce the size of the /system folder
- Added a new version of GAPPS
- Very minimal app install (includes: Calender, Music, Youtube, Gmail, Gallery, Market)
3DGtaB_GAppZ_v7B.zip 03/17/12
- Added new market/music Google play apps
- Updated Google applications
TeamDRH-ICS-Beta-1.0.zip 03/17/12
- Changed ROM naming convention for future use
- Overclocking (max 1.2GHz for now)
- ROM is reworked and running on CM9 as a base
- Noticeable speed improvements
- 250M system partition is a MUST now
- Stability is improved
- In-ROM battery stats should now be fixed for almost everyone
- Added new market/music Google play apps
- Updated Google applications
- New DRH-News App
- Added Play Store (Google Market)
- Added Play Store (Google Market)
- All Google applications are now updated and latest
TeamDRH-ICS-Beta-1.1.zip 04/01/12
- Performance enhancements (based on some SuperCharger settings)
- Kernel updated with new governors
- Kernel updated with new i/o schedulers
- Android updated to 4.0.4
- Rom control has additional performance settings
- Updated Gmail to 4.0.4
- Update to Google Books
- Fixed calender sync issues some people were having
- Added the new installer that TeamDRH will now be using! (it's awesome!!!)
- GAppZ full and lite will now be an all inclusive package. Just flash and follow the instructions.
TeamDRH-ICS-Beta-1.2.zip 04/21/12
- ROM has been updated to include various performance tweaks
- Kernel has added touchscreen fix (hopefully fixes most games)
- Most i/o schedulers removed for now due to incorrect throttling
- Rom control has additional performance settings and is reorganized
- WIFI modules updated
- Incorporated TeamDRH Aroma installer (now includes ROM and GAppz)
- ROM does have issue where at times, will not go to sleep (screen will turn off then flash back on) aka "blinkies"
6
That's unrelated to whatever slowdowns you're experiencing. But, to clean up /cache, just boot into CWM and "format /cache".
Yeah. The performance is pretty bad and I'm not sure exactly where the problem lies. Most people point to the paucity of memory being the culprit, and while it may contribute quite a bit, I don't think that's all there is to it: For one thing, there are phones with just 512 MB of RAM comfortably running ICS on them. For another, I see a lot of ANRs and processes being sent SIGQUITs (SIG 3 in the logs) to generate those ANRs. For yet another, the CPU load looks very high when there's lag.
I also see that the ro.build.type is set to "userdebug" in /system/build.prop instead of the commonly seen build.type of "user". Changing the build.type to "user" stops most of the ANRs. I don't know how Android is built, but, in the Linux world, we usually have 2 kinds of builds for a product: release (what gets shipped) and internal (AKA engineering). The difference is mainly in what compiler flags are used when building the product. For engineering builds, compiler optimizations are turned off and the debugging flags are turned on. These builds are pretty slow and use a lot more memory and CPU than the release builds. Going by what I said about the build.type and ANRs above, this is one thing for the devs to check.
Try these things to reduce lag:
In Settings > ROM Control (set on boot if you're happy with)
1. Reduce dalvik VM heap size for apps to 64M.
2. Reduce the free memory setting to 50MB.
In Settings > Developer options (need to set on each boot)
3. Reduce the no. of Background Processes to 1 or 2.
4. Check the Destroy Activities ... option.
Those last 2 really make a noticeable difference, but, you can, if you wish, skip 1) and 4) and still not impact performance all that much.
It's the battery. Don't know what triggers it, though, or how to fix it. I'm trying to look into it.
One final thing before I hit the sack:
Most things that people do to detect bad blocks on the NAND (only looking at the dmesg output, for instance) is not very effective. Here's a simple way to be absolutely certain that the ROM has been installed correctly and fully onto the gTab. The idea is an old one, going back to Dan Farmer and his COPS package (early 1990s). Basically, it is to:
1. have the ROM packager calculate on his dev box the SHA1 checksum of every file that will be installed.
2. Install this SHA1 checksum file along with the ROM--as, let's say, /system/etc/ROM-files.sha1. (Remove entries for files not installed during installation--not very hard)
3. User can check using a shell script (or the command below) that the ROM is OK any time he/she wants. If the checksums compute OK, then you too, like me, can sleep blissfully, untroubled by thoughts of any bad blocks doing naughty things to your nice ROM.
Sample creation of ROM-files.sha1 on packager's dev box. Assuming that all files that go into the ROM are in the system/ and data/ directories in their correct locations:
To check ROM state (on gTab):Code:$ [B]sha1sum `find system data -type f` | tee ROM-files.sha1[/B]
Code:gTablet$ [B]su[/B] gTablet# [B]cd /[/B] gTablet# [B]sha1sum -c system/etc/ROM-files.sha1 2>&1 | fgrep -v OK[/B] gTablet# [I]No news is good news[/I]5
Nope. No such "clearing out" happens with that kind of double/triple/... partitioning. It's simply a waste of time and a distraction from real troubleshooting. An explanation of what happens when you repartition an SD card might help:
A repartition step on an SD card using CWM on the gTablet involves 2 operations.
1. The actual partitioning.
Here, only the MBR--the first sector--on the SD card is written because all SD cards (and also things like USB sticks) are NAND- or NOR-based flash (MTD) devices, but they all look like regular HDDs which means that they all have interface-matching, sector-translation and wear-levelling circuitry (and, on the expensive ones, firmware) built into them. This is also why you can put the standard HDD filesystems like extn, FAT32, etc on them. Raw (untranslated) MTD devices need specialized filesystems like yaffs2 and jffs2 which are coded specifically for them (and, incidentally, you can't put these filesystems on SD card partitions).
2. The filesystem creation.
During a filesystem creation operation, only a few scattered bits of data are actually written to the device. If we run through the creation of an ext3 filesystem on an SD card (relevant bits in bold):
you'll see that the size of the partition is 594405 1K blocks, but, only 9365 1K blocks (594405 - 585040), ~ 9.4 MB, scattered all over the place, are written to initialize the filesystem--which involves, mainly, writing a new bootblock, new superblocks and group descriptor blocks, and bitmap and inode-related blocks; plus odds and ends like the bits needed to create the /lost+found directory and the journal (16MB in our example run above, and even here the journal is not "written" fully--only the space needed for it is marked as "allocated").Code:~ # [B]fdisk -l /dev/block/mmcblk2[/B] Disk /dev/block/mmcblk2: 15.9 GB, 15931539456 bytes 255 heads, 63 sectors/track, 1936 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/block/mmcblk2p1 1 1581 12699351 c Win95 FAT32 (LBA) /dev/block/mmcblk2p2 1582 1825 1959930 83 Linux /dev/block/mmcblk2p3 1826 1862 297202+ 83 Linux /dev/block/mmcblk2p4 1863 1936 [B]594405[/B] 83 Linux ~ # [B]/root/mke2fs -j -m0 /dev/block/mmcblk2p4[/B] mke2fs 1.42.4 (12-June-2012) Filesystem label= OS type: Linux Block size=[B]4096[/B] (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 37200 inodes, [B]148601[/B] blocks 0 blocks (0.00%) reserved for the super user First data block=0 Maximum filesystem blocks=155189248 5 block groups 32768 blocks per group, 32768 fragments per group 7440 inodes per group Superblock backups stored on blocks: 32768, 98304 Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done ~ # [B]mount /dev/block/mmcblk2p4 /root/[/B] ~ # [B]df[/B] Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 224188 32 224156 0% /dev /dev/block/mtdblock4 222208 1296 220912 1% /cache /dev/block/mmcblk2p4 [B]585040[/B] 16860 568180 3% /root ~ #
The creation of a VFAT filesystem is roughly similar. So, in both cases, not a lot of actual data is written, and in each case the writes are generally scattered all over the device.
Thus far, this discussion has been at the level of logical filesystem blocks. When it comes to which physical blocks on the SD card are actually written during filesystem creation, things look even worse for people who think some sort of clearing out happens because of the intervening wear-leveling circuitry: Only the HW knows which MTD blocks correspond to which logical filesystem blocks, and the physical MTD blocks standing in for the logical filesystem blocks keep getting rotated as needed by the SD card itself.
What I think people imagine happens during a repartition is something like this:
That command writes zeros to every sector of the internal SD card. Run the command while in CWM (repartition afterwards, please) and see how long it takes to complete. If a repartition step really cleaned out the internal SD card as people imagine, then you would have to wait 45 mins or so for that operation to complete instead of the minute or so that you have to now.Code:~ # [B]time dd if=/dev/zero of=/dev/block/mmcblk3[/B]
See the description above. I can guarantee you that unless there are ghastly bugs in CWM, the parted/e2fsprogs code or in the HW, a single repartition operation will get rid of all (user-visible) data on the SD cards.
---------- Post added at 02:06 PM ---------- Previous post was at 01:56 PM ----------
Looking at the logs, I see that the ROM installation script is still cheerfully corrupting the /cache filesystem for no good reason. It also seems to be trying to remove the dalvik-cache from non-existent devices. Somebody should really scrutinize that install script.
---------- Post added at 02:35 PM ---------- Previous post was at 02:06 PM ----------
Nope.
Only a "wipe data/factory reset" is needed. You'll see that it does the other 2 (wiping cache and dalvik-cache) if you look at the messages the operation prints.5CWM 5504 B15+Touch and ICS
Process I followed to actually get the latest ClockWorkMod w/touch working AND be able to install ICS (I had a TON of issues with boot-into-recovery-only, not booting at all and only showing the birds, booting into stock rom but not being able to get into recovery anymore... this is how I got it working.)
Following this exact process I get success everytime now.
1) Turn your tablet OFF and REMOVE THE microSD CARD!! I repeat, remove the microSD card!!
2) Download THIS "nvflash_gtablet_2010110500.zip" from HERE (delete the other zip if you downloaded elsewhere):
http://dl.dropbox.com/u/66090731/nvflash_gtablet_2010110500.zip
3) Download THIS "nvflash1.2_5504b15.zip" from HERE:
http://dl.dropbox.com/u/66090731/nvflash1.2_5504b15.zip
4) Unzip "nvflash_gtablet_2010110500.zip" to "nvflash_gtablet_2010110500"
5) Unzip "nvflash1.2_5504b15.zip" to "nvflash1.2_5504b15"
6) Press and hold Volume - (VOL. DOWN) and the power button at the same time, release the power button once the screen turns on, keep holding VOL - until screen turns off; you're now in whats called APX mode.
7) Plug your USB cord into your computer, and into your G-Tablet
If you have NEVER installed the USB drivers before, do step 8, otherwise skip to step 9:
8) Go to Start/Control Panel/Device Manager and hit the Update Driver button for APX. In the popup, choose to specify manually and browse to the "nvflash_gtablet_2010110500" directory and choose the "USB" directory. Let the drivers install and proceed to step 9.
9) Go inside the "nvflash_gtablet_2010110500" directory
10) Double click nvflash_gtablet.bat , a CMD prompt window will open and start doing stuff - let it run until it says press any key to exit - that means its done.
11) Let your G-Tablet do a full boot up into the TnT ROM, then shutdown (Power Off)
12) Put your G-Tablet back into APX Mode. (Press and hold VOL. DOWN and the power button at the same time, release the power button once the screen turns on, keep holding VOL - until screen turns off).
13) Go inside the "nvflash1.2_5504b15" directory
14) Double click nvflash_gtablet.bat , a CMD prompt window will open and start doing stuff - again let it run until it says press any key to exit - that means its done.
15) Let your G-Tablet do a full boot up into the TnT ROM, then shutdown (Power Off)
16) Put your G-Tablet into Recovery Mode. To do this, press and hold VOLUME + (VOL UP) and the power button at the same time, release the power button once the screen turns on, keep holding VOL + for a few seconds; now you should be in the ClockWorkMod recovery with touch capability. At the top it should say 5.5.0.4 Beta 15.
Now its time to follow the "How to install" steps from the first post. DO ALL OF THESE!
1)
a. Wipe Data/Factory Reset
b. Wipe Cache
c. Wipe Dalvik Cache
2)
a. Format boot
b. Mount then Format data
c. Mount then format system
d. Format cache
3) Re-partition internal sd with 2048/0
4) Mount USB and copy your ICS ROM and Gapps zip files over
5) Flash the ICS ROM (this may take a while to complete, do not mess with it until it's DONE)
6) Flash Gapps (this may take a while to complete, do not mess with it until it's DONE)
7) SHUT DOWN / POWER OFF
8) Insert your microSD card back into your G-Tablet
9) Start up normal and let it boot into the ICS ROM.
10) Complete first setup and then let sit and sync for half an hour to an hour.
Special Thanks to:
butchconner http://xdaforums.com/showthread.php?t=989320
fosser2 http://xdaforums.com/showthread.php?t=1525424
roebeet http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
ViewSonic G-Tablet for Dummies http://viewsonic-gtablet-for-dummies.webs.com/
