Hi all my name is Todd. I am a complete newb to the Gtablet. Just bought it yesterday after spending days reading on this forum and others about modding it.
I was able last night to install the clockworkmod and then flashed to TNTlite 4.0 and then to TNTlite 4.2.3.
I was following the thread on here about how to do this. The first problem I ran into was I could not get the g to accept my gmail account. After much searching I found the fix of entering it into youtube and this worked fine.
I then did the marketfix and every time I try to get into the market I get a server error retry, or cancel. I have followed the directions to the letter. I even rebooted into clockwork and formatted the sdcard still the same error. I have searched and search for answers (stayed up till 3:00 am this morning, work sucks this morning!). I have found many threads from back in December where folks were having this problem but no real resolution. Most everything I found pointed to an issue with the market not the g.
Sorry I just saw the thread above this with the same issue.
http://forum.xda-developers.com/showthread.php?t=954666
Any pointers I could try?
Related
I have googled the topic extensively but I could not get the proper answer till now.
My problem is I just wanted to root the my Nexus S, the instructions from the forum seemed easy. Reading about different methods, i went with the Superboot one, after preforming the task and everything seemed well what the terminal (mac) output meant. After it restarted it never rebooted the UI and just stuck with the boot screen ( Google written in the middle and a lock sign on the bottom).
I'm not pro with android since I only got the phone a few days ago, after more than a decade on simbian.
Anyway does anyone know what happend? Even better how to fix it? Flash the Rom?
Answer
I figured it out made, got a new version of Superboot and redid it and it works now.
I originally purchased a GTablet from the original Woot! sale based on reviews during that sale that this was a wonderful tablet once a new rom was installed. The first tablet I purchased as a gift for my wife. I received it on a Friday after I got off work. Within about an hour, I was up and running with TNT Lite, a fully functional app market and Adobe Flash Player.
I primarily followed this guide from these forums. I had zero problems and everything worked flawlessly following the guide.
I was so impressed with the tablet, when it came up on Woot! again, I decided to purchase another one. This tablet arrived quickly, and by all appearances was the same as the tablet for my wife. I checked the stock OS, installed the OTA update and verified I was on 1.1 3588. I proceeded to follow the guide again and ran into problems immediately with the app market.
I used the basic app market fix listed and no matter how many times I did it, I couldn't see the majority of apps. I then began looking around the forums and found this guide for the titanium backup method. I followed this exactly and still the market wouldn't work.
I found one more guide (can't find the link now) that instructed me to edit files on the tablet to known working configurations. I grabbed the files and they already had exactly what the guide was telling me to change to. So no luck there.
I then remembered reading that some Roms had a working app market out of the box. I figured I'd try VEGAn or Cyanogen Rom instead of TNT Lite to see if this fixed this problem. This is when I ran into another brick wall. I was completely unable to load these Roms on my tablet. After performing the install in ClockWork Mod and rebooting, the tablet would get the ViewSonic screen with Birds and never complete the boot. I left it on that screen for as long as an hour and still nothing worked.
I came back to the forums looking for more information. Buried deep in the VEGAn 7.0 thread I found a gem from someone who had a similar boot problem (they made no mention of market problems). This person said they were able to fix the boot problems by using NVFlash to restore the tablet to original settings and pointed towards this thread as a possible fix.
I followed the steps in there directly. I was hung up for about 20 minutes trying to figure out how to use NVFlash and ClockWork mod until it dawned on me that accessing for NVFlash was used with the Volume Minus button instead of the Volume Plus button. So if you are confused in that section, keep in mind they use different power up methods and don't conflict.
After using NVFlash and restoring back to the original settings I was able to get into the stock rom. I tried the OTA update immediately and it failed after the download. Restarting the tablet fixed the problem. After you are able to boot back into the stock rom, I recommend a restart just in case. Then do the OTA 1.1 3588 update.
I then followed the original guide again. This time, everything worked as expected. Using TNTLite and the Market Fix worked the first time. I formatted and installed VEGAn and it worked on the first time too.
I decided to make this post as a thank you to everyone out there who works on these ROMs and everyone who has posted fixes to their problems. Hopefully this will help anyone else that is having problems.
My wife and I absolutely love our tablets and this wouldn't be possible without the fine people here.
TLDR;
Market was broken and known Market Fix didn't work. Used NVFlash and it fixed it.
NVFlash uses Volume Minus not Volume Plus
Restart Stock OS after first boot before installing OTA update
Thanks for posting this. I plan on switching to vegan from tnt lite soon. This is good info to know ahead of time.
Thanks for the info from someone who is waiting to theirs in the mail.
Hello.
First off i will start with the fact that i've read most of topics proposed by Google and Xda forum search, so please don't treat me like an idiot.
From what I've noticed there's quite a few people with similar problem - after going back to stock ICS everything was fine for a week then boom, this morning i wake up and my TF101 is refusing to turn on. First off I've thought its just a fail and i will fix it easily but now I'm seriously scared. So far I've wiped device around 10 times, and so did i tried to install other system software (I've had couple zip files with other rooms stored on my SD, and Clockwork recovery works fine except for the fact that when i use "Super wipe" from android revolver it's getting stuck on clearing DATA).
Some detailed info :
After installing energy ICS device does not even go to loading screen, just keeps on boot loop.
After installing CM10 there's no boot animation change...
After installing any ROM and rebooting there's this installation bar... it progresses instantly.
Did anybody had similar problem which they got fixed by some magic method... or should i just throw my transformer into the bin? I'm clueless now, hope you can help me out.
Regards Nekyo.
Edit : 2h later , Fixed it through the NVFlash... thanks for all support.
nekyo said:
Edit : 2h later , Fixed it through the NVFlash... thanks for all support.
Click to expand...
Click to collapse
You wait 2 hours and then complain there was no support?
If you run into a problem you can't fix on your own, you're not going to make many friends expecting people to jump on your issue within 2 hours.
This is XDA, basically a DIY forum, if you want support here, expect a few days delay for an answer that helps.
I hope I am not wasting anyones time by posting something that may be and I hope is a simple fix, but I have a problem with my Verizon Xoom, a 602 (without the 4g upgrade- don't even have verizon service) that I can't figure out- and it's not for lack of searching. I have been rooting my devices and running custom Roms since my HTC Touch, (a big thank you to all of you here at xda for all the knowledge and instruction I have been able to leach) but I am very much still a noob with only the vaguest since of how Linux, android or the devices themselves actually work- and that is especially true of my xoom with all its post release changes in storage and whatnot since I bought mine, so please don't flame me to hard if this is just my ignorance- I promise you I'm not just being lazy, I just can't figure this one out. I have been running EOS for a while now without a hitch, and recently installed 150 when it became available. everything was fine until a couple of days ago when it started freezing on unlock which just took turning the screen off and back on to fix, but every app started crashing, some periodically and some such as android.process.acore, browser, and google play that won't open at all. I use Team Win's recovery and tried a wipe and reinstall, but same thing. When I try to fix permissions I get a failure with the message "E: Unable to chown '/data/app/com.google.android.youtube-2.apk' 1000 1000". Also when I try to wipe internal storage I noticed everything was still there even though my recovery was saying I had a successful wipe. I switched to clockworkmod recovery and tried to use eraseData file in the folder to wipe the old way but that didn't seem to work either (which I'm not even sure I did right but figured I better get some advice first anyway), and when I tried to flash EOS 3 stable it won't get past the EOS boot animation at all. If anybody out there knows whats up and has the time to point me in the right direction it would greatly appreciated... Thanks
Wowzers! When all else fails ... unroot / re-root. That will wipe everything.
Hi! I realise this if my first post I'd like to tread lightly; but I'm about 4 days into solving my issues and I just want to finish it...
I've had my Nexus i9020a (bought from Koodo) since ~May 2012. I upgraded to ICS sometime in the summer and sometime in the last few weeks it has started rebooting. I hadn't been installing new apps, etc. I'm not sure what the cause is. I 'Factory Reset' today in an attempt to resolve the issue, thinking it may be a program gone AWOL; but it has rebooted a few times since. I *just* looked through rebooting FAQ on this site and have edited the first few features listed there. I'm not sure if it has worked yet, but I'll get back to you on that. For the record, the only programs I have installed now are Swiftkey 3, Handcent and Beats (DDR simulator, updated in November).
In the meantime, before I found the solutions here, I decided to take another shot at unlocking the bootloader and try installing... probably CyanogenMod.
Specs: Windows 7 64 bit with Nexus S I9020a (Koodo) running 4.0.4 (4.1.1/2 OTA haven't come through, despite dozens of attempts at clearing the GSF cache, etc)
So I've been using the Nexus S: Full Update Guide found at:
hxxp://wiki.cyanogenmod.org/wiki/Nexus_S:_Full_Update_Guide
(It won't let me post the link)
I've followed the guide for installing the Android SDK, gone to CMD and typed 'adb devices' and had it show up. Theoretically, the SDK should be running fine.
Next, I turned on the USB debug mode. Then I booted up the bootloader, plugged the NS into the PC... and despite not having issue when the it's turned on (driver installed properly) windows says drivers have not been found for the device. Thus, when I type fastboot devices, it comes up with nothing.
I've been, and will continue perusing forums for this, but so far I haven't seen anyone with this specific problem.
Edit: I have also gone to the directory with fastboot/adb and used cmd to reboot into the bootloader, only to have windows 'ding ding ding' an unrecognised device.
2nd Edit.
I've gotten a stage further! I'll keep the thread open because I may come across something and it's nice to write my issues down. Seems my head can wrap around the problem a bit better. Anyway, I installed PDAnet and BAM, it works. Onto getting CWM installed! Thanks for the, uh, help!
3rd Edit.
CyanogenMod 10.0 stable is booting for the first time!! It's taking a while... but I appear to be on the home stretch! Also, my phone didn't reboot for a few hours before I installed CM. So if I don't end up somehow bricking it... and I mean, this first boot is taking a heck of a long time... The animation sets me at least a bit at ease... maybe 4.0.4 will work out...
Edit 4
I forgot to clear the app and cache data before flashing the ROM to the phone and thus the issue... after a VERY tension filled moment of pulling the battery during first boot... I rebooted, cleared said data and reflashed the ROM. After a boot, I realised I forgot the GAPPS zip and fixed that. Now I'm running CM10 Stable!! I'm stoked that after months of putting it off cuz last time I did it I didn't get anywhere after many days, but now it's done!! Thanks again for such an awesome site!
Thanks for sharing your experience instead of just saying "Mods please delete this i solved my own problem" :good: