yashsingh1/xdaforums huggingface dataset:
[Xoom Q&A, Help & Troubleshooting] newskate9:
Champers - thanks for the quick reply. I was afraid of that. I've not worries about rooting and installing tools, etc. I'm pretty careful and (knock on digital wood) have never had an issue.

Being on stock xoom 3.2, I'll be searching now for how to root it. I was going to install the rooted version but thought I might not need it. Go figure - 12 hours after I got the update, I need to change it to be able to tether. Nuts.

So, off to google land we go, unless someone has a "look here" to ROOT the stock XOOM 3.2.

EDIT 1: GOOGLE success!!! Took 3 seconds. Just as of yesterday - HA!!!

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

You guys are GOOOOOOOD!

EDIT 2: As proof how fast I found it......... I can't even post these edits yet! DOH!
[Xoom Q&A, Help & Troubleshooting] migespi:
So did it work. Are you able to tether now? I am waiting on rooting to see if it works for you
[G2 and Desire Z Q&A, Help & Troubleshooting] rickyiswhite:
I was messing with my browser settings and I came across an option titled User Agent or something like that, then it a list showed up with options like Froyo, Eclair, Linux, iPhone, etc... I also noticed that somewhere else but it had to do with I think MMS or SMS I forget which, anyone have a clue what you can use that for and what are benifets?
[G2 and Desire Z Q&A, Help & Troubleshooting] c00ller:
The user agent is how websites identify the device you're browsing from. For example, if you choose desktop, going to a website like amazon.com will always show the full, desktop version. If you change it to Android or iPhone, it will load a "mobile" version of amazon.com that is optimized for small screens and minimizing data usage. No idea what the SMS/MMS context is.
[G2 and Desire Z Q&A, Help & Troubleshooting] martonikaj:
It has no context to SMS or MMS. It simply defines what the phone tells the website it is like you said.

For many up-to-date websites, 'Android' will offer a slightly different page than 'iPhone', because the iPhone site is optimized for HTML5, whereas many pages will show flash for Android.
[G2 and Desire Z Q&A, Help & Troubleshooting] Nospin:
You are thinking about the sms user agent, where cyanogenmod lets you change what phone the network thinks is sending the message. I believe changing it to Nexus One fixes the heavily compressed mms issue, but don't quote me on that.
[Samsung Infuse 4G] nash2000:
Can someone tell me what cwm stands for. I would like to install the updated infused rom over my 1.5 version but for what I've read they said not to use rom manager but to do it in cwm
[Samsung Infuse 4G] Enraged21:
Clockwork mod. They're the devs of rom manager.

So your statement makes no sense to not use ROM Manager but to use CWM...

Evo SHIFT
[Samsung Infuse 4G] nash2000:
Your right, it doesn't but that's what I read...I think. Ill go back and copy what I read.
[Samsung Infuse 4G] tyshemi:
Rom manager uses green cwm more for non voodoo Roms. Red cwm is more geared toward voodoo enabled roms
[Samsung Infuse 4G] nash2000:
That's what I read.
[Samsung Infuse 4G] nash2000:
So what's the best way to flash the updated rom over my 1.5.
[Samsung Infuse 4G] jayson94538:
If you want to know how to get into red cwm, simply hold the power button and press on "Recovery" or manually do it by fully powering down ur phone. And then hold both volume buttons down and hold the power button. When the samsung logo appears, let go of the power button and itll boot into red cwm.
[Samsung Infuse 4G] tyshemi:
Red cwm
[Samsung Infuse 4G] Entropy512:
CWM installed via ROM Manager is the same as any other CWM for our phone. CWM means ClockWorkMod Recovery.

