Folks...
I've been using ClockworkMod for a while on my HTC Incredible and today I received my Woot table.
I installed ClockworkMod on the tablet and did a backup of my "stock" image (I applied the 3588 update).
From reading these ROM threads, it looks like there's some differences in how I am used to interacting with Clockwork and some of these warnings sound pretty ****ing dire...
If I install a ROM, isn't going back to my previous backup a matter of formatting and restoring? It sounds like some of these ROMs interfere with Clockwork in such a way that could result in a bricked device. I've been wiping and restoring on my Incredible for almost a year now and I've never heard of a ROM dicking with Clockwork before...
What's the difference or am I making a mountain of a molehill here?
There is a very specific version of CW that bekkit put together for the G=Tab. The problem isn't the rom messing with CW, it usually is Rom Manager that will mess with it. Rom Manager usually will want updated, especially with CM installs.
I have had to nvflash the tablet in the past after upgrading CW via rom manager.
The other issue that is common, and I have had happen to my beloved Dinc, is having to repartition the storage. The groundwork for the Dinc was much, much more stable than the default tapNtap that is released with the tablet.
Something some people may also miss is the kernel for GB is much different than the kernel with froyo.
Rest assure, bricking this thing seems to be an accomplishment and almost impossible. Trust me, I have given my best effort to do so. With nvflash or adb almost any tablet can be recovered.
One last thing to look out for, how internal storage is handled. Some roms use internal as emmc (like the Dinc), while others mount as sdcard. CW doesn't handle this switch gracefully. You can mount usb storage in advanced menu and move the recovery files over if needed.
While dharr18 is mostly correct there are a few ROMs floating around out there that will have trouble with clockworkmod. TwoTapsX and TnT Lite 5.0 (both currently held from distribution by the developer) are based on a UAT build (3991) that require using the stock recovery and bootloader from build 3588+ to install correctly. There is some speculation that this may be the standard going forward.
Thanks KJ, I forgot about those two as I have not loaded them to date.
dharr18 said:
The problem isn't the rom messing with CW, it usually is Rom Manager that will mess with it. Rom Manager usually will want updated, especially with CM installs.
.
Click to expand...
Click to collapse
Yeah, I fell into that trap... really FUBAR'ed my tab until i had to nvflash a full recovery.
dharr18 said:
Thanks KJ, I forgot about those two as I have not loaded them to date.
Click to expand...
Click to collapse
You're welcome. I run TTX regularly (well... in between my attempts to find creative new ways to brick this thing...).
Deacon,
The truth is there ARE some dire consequences. Bricking a G-Tablet is extremely hard,
but you can lose data. If something breaks on your tab and your have loaded a ROM
you do not have a warranty. There are risks involved.
And in my opinion a lot of people try to do too much too fast and too often wind up
in dire straights.
There are stickies on most of the recovery/problematic stuff. Good to read them first.
Rev
the problem isn't with the ROM
I follow roebeet and the tnt lite ROM - VS is updating their boot loader from 1.1 to 1.2 in some of their OTA updates. Mostly the 3588 and the 3991. If you are playing with those or it came installed then it can be a bit of a hassle depending on what ROM you are playing with. I updated my gtab to 3991 and was able to nvflash it back to 3588 and install vegan5.1 and tnt lite up to 4.2 without any issues. Just be sure to read up and be able to complete an nvflash if it gets ugly on you. I really recommend learning a little linux - nvflash is a breeze in there.
Related
...a pain in the ass for the Fascinate. The gf has one of these phones, and after seeing what I've done with my G2, she wants me to root and flash a nice rom.
Problem 1 (not so small): we both use macs at home.
Problem 2 (huge): after reading through the development forum - it doesn't look that easy to root, nor flash a decent rom on the Fascinate!
not only do some roms require you to have a specific kernel flashed to use them. Some roms require that you don't use the latest CWM. Also, none of roms seem to be using Gingerbread AOSP completely. They seem to be pieced together with Froyo.
Believe you me, I am not a dev in the slightest. Therefore, I am looking for a safe way to root and flash a decent rom to her phone. If there isn't, then I'll just let her run stock.
Is this easier than I'm seeing it?
enserio said:
...a pain in the ass for the Fascinate. The gf has one of these phones, and after seeing what I've done with my G2, she wants me to root and flash a nice rom.
Problem 1 (not so small): we both use macs at home.
Problem 2 (huge): after reading through the development forum - it doesn't look that easy to root, nor flash a decent rom on the Fascinate!
not only do some roms require you to have a specific kernel flashed to use them. Some roms require that you don't use the latest CWM. Also, none of roms seem to be using Gingerbread AOSP completely. They seem to be pieced together with Froyo.
Believe you me, I am not a dev in the slightest. Therefore, I am looking for a safe way to root and flash a decent rom to her phone. If there isn't, then I'll just let her run stock.
Is this easier than I'm seeing it?
Click to expand...
Click to collapse
Honestly, it is not that difficult. Just takes some getting used to. Obviously you have done a bit of reading, I know it seems daunting, but I promise, once you have it down it is nothing. The kernels...Most ROMS are kernel switchable, within reason. MOST of our ROMS require the RED CWM, which honestly is not a big deal, the orange is just too glitchy. And as far as the ROM's being pieced together with Froyo...Well, I am no dev either, but yes, I believe most of the ROMS are a Frankenstein of sorts, but we don't even have a Froyo source to work with yet. So the dev's, in my opinion, have done an AMAZING job. In terms of flashing on a Mac, I am not sure if Odin works on a Mac, Heimdall does though I believe. Rooting is extremely simple, it is only the flashing the right CWM, modem, etc. that may confuse you. Honestly, if you just keep reading the right things, you'll see it is pretty simple. I recommend Adrynalyne's Super Clean 2.9, and Big Loof's Steel Blue theme, with the EB16 kernel (Also Adrynalyne's).
http://forum.xda-developers.com/showthread.php?t=948722
This thread has a good walkthrough, I'd follow it through Post #5... using Superclean. It's an incredibly performing full Froyo rom. Remember that Froyo is not officially out on this phone, she's running Eclair right now. Gingerbread is a ways off (though punk kaos is making great progress).
Before EB01, rooting for me was just clicking a single button.
I never had to root again since flashing EB01. For flashing itself, its just download, reboot to recovery, and flash. Not sure how its a pain in the as as it doesnt even take a minute or so.
I did end up installing 3.XX CWM from ROM manager, but I only reboot into orange CWM if i reboot using ROM manager. If I dont, I end up rebooting to red CWM.
Thanks for the responses. Put a few things in perspective. I totally forgot that she is still running Eclair and Froyo isn't officially out for these phones. My mistake, and now that makes complete sense to me why most of the roms are froyo based or patched. Another thing that made me hesitant is that Odin doesn't run on mac, and I would have anything to save the phone (unless I use one of the pcs at work) if something goes awry. I will read up on Heimdall and see if I can use that.
My apologies if I sounded bothered or uptight about the situation, thanks for the well-mannered responses to my mini-rant. Of to read up a bit more, starting with the link postd and Heimdall.
Found a quick guide for rooting the Fascinate with a Mac. Now my issue is...switching to EB01 without Odin because SuperClean needs it, correct?
HI all,
I see that Viewsonic is pushing out 4349 update and i have been reading up on it. I currently use TNTlite 4.40. Is it safe to apply this or wait until it is fully tested and then apply it when it is compatible with the latest roms.
Roebeet i know that you have been testing this.. What do you think..
Let me know.
thanks
Don't touch 4349 if you are on a mod, or if you use clockworkmod
...unless you want a soft-brick your device.
I'm still testing, but right now I can tell you that if you are using clockworkmod and flash to 4349, you WILL soft-brick your device. It seems to have the same traits as the infamous 3991. Again, still testing.
I'm not sure about TNT Lite 4.4.0 yet - that's on my list of tests but I want to test VEGAn first, as that's probably the most popular ROM here.
roebeet said:
...unless you want a soft-brick your device.
I'm still testing, but right now I can tell you that if you are using clockworkmod and flash to 4349, you WILL soft-brick your device. It seems to have the same traits as the infamous 3991. Again, still testing.
I'm not sure about TNT Lite 4.4.0 yet - that's on my list of tests but I want to test VEGAn first, as that's probably the most popular ROM here.
Click to expand...
Click to collapse
Sounds good Roebeet.. Let us know.. I am going to hold of on the update until we hear from you..
i upgraded from stock 3588 and everything works flawlessly.
Confirmed as bad as 3991. I will write up a new post with details, warnings and suggestions.
Roebeet,
Plainly said -- VS always has been oriented to stock and has said the alternate ROMs
will void your warranty.
It seems apparent to me that this update is designed to work on top of the other "stock"
software they hope you are running (and probably aren't).
Stock rules in their world.
Rev
P. S. -- I just remembered -- somebody asked earlier about the "Enhancements"
on this ROM. I don't know, but I do remember trying it on 3991 and it semi-bricked
my tablet.
It has same brick issues with enhancement. How hard is it gonna be to get the Roms working with it? Specifically vegan 5.1.1?
I did it over stock, and I now have a clock/calendar, with nothing else working.
cd112 said:
Sounds good Roebeet.. Let us know.. I am going to hold of on the update until we hear from you..
Click to expand...
Click to collapse
Can this be reverse engineered? Meaning can we flash back to our previous rom before the update by nvflashing?
This is very similar to UAT 3991, so far
The good thing about that is that we a month of experience that we can apply, here. I've been tested my own mods that I added a failsafe into and, so far, that failsafe is working. But I have a lot more testing to do -- I haven't even LOOKED at this update yet.
That failsafe, btw, was adding the 3588 bootloader as part of the flash process. That way, if someone was on 3991 (or now 4349) and flashed to TNT Lite 4.4.0 for example, the bootloader gets downleveled so that way it shouldn't soft-brick. Same should apply if you flash from stock 4349 to 3588, or vice versa.
Keep in mind that clockworkmod is about the worst thing you can use, between 1.1 and 1.2 based ROMs. It doesn't flash the bootloader, which is required.
edirector said:
Can this be reverse engineered? Meaning can we flash back to our previous rom before the update by nvflashing?
Click to expand...
Click to collapse
Never-mind i nvflashed and am restoring gtab back to the way she was. I couldn't deal with not having market and my favorite apps. Also I lost sound. VS did well for those whose gtab wasn't running smoothly but as for mine she was sweet before the update running like a fine tuned engine. Much faster than with the update. She hit the desktop on a dime.
For the rest enjoy your update! I just got my dream girl back.
How about if you are on a total stock gtab can you upgrade to 4349 -THEN Root the device? or is it not supported yet?
I have been reading around for a while now, and noticed a lot of ppl soft-brick there device and are asking devs for help. I have noticed a lot of issues revolve around people trying to hop form on ROM to another.
A very easy way to recover from any sort of brick(or issue) is to use nvFlash. Its is very easy to setup and use and I highly recommend that everyone should setup nvFlash. You can find the guide on how to set it up from http://forum.xda-developers.com/showthread.php?t=861950
I think after the update last night a lot of people will brick there devices trying to mod it, and nvFlash will help you recover. I think we can really help out the dev if we all learn how to use nvFlash, because then they wont have to ans to alot of the support issues that keep coming up, and it will free up some of there time which they can use to create newer roms that will work with the new update.
If for some reason you follow that guide and are not scussefull in setting up nvFlash, then feel free to leave me a pm and i'll help you set it up.
Good post!!
You absolutely right because most of them (especially new users) won't take time to read stuff about the new update, which will in most cases soft brick the tab when coming from a non stock rom.
So yea they all should have Nvflash setup, just in case
Great advice.
I was messing around with Vegan Ginger the other night and wound up borking my gTab. Followed the instructions in that thread and had no problem using NVFlash to get everything back to normal.
Noob here Hi!
I Actually used the NVFlash yesterday to clear up some issues i was having. it works well and was easy to use.
Some how i screwed up my copy of Clockworkmod. When ever i attempted to flash any Custom ROM it would just sit at the view sonic boot screen...Although TNTLite always flashed with no issue.
I used NVFlash to get back to defaults then updated to 3588 then Reflashed CWM. Now I am able to load Vegan
Thanks for the post i think it will be helpfull for us N00Bz
WildBidoof said:
Noob here Hi!
I Actually used the NVFlash yesterday to clear up some issues i was having. it works well and was easy to use.
Some how i screwed up my copy of Clockworkmod. When ever i attempted to flash any Custom ROM it would just sit at the view sonic boot screen...Although TNTLite always flashed with no issue.
I used NVFlash to get back to defaults then updated to 3588 then Reflashed CWM. Now I am able to load Vegan
Thanks for the post i think it will be helpfull for us N00Bz
Click to expand...
Click to collapse
Actually, you probably didn't screw anything up. Some Gtabs have a partitioning issue (I had it) which is only corrected during nvflash. I was unable to install any ginger roms until I nvflashed. Worked like a dream after nvflash.
This has been the most frustrating experience I have ever had with an Android device...
I was one of the lucky few who got one for $280 on Amazon and apparently it had the newest build on it that has the boot loader locked down.
I went through all the stickied guides, warnings about the locked bootloader and NVFlash. Needless to say, I have done my homework.
I tried in vain to install any ROM, but the only one that would install is TnT, which to the dev's credit it was a huge step above the stock ROM, but *shudder* that interface...
Long story, short; I managed to install CWM, fail at any install of a ROM (3 bird screen) and and ended up flashing with NVFlash to 1.0-2638, tried to flash ROM's again and again only to reflash 2638. It has been a LOOOOONG day with this thing.
I am at my wit's end.
Here is what I have 1.0-2638, no CWM and a bottle of Patron Silver...
How do I get a ROM on here...
Hey
Compusearch said:
This has been the most frustrating experience I have ever had with an Android device...
I was one of the lucky few who got one for $280 on Amazon and apparently it had the newest build on it that has the boot loader locked down.
I went through all the stickied guides, warnings about the locked bootloader and NVFlash. Needless to say, I have done my homework.
I tried in vain to install any ROM, but the only one that would install is TnT, which to the dev's credit it was a huge step above the stock ROM, but *shudder* that interface...
Long story, short; I managed to install CWM, fail at any install of a ROM (3 bird screen) and and ended up flashing with NVFlash to 1.0-2638, tried to flash ROM's again and again only to reflash 2638. It has been a LOOOOONG day with this thing.
I am at my wit's end.
Here is what I have 1.0-2638, no CWM and a bottle of Patron Silver...
How do I get a ROM on here...
Click to expand...
Click to collapse
Thats sucks, and i feel for you. I am also someone that just purchased the gtablet from amazon, and have been reading the forums throughly and it clearly says to downgrade before attempting to load cwm and flashing a given rom. So i guess my question is, did you downgrade before flashing?
@Compusearch... welcome to the G-Tablet world...
before you go ahead... look though the forum and FAQ posts...
do you have a particular ROM in mind??
keep these in mind...
if you install the latest 1.2-4329 ROM, you cannot install a custom kernel... so most custom ROMs like CM will not work... there are three 1.2 based custom ROM available (can't post the links so google Century Eyes or Mountain Laurel)
if you install a Gingerbread ROM like CM7, hardware video decoding will not work...
a start up from where you are... get the 1.1-3588 ROM from http://forum.xda-developers.com/showthread.php?t=842000 and flash it with the stock recovery... it's the best base ROM... then you can flash CWM 0.8 bekit if you want to install a 1.1-based ROM (most ROMs available here) or move to 1.2-4329 and install a 1.2 based custom ROM...
you can easily nvFlash back to the 1.1 based ROM even after you move to a 1.2 based ROM...
craigacgomez said:
@Compusearch... welcome to the G-Tablet world...
before you go ahead... look though the forum and FAQ posts...
do you have a particular ROM in mind??
keep these in mind...
if you install the latest 1.2-4329 ROM, you cannot install a custom kernel... so most custom ROMs like CM will not work... there are three 1.2 based custom ROM available (can't post the links so google Century Eyes or Mountain Laurel)
if you install a Gingerbread ROM like CM7, hardware video decoding will not work...
a start up from where you are... get the 1.1-3588 ROM from http://forum.xda-developers.com/showthread.php?t=842000 and flash it with the stock recovery... it's the best base ROM... then you can flash CWM 0.8 bekit if you want to install a 1.1-based ROM (most ROMs available here) or move to 1.2-4329 and install a 1.2 based custom ROM...
you can easily nvFlash back to the 1.1 based ROM even after you move to a 1.2 based ROM...
Click to expand...
Click to collapse
Trust me, I went through all the FAQ's and Guides here. I even found a bunch of youtube video's showing how to do the installs of CWM and ROM's. I can follow along, but the end result is always the 3-bird boot screen.
I am seasoned veteran of installing ROM's: Droid, DroidX, Nook (too easy), Galaxy Tab, Captivate, HD2 (winmo7, android), MyTouch3G, and HTC Inspire. I know the procedures and concepts very well.
I think the variable that is screwing me over, is what was initially installed on my gTablet when I got it this week.
I assumed that I had 4349 as there was no available update when I checked for it over wifi. With that in mind, I did downgrade it to 3588 per:
http://forum.xda-developers.com/showthread.php?t=1036956
Even with that, I could not install any ROM's other than TnT Lite.
I am wondering of the latest batches of gTablets are locked down beyond what the newest update 4349+ already does.
Technically as it stands, I have 1.0-2638 installed and that should have the unlocked bootloader and I should be able to follow this guide:
http://forum.xda-developers.com/showthread.php?t=865245
I would assume that logically, if I have an earlier version of the original TnT, that I can install CWM and then any gTablet ROM.
Am I wrong to assume this?
[edit] I want to be able to use the Vegan Beta 5.1.1 ROM
Stupid question but have you actually tried to install a rom after nflashing. The problem you were having before was the partition structure was wrong and nvflash should have fixed that. You can also extract "recovery.img" from bekit 0.8 zip file......
Copy recovery.img to your nvflash directory
Rename part9.img to part9.bak
Rename recovery.img to part9.img
Run nvflash again
This will flash cwm for you. Then try clearing data and flashing anather rom
Compusearch said:
Trust me, I went through all the FAQ's and Guides here. I even found a bunch of youtube video's showing how to do the installs of CWM and ROM's. I can follow along, but the end result is always the 3-bird boot screen.
I am seasoned veteran of installing ROM's: Droid, DroidX, Nook (too easy), Galaxy Tab, Captivate, HD2 (winmo7, android), MyTouch3G, and HTC Inspire. I know the procedures and concepts very well.
I think the variable that is screwing me over, is what was initially installed on my gTablet when I got it this week.
I assumed that I had 4349 as there was no available update when I checked for it over wifi. With that in mind, I did downgrade it to 3588 per:
http://forum.xda-developers.com/showthread.php?t=1036956
Even with that, I could not install any ROM's other than TnT Lite.
I am wondering of the latest batches of gTablets are locked down beyond what the newest update 4349+ already does.
Technically as it stands, I have 1.0-2638 installed and that should have the unlocked bootloader and I should be able to follow this guide:
http://forum.xda-developers.com/showthread.php?t=865245
I would assume that logically, if I have an earlier version of the original TnT, that I can install CWM and then any gTablet ROM.
Am I wrong to assume this?
[edit] I want to be able to use the Vegan Beta 5.1.1 ROM
Click to expand...
Click to collapse
nvFlashing back to the 1.0 release will definitely downgrade your bootloader... and then I recommend upgrading to the 1.1 branch (3588)... install CWM using the stock recovery or using nvFlash (as @thebadfrog said)...
Format all partitions using CWM... and even try re-partitioning the internal SD card using CWM to 2048MB ext, 0MB swap... and then install a custom ROM
craigacgomez said:
nvFlashing back to the 1.0 release will definitely downgrade your bootloader... and then I recommend upgrading to the 1.1 branch (3588)... install CWM using the stock recovery or using nvFlash (as @thebadfrog said)...
Format all partitions using CWM... and even try re-partitioning the internal SD card using CWM to 2048MB ext, 0MB swap... and then install a custom ROM
Click to expand...
Click to collapse
Trying that now:
1. upgrade to 3588 -Done!
2. install CWM -Done!
3. re-partition SD 2048/0M -Done!
Wipe Dalvik Cache -Done, but with error "Can't Mount /dev/block/mmcblk0p2"
Wipe data/factory reset -Done!
Wipe cache partition -Done!
Format SYSTEM -Done!
Format DATA -Done!
Format CACHE -Done!
Format SDCARD -Done!
4. Custom ROM - VEGAn-TAB GingerEdition STABLE RC1 - INSTALLED!!!
Thanks, Craig and Frog for the tips. This really should be added to the current FAQ.
Sadly, now that I can actually use the tablet, I am HATING the view angles on it.
For a company that prodomiately makes nice monitors and LCD's this is some BS right here.
I know that ViewSonic slapped their name on it, but seriously, who over at VS said that the screen was great and ready for production?
Yeah, the viewing angles aren't great... but it's perfect for a traveller like me... I can sit on the plane and use my tablet without anyone seeing what I'm doing!!
And ignore the dalvik wipe error!!
I wish more people would look at repartitioning as a "step" during the flashing process as apposed to a maybe. All the roms and recovery images are built off of one specific partition set and it is in my book a necessary step to make sure we are all on the same page.
Glad you got it sorted
Mantara said:
I wish more people would look at repartitioning as a "step" during the flashing process as apposed to a maybe. All the roms and recovery images are built off of one specific partition set and it is in my book a necessary step to make sure we are all on the same page.
Glad you got it sorted
Click to expand...
Click to collapse
We have debated that for several months since discovering the different partitioning. The only real way to "brick" for real is through a bad nvflash therefore it makes since to skip that step until necessary.
I think all roms should be nvflashed anyway so you have to understand and be able to use the recovery tools to even modify your tab. But thats my own opinion
I'm trying to do my very first mod to my gtab. I've posted some questions already but have more before I proceed. I'm running bootloader 1.2-4349. Do need to set up nvflash before I attempt flashing to a different ROM? Is there a CWM that is specific for my bootloader? I've searched for these answers on the forums but was unable to find them. I found many posts about these subject but no one answred them directly. Any help is much appreciated.
NVFlash is never needed to flash a rom. It's a tool typically used to recover from a "softbrick." It CAN be used to flash a rom, but there are much safer alternatives. In fact, NVFlash is considered to BE the alternative to the regular methods.
starting with 4349, 1.2 bootlaoder, you can use the stock recovery to flash just about any of the 1.2 roms.
Which Rom are you interested in? The only roms that do not have a 1.2 equal are the gingerbread type roms. For instance, if you wanted Vegan 5.1.1, then Brilliant Corners is the 1.2 alternative. That's what I'm running. It's got to be one of, if not THEE, most complete rom available right now.
most 1.2 rom information is located at Slatedroid, not here.
I suggest that you check out the new website created by a user here (GoodIntentions). It's a "G-Tablet for Dummies" website. It contains a ton of useful information for beginners like yourself.
There IS a CWM that is specific to the 1.2 bootloader, but becuase the recovery on stock 1.2 has more options than the stock recovery used on 1.1 bootloader, it's not absolutely necessary. It's a good tool to have, but not necessary.
Your basic flashign technique for a 1.2 rom is as follows...download the .rar file the coincides with the rom you want. Unzip it to the root of your G-Tablet's memory. Restart the G-Tablet while holding down the volume up key. The tablet will boot into the stock recovery, and use the files you unzipped to flash the new rom. The rar file will contain to objects, a file called update.zip, and a recovery folder with a "command" file in it. What will happen when booting into recovery is that the tablet will first check to see if there is a recovery folder present. Think of this as a PC checking the floppy drive for a boot image before booting from the hard disk. If it sees the recovery folder, it will, by default, run the command file within it. The command file will unpack and install (flash) the rom image from the update.zip file.
With most of his roms, Roebeet has included the 1.2 CWM image in the package. It will not install automatically. There are threads available (on slatedroid) that contain instructions on how to activate the 1.2 CWM. There are various methods, if one doesn't work the first time.
If you are dead set on flashing a 1.1 rom, you'll first need to downgrade back to firmware 3588, which is a 1.1 bootloader firmware. Gojimi has posted instructions on XDA on how that is done.
So, your first step, is research the roms on XDA, Slatedroid, and other Android Tablet forums to find which one would best suit your needs.
As a beginner, I highly suggest that you steer away from the honeycomb roms, as they are still in alpha status and mainly used for testing and troubleshooting. In other words, they won't work perfectly, so to save yourself headaches, wait until your more comfortable with a more polished rom. ALL HC ROMS ARE 1.2 BOOTLOADER ROMS
The gingerbread roms are pretty stable, and from what I hear, pretty fast, but they lack a few things, namely full hardware acceleration. At the same time, if your heart is set on streaming netflix movies, then these might be the best choice for you. THE MOST POPULAR GB ROMS ARE 1.1 BOOTLOADER ROMS
The Froyo roms, while the most prehistoric are the most stable, most complete, and less "buggy" of all the roms. There are many varieties, based on various tablet user interfaces. FROYO ROMS CAN BE EITHER 1.1 OR 1.2 BOOTLOADER ROMS...BUT, the 1.2 branch has more of them, and there are 1.2 equalivents to just about all of them, so sticking with 1.2 for a Froyo rom is the best option because you'll still have the advanced stock recovery if you decide to stick with it.
That being said...why not mess around with the stock 4349 firmware to get a feel for the tablet a bit more? Check some things out. Get Titanium Backup and practice a bit with backup up apps and restoring them (you'll use this a LOT, especially if you rom jump trying to find the best one for you). Find out what you want the tablet to do, based on the stock firmware limitations. Some people are still using stock and not finding it too horrible. Spend a week with it, see what else you want it to do, and ask again when you know what you want out of your G-Tablet. And above all, ENJOY...you just entered a whole new world of personal computing...don't rush into anything and end up regretting your purchase.
P.S...I highly recommend you check out "G-Tablet for Dummies"
DarkHorse281 said:
I'm trying to do my very first mod to my gtab. I've posted some questions already but have more before I proceed. I'm running bootloader 1.2-4349. Do need to set up nvflash before I attempt flashing to a different ROM? Is there a CWM that is specific for my bootloader? I've searched for these answers on the forums but was unable to find them. I found many posts about these subject but no one answred them directly. Any help is much appreciated.
Click to expand...
Click to collapse
Check out my website written for beginners. It will explain everything you need to know.
http://viewsonic-gtablet-for-dummies.webs.com/
Added by edit.
Make sure you read my page on flashing a rom.
http://viewsonic-gtablet-for-dummies.webs.com/rom.htm
Also, check out my page on CWM.
http://viewsonic-gtablet-for-dummies.webs.com/clockworkmod.htm
Much appreciated...awesome!
You guys are both awesome and a credit to the anroid community. I can't tell you how much I appreciate you help. I didn't go into much depth on this thread because I had already written one earlier in the day that shared my background and future intentions for my gtab. I didn't want to sound repetative plus I realize people don't care to read a novel in these forums. So I figured short and sweet I might get a better response, and I was right. Anyway, I hear what you're saying about messing around with the stock firmware TJ. The truth is I've had the tablet now for 3 weeks and I've played with it constantly. I have to say it's not as bad as I thought it would be but it lacks so many things that I've come to love about my Samsung Galaxy Indulge. Many people make fun of or pick on Metropcs and make fun of them as a company, but I have to say here in Florida they're great. I love my phone even though its not the top of the line galaxy phone. And their 4g service is fast in my neck of the woods. Having had such a great experience with that android device, I would really like to make something awesome out of my gtab. I want to use the 4g on my phone to connect to the internet and turn this tablet into a completely mobile multimedia device (Xvid, Avi, Mp3, Netflix, Hulu). I would also like to get the gps software put on it so that I can put my google maps app from my phone on it. Once I am be to get the phone rooted and the wifi or usb tethering up I can use it for navigation as well. I also miss the Android Market. I would love to get that back up and running on my tablet so that I can download some of the apps that I'm familiar with. I really like the dolphin browser on my Indulge and would love to have it on my tablet. I had it for a while on the gtab but had to do a factory reset because of something my kids did and now that I'm back to having nothing on my tablet I thought now would be a good time to try a different ROM. Besides it seemed a little glitchy anyway. Sorry about the novel guys, but now that you know a bit about me and what I want to use my tab for, which ROM do you think will suit my needs? Do you still think that Brilliant Corners is going to cover what I'm wanting out of my gtab? I'm going to check out GoodIntentions' web site and maybe I will get a clue. Thanks for your help guys. I hope to hear back soon.
P.S. One additional question. What's up with the bluetooth pairing? I can't get this thing to pair with any phones. I've tried mine and my gf's and it absolutely will not work.