So I finally got my Viewsonic back to Stock 3588, thanks to all on here and their problem i was finally able to diagnose mine.
Well my question is I've been watching the videos and reading the forums again to to make sure I have the process down right and I'm confused as to whether i need to partition my Viewsonic G to 2048/0 or not?
I was watching the install video on Clockwork Mod and Tnt 4.2 and it didn't seem he needed to partition and just went... but reading the thread description it was step 8 after installing CWM but before installing the rom.
Just a bit confused about this part.
As I understand it, if you're flashing a froyo ROM then it is not necessary. If you're flashing a gingerbread ROM then it is necessary.
It only adds about 30 seconds to the process of prepping the Gtab so I do it no matter what ROM I'm flashing (and I've flashed my Gtab about 6 times in the last 4 days.
If you ever get caught in a boot loop you need to repartition. If you can't install A Gingerbread rom then you need to nvflash to fix your internal partitioning order.
From what i understand if you are ever going to update to gingerbread you should do the partition upfront. This will save you from having to do it going from froyo to gingerbread. So if you do it now to update to GB edition in the future you would just need to clean, flash rom, and possibly update kernel. I'd do it now while you are doing it.
Related
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.
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 gyus,
do you think we will ever see built 4349 again from ViewSonic? I'm waiting to see it again for weeks now... nothing.
Should I wait or do the manual flash, unless you guys tell me it's a very buggy ROM.
Thanks,
Charles
If your gonna stay stock then flash it. If you want to run mods and custom kernels don't
cjean said:
I gyus,
do you think we will ever see built 4349 again from ViewSonic? I'm waiting to see it again for weeks now... nothing.
Should I wait or do the manual flash, unless you guys tell me it's a very buggy ROM.
Thanks,
Charles
Click to expand...
Click to collapse
I'd think twice before manually flashing. I have tried this at least a half dozen times and it didn't work. I followed instructions to a tee and have sufficient experience flashing the G-Tab. For some reason I can install any 1.1 based ROM with no issues but when trying to move to a 1.2 based ROM or the Stock 4349 ROM, my G-Tab shuts down right after the 3-Birds screen or just goes to a blank screen. I always flash back to stock 3588 (with no CWM) before trying to move to a 1.2 ROM as suggested by others. I also have tried wiping cach, data resets, etc.. I must have NVFlashed this thing 20 times in the last week. I have decided to stay with stock 3588 until either VS puts out an OTA 4349update or someone develops a HC Rom.
Well,
I'm sitting on the fence with the above answers?
anyone else?
Charles
you can safely use 'newbl' custom kernel (from myself) if you are running 4349 stock (with the new bootloader).
check droidbasement (ive just updated the compatibility).
tsg2513 said:
I'd think twice before manually flashing. I have tried this at least a half dozen times and it didn't work. I followed instructions to a tee and have sufficient experience flashing the G-Tab. For some reason I can install any 1.1 based ROM with no issues but when trying to move to a 1.2 based ROM or the Stock 4349 ROM, my G-Tab shuts down right after the 3-Birds screen or just goes to a blank screen. I always flash back to stock 3588 (with no CWM) before trying to move to a 1.2 ROM as suggested by others. I also have tried wiping cach, data resets, etc.. I must have NVFlashed this thing 20 times in the last week. I have decided to stay with stock 3588 until either VS puts out an OTA 4349update or someone develops a HC Rom.
Click to expand...
Click to collapse
Did you try upgrading to 4349 using stock recovery from 3588. Just name it update.zip from bone stock 3588. BC 1.2 is now being distributed with pershoots kernel, just update with it from 4349 when you get there. If memory serves me this is how I did it.
SirhanSirhan said:
Did you try upgrading to 4349 using stock recovery from 3588. Just name it update.zip from bone stock 3588. BC 1.2 is now being distributed with pershoots kernel, just update with it from 4349 when you get there. If memory serves me this is how I did it.
Click to expand...
Click to collapse
I sure did. I have tried everything I could find in thr forums. Partitioned internal SD, wiped cache, factory reset...Everything appears to go right until it reboots to a back-lit black screen.
I am certainly not the expert here, but did you copy the recovery folder with the command file to root? In other threads concerning this type of problem, that seemed to be the cause. Actually, I do not think it would update at all without it, should not be the problem. Once you get 3588 up and running do a factory reset. Verify partition size. Still not working, give up until someone smarter than me can offer advice.
tsg2513 said:
I'd think twice before manually flashing. I have tried this at least a half dozen times and it didn't work. I followed instructions to a tee and have sufficient experience flashing the G-Tab. For some reason I can install any 1.1 based ROM with no issues but when trying to move to a 1.2 based ROM or the Stock 4349 ROM, my G-Tab shuts down right after the 3-Birds screen or just goes to a blank screen. I always flash back to stock 3588 (with no CWM) before trying to move to a 1.2 ROM as suggested by others. I also have tried wiping cach, data resets, etc.. I must have NVFlashed this thing 20 times in the last week. I have decided to stay with stock 3588 until either VS puts out an OTA 4349update or someone develops a HC Rom.
Click to expand...
Click to collapse
While on my own tablet I haven't had any serious trouble with this, I've found that flashing back to 3588 isn't always quite enough to prepare for the update to 4349. It seems to be much more reliable to flash or nvflash down to 3398 or below then OTA or manually update to 3588. I also make sure to clear/wipe everything before beginning the process and then again when it's complete.
Hello folks,
I got my GTab a couple of weeks ago and the first thing i did was follow the awesome guide to flash the 'Flashback' Honeycomb rom. I've been running it for 2 weeks and have also updated to the latest alpha release. I love the HC overall but since there are a couple of basic issues in all HC roms, i've decided to move back to Gingerbread.
I've searched around but haven't found the method to go back to GB from HC. I understand that I can't just flash it from CWM as it gives some errors.
I flashed HC throught NVFlash so I'm guessing there's got to be some other way of moving to GB, maybe repartitioning?
I would really appreciate if someone here can point me to a guide to flash GB from HC, including the partitioning requirements.
I will check out the GB roms and their functionality but i might move back to HC once some stable roms are out, so i would like to keep that door open.
Thanks for your help in advance!
are you trying to go from a 1.2 bootloader HC rom to a 1.1 bootloader GB rom?
Visit the Gtablet for dummies website. You can download the 1.1 bootloader NVFlash and use it to get back to stock 3588. I suggest you get the one with CWM built in. Once there, you can flash any GB rom you want.
If you're staying on the 1.2 bootloader, just flash the Rom from CWM, and make sure that you wipe Dalvik cache, and a wipe data/factory reset in CWM and it should work fine.
problems arise when jumping bootloaders, using different versions of CWM...they don't play well with eachother.
I bought a used, already rooted g tab about a month ago. While watching tv (or something) I was reformatting the internal memory in CW recovery and my computer froze completely while reformatting. Anyways, it messed up some of the other partitions I think because it wouldn't boot into 1.1 based flashback, and I couldn't get 1.1 gtabcomb to boot up either.
There are so many dated tutorials around here that I'm not sure which one to follow. How can I repair the partitions and make sure everything is good, while also upgrading my gtab to the 1.2 bootloader so I can install the new flashback. Any help please? Sorry for such a newb questions but I just want up to date info!
parkgrrr said:
I bought a used, already rooted g tab about a month ago. While watching tv (or something) I was reformatting the internal memory in CW recovery and my computer froze completely while reformatting. Anyways, it messed up some of the other partitions I think because it wouldn't boot into 1.1 based flashback, and I couldn't get 1.1 gtabcomb to boot up either.
There are so many dated tutorials around here that I'm not sure which one to follow. How can I repair the partitions and make sure everything is good, while also upgrading my gtab to the 1.2 bootloader so I can install the new flashback. Any help please? Sorry for such a newb questions but I just want up to date info!
Click to expand...
Click to collapse
You must first research on how to do this before hand. I tryed the same thing that you did and almost HARD BRICKING my device. Know your bootload.
http://forum.xda-developers.com/showthread.php?t=1035983
To my understanding is that Flashback is only offered in the 1.2 bootload so NVFlash is your friend in this case.
yep I'm on the 1.1 bootloader. When flashback 8.1 was released, it was actually released with a 1.1 version, but was pulled shortly because of some problems. It worked fine for me so I just lived with it. Alright I'll see if I can get to stock 1.2 and then flash to the new flashback rom.
EDIT: Ok so if I follow the instructions here, and I'm currently on the 1.1 bootloader, can I just use nvflash to flash over the the 1.2 version of tnt?
(it wont let me post the link, but its on the gtab for dummies nvflash instructions)
Yes you should be able to just be able to flash the Stock 1.2 rom. There are nvflash setups with the stock 1.1 and 1.2 roms that come with the CWM recovery kernal already on them. Being a noob they won't let me attach links from the Dev. portion just yet, but that's how I got mine.
I believe it's nvflash for dummies. The Dev. created a link to the site to be able to download both if needed. Make sure that you have ADB setup first before flashing. Read up on all that from the dev forum.
OK so I managed to fix the partitions through CWM, but I can't get NVFLASH to flash it over to the 1.2 BL. I was able to install the 1.1 gtabcomb but I want to switch boot loaders.
When I click on the .bat file it just says "unknown device detected" I installed the proper drivers ect. This is while I have my tab in CWM. Also I don't know if this is important or not, but when I boot up it says NVIDIA TEGRA Development unit, and in the top right corner there is an android peeing on the apple logo. Maybe I have a weird cwm recovery or something? Am I even in APX mode when im in cwm?