However, for whatever reason, when accessing CWM by using "Recovery" from the poweroff menu (only on custom ROMs, not stock to my knowledge) and via the trick mentioned above (Although I think it's either VolUp or VolDown only when powering up - both leads you to bootloader mode, aka Odin downloader mode), the text of CWM is red. AKA "red CWM".

When you enter Recovery via ROM Manager, you get Green CWM (all text is green) - Don't know what the difference is or why there is one.
[Samsung Infuse 4G] hoofadoo:
Rule of thumb. If you are on stock, you may flash any rom from Green cwm and via rom manager.

If you are on any Voodoo enabled rom with lagfix (which all of these custom roms are), DO NOT EVER use Rom manager to flash anything. It flashes from green cwm, and you will brick.

Manually copy the ROM to your SD card and boot into red CWM, and flash from there.
[Samsung Infuse 4G] bradbusa:
but WHAT IF you're on a stock rom.. and you boot into recovery from rom manager? lol
[Samsung Infuse 4G] hoofadoo:
Ummm. As i stated, in the first line of my response, you may flash from the recovery in rom manager...
[Samsung Infuse 4G] bradbusa:
lol i'm just being ornery
[Samsung Infuse 4G] tyshemi:
Hoofa LOL whats this LOL. I'm edumacated now lol
[Samsung Infuse 4G] geff603:
Well not that I really know what I'm doing but, I just open rom manager and down load the rom and follow the prompts. I flashed 3 infused roms this way. currently on 1.5.2 never really payed attention to the color of the text. Am I doing it wrong? Lol
[Samsung Infuse 4G] MisterEdF:
Or download Quickboot. When I select "boot to recovery" using Quickboot it always takes me to "red" recovery.
[Samsung Infuse 4G] hoofadoo:
lol i just thought you were being stupid... :p sorry
[Samsung Infuse 4G] nash2000:
Can I do all of this from my phone?
[Samsung Infuse 4G] Dani897:
if this hasnt been properly cleared up clockworkmod developed cloclworkmod recovery and rom manager. cwm recovery can be used independant of rom manager. rom manager is just an app to access the features of cwm recovery when the phone is booted. but using any of those features will cause the phone to reboot into cwm recovery to complete the action. rom manager also has an interface to download roms and make unique names for your backups.

there are many versions of cwm recovery. some use edify scripting, some use amend scripting. there the infuse uses the same versions of cwm recovery as the i9000. but there is also red cwm recovery which is modded with controls for voodoo lagfix and is integrated into voodoo enabled kernels. if you have a voodoo kenrel installed you have red cwm and should be able to get to it from rom manager, but it may try to launch the update.zip instead.

rom manager is not needed, it is totally optional. having rom manager doesnt automatically give you green cwm recovery. you still need to flash it. (unless you have a voodoo kernel)
[Samsung Infuse 4G] nash2000:
All I have is infused 1.5, I haven't installed a differnet kernal. So do toy think I have green cwm
[Samsung Infuse 4G] bradbusa:
is that a serious question?
[Samsung Infuse 4G] byuboy87:
all current custom roms have a voodoo enabled kernel, & thus, is not the stock kernel. with this voodoo enabled kernel (which you now have) your phone now has the ability to boot into red CWM, which is the recovery screen with the red text. the simplest way to accomplish wat ur lookn to do is to save the rom's .zip to the root of your internal sd. then hold power button & select recovery (you will boot into red cwm). select ur .zip from sd, flash, & reboot... hope this helps

message from Sams inFuse... REFUSE 1.6, INFUSION 1.8
[Samsung Infuse 4G] Dani897:
you should have the voodoo enabled comunity kernel with red cwm recovery.
[Samsung Infuse 4G] nash2000:
If it wasn't I wouldn't ask. I apologize for my lack of android know how. Ill try and keep my dumb questions to a minimum.
[Samsung Infuse 4G] nash2000:
Perfect explanation, thank you.
[Samsung Infuse 4G] Dani897:
i reread my previous post and others. ok, apparently using rom manager to launch red cwm is not recommeded. i haven't had issues with it. but that's not to say it isnt a bad idea. i know if the file named "update.zip" is on the internal sd card it could potentially launch the wrong recovery. so to be safe look for and delete update.zip and also just use the extended power menu to access red cwm recovery. no njeed for rom manager. rom manager really has limited usefulness anyway.
[G Tablet Q&A, Help & Troubleshooting] Vip3rs:
Hi

my Tap UI Version Is 1.1-3389 and build number is FRF91 , now I want to Install Android Illuminate Alpha 2.2 . PLZ help me to install Them ?

Tnx My FriendS
[G Tablet Q&A, Help & Troubleshooting] Vip3rs:
dont anybody to help me ?
[G Tablet Q&A, Help & Troubleshooting] nvanlaar:
Check out Gtablet for Dummies. Then come back here.
[General Questions and Answers] hakeem.abbas:
I am an undergrad student of computer science. I want to contribute to Android Open Source Project as my Final Year Project.

I have no idea at all what can i build. I am less informed about the components that other third parties have build for AOSP.

I wet through the source.android.com and found useful information on getting started.

I want some suggestions whether i should take this as my Final Year Project or not. What kind of challanges i will be facing if i go with it. And kindly do share your ideas about what can i build?

And tell where can i find the descriptions of components that other third parties have build for android.

Thanks in advance.
[G Tablet Q&A, Help & Troubleshooting] sesteinberg:
Joining the ranks of the "what was he thinking" Had TNT4.0 lite running fine. tried to upgrade to: GtabComb_b3.1_bl1.2 hung on 3 birds. A post said "go to cwm and partition the internal sd" ...fool that I am, I did. So now it hangs on booting and there's no update.zip on the internal sd to use to restore 'cause it all got wiped by the partition. Soooo managed to get the drivers (including NVIDIA boot recovery) so that NVIDIA Harmony shows as a device on my win7 notebook, but NVIDIA's "d:" drive, while listed, is grayed out and not available.

Back to CWM tried formatting and partitioning (ignorantly screwed with the sector and swap sizes) the internal SD card, mounting and unmounting (never shows and storage space, just mount/unmount) with no access from my pc to get some recovery files on it. HELP PLEASE-

1.suggestions to get access to the internal sd card and what files to put there

2.possible to get cwm 2.5.1.1 to see either the external sd or usb as location for update.zip file

3. proper settings for the internal sd card (sector size,swap size)

4 place to get my head examined
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
So you were on a 1.1 bootloader and you decided to jump to a 1.2 bootloader-based ROM (when that ROM has a perfectly good 1.1 bootloader-based version)?

First things first: Are you able to boot into ClockworkMod?

If yes, then you can copy any files you want to either sdcard, internal or external, using adb.

To copy files to the internal SD card:

C:\some\path\platform-tools> adb shell mount /dev/block/mmcblk3p1 /sdcard
C:\some\path\platform-tools> adb push c:\some\path\file.zip /sdcard/xyz.zip
C:\some\path\platform-tools> adb shell umount /sdcard

To copy files to the external SD card:

C:\some\path\platform-tools> adb shell mount [B]/dev/block/mmcblk2p1[/B] /sdcard
C:\some\path\platform-tools> adb push c:\some\path\file.zip /sdcard/xyz.zip
C:\some\path\platform-tools> adb shell umount /sdcard

If the "adb shell mount /sdcard" at the beginning complains about /sdcard already being mounted, just unmount the sdcard as shown in the last step, then start over again.

If you have inadvertently loaded a 1.2 bootloader, downgrade to 1.1 by following the steps given here.

After this, remove any external SD cards you may have so that there is no confusion when you format the SD card, then:

1. Reflash clockworkmod if needed, then boot into CWM.

2. Repartition internal SD card again with 2048 MB for /data and 0 for swap (no swap) and the rest for /sdcard.

3. Do a "wipe data/factory reset".

4. Use adb push to copy the GtabComb_b3.1_bl1.1.zip file onto the internal SD card using the commands above.

5. Install this zip file using CWM.
[G Tablet Q&A, Help & Troubleshooting] sesteinberg:
thank you very much for your help- i'm not experienced enough to know how to run adb...see below and thanks again

So you were on a 1.1 bootloader and you decided to jump to a 1.2 bootloader-based ROM (when that ROM has a perfectly good 1.1 bootloader-based version)? ***yes- saw a post that said that if the opening screen showed the slide lock, that bootloader was 1.2...go figure****

First things first: Are you able to boot into ClockworkMod? *yes**

If yes, then you can copy any files you want to either sdcard, internal or external, using adb. **can you help me understand how to do this- downloaded the java sdk; and the android sdk, but haven't been able to find out how to use them to move the files to the internal sd card....haven't figured out how to use adb***

To copy files to the internal SD card: ***I'm sorry, i don't understand the steps to do this...been looking on line so as not to bug you****

Code:

C:\some\path\platform-tools> adb shell mount /dev/block/mmcblk3p1 /sdcard

C:\some\path\platform-tools> adb push c:\some\path\file.zip /sdcard/xyz.zip

C:\some\path\platform-tools> adb shell umount /sdcard

To copy files to the external SD card:

Code:

C:\some\path\platform-tools> adb shell mount /dev/block/mmcblk2p1 /sdcard

C:\some\path\platform-tools> adb push c:\some\path\file.zip /sdcard/xyz.zip

C:\some\path\platform-tools> adb shell umount /sdcard

If the "adb shell mount /sdcard" at the beginning complains about /sdcard already being mounted, just unmount the sdcard as shown in the last step, then start over again.

If you have inadvertently loaded a 1.2 bootloader, downgrade to 1.1 by following the steps given here. ***how would I know this?***

After this, remove any external SD cards you may have so that there is no confusion when you format the SD card, then:

1. Reflash clockworkmod if needed, then boot into CWM.

2. Repartition internal SD card again with 2048 MB for /data and 0 for swap (no swap) and the rest for /sdcard. **done***

3. Do a "wipe data/factory reset". **done***

4. Use adb push to copy the GtabComb_b3.1_bl1.1.zip file onto the internal SD card using the commands above. **same problem as above**

5. Install this zip file using CWM.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
OK, this is very important. In your first post, you said you, "Had TNT4.0 lite running fine." TnT Lite 4.0 is a 1.1-based custom firmware. Which is why I thought you were on a 1.1 based firmware. Are you in fact running ViewSonic's new stock firmware with the TapNTap UI?

Read this thread. As the first post there says:

TnT Lite is very close to stock, so you can, I think, still go to Settings > About Tablet > TapUI Version and check the firmware version which indicates the bootloader being used.

If, however, you find out that you do, in fact, have a 1.2 bootloader, then just flash the file you originally used: GtabComb_b3.1_bl1.2.zip. By reformatting the internal SD card and doing a factory reset, you've done all that's needed to prepare for a new ROM install.

To set up adb on Windows, see this thread.

For quick one-shot use, follow the instructions here, and just replace the "adb" in the commands I gave with "sudo ./adb".
[G Tablet Q&A, Help & Troubleshooting] sesteinberg:
***Bought the tablet early this year, rooted it and installed a new rom tnt lite v 4.1.1 or 4.2.1 (i'm travelling and don't have the download--not viewsonic stock); I looked at the settings before this fiasco and did not see a 1.1 or 1.2 (because it was not longer stock?)- that's why I relied on the opening screen with the slide lock to (falsely?) conclude it was 1.2.

***on start-up the tablet loops at 3 birds--so I can no longer get to g-tab settings; I can reliably get to ClockworkMod Recovery v2.5.1.1-bekit-0.8- I did use it to "reset" the internal sd by partitioning it and using 2048mb and 0 for swap-no messages to suggest the internal sd was faulty**

***when I first flashed GtabComb_b3.1_bl1.2- it hung at 3 birds but I was able to revert to the tnt 4xxx by using CWM to select it on the internal SD card; when I flashed GtabComb_b3.1_bl1.2 the second time it hung again I found a posting on line that suggested re-partitioning the internal SD card which of course did not resolve the problem and took away my CWM restore possibilities***

***i've just finished downloading Knoppix with the hope of using it to run Adb to get access to the internal SD card---I do have NVIDIA Harmony as a "device" in win7-but the "d:" drive on it is grayed out and not browsable ***

this help you help me?

thanks again
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
The fact that you remember installing TnT Lite 4.x and also have CWM v2.5.1.1-bekit-0.8 working strongly suggests to me that your bootloader is 1.1.

It might not show up as a USB disk, but, you should still be able to use adb on Windows. I'm not a Windows user--don't even have it on my PC--but, try this:

In CWM, select "mounts and storage", then "mount USB storage". See if the external SD card shows up as a drive on Windows.

EDIT:

If you don't have an external SD card, you can make the internal SD card's VFAT partition appear as a drive on Windows/Linux by using these adb commands:

1. Create a new file called fstab.txt with these contents:

/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mmcblk3p2 /data ext3 rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk3p1 /sdcard vfat rw
/dev/block/mmcblk2p2 /sd-ext auto rw

2. Copy this fstab.txt onto the gTablet using adb:

C:\> adb push C:\some\path\fstab.txt [B]/etc/fstab[/B]

3. On gTablet, create a symbolic link (it's like a shortcut) from /dev/block/mmcblk3p1 to /dev/block/mmcblk2p1, which is what CWM is trying to mount:

C:\> adb shell ln -sf /dev/block/mmcblk3p1 /dev/block/mmcblk2p1

4. Back in the CWM main menu, select "mounts and storage", then "mount USB storage".
[G Tablet Q&A, Help & Troubleshooting] Frogbone:
I am having a similar issue with my G Tablet.

After farting around with it the other day I lost track of what I was doing and now at start up it just sits with the three birds image and does nothing.

When I try to boot into recovery I get:

"Detect a recovery key pressed"

followed by

"Booting recovery kernel image"

Then it just sits there.

So I searched all over for solutions and found the nvflash threads. I downloaded all the files needed but my PC's just won't detect the tablet and therefore I can't install the drivers for it.

I have two Win 7 machines, on 32 and on 64 . Both do the same.

What should I be doing next ? Any ideas ?
[G Tablet Q&A, Help & Troubleshooting] sesteinberg:
tried the various mounting options- internal sd mounts but makes no difference in terms of being visible on my PC; external sd (with memory card inserted) gives an error message; usb storage mount- no apparent effect

burning knopp disk now- and will try to get adb to allow commuication with tab...any tricks?
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Is the USB cable OK?

Google "Viewsonic GTablet For Dummies" and follow the Code RED instructions there.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Did you try the adb push ... method? That should've worked without mounting anything.

That's no good. Need exact steps/commands tried and exact error messages returned.

If all else fails, Google "Viewsonic GTablet For Dummies" and follow the Code RED instructions on that site.
[G Tablet Q&A, Help & Troubleshooting] Frogbone:
This ^^^^ :)

I must have missed the Power plus Volume- to get to APX mode in all of the other procedures I read.

Thanks for pointing out this great site !!
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
It is the distilled wisdom of the xda-developers gTablet forum in one place.

Consider making a donation to keep that site up.
[G Tablet Q&A, Help & Troubleshooting] sesteinberg:
Back home and at this again- went to "Dummies" "code red"

downloaded the USB driver (had done this previously through SDK tools) and while I don't get any error messages when connecting the g-tablet; Device manager shows only a "Android Debug Bridge Interface" working ok and drive up to date. below is from the code red instructions:

Using your PC, download the driver for USB connector here (clicky). Alternate source driver for USB connector. ***done***

Unzip the SystemUSB.zip file and place the folder "Flash USB driver" somewhere easy for you to find. I suggest your desktop. ***done***

Turn on your gtab by pressing the power button and volume less (-) button simultaneously and hold. Your screen will turn on with the 3 viewsonic birds and then it will turn black. Looks like it is off, but I promise you it is on in APX mode. ***As I mentioned before, I have CWM which reliably starts on holding the power button and the volume (-) button- I was able to get to a state (using the "menu" key) where the device is clearly on- black screen, but backlighting obvious.... is this APX mode?***

Do not click here.

Connect your gtab to your computer via usb. Your computer will say driver install unsucessful. ****doesn't happen...did before I installed the USB driver from the SDK****

Right click on Computer icon --> Properties --> Device Manager (left side) --> right click APX and choose upgrade driver. ***I see the Android Debug Bridge (working properly) but no APX; updated this driver with the USB driver recommended in code red- shows up to date, but still no APX reference*** Navigate to where you put the USB driver folder and select the folder. Your computer should now recognize the gtab in APX mode. ***I have no idea if this has occurred. In device manager it is listed as a "Portable device" drive d...but drive d isn't accessible....any way to confirm that the gtablet is in APX mode and that I've got the correct driver on my PC---again, no error on initial connection.

I downloaded NVFLash with CWM for 1.1 (the boot loader it seems most likely I had)- unzipped and ran it under the conditions above....ran nvflash_gtablet.bat (with CWM) --I get: "NVflash started" then "unknown device found" then "press enter to continue:" pressing "enter" closes the dos window but no activity on the pc and none on the tablet. If I run NVflash at the three birds screen on the tablet I get NVflash started and then "USB device not found" which I guess makes sense. Do I have the wrong USB driver on my PC? Am I not getting into APX mode on the tablet? Are the instruction different when Cwm is already installed -- should I have used the NVflash without CWM? thanks as ever.