Related
Why are we not getting honeycomb to play with?
You really need to read some threads before posting a question that has already been answered many times.
Sent from my Viewsonic G Tablet running TnT Lite 4.2.2 w/ Pershoot's Kernel using Tapatalk Pro
And the honeycomb you are referencing has no practical use in the real world. Its a hacked together UI that does nothing but run the preview sdk
if it was worth it we would have it. our devs kick ass
Moved to general
I hate to sound like a jerk but what is it with all the people whining about honeycomb. The only version out so far is a hacked version built off the prelim sdk and in no way will work for the g tablet. Anyone who has been Modding for anytime knows the cardinal rule for android...
DON'T ASK FOR ETA'S.
When honeycomb is officially released by Google I'm sure it'll be like every other release and in a short time we'll have our own version. Until then have some patience please and do some research.
or if you want honeycomb straight away then get a xoom and pay the big bucks
What i dont get is why do people ask and ask...........
Doesnt your gtab do everything you need It to?
honeycomb... Hero cookie....danish....pop tart...soda cracker........flap jack or royal with cheese
Just names I dont see anything i cant wait for.
Now when they say the next android version will give my gtab the ability for it to make me samwiches and give me oral pleasure on demand that is when i will be all over the devs to build that $hit....
Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!
Really?
BilliamB said:
Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!
Click to expand...
Click to collapse
Let me get this straight. You post in the wrong section, you ask for an ETA, and you obviously did not search, which also means you did not read any of the forum rules or stickies. Yet, somehow we are all assholes. You know if you just follow a few simple rules your experience with XDA will be much better. The rules here are no different than any other forum. I am going to assume you are new to this, so I will help you a bit. Search for what an SDK port is and you will quickly realize why you do not want this.
BilliamB said:
Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!
Click to expand...
Click to collapse
I think you should flash the Nook Color ROM BilliamB, you obviously know what you're doing, I'm sure you can get it to work. I mean come on, the G Tablet has a Tegra 2 processor, it should totally work right? Although you may want to read a few threads.... oh wait, you obviously don't do that. Come on dude, the only one here being an AH (as you put it) is you.
Sent from my Viewsonic G Tablet running TnT Lite 4.2.2 w/ Pershoot's Kernel using Tapatalk Pro
Seriously.... You will not see Honeycomb on the G Tablet until another unit is released with Honeycomb and has the Tegra 2 chip. The issue is the instruction sets are different enough that its not a one for one port. The Nook, Dell Streak 5, Tegra 2, etc. are all based on the ARMv7 instruction set but there are difference in their implementation enough that make them incompatible. In addition the biggest differences lay in the I/O subsystem which makes these platforms completely different. With these major differences it makes porting from the emulator (which is how they are getting Honeycomb to work) a daunting tasking and nearly impossible on a Tegra 2 based device.
I am very confident after the first Honeycomb system image is posted it will be running on our tablets... It will be a race as to who gets props on Engadget for being the first to port to the G Tablet..
You would get less hostility if you read, learned and asked accordingly. Its a give and take community. Unfortunately the way you asked makes it seem your less inclined to contribute and just take...
BilliamB said:
Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!
Click to expand...
Click to collapse
Honeycomb is coming to the g-tablet in March, till then.
RERRRAAXXXX
BilliamB said:
Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!
Click to expand...
Click to collapse
Seriously dude....This is about the 10th thread with this same topic started since the nook got the honeycomb sdk running. You ask questions without searching and then cause you dont get the answer you want you call us names. Don't worry, most of us won't answer your questions anymore.....ever.
BilliamB said:
Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!
Click to expand...
Click to collapse
Whoa!!! Bad move man, bad move. You need realize that you can't call people who are willing to spend rediculous amounts of thier personal time to provide the community with amazing firmware AH's! Quite the contrary - They are saints (and, actually, you serve no purpose).
Swyped from my VEGAn-TAB-v1.0.0B5.1
deep_powder2012 said:
Whoa!!! Bad move man, bad move. You need realize that you can't call people who are willing to spend rediculous amounts of thier personal time to provide the community with amazing firmware AH's! Quite the contrary - They are saints (and, actually, you serve no purpose).
Swyped from my VEGAn-TAB-v1.0.0B5.1
Click to expand...
Click to collapse
Totally agreed. XD.
Hey Alpha06...
I'm just curious if that is a confirmed news or word of mouth that the G-tablet would have Honeycomb around the March?
I wouldn't guarantee that Honeycomb for the G-tab would be available for sure in March, however I wouldn't be surprised to see Alpha-versions of Honeycomb ROMs shortly after the first Tegra2 devices are released and rooted. Like everyone has been saying around here, don't ask for an ETA, because the people around here that do develop do it on their personal time. They have lives, work, and possibly kids, wives, or whatever that also wants their time as well.
Remember, porting a ROM is a lot easier if there is solid reference material to build from. As you may notice, TNT-Lite comes from his building on and improving the existing TNT version of Android that came with the G-Tablet. Vegan is a modification and improvement of the Vega OS. I don't believe that the developers of either package (and correct me if I am wrong) went to Google's GIT repository for Android and compiled their own versions of the OS specifically for the device - along with writing their own custom device drivers for all of the internal hardware. They built off of, and improved what was available.
IIRC, the Nook port of Honeycomb is only partially functional. The just released port for the Dell Streak (http://www.mytabletlife.com/2011/02/08/dell-streak-honeycomb-port/) is as well. Why, because they are essentially starting from scratch.
Which brings everything back to my original point. As soon as reference devices are out in the wild, I'm sure that will be the point where we will see Honeycomb ports start to pop up here as well.
BigJohn
march can not get here soon enough... heh.
Guys,
Have at it ! Here is the Xoom build.prop thanks to thefredelement... Give him a HUGE thanks for sharing this
Just download it; then extract the zip file and there you go!!!
Thanks again thefredelement !!!
Does this mean we will have honeycomb soon or do we still need the drivers from nvidia?
You still need a boot.img. Just so you know people have had access to the xoom for more than a week already and have been working on this.
Thanks, but based on the early indications this fingerprint will actually cause the market to shrink rather than expand. It is interesting to read though as it specifically states nosdcard, and does include the telephony stuff, if nothing else there is potential that once we have a honeycomb port 3G usb modem drivers may become available.
I just posted this so we could take a look at what was in it... it is a good read if nothing else ;-)
thebadfrog said:
You still need a boot.img. Just so you know people have had access to the xoom for more than a week already and have been working on this.
Click to expand...
Click to collapse
I would have thanked you but I've exceeded my max per didn't know there was a maximum. You learn something new everyday.
Anyways, it's also my understanding that to get the boot.img, the Xoom will need to be rooted. Is that correct? So, is that what we should be really looking for? Xoom has been rooted threads?
Look for "Rom based on Honeycomb". And yes it needs root. It will happen people. Posting endless honeycomb threads is not gonna make it any faster.
Ok I'm kind of a noob, please don't slam me 'frog. Since the whole purpose of Android and the whole Open Source thing is to make source available, don't either Motorola, nVidia or Google NEED to release this Honeycomb-Tegra 2 code at some point. I do realize that there may be proprietary pieces but I thought once you used open source code, you were obliged to release your resulting code to the community. Am I missing something here or is all this chatter just an attempt to get it faster?
I hate seeing all of the teaser threads as well, but I also try to keep an open mind and view it more as humorous than obnoxious. I'm sure the real dev's are quite adept at skipping and ignoring the stupid comments by people like me.
I'm just saying ...
thebadfrog said:
Look for "Rom based on Honeycomb". And yes it needs root. It will happen people. Posting endless honeycomb threads is not gonna make it any faster.
Click to expand...
Click to collapse
Lol. I shouldn't have posted the last two sentences. It's not like I was saying that I was being impatient. Just wanted to learn that's all.
I'm assuming we'll see a lot of the bits and pieces of the XOOM system posted in here and just wanted to know what's relevant or not.
Thanks again.
Its all good. I understand people wanna learn.
Yes they have to release anything that is open source but if you use linux you can use the nvidea and ati example. They don't release their proprietary libs for their cards and as a result its quite likely when you upgrade your kernel you break your video drivers. Its not so bad now but a couple years ago I couldnt keep an ati card working.
All the endless threads that are repeats make it nearly impossible for noobs to find good information and it makes it harder for me to link the correct posts for noobs to follow. Everyone was new at one time but you will never learn anything if you keep asking and not looking. This is a developer forum....xda DEVELOPERS.... not a customer service forum. Most devs here go out of their way to answer questions as do a few of us power users. My tirades are not directed at people like the 2 previous posts. Its the ones that dont want help. They want someone to hold there hand and type out each and every command for them and supply them a fix for every problem. And they want it now
sverbanic said:
Ok I'm kind of a noob, please don't slam me 'frog. Since the whole purpose of Android and the whole Open Source thing is to make source available, don't either Motorola, nVidia or Google NEED to release this Honeycomb-Tegra 2 code at some point. I do realize that there may be proprietary pieces but I thought once you used open source code, you were obliged to release your resulting code to the community. Am I missing something here or is all this chatter just an attempt to get it faster?
I hate seeing all of the teaser threads as well, but I also try to keep an open mind and view it more as humorous than obnoxious. I'm sure the real dev's are quite adept at skipping and ignoring the stupid comments by people like me.
I'm just saying ...
Click to expand...
Click to collapse
Typically one week is the lead time afforded the trail blazing device for each generation of Android, and then the plain vanilla source AOSP is posted at source.android.com (read about git first, where the kernel is posted). However none of the proprietary information in specific devices needs to be made available right away.
Will th devs that made the honeynook sdk preview be able to update that if they get a Xoom, amd in turn would that help the g tab devs?
I'm just curious about how much of a problem the fact that the XOOM has a Gig of system ram rather than 512 megs will be. I could see an easy way to protect some exclusivity under the guise of "ensuring compatibility" where one of the first boot steps is to check for enough available ram...
Good thing my Zpad has 1 gig ram then eh
boot img and tegra 2 aosp source here
http://android.modaco.com/content/advent-vega-vega-modaco-com/333138/xoom-rootboot-img/#entry1614605
I think.
Alpha06 said:
boot img and tegra 2 aosp source here
http://android.modaco.com/content/advent-vega-vega-modaco-com/333138/xoom-rootboot-img/#entry1614605
I think.
Click to expand...
Click to collapse
It's a Xoom boot.img, and the (tegra 2) kernel source for honeycomb (2.6.36).
Ok, per Engadget Xoom has been rooted... Next?
Here are the init files as well: http://forum.xda-developers.com/showpost.php?p=11615922&postcount=9
You can get a rooted boot image here: http://www.koushikdutta.com/2011/02/motorola-xoom-rooted.html
Love it when things start moving at nearly the speed of light,... uh oh, getting dizzy... frog, will you hold my hand?
MikeTheSith200 said:
Will th devs that made the honeynook sdk preview be able to update that if they get a Xoom, amd in turn would that help the g tab devs?
Click to expand...
Click to collapse
The Nook is so heavily supported because it's so god damn cheap for a tablet. (it's really an "e-reader")
there was no touch interface released with the version of honeycomb from the preview sdk.
With a real Honeycomb product (and full SDK) full development is possible.
If you wait, They will build it, we will come. =]
This is going to be long, but I have a lot to say.
There's been a LOT of heated debate about TNT Lite 5, lately. This build is based on the vendor's 3991 UAT build. This build is a "1.2" build which means it's a major update from Viewsonic, and it replaces the bootloader. Not only that but the new kernel REQUIRES the new bootloader. We are not certain yet, but Viewsonic is likely to be moving into this direction.
Now, many forum members use clockworkmod. What I have recently learned is that clockworkmod does NOT update the bootloader. In the case of stock 3991 (and TNT Lite 5.0.0) that means that clockworkmod cannot be used as an upgrade tool - IT DOES NOT WORK and, in this case, will actually break your device.
With that in mind it's my opinion that, since clockworkmod has this caveat, then it is a risk and the user community should be made aware of this. If you are willing to take this risk, be aware of the caveat and that, if needed, that you will need to use the nvflash tool to fix your device.
Some of us have been dancing around the issue saying that nvflash is not for non-technical users, and thus TNT Lite 5.0.0 should be pulled completely given the problems with upgrading with clockworkmod. My rebuttal is a simple one -- imo, if a forum user decides to take the risk of using clockworkmod, then they should also understand how to use nvflash as a backout - they go hand in hand and should be a requirement, not an option.
I have heard many complaints about TNT Lite 5 upgrades, but the two most common ones are these:
1. Backing out to stock 3588 breaks recovery (originally clockworkmod).
2. Upgrading to TNT Lite 5.00 by using clockworkmod, by mistake.
Imo, most of the issues we've seen have been clockworkmod related - that's not to say that there have not been other issues, but I believe that the vast majority of them were related to clockworkmod.
I am still under pressure to pull TNT Lite because of the increase in user issues - I think this is the wrong thing to do and I am getting some flak because of my stubbornness. If VS sticks with their new bootloader, this is something that every modder here is going to have to deal with, eventually. But if they backpedal, then I made the wrong choice and we'd need to undo TNTL 5. We just don't know yet.
I think you are right that it maybe something that needs to dealt with sooner or latter as this update could be in anticipation of a even bigger upgrade to 2.3 or 3.0?
It seems from reading threads that not everyone is familiar with reflashing or I hate to say but reading and understanding the steps. The very worse comment I read was "I'll just return my tab and blame insert a cause " What horse hockey.
If they don't know or care to take the time and proceed with caution and then not take responsible for it then they should leave well enough alone.
I actually would like to hear replies (for and against) because maybe I'm looking at this the wrong way. I am stubborn, but if someone gives me a good enough argument I could change my way of thinking. One valid argument is that Viewsonic hasn't even released 1.2 yet, which is a good point. They have to do something very soon (due to Flash) so hopefully by the EO this month we will know what happens.
One of my theories on why they updated the bootloader in this last release was to consolidate development between the GTablet and their newer devices. I don't know if I'm even close to the mark here, it's just a guess. Their kernel is back to an svn #1, so maybe they are using a new development branch.
I vote you not pull it. Like you've said here and in the TNT Lite 5 thread, if someone decides to use a rom they should read the instructions (several times if necessary) before they embark on trying this or any other rom.
If people are throwing caution to the winds and jumping in before they have an understanding of what they are about to do then I say the fault is on their part not yours. You can only do so much hand-holding but in the end the people that use this site and are interested enough to try different roms should know better. Personally, I think you're being more diplomatic than most people about this.
Who knows, since our gTabs have proven to be almost unbrickable maybe people have lost their usual caution?
Vote Don't Pull -- NVFlash Not That Bad...
I vote to keep 5.0.x up.
I have two tablets and had not had to flash one after several months.
But having had to learn nvflash and subsequently doing what I could to help
others -- it's just simply not that bad (at least for the Windows version since
that's what I use.)
Now that a number of us have made sure USB, nvflash and .img files are
available -- and that there are several posts with instructions out there -- I
don't think the nvflash process is any harder than learning the normal
"recovery" process.
If we -- any of us -- are going to play.....then we need to man up
(or woman up, sorry ladies!) and do it right and not complain about it.
Honestly, many times when folks have trouble, it is their own fault.
"Laissez le bon temps roulez" they say during the Mardi Gras celebrations down
here. "Let the good times roll."
Rev
Don't Pull It! Keep it up! We will support you
I have not and will not be flashing your rom at least until it is found out that there is a permanent change coming and the new bootloader is part of that change. I have tried just about every rom I have found for the gtab except tnt 5.0 but that is not because I don't want to screw up flashing it, I am sure with nvflash I would get it back on track, but it is because I have not found the previous releases my preference and I doubt 5.0 would make that change.
By the way no offence to you roebeet, your work and developing here have been beyond superb and are much appreciated. I unfortunately just don't prefer tnt on my tablet. But don't let anyone tell you that you need to remove your work. Your work is not the one borking their tablets they are.
Thanks for all your work Roebeet, even the work you do that I may not use myself
I had zero issues with the upgrade to 5. I thought the instructions for it were clear and concise . I used nvflash to fix my GTab after I noobishly tried to update from Rom Manager when I first started testing the different roms, so nvflash is my friend.
My GTab is running great on 5.0.1 right now, so I hope you will continue to to work on it and not pull it.
Thanks for all your hard work
Jeffrey
Keep it up. at least we have NVflash and its not a real brick. I remember having to update to Danger SPL on my G1, and people were getting real bricks.
IMHO if people are flashing ROMs they need to take a little time to learn what they're doing.
You can't pull it because of ignorance on our part... that defeats the whole point of hacking. Heck, it was the first full rom i installed and guess what? I followed one of the howto threads ignoring your instructions and got to learn all about nvflash. Pull the inaccurate howtos or get their ops to update them.... that'll definitely cut down the failure rate.
I'm glad I bricked my gtab after a whole hour of ownership. I now have a very nice Nvidia Tegra system post bitmap instead of the 10 year old viewsonic birds as a result of it!
The new viewsonic recovery does sd updating if I recall correctly... People can offer kernels and other updates in multiple formats.... They're going to have to if viewsonic goes GA with it.
Keep up the good work!
Sent from my Gingerbread VEGAn-TAB using Tapatalk
I agree with what seems to be the majority so far. Don't pull it.
I have been on this site for quite a while through at least 5 phones (all of them winmo). I do not count myself as an expert and rely heavly on others to develop what have turned out to be excellent ROMs and software and the means by which we can load them on our phones and tablets and other devices.
I have read and read and read and read some more. I have asked questions too. Most of the time becasue the knowledge is too technical for my small mind.
Too many people here expect hand holding and rather than reading, expect, or worse, demand, help when they haven't read the instructions.
To pull your ROM because people can't be bothered to read is to let them win and, in my opinion, dumb down this site.
There are warnings posted everywhere advising of the risks of modding our devices, including bricking the devices. In fact, the people most at risk of bricking are the developers, like you. If you are willing to risk bricking in the name of development, why can't others take responsibility for their actions?
No one points a gun at members' heads and tells them to flash. They join here of their own free will and perform upgrades to their devices in the hopes of making them better. If you are flashing a device, then you are aware that you could brick, or bork, your device.
Moreover, there are countless people here who are more than willing to help unbrick a device. So after bricking, people are forced to learn and read.
Here is a novel idea: Let's take responsibility for our own actions. Not just here, but everywhere.
Keep putting out your ROMs and mods and we can, as adults and willing participants, decide whether to use them or not.
I am now stepping down off the soapbox.
Just saying,
From what I have seen as a daily follower of this forum. It seems more and more users are just getting bolder knowing if something goes wrong, they have nvflash to rescue them from thier "Inevitable" - "User Error".
Heck, I've foolishly done it myself and I had to learn nvflash.
The risks of flashing Custom ROMs is clearly present. You (Roebeet) as Dev should not have to brunt the burden of an inexperienced user when something bad happens. After all, we were all inexperienced at some point or another. And the GTAB makes for a great learning device considering all the tools and support available here to backstep when something does go wrong.
I suggest you don't pull the ROM, but considering the extra complications involved with flashing 5, I could only suggest users clearly have an understanding
of said steps for a successful flash.
Best of Luck dude, and thank you for all your hard work.
It does not go unappreciated here!
T!
I think you should leave it up i myself accidently locked up my tab but i was able to find a resolution and get back up and running there are always issues with new things people just have to relax and go with the flow.
Thanks to everyone, so far! This was how I felt, as well - seems that it's not an easy path, but it's worth it in the end.
I just hope to FSM that Viewsonic doesn't beckpedal on me, because TNT Lite 6 will be as much fun as TNT Lite 5. /sarcasm
I don't see how anyone can complain. Rooting and installing software that is NOT from the manufacturer is at your own risk. I took that risk when I rooted and installed TNT 2.4 and then 4.2.5.
So keep it up and continue with 5.0.1 Let the reader decide if they wish to install the ROM.
With my history, I'll wait till TNT 6.2 before upgrading.
you've been given how to do/don't instructions, you're not to blame. Thank you for your hard work Roebeet;
Ok I am a total noob. .....a danger to mess anything up. ....I was spooked. Because I got this tab to mod and before I received it I studied here and YouTube on how to flash using cwm. .I thought. I was ready then came 5.0 and changed the game I then studied your tutorial and asked questions, alot of them until I felt comfortable I flashed to 5.0 without a hitch but I had nvflash ready to go...my point is that I knew I could Bork this up it was my risk I took it, roebeet has gone way far and above to give us this and help everyone out. Keep 5 up until a major change has to be done if not we know you will be on top of it...Thank you for your efforts!!!!
Signed,
Noob
I don't see any reason to pull it. The instructions and warnings are perfect.. And if you happen to be one of the ones that doesn't read the big giant print first then I suppose you deserve the lesson in learning NVflash. Might actually have a positive outcome by teaching people to read first...
One question I have though has to do with TnT 5 and Calkulins rom. They are both based off of 3991 yet Calkulins rom does not require a special clockwork, or need to be installed from 3588.. How come TnT 5 does? Calkulins rom is very fast, and from my impressions looks almost the same as TnT 5..
Just curious....
I vote to leave it up. I think those having issues are not reading /understanding correctly. I think some of the fear of nvflash is there are several conflicting sets of instructions also slightly vague instructions. Maybe one updated very detailed set of instructions (sticky) will eliminate fear and questions.
F*ck the haters, leave it up. I'm on 5.1 now, read everything and had no issues.
Keep it up, that's my vote. You are taking a calculated risk and that is valid in order to go forward. If VS takes another direction, so be it. The alternative is wait and do nothing and I don’t think you want to do that, but it's your call. We support you one hundred percent.
Thanks for your work I can say so because I'm a v5.∅.! User.
I just read a post by roebeet (well known dev who put together the TNT Lite ROMS) and something he said made enough sense to me that I thing everyone needs to hear it.
If you are going to flash and try everything you find on this site -- you run a real risk have having problems. Everything you flash adds, changes and deletes stuff from your tablet and some of that gets carried over from ROM to ROM to program.
Just because you partition/erase/delete/overwrite does not mean your tablet content is destroyed. There are a bunch of partitions on your tablet (12?) and some are preserved and some are modified depending on what you do.
So am I saying "Don't mod you G-Tablet" or "Don't try out new stuff." NO.
1. Make real sure you know what you are doing. Too many people just rush ahead and wind up with real problems.
2. Read directions and read all the posts about others who have done the same thing you want to do.
3. When you are making changes, do them one at a time and make sure it's working right before moving on. When you change a bunch of stuff it's hard to tell what the problem/problems is and where it came from.
4. IMHO, too many people see the modding as a game and then they get mad at the dev or people who are trying to help them -- when all the time it was their own fault!
I think it would even be a good idea if someone knowledgeable could help us see if we could put together a flash which would actually delete/erase what's on a
troubled tab so it could be rebuilt. Sorry, but I don't talk enough Android yet to do that.
Think about it.
Rev
butchconner said:
I think it would even be a good idea if someone knowledgeable could help us see if we could put together a flash which would actually delete/erase what's on a
troubled tab so it could be rebuilt.
Rev
Click to expand...
Click to collapse
I would recommend running a format zip before any reloading on a Gtab whether a new rom or the stock. Just like all the computers I work on for people the first thing I do is run a program to erase the hard drive to make sure nothing old can interfere with a new reload of the operating system
Calkulin has this format zip from his rom thread or you could use the other one from here
http://forum.xda-developers.com/showthread.php?t=974422
Start fresh don't just overwrite!
ale
Calkulin's Format all is awesome
Exactly. Calkulin's format all is a life saver. It is much cleaner and faster way than to do three or four steps to clean stuff out (Invariably one forgets one of the steps which causes all the problems).
I have used this file to solve many problems going from rom to rom... Good stuff.
[Q] Should I step back and use the format zip?
notsob2002 said:
I would recommend running a format zip before any reloading on a Gtab whether a new rom or the stock. Just like all the computers I work on for people the first thing I do is run a program to erase the hard drive to make sure nothing old can interfere with a new reload of the operating system
Calkulin has this format zip from his rom thread or you could use the other one from here
http://forum.xda-developers.com/showthread.php?t=974422
Start fresh don't just overwrite!
ale
Click to expand...
Click to collapse
Two days ago I reset my gtab to stock. I have the 3389 zip saved and installed that using clockwork. I also used clockwork and did the data wipe/factory reset right before actually applying the rom.
Loading the stock VS rom removes clockwork and after reboot it pulled the OTA update and currently running the 3588 version.
I did this in anticipation of the upcoming VS update. The tablet seems to be running fine and as I said it's able to find and apply OTA updates.
Would you still recommend running this format zip, and then re-apply the 3389 I have saved?
Thanks,
Neudle
** Would like to point out there is a comment in the referenced post concerning using this format zip..."So this is a "detox" program for our gtablet that we can choose to run prior to NVflash process. And this process should not be done unless absolutely necessary, right?" "Yes, exactly..."
Neudle,
If you were at 3389 and did 3588 via OTA, I would try my recovery. If it does not
come up with your old CWM, then it should be stock recovery and you should be
good to go.
If needed, you always have the option of manually loading recovery and the 3588 update.zip into /sdcard and flashing stock again.
Rev
butchconner said:
Neudle,
If you were at 3389 and did 3588 via OTA, I would try my recovery. If it does not
come up with your old CWM, then it should be stock recovery and you should be
good to go.
If needed, you always have the option of manually loading recovery and the 3588 update.zip into /sdcard and flashing stock again.
Rev
Click to expand...
Click to collapse
Thank you for the response.
Actually I think my tablet is fine. Unless I'm really confused (which is certainly possible) 3389 was the update from late december/early january. The 3588 is the update that came up in like febuary. Isn't 3588 the most recent?
This isn't the first time I've reloaded the stock rom and it seems it always over-writes/removes the clockworkmod.
I was simply more curious if you folks do feel it's always best to use the format.zip when swapping roms?
As I said, I'm simply prepping and anticipating the upcoming update from Viewsonic and not worried about clockworkmod for the time being. From what I've seen the update includes a recovery that looks similar.
Thanks again,
Neudle
I think the OP makes an excellent point for all us weekend tinkerers. The G-Tab is my first experience with an android device and although I have experience with rooting and flashing roms and kernals on another platform (WEBOS on my Palm pre), I have spent my first few weeks with this device just reading as much as I can on these forums before trying anything myself.
I was fortunate enough to get a great deal on this tab second hand from somebody who had already flashed it with Vegantab ( I believe 5.1.1). As it stands, it pretty much does everything I need it to do and there is no reason to break what alreday works...... except that I am a weekend tinkerer...... and I am thinking that I would like to try Calkulin's rom.
At the moment, I am not sure that it represent's an upgrade over what I have and I may wait for something gingerbread or honeycomb based that people report to have a signifigant benefit over Vegan 5.1.1...although I am sure I will convince myself differently at some point.
I know that I have CWM installed and that I can use this to clear up caches and personal info before flashing another ROM. Does Calkulin's format erase this? If so, does it need to be re-installed before putting on a new ROM? I am reading posts about people flashing back to stock and receiving updates before flashing a new rom. This completely confuses me as I don't understand the benefit unless, as the OP seems to indicate, there are bits that are left over from the old ROM when a new one is flashed. Is this desirable?
Sorry if I am asking so many questions in this thread. I know that there are bits and pieces of info scattered among many threads but some of it seems contradictory and some I am sure is outdated.
Can someone either outline or point me in the right direction to a step by step that outlines the most current and least likely way to brick upgrade from Vegan to Calkulin's ROM?
Thanks
butchconner said:
2. Read directions and read all the posts about others who have done the same thing you want to do.
Click to expand...
Click to collapse
Here's my problem. Where is the step by step, this is how you take a GTab you just bought, to ROM "XYZ" the correct way? There are lots of "how to"s scattered all over this forum, but no one sticky at the top that says "Here's a step by step". Right now, I'm reading through everything again, before I try and mod my tablet, and it's a mess. It would be nice is someone+moderator made a nice, straight forward LOCKED thread that is stuck, that explains it all. The FAQ isn't quite the information necessary (in my eyes).
I'm pretty technical (engineer by trade) and if it takes me a bit to figure out how to do something, the general n00b is going to screw something up.
Just my thoughts.
h3llphyre said:
Here's my problem. Where is the step by step, this is how you take a GTab you just bought, to ROM "XYZ" the correct way? There are lots of "how to"s scattered all over this forum, but no one sticky at the top that says "Here's a step by step". Right now, I'm reading through everything again, before I try and mod my tablet, and it's a mess. It would be nice is someone+moderator made a nice, straight forward LOCKED thread that is stuck, that explains it all. The FAQ isn't quite the information necessary (in my eyes).
I'm pretty technical (engineer by trade) and if it takes me a bit to figure out how to do something, the general n00b is going to screw something up.
Just my thoughts.
Click to expand...
Click to collapse
I haven't found that to be the case at all. In fact, I've seen nothing but repetitive reinforcement of proper procedures from every knowledgeable source. If the ROM Creator says use clockworkmod to install then wipe data... well do it. If he/she says use standard recovery... well... This isn't rocket science. I've installed and tested every ROM listed here with no failures by following the included instructions. I can't believe that is an anomaly.
If you want to be truly successful, learn what each of these tools (clockworkmod, nvflash, etc.) does and more importantly what they do not do. When you educate yourself to their proper use you won't be finding yourself using a hammer when you need a screwdriver.
hotfire!,
I think that's one of the points I hoped to make in this thread.
I appreciate the "format" tips -- but I have not used it and none of the folks whose opinion I watch for have put their stamp of approval on it -- so my opinion of it is still
in the making. I will use it only cautiously until I have confidence it is good.
But as you have said, we do have a hodgepodge of stuff here. People try to do
too much too fast -- and others suggest stuff that doesn't need to be done.
For example -- if somethings crashes on my G-Tablet, I go back to a basic CWM/ROM combo that I know is good so I have a solid place to start and then rebuild. Takes a little longer, but I think it save me a lot of anquish.
So like a lot of others, I just help where I can. But I do try to be conservative and consistent making suggestions the will not "snow" the new or offend those who think
they know what they are doing.
And to everyone I suggest the wrong thing, OOOOPs, and apologies. To those who
help me an give others good help -- thank you.
Rev
K J Rad said:
I haven't found that to be the case at all. In fact, I've seen nothing but repetitive reinforcement of proper procedures from every knowledgeable source. If the ROM Creator says use clockworkmod to install then wipe data... well do it. If he/she says use standard recovery... well... This isn't rocket science. I've installed and tested every ROM listed here with no failures by following the included instructions. I can't believe that is an anomaly.
If you want to be truly successful, learn what each of these tools (clockworkmod, nvflash, etc.) does and more importantly what they do not do. When you educate yourself to their proper use you won't be finding yourself using a hammer when you need a screwdriver.
Click to expand...
Click to collapse
But therein lies the problem. There *is* a great thread on installing CWM and then ROMs using that. Step by step, it's fantastic. Installing a new kernel *is* found in some of the threads, but I wish that great thread with the CWM and ROM installation also had Kernel info.
Regardless of if you know how these tools work, it's nice to have a step by step to follow, just to ensure you're doing everything in order. I do it at work when I'm working with a new system (I write it myself) just to make sure I follow the same procedure every time. It helps when problems arise.
I'm just saying, for the n00bs, it would be nice to have a "one size fits all" thread. I was able to successfully install CWM and Vegan without a single problem, as I've been reading this forum for MONTHS, but I'm not a normal person (nor are most of the regulars here).
One thing I try to do, is demystify technology. Make it easy, explain it in simple ways while still being effective as describing what is going on, and then you don't get "stupid questions" later. Essentially, trying to run in the opposite direction that most Linux forums tend to be. Threads buried 2 years back have the info, everyone screams at the n00bs saying "USE THE SEARCH".
Love this forum, the people here are REALLY helpful, but there is room for improvement. That's all I'm saying.
h3llphyre said:
But therein lies the problem. There *is* a great thread on installing CWM and then ROMs using that. Step by step, it's fantastic. Installing a new kernel *is* found in some of the threads, but I wish that great thread with the CWM and ROM installation also had Kernel info.
Regardless of if you know how these tools work, it's nice to have a step by step to follow, just to ensure you're doing everything in order. I do it at work when I'm working with a new system (I write it myself) just to make sure I follow the same procedure every time. It helps when problems arise.
I'm just saying, for the n00bs, it would be nice to have a "one size fits all" thread. I was able to successfully install CWM and Vegan without a single problem, as I've been reading this forum for MONTHS, but I'm not a normal person (nor are most of the regulars here).
One thing I try to do, is demystify technology. Make it easy, explain it in simple ways while still being effective as describing what is going on, and then you don't get "stupid questions" later. Essentially, trying to run in the opposite direction that most Linux forums tend to be. Threads buried 2 years back have the info, everyone screams at the n00bs saying "USE THE SEARCH".
Love this forum, the people here are REALLY helpful, but there is room for improvement. That's all I'm saying.
Click to expand...
Click to collapse
Short answer: Great idea! When will you have it ready? ;-)
Long answer...
I understand what you're saying. What I'm saying is that there isn't a one size fits all answer to this "problem" (certainly not since the addition of TwoTapsX). The step by step instructions for installing ROMs, kernels, other hacks, etc. exist in the threads that contain the product (and most of those are stickied) because they aren't always identical. One "Superpost" meant to encompass all of those instructions would grow to be much too large and include far too many logical branches to be effective when you take into account the individual caveats for each. However, the methods for installing many of the products is similar in most cases even if the tools are not identical. Understanding which tool to use and how it works is the key to a successful experience.
For example are the recent cases of problems with TwoTapsX (formerly TnTLite 5.0.x). The instructions in the thread clearly stated that the users should start from a clean Viewsonic ROM without CWM (very different from other ROMs). It even stated an nvflash might be necessary if you had any problems with the install (also not usually necessary with other ROMs). Still, the overwhelming majority of users that had problems had failed to follow the instructions correctly and were unprepared to do an nvflash. These were generally not people that were new to the process, either. In cases where they were, a simple search for the error message they were getting or the condition they were experiencing turned up an answer within the first two or threes responses and virtually all of them were addressed in the original instruction thread or another recent thread with a similar title.
Another example, I still see threads daily about someone recently installing VEGAnTab 5.11 and all of a sudden their media disappears from their sdcard. This is a well known and very well documented problem with a long used successful work around. It isn't a case where their particular installation went awry, it's a known issue with the ROM. How many of those issues would need to be addressed in the "Superpost" in order to be effective and yet not be cumbersome?
To complicate things further, we now have indications that the next official release may change recovery to be incompatible with previous methods. It's possible we'll see further forking of these processes based on the developers preference of recovery which would reinforce the need to customize instructions for a particular product.
Room for improvement? Sure. I just think education is better than hand holding. I always encouraged my engineers to learn more and develop their own processes because they might actually be better, cheaper, more efficient, than whatever we currently had. I understood that MY answer might not always be the best one and I preferred to empower my associates.
All that being said... I'm all for anything that improves the community and more importantly helps its members. If you feel that it would be helpful then feel free to put something together or team with a few others to produce a document to address the issues you've identified. I'll be more than happy to link people to it if it fills a need for them just as I have to others in previous threads ;-)
Modding
You know normally I just read and lurk around here, but I can't keep my mouth shut any longer.
**WARNING** Not that I expect anyone to notice because apparently half of you can't read or don't comprehend what you do read, but anything past this point is probably not contributing to the conversation in a constructive way and should be considered as me ranting.
I have had my tab since December and have flashed every single Rom found on this forum at one time or another and the problems I see people have just amaze me. It's amazing because 9 out of 10 times it's because they didn't bother to read/comprehend the darn instructions or they are to lazy to search/read/comprehend on how to fix it or start over.
I am by no means a rocket scientist/programmer/developer/modder myself but I can read something 3-4 times first to make sure I comprehend before I go off deliberately voiding the warranty on a $400 device. And if I break it? Guess What?? There are instructions for that to if people would bother to look. Granted the information can be scattered around but if you can't be bothered to search/read then you should probably not be using a android device.
Last thing and I'll shut up. The entitlement I see coming from alot of people really makes my blood boil. You are an early adopter of bleeding edge technology, there are going to be problems and alot of them! If you didn't do research on the tab before you bought it you have no right to complain. The devs are not paid except by an occasional donation. They do this on their own time with their own equipment for the community. THEY DO NOT OWE YOU A THING, AND YOU SHOULD WORSHIP THEM SINCE WE ALL GET TO BENEFIT FROM THEIR HARD WORK!!!
Be Contented....
After tried two ROMs (TnT and NI) and finally sticked to NI, am well contented and satisfied. I think being contented may less your problem...
K J Rad said:
Short answer: Great idea! When will you have it ready? ;-)
<Plus lots of other stuff you said>
Click to expand...
Click to collapse
As you can see from my post count, I'm historically a lurker. I've literally read every single thread in the GTab section since December. The problem for me, mostly came down to once I bought the device (I research stuff to death before I pull the trigger) and was ready to try a new ROM, it was information overload. There *is* a good thread about ROMs and CWM as I said, so I followed that, after reading it 6 times to ensure there were no gotchas.
I want to try out Pershoot's kernel, but I don't feel like I've read the procedure enough times to feel confident I'll be able to do it without having to fix something I broke. So, I'll read it a few dozen times, research the tools used, and finally get to it.
End of the day, I'll probably ask the person who did the ROM thread if they wouldn't mind added text that I've put together for the Kernels (as a supplement to what he did). I do want to give back to the community.
Also, you'll hopefully be seeing some hardware mods coming soon from me, fully documented. My true love is hardware, so I'll leave the ROMs and Kernels to the software guys, and focus on improvements on the physical side of things.
Thanks for keeping the conversation friendly. Always great to hear other people's opinions on matters.
Hardware mods would be VERY cool. Just remember to put something in the thread about how to talk your wife into letting you replace the smoldering mess on the kitchen table so I'll be covered... ;-)
h3llphyre said:
Also, you'll hopefully be seeing some hardware mods coming soon from me, fully documented. My true love is hardware, so I'll leave the ROMs and Kernels to the software guys, and focus on improvements on the physical side of things.
Thanks for keeping the conversation friendly. Always great to hear other people's opinions on matters.
Click to expand...
Click to collapse
I think I speak for everyone here when I say "Bring them on!"
2 cents to add
I have worked in various areas of IT for over 30 years. Unfortunately android has not been one of them but the basic ideas are always the same. As one reader noted (with a little bit of steam coming from his ears) no one owes you anything here. You aren't paying and you're pretty lucky to have so many talented people making their efforts available to you. I, for one, am very appreciative. I do see the point however about documentation. I have been slowly (and painfully) coming up to speed on the various facets of this g-tab experience. What I find most frustrating is not the lack of directions (there are plenty if you look) or even responses (Clemsyn responded to my request for kernel updating info) but the lack of basic information. I recognize a linux type structure when I snoop around the file system. What is the relation of the ROMS to that? What exactly does clockwork do and where does it live? When you "clear caches" what exactly are you clearing? etc. I'm not expecting answers to these questions here but I think that is the problem a lot of us "caught in the middle guys" have. Sure, we can follow directions and usually everything works just the way it is supposed to but we don't know WHY. If you just blindly follow directions that makes you a "user" not an "admin" and who wants to be a user???? ha-ha What I really want to know is how/where do the more experienced people here (including devs) get their base information to know how to tinker with kernels, ROMS, etc? Where is the G-Tab Development for Dummies book hiding????
enigmas 0456,
You will find that lack of documentation is the hallmark of Android -- not just
here but everywhere. Probably more info here than most places.
Rev
I may be imagining it, but it seems like there's a steady increase of "help, I bricked my gtab" threads as people are starting to receive their woot's gtabs. Please stop and think. Have you ever done something like modding an android device before? Is it worth it?
If it ain't broken, don't try to fix it.
I currently got 2 gtabs. One I have modded the hell out of and the other I'm keeping the stock rom. What you can do is go to settings and set it to classic. The annoying weather TnT thing will go away and your gtab will work just fine. Very fast. Very sexy. Love you long time.
I beg you, please help yourself and consider just staying with the classic stock rom. I've been playing with it and I see nothing wrong with it. Works wonderfully.
One user on here came and said when he first started playing with the gtab in office depot he was expecting the worst screen ever because of all the negative reviews about the screen. But to his surprise, it turned out to be very pleasant. Why? Because people on the internet like to exaggerate.
And in this case, people really did exaggerate the unusability of the stock rom. If you're not doing aerobics and yoga with the gtab, you won't notice it. Please do yourself (and us all) a favor by not simply plunging into modding as soon as your gtab arrives. Play with the stock rom first. Make sure you set it to classic. Give it a couple days before you decide to whether put a custom rom on there or not.
Please think about what I just said. Amen.
+1 good advice!!!!!!
x2. And please read up on things like adb and nvflash BEFORE you you start modding. Imo, anyone modding their device should have these tools handy, in advance.
"adb", for example, is almost a standard requirement in other Android phone forums. But for some reason it's not stressed here - I am guilty of that as well. I think that, if you are taking the risk (and it IS a risk) to mod your device, you should have the tools to save yourself from yourself. There's a nice writeup on nvflash that I posted (and "Rev" wrote) and adb instructions are all over the place, not just here.
Thanks!
i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.
Also, I forgot to add.
I work in a research lab. Even though I'm an engineer, I'm really the acting tech guy. As a side job, occasionally I make house calls to fix people's computer problems.
It is my experience that not-so tech savy people always manage to find problems that us techies would never find. Not only that, not-so tech savy people most of the time can't remember what they did and can't verbalize what they did. This makes it 100x harder on us techies.
You see, there are unspoken rules in the world of tech. For example, dealing with system files is risky. Deleting them is bad. Things like that. Not-so tech savy people don't know these rules and so they just stumble all over the place finding and creating problems that the tech people would never find.
What I just said above means that when you find (or create) a problem and you didn't follow the proper procedures, you're not always going to find someone that knows a solution. Why? Because the rest of us never dared to go down that dark narrow alley that you decided to run into. We don't know what's in there. And if you manage to find a 3 headed troll, how are we to know what to do since we've never been down that alley?
Take it for what it's worth. If I haven't detered you, at least have adb and nvflash ready. And make sure you know what you're doing with those.
fridge011 said:
i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.
Click to expand...
Click to collapse
(1) Not-so tech savy people like to take short cuts for whatever reason. They also sometimes skip important steps in a procedure even though it's right there in front of them. At least one wooter has already bricked his gtab without backing up.
(2) No, they're not all exactly the same out of the box. Nothing is ever all exactly the same out of the box.
(3) Everything seems simple to me, too. But according to my experience, what seems simple to someone with experience isn't always simple to everyone else.
Just last week, I went to a woman's house to help her with computer problems. She made it sound like life and death on the phone. The only reason I tolerate her is because she might be my in law one day. Anyway, it turned out that the problem was she thought the monitor was the computer. We have explained to her over and over that it's only the monitor and that the box sitting below is the computer. Seems silly to us, but there it is.
fridge011 said:
i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.
Click to expand...
Click to collapse
My transition from stock 3588 to tnt lite 5 now twotapsx went smooth as butter however some devices moving from other mods back down to 3588 and then to twotapsx had problems!!! The biggest issue was a confusion on using clockwork mod recovery as those who tried it with the ttx mostly found themselves semi-bricked which led to a literal borkathon . Most issues were from user error but on some cases there were oddball problems that just popped up!! So my point is that in Modding your tablets to anything other than stock you are risking a BORK but if you follow directions and have the proper backouts tools ready such as nvflash and adb you should be ok.
goodintentions said:
(1) Not-so tech savy people like to take short cuts for whatever reason. They also sometimes skip important steps in a procedure even though it's right there in front of them. At least one wooter has already bricked his gtab without backing up.
Click to expand...
Click to collapse
+100 on this one. I have a friend that I had to help with rooting her evo and Gtab, and had to ask her every step she took to make sure she actually took them. Luckily she learned early on to use Nandroid and keep a backup of the stock rom and any working roms before you switch to another one.
fridge,
I've skipped posts after yours to answer you, so I apologize if I duplicate something.
YES, if you do everything right bad things CAN happen:
1. Android is not a well-documented operating system and something you just "think" your doing it right.
2. The G-Tablet can be cranky. Unexpected things happen. The other day my pristine, perfect tab
was shut down properly. Next time I turned it on I had huge
"android.process.acore" errors and I had to fix it.
3. I don't know of anyone who has revealed themselves on this forum that thoroughly
understands the structure of the OS software on the G-Tablet. Read all the posts
on boot.img and partition structure. It really would help us all if we knew more.
4. There are a lot of good people who "help" others on this forum Most give good
advice most of the time -- but those of us that are human make mistakes once in a while.
And honestly, some helpers may not give good advice -- don't do it if you don't
understand and feel good about it.
5. Some people don't abide by good IT practices. I saw someone trying to get help
the other day that had barely gotten started with the G-Tab and already had CWM and had
tried three or four ROMS and other related software -- and had a soft-brick!
People need to move slow and check things out more carefully.
6. And some of the software posted here for your use may not even work right. I know a
couple of programs I have seen associated with lots of crashes. If a program
is listed in the threads with lots of crashes around it -- you better be careful!
I could go on for a long while further. If you REALLY read the forum and what's going
on instead of just looking for things to install, you will see these patterns.
Rev
Agreed completely with the intention of this post but I don't think the increase of people messing theirs up is due to woot just yet. I ordered one from the woot sale and i am fairly sure that it hasn't even shipped yet, the email said within 5 days. They aren't the fastest at shipping stuff.
It's probably more so just due to the dropping price in general.
People who have not done any moding of other android devices before should absoltely so slow and wait on loading whole roms until they get familiar with it and read up a lot and do their homework otherwise they will risk breaking their device.
Sent from my ACS frozen Epic
May or may not be Wooters but several *have* posted that they have recieved them.
Adding one small thing I've learned over the years: sometimes an install/upgrade/mod just doesn't take the first time. Or the second. Or the third. Patience is a key to sucess in these things. If it doesn't work the first time, come back the next day and try it again.
Repeating again: READ the forums and all the old threads. Go back and read them again.
And if you don't do backups, I have no pity for you.
iamchocho said:
Agreed completely with the intention of this post but I don't think the increase of people messing theirs up is due to woot just yet. I ordered one from the woot sale and i am fairly sure that it hasn't even shipped yet, the email said within 5 days. They aren't the fastest at shipping stuff.
Click to expand...
Click to collapse
Actually, mine from woot is due to arrive tomorrow. May be that's because I ordered mine 10 minutes after midnight.
But regardless, people need to think twice before deciding to take the plunge.
Edit.
And I'm just cranky because I just found out this morning I've been a victim of credit card fraud. Someone's been doing a lot of shopping online with my credit card. Mostly games, so I'm guessing it's some spoiled brat somewhere who got lucky at hitting random numbers and got mine.
roebeet said:
x2. And please read up on things like adb and nvflash BEFORE you you start modding. Imo, anyone modding their device should have these tools handy, in advance.
"adb", for example, is almost a standard requirement in other Android phone forums. But for some reason it's not stressed here - I am guilty of that as well. I think that, if you are taking the risk (and it IS a risk) to mod your device, you should have the tools to save yourself from yourself. There's a nice writeup on nvflash that I posted (and "The Rev" wrote) and adb instructions are all over the place, not just here.
Thanks!
Click to expand...
Click to collapse
I've been lurking on the gTab forums here for the last several days, and have been trying to absorb all of the info I can. I tend to research everything in depth before I plunge into anything. While much information is here, it is fragmented, and what is easy to follow for a developer is not as easy to follow for others. roebeet, you do the best of any I've seen, and I appreciate it. I've done a lot of searches which have helped some. I'm not new to Android (or XDA) as I have a stock Droid Incredible, but I am new to mods to Androids. I have also used Linux in the past, and modded kernels for newer drivers using cookbook approaches, so little scares me if I have enough information. I've sort of figured out how to install and use nvflash, ADB, and CWM using the various guides, but I'm missing some fundamental knowledge on WHEN and WHY I should really be prepared to use them. I've also tried to do some reading on Nandroid, but have found little pertinent to the gTab. So here goes:
1. What is the primary use of each of the following tools, nvflash, ADB, and CWM? When should I expect to have to use each of them? Are there gTab specific guides to their uses and the options for each outside of ROM installation guides, etc? Specific examples of when I should use each, and even more important, when NOT to use them, would be helpful. I've read all of the ROM, nvflash and ADB installation guides, and the various FAQs, and I understand HOW to install each of, just want to understand the best practices for each.
2. After reading a lot, it appears that having a complete backup of my particular ROM would be a good idea since partitions seem to differ even on stock gTabs. I've read posts here that refer to Titanium, and the use of ADB and CWM to do backups, and others that refer obliquely to Nandroid. What is the use of each of the above to do backups? It appears that Nandroid is a piece of CWM, but I may be mistaken. And if I install TnTlite using roebeet's guide, I'm not supposed to use CWM anyway. So how do I do a backup?
3. I plan to use my gTab as I get it, allowing it to do OTA updates only, for a few days, playing with the TNT and normal Android interfaces. I understand that a major OTA may be imminent anyway, possibly based on the leaked 3991 ROM, so my current plan is to wait for it, at least for a week or two. I plan to explore the guts of the file system carefully to fully understand the various instructions I've found here. Is there a way to safely install nvflash and ADB and explore more, or do I need to have an already rooted ROM installed on the GTab.
4. Some people recommend updated to newer or tweaked kernels. I've found the kernels, but haven't found any good step by steps on how to install them. Any links you can point to?
As an aside, I think roebeet's idea of a good wiki for this forum is a good one. The main XDA wiki is about useless. I would expect to see beginners guides to nvflash, ADB, CWM, etc.
Thanks for your help.
Jon
Suggestion. If you are going to install a ROM, pull the detailed instructions from one of the reputable Devs here, paste it into a word processor and add a check box before each step ( can use bullet tool) Then make sure you go thru one step at a time and check the box just in case you get interrupted. If you are unclear on a step ( ie clear cache) research it before you do anything.
thanks for your replies guys, it is definitely good to know that even if i do it perfectly it might still not work the 1st time. ill just nvflash it and try again. this is a really informative forum.
I think a centralized FAQ and / or Wiki is needed, for all the concerns you stated.
"How do I setup adb? What is it used for?"
"What is nvflash? How do I backup all my partitions?"
"What's the difference between clockworkmod and standard recovery? What are the pros and cons of both?"
"What are the difference ROMs available and what are their differences?"
"What is a customized kernel and why would I use it?"
"I have an error <fill in the blank> -- what do I do?"
etc etc. With potentially hundreds of Woot users about to jump into XDA, I think this would be a fantastic thing to have. Heck, it would a good thing to have for ALL of us, myself included.
It's NOT an easy task, however. I would argue that it's a very arduous task and something that would need to be ongoing. But I think it would ease some of the repeat questions here, and give new users a good guide to understand some of the basics.
lamchocho,
Wrong! The wooters are here!
And as the days go by there's going to be more.
Gonna be interesting.
Rev
jonalowe said:
I've been lurking on the gTab forums here for the last several days, and have been trying to absorb all of the info I can. I tend to research everything in depth before I plunge into anything. While much information is here, it is fragmented, and what is easy to follow for a developer is not as easy to follow for others. roebeet, you do the best of any I've seen, and I appreciate it. I've done a lot of searches which have helped some. I'm not new to Android (or XDA) as I have a stock Droid Incredible, but I am new to mods to Androids. I have also used Linux in the past, and modded kernels for newer drivers using cookbook approaches, so little scares me if I have enough information. I've sort of figured out how to install and use nvflash, ADB, and CWM using the various guides, but I'm missing some fundamental knowledge on WHEN and WHY I should really be prepared to use them. I've also tried to do some reading on Nandroid, but have found little pertinent to the gTab. So here goes:
1. What is the primary use of each of the following tools, nvflash, ADB, and CWM? When should I expect to have to use each of them? Are there gTab specific guides to their uses and the options for each outside of ROM installation guides, etc? Specific examples of when I should use each, and even more important, when NOT to use them, would be helpful. I've read all of the ROM, nvflash and ADB installation guides, and the various FAQs, and I understand HOW to install each of, just want to understand the best practices for each.
2. After reading a lot, it appears that having a complete backup of my particular ROM would be a good idea since partitions seem to differ even on stock gTabs. I've read posts here that refer to Titanium, and the use of ADB and CWM to do backups, and others that refer obliquely to Nandroid. What is the use of each of the above to do backups? It appears that Nandroid is a piece of CWM, but I may be mistaken. And if I install TnTlite using roebeet's guide, I'm not supposed to use CWM anyway. So how do I do a backup?
3. I plan to use my gTab as I get it, allowing it to do OTA updates only, for a few days, playing with the TNT and normal Android interfaces. I understand that a major OTA may be imminent anyway, possibly based on the leaked 3991 ROM, so my current plan is to wait for it, at least for a week or two. I plan to explore the guts of the file system carefully to fully understand the various instructions I've found here. Is there a way to safely install nvflash and ADB and explore more, or do I need to have an already rooted ROM installed on the GTab.
4. Some people recommend updated to newer or tweaked kernels. I've found the kernels, but haven't found any good step by steps on how to install them. Any links you can point to?
As an aside, I think roebeet's idea of a good wiki for this forum is a good one. The main XDA wiki is about useless. I would expect to see beginners guides to nvflash, ADB, CWM, etc.
Thanks for your help.
Jon
Click to expand...
Click to collapse
I'm quoting Jon's post in its entirety because he both perfectly articulates a number of my questions as well as captures my sense that after days worth of information mining on this site, I'm semi-well-informed enough to do the kind of damage that will surely add to the confusion you all seem to realize is imminent here.
I may be able to help with question 4. Buried in Clemsyn's kernel thread (52 pp!) ...
http://forum.xda-developers.com/showthread.php?t=895825
...is this:
INSTALLATION INSTRUCTIONS:
1. ROOT, Flash CWM Recovery (if you haven't done this yet)
2. Create a FULL nandroid backup (optional since its just a kernel)
3. Download a kernel of choice
4. Put the kernel on root of sd
5. Boot into Clockwork MOD recovery (either from ROM Manager or manually- hold volume up and down at same time and press power button, then select "apply sdcard: update.zip"
6. In recovery select "Install zip from sd card"
7. Select "Choose zip from sd card"
8. Navigate to the kernel file and select it
9. Let it install, it will take a few minutes...screen will go weird (black with big blue letters) then take you back to recovery.
10. Reboot phone
Click to expand...
Click to collapse
goodintentions said:
Just last week, I went to a woman's house to help her with computer problems. She made it sound like life and death on the phone. The only reason I tolerate her is because she might be my in law one day. Anyway, it turned out that the problem was she thought the monitor was the computer. We have explained to her over and over that it's only the monitor and that the box sitting below is the computer. Seems silly to us, but there it is.
Click to expand...
Click to collapse
Just a fair warning, they (the in-laws) never change.
A little note as to why we'll probably start seeing a lot of uninformed people here is because Viewsonic actually has a link to XDA on the "Favorite gTablet Apps and Resources" page of their site, which is accessible from the main G Tablet home page
It's in the developer resources section, but as everyone already knows that doesn't stop some people.