yashsingh1/xdaforums huggingface dataset:
[G Tablet Android Development] veladem:
I have literally read evey post on this thread and for some reason I cant get the market to work on my g tab. My tab keeps popping up a toaster to link a account to the tab, however if I press ohk it doesnt take me to any account pages. If i try to go through the main account settings in the main setting it doesnt work. also I have tried to get the market to "crash", and for some reason I cant find the "google services framework." Im on branch 1.1 running CM 7.1.0.1 TY in advance!!!
[G Tablet Android Development] TEK112:
Have you tried removing your google account and readding it, if so, have you tried:

Settings-Applications-manage Applications-Market (clear data and force close), press back and then go to Google Frameworks Services (you may have two of them) and then clear data and force close both. Try to open the market and you will get an error, if not, repeat the above steps until you do. Then reboot the phone and try again.
[G Tablet Android Development] veladem:
I dont have a google framework service file though but I had tried that before... any other thoughts? TY for the input.
[G Tablet Android Development] TEK112:
Sorry, I should have been more clear when you goto settings-applications-manage applications you have to select the "all" tab from the top. It defaults to downloaded and since the market nor the google services framework was not downloaded they will not appear. If you tried that and it did not work, how about removing and readding your google account?
[G Tablet Android Development] veladem:
Well you see the thing is that the g account never would add. And I don't have it under all that's where I first looked.
[G Tablet Android Development] TEK112:
Hmmmm... that would explain a lot. What happens when you go into settings, accounts and settings and try to manually add your Google account?
[G Tablet Android Development] veladem:
It wont connect to the server.
[G Tablet Android Development] TEK112:
Are you certain that you are connected to wifi?
[G Tablet Android Development] veladem:
Positive. I tried re doing the rom dl also just too make sure it wasnt botched.
[G Tablet Android Development] TEK112:
Do you have two step verification enabled?

Or... I almost forgot... go to settings-accounts and sync and then add an account - select google and at the username and password screen press the menu button and select browser sign in. This should work.
[G Tablet Android Development] nixie2121:
help please? I had my gtab serviced and now need to re-install clockworkmod...nothing is working. I am on the 1.2 branch..

I tried internal and external, error =

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

(no such file or directory)

E:Can't mount SDCARD2:recovery/command

Thanks
[G Tablet Android Development] TEK112:
Go here:

http://xdaforums.com/showthread.php?t=1392761&page=3

Download nvflash and it will install clockwork, then try Flashback!

If you have never nvflashed before don't forget that you will need drivers.
[G Tablet Android Development] Apodidae:
Make sure you grab the correct CWM installer. There is one for installing from internal SD, and one for installing from external SD.
[G Tablet Android Development] dimillusi:
Very helpful post. now running GTAB COMBOVER
[G Tablet Android Development] tunnyj:
[GUIDE] Install ClockworkMod, a ROM, Flash Player, and the Market Fi

Hi guys I'm a bit of a noob with tablets but I've got a bit of knowledge regarding rooting and updating ROMs on phones (so not a complete noob)

I just wondering does anyone know if this guide will work on the viewpad 10s as I've seen in other posts that it is basically the same tablet plus is so will the roms listed work also. :confused:

Cheers all I hope someone can help
[G Tablet Android Development] XQuisite:
Help?

Thanks in advance! I'm stuck here, literally. I've downloaded CWM in the first post and tried to install it via MicroSD. Everything went fine and got into recovery with blue text with the screwdriver and wrench(?) background. Then I rebooted without partitioning anything and now I don't know what to do next. I don't think I fully installed CWM because when I boot it up now with the Vol+ button pressed, I just get the Viewsonic screen (birds) and it sticks there. What did I do wrong? =(

Sorry for being a noob! And please, someone help! I'm trying to root it after getting the charge port fixed from warranty!

Thanks community!

PS: When I try to boot without pressing the Vol+ button, it goes into preloaded TapNTap just fine.
[G Tablet Android Development] rajeevvp:
You installed the wrong version of CWM. The one in this thread is for 1.1 bootloaders. Install either CWM-3.0.2.8 (follow 1st link in OP and do Code Green) or the 1.2 bootloader version of CWM-4.0.1.5 using nvflash.
[G Tablet Android Development] XQuisite:
Thanks for your help, rajeevvp. I was able to get CWM on there but I've run into a different problem now. When I use nvFlash to get everything on there, I've now downgraded to a 1.0 build and can't upgrade to 1.1-3588. Every time I try to upgrade the tablet through it's own upgrade process, it hangs on the 3 birds Viewsonic splash screen trying to boot into the recovery image. Is it supposed to stay on that screen for a while? I feel like I keep on soft-bricking my GTab.

Now that I'm comfortable using nvFlash, is there a way to nvFlash up to the 1.2 update and go from there?
[G Tablet Android Development] rajeevvp:
If you intend to use the OTA update process, then you should put the stock recovery back.

There are easy guides for this on this board and elsewhere (Google "Viewsonic gtablet for dummies"). Or, you can just let the OTA installation process to update you. The latest VS firmware update is 1.2 based.

Since you're comfortable with nvflash, let OTA update process get you to 1.2-5699. Then, after the installation has been verified to be working correctly, use nvflash and make a complete backup of the NAND flash--in case disaster strikes.
[G Tablet Android Development] JMillion:
great stuff here. i was able to put CWM and G-Harmony Gingerbread 2.3.5 on the gTab for my friend
[G Tablet Android Development] alainalemany:
Recovery gone :(

OK I have a problem once I get to Step 5. Until there I followed every step and check what happened:

I have my GTablet without a microsd card, so I downloaded cwmod_internal.zip because I'm working with the internal memory, right? OK. I extracted the zip and put the files ("recovery" dir & "update.zip") on root. Then I shutdown my device and power it on pressing Power button and Volume+ at the same time and I release it when the Viewsonic birds screen appeared, "Recovery key detected" appeared and then "Booting recovery kernel image" followed by the recovery menu which tried to install the "update.zip" file previously copied by me. The problem is I waited like 5 minutes seeing the "Installing update.zip" message when in Step 5 it says it won't take long, so I shutdown my GTablet and now I can't enter to he recovery menu, I just press the required keys, "Recovery key detected" and "Booting recovery kernel image" appear and that's it, I get stuck in the birds image without entering to the recovery.

My GTablet isn't bricked because I can reboot again without pressing the recovery keys and I can enter to my stock Froyo without any problems. My only problem is I can't enter to the recovery.

I have my GTablet previously rooted via SuperOneClick... so I honestly don't know what happened here and I hope anyone can help me to get the recovery back.

Best regards.

EDIT 1: I have 1.2 bootloader :(

EDIT 2: Since this thread is for 1.1 BL and I have 1.2, I assume I did all this wrong, ok, I went to the Dummies page, then to Code Green and follow every step, this time I downloaded the proper BL files (I'm in 1.2 BL), extracted and copied to the root of my internal memory and nothing, I get the same problem of stucking on the birds and not entering to any recovery. Also I tried to erase the files from my internal memory, even format the entire memory and nothing, I still being not able to enter to the recovery and honestly I'm worried. I've been reading and if I'm not wrong I can't install CWM with NVFlash method because it only works with custom ROMs already pre-installed, right?

I'm starting to feel in a dead end... please anyone HELP.

EDIT 3: I use NVFlash and everything goes like heaven, it comes with a stock 2.2, 1.2BL, and touch CMW included. Via CWM I installed a Honeycomb rom, which also worked fine... BUT if I turn off the device I'll never be able to enter to CWM Recovery and also get stuck in birds Viewsonic logo... and I have to start the NVFlash and ROM installation processes again... it's almost like it is untethered.

Now I put my hands up... I did everything at my sight... I NEED HELP! :)
[G Tablet Android Development] rajeevvp:
Follow the instructions in this thread. It should let you get past the 3 birds screen.

Boot into CWM and the first thing you should do there is update CWM to the latest one available here. The CWM-5.5.0.4 that's present on the viewsonic gtablet for dummies website is old and causes that hang you experienced.

The next thing to do while still in CWM is repartition the internal SD card. Remove any external micro SD cards before you do that, though.
[G Tablet Android Development] Kocrachon:
perhaps some one can help me out.

I recently upgraded from BL 1.1 to 1.2. It works fine and I can get into CWM just fine. However, when I installed [BL1.2]G-Harmony Gingerbread 2.3.7, it sits at the "Android" screen forever, never moving on. I restarted the tablet and the same issue. Re-did the entire installing of the rom, and same issue. I used NVFlash to get to 1.2, using the 1.1, then 1.2, and then 1.2 w/ CWM.

Before that I was using an older CM7 on BL 1.1. I went through the process of setting the partition to 2048 / 0, mounting system and data, and then installed the ROM, did a factory reset for the cache and such. So I am at a loss...
[G Tablet Android Development] TEK112:
List the exact steps you took.
[G Tablet Android Development] Kocrachon:
So essentially, the first thing I do, is I go into CWM and advanced, and then I re-partition the SD Card to 2048 / 0.

I then go to mounts and storage. I mount /data, and mount /system. I then mount USB Storage and I put my .zip file on there, by creating a folder named ROMs. I then unmount the USB Storage and then I go to install zip from SD Card. I go into the rom folder and select it. It flashes it and says install completed successfully.

After that I go into mounts and storage again, to make sure that /data and /system are still mounted. I then do a "wipe data/factory reset" and then restart. It is at this point that it hangs.
[G Tablet Android Development] TEK112:
The second data/factory wipe is probably what is tanking your setup.

Try:

Wipe data/cache

Wipe cache

Advanced - Wipe Dalvik

Mounts and Storage - Mount system and wipe system

Partition sdcard 4096/256

Partition sdcard 2048/0

Install update from zip

Reboot

Literally these steps, don't play with mounts and such other than what I explained to do.
[G Tablet Android Development] Kocrachon:
Sounds good, I will try that when I get home. But a real quick question, why do I partition it twice, two different ways?
[G Tablet Android Development] TEK112:
This are rumors out there that residual data can linger. By manually changing both sizes and then changing them back it will forcefully destroy the underlying files and eliminate the chance of left over bits.
[G Tablet Android Development] rajeevvp:
Which is why one should not put much faith in rumours.

Barring the usual hardware problems and/or SW bugs, a SD card repartitioning, followed by a format of the cache partition will wipe all user data on the gTab. All the other additional steps that most folks do for this are, frankly, redundant.
[G Tablet Android Development] TEK112:
I don't know if it stemmed from early versions of CWM, but this came up the most frequently for tablets new to the 1.2 bootloader. Double partitioning seemed to be the most effective. I personally never experienced this, but for those having frequent issues it seemed to help them get through installation.

Test revealed that data could survive a factory reset through recovery in gingerbread devices. So, I definitely agree it could be a software glitch.
[G Tablet Android Development] rajeevvp:
I mentioned the HW and SW problems as a sort of "standard disclaimer", but, its very unlikely to be a SW problem (for what you describe) for a variety of reasons: Repartitioning and creating filesystems are pretty basic steps which are very well characterised. So bugs there won't present as left-over data on some tabs and not on others. The other thing is that both those steps use external programs (GNU parted and e2fsprogs) present in CWM recovery which have been very well tested. So again, SW bugs are unlikely.

HW problems are a remote possibility. HW problems can be intermittent, but, they tend to be persistent and not disappear after something as simple as 2 back-to-back filesystem creation operations.

BTW, what test was it that revealed persistent data on GB ROMs?

Going back to the redundancy bit:

A SD card repartitioning will wipe clean both /data and /sdcard, so:

Yes.

Repartition does not touch /cache. And, I would "format" cache rather than "wipe" it.

Unnecessary.

Unnecessary.

/data has already been wiped by repartitioning.

Unnecessary.

The first thing a new ROM install does is format /system.

Just do this once. Why increase wear on the internal (non-replaceable) SD card by doing it twice?
[G Tablet Android Development] TEK112:
That article was from a while ago, but a quick google search revealed:

https://www.hatforce.com/blog/android/wipe

http://androidforums.com/optimus-v-all-things-root/419080-truth-about-rom-manager.html

Also, some steps may be redundant, but from extensive troubleshooting these steps lead to a fool proof install. Some people miss or skip steps, not everyone is as technically knowledgeable as you. For the occasional flasher this is fine as it compensates for missed steps and the risk of overflashing in minimized. The crack flasher won't follow these steps and will most likely not follow any directions, but their own.
[G Tablet Android Development] rajeevvp:
I don't think you read those articles carefully enough, TEK.

The 1st link talks about data still being accessible when you do a raw read of the SD card. Well, this is to be expected, no? Unless it is a secure wipe, you would be able to get some data by doing a raw read of a block device. This is true of SD cards, NAND flashes and HDDs no matter what the OS. Removing or, even, formatting a HDD or SD card won't wipe the contents because only the meta-data is erased by those operations.

The point of our little discussion is whether any data is still accessible and/or visible via the filesystem--ie. normally, after a mount--after an erase, reformat, repartition operation. If it is not, then whatever left-over data that's still lingering on a block device simply does not matter.

Plus, that blog post is a bit vague on the specifics, and, even in the terminology used, so I'm not very inclined to put much faith in the other things it says.

The thread in the second link is also not pertinent and is, again, very vague with the details. It's mostly about the ROM Manager and we already know that the ROM Manager has problems on the gTab.

I can give you a list of all the problem I've noticed in both those links, but, I hope you will spare me the typing.

Well, the "troubleshooting" that I see here and on SLD by most folks doing it isn't very rigorous. It's mostly "follow the leader". Somebody did something some time ago and everybody just uses it now with no one asking the difficult questions: How does it work? Is there a logical basis for the steps? Are all steps needed? Can some of them be skipped...

In that case a reduction in the no. of steps is what's needed, right? You can wipe data in just 2 steps (re-partition, format cache) rather than the 5 or 6 that you've recommeneded.

Aaaand, the phrase of the day for today, ladies and gentlemen, is: "crack flasher".

Dude, please tell me that was deliberate :D
[G Tablet Android Development] TEK112:
You and I have been down this road before. ;)

I have never experienced these issues with persistent data. However, many have. I have no clue what they are doing and honestly with the number of PMs I get each day asking for help, I don't have time to really investigate. What I can tell you is that there is a huge group out there that have had data persist in some way after "following directions." It comes down to people not following the correct steps or performing a hybrid because they don't understand what they do.

It is in fact follow the leader. A lot of people look at flashing as Voodoo and do very superstitious things to avoid a bad flash. Like a bowler nodding twice before his release or a baseball player that doesn't shave during the playoffs. In fact, most people learn to flash one way and do it the same every time. Yes, the process could be streamlined and have steps cut out. However, by making people perform redundant steps it helps make up for those that cut them. It is a double edged sword.

You know more than the average user and when it comes to Android, more than me. In fact, your flashable zip to fix the magic value mismatch after rebooting recovery has saved a lot of people headaches. However, if you see it and don't like it do, do something about it. Reach out to the devs that post the installs and help them rewrite it. My methods may be archaic in your eyes, but in the end the user has a working ROM. You see things on a granular level and I understand that. I just want people to enjoy a working ROM.

As for crack flasher, well... I am a big fan of DT and what he has done with Team Kang's work. Since DT has made his come back the newest buzz word is crack flasher...:D
[G Tablet Android Development] rajeevvp:
Yeah, its a pity its the same old road, though...

Again with the vague "persistent data" business. Can you answer these questions, please, TEK?

1. What persistent data is this? Is it a directory, a file, a bad block, what?

2. Which partition is it present on? /cache, /data or /sdcard?

3. How can data persist after a repartition operation using very reliable programs?

4. How does repartitioning twice "fix" things?

That's a bizarre justification. Simplification and understanding are what's needed, not more useless steps. For example:

After you do a "Wipe data/cache" step, can you tell me how this step--"Advanced - Wipe Dalvik" will help?

I don't have a "flashable zip to fix the magic value mismatch after rebooting recovery". I have plenty of other zips here.

See, I've spent 3 posts doing just that. Seriously, did you not follow at all what I've been trying to say?

Eh? What "install"? The original question that prompted this discussion was: "why do I partition it twice, two different ways?"

They're not "archaic"; they redundant. And, as you yourself said, indicative of superstitious behaviour.

So do I, but, I don't see what help waving a dead chicken also (so to speak) is.
[G Tablet Android Development] TEK112:
1. Sometimes it is bad blocks, which are flagged by the ROM, but bad blocks seem to occur randomly and is thought to be resolved in some instances by reflashing factory TNT software. I personally have gone from 11 bad blocks to 8 bad blocks after flashing a few different ROMs. However, I have had people report (this is where it gets weird) that they wiped their sdcard and after they reflashed the same ROM over itself the sdcard came back. Others have reported the system folder persisting after a partition. Sadly, I have to take it at face value which is why my suggest is usually the nuclear option. These are the same people that frequently get stuck at the birds. A lot of this was due to inserting an sdcard with Plastikmans touch recovery all of the formatting and parittioning was being done to the external card, not the internal one. However, it doesn't explain the issues the others were having.

2. data and sdcard is what I hear the most. The cache from my interactions has never survived.

3. Why can one person use a kernel and another can't without an SOD? Sometimes it just doesn't make sense. Usually I chalk it up to user error.

4. Not sure, but a suggestion that simple has made it so countless people could get a ROM to boot that would not normally. Once again, I don't have my hands on the tablet so I can't say for sure what they are actually doing.

You're repeating yourself. It may be a useless step, but without education people will keep doing it and some swear it makes a difference. It is a redundancy to ensure the parts are being wiped. Most ROM zips have wiping scripts built into them, but people still wipe manually anyway. It is just reassurance. Just like the person who clicks the lock button on their car alarm remote several times when one click will do.

Sorry, I didn't mean magic value mismatch error, I meant recovery loop. I thought you created that zip.

I am not a developer, never claimed to be. You are the one not following. Your frustration with unnecessary steps can be corrected by going to the source. I am not the source. When I reference the "install," I am referring to flashing instructions provided by each developer.

Some steps are redundant and in theory they don't make a damn bit of sense. Then again, neither does a sugar pill curing cancer, but it happens.

There is a huge variance with these tablets and I am not sure what the cause it. Perhaps different hardware? Different vendors for the hardware? I had one tablet that would not tolerate an nvflash and would constantly reboot into APX. At the rate US Merchants has replaced motherboards left and right (including my own), it makes me wonder if there is a deeper underlying cause.

I'm not sure what you are looking to get out of this. If you want to prove your superior Android knowledge, you don't need to. However, don't knock someone for helping. These public calling outs that you do are one of the main reasons that XDA has a bad rep to begin with. Seriously dude, why are you so mad?