nvflash question... - G Tablet Q&A, Help & Troubleshooting

Ladies and gentlemen,
I'm getting my viewsonic g tab tomorrow and have been reading the threads about nvflashing bootloaders. My question is (if my tablet comes with bl1.1) can I just nvflash from bl1.1 to bl1.2? I ask this because it seems some of the folks here either don't want to upgrade their bootloaders to 1.2 because theyre either too scared of bricking or "like" (?) bl1.1 but I like the rom branch and veriety of the 1.2 bootloaders. Thanks in advance folks.

BTW, I have read the guide on nvflashing (very great write up and summary of nvflashing the g tab) and it covers everything except if you can nvflash back and forth between the 2 bootloaders. This is my first tablet and please excuse my noobness on the subject of nvflashing. I know most topics regarding cwm and how to use it and have owned, rooted and flashed MANY ROMs on a total of 4 android phones. Thanks again.

You should be just fine to nvflash to 1.2. Many consider it "safer" to flash to the stock 1.1 TnT first but if your tablet comes with 1.1 you will already be there. Once you are on 1.2, you probably will not want to go back, but it is possible.
However, if your tablet comes with 1.1 you could also just take the OTA update to get to 1.2 and not have to nvflash. Then you can install CWM and a rom. Check out this site for lots of good info if you decide to use nvflash, and also make sure you read this thread. Backup your .bct file and use it any time you use nvflash. Some roms will require you to nvflash to change the size of the system partition (ICS for example).
Also, be sure to use the correct version of CWM:
CWM v08 - use for bootloader 1.1 only
3028 rev.5 - use for bootloader 1.2 only
5504 touch - use for ICS rom only (is included in the nvflash file found in the ICS thread)
BTW - if you do take the OTA update to get to 1.2 make sure you have the stock recovery installed NOT CWM.

OK, so my understanding here is; tab comes with 1.1-update to 1.2 with ota (no cwm, install after update)--> tab comes 1.2-downgrade with tnt 1.1 tool then nvflash back to 1.2 w/cwm? Hope that sums it up. And my whole point here is to end up with 1.2 w/cwm so I can start flashing bl1.2 branch ROMs. I think I'm pretty sure what I'm doing now. Thanks bud.

Yep, except that if the gtablet comes w/ 1.2 already there is no need to downgrade, and you only need to nvflash if you are going to use a rom that requires it. Just install CWM and then your rom of choice.

Thank you again daggerdave. My g tab didn't show up today. Tracking says tomorrow. Excited to have my first tablet!!!!

Related

[Q] Brand new GT, NVFlashed to 1.0-2638, what next?

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

[q] what is 1.1 and 1.2 stock? what is the bootloader?

i know these questions can probably be found somewhere but would someone be able to give me a quick run down of what 1.1 and 1.2 stock is and how does that relate to 3588 and 4349? also what is the bootloader and why do some things require the stock bootloader and not CWM? and also, how do you go back to the stock bootloader, just nvflash the stock 1.1 or 1.2? and also why are 1.1 and 1.2 bootloaders not compatible with certain roms and such?
thanks in advance!
joshtb86 said:
i know these questions can probably be found somewhere but would someone be able to give me a quick run down of what 1.1 and 1.2 stock is and how does that relate to 3588 and 4349? also what is the bootloader and why do some things require the stock bootloader and not CWM? and also, how do you go back to the stock bootloader, just nvflash the stock 1.1 or 1.2? and also why are 1.1 and 1.2 bootloaders not compatible with certain roms and such?
thanks in advance!
Click to expand...
Click to collapse
I can answer some ...
1.1 and 1.2 are the 2 common bootloaders for the gtablet.
I think of bootloaders as a layer of software that sits underneath a ROM and provides services to it. ie between the ROM and the hardware.
1.2 is the newer bootloader, which is needed by 4349, Bottle of Smoke (BOS) which is a Honeycomb distribution, and a few other. (Mountain Laurel, and Brilliant Corners which are 1.2 versions on TNT Lite and Vegan Tab).
All others 3588 (and before), TNT Lite *, Vegan Tab, CM (all versions maybe except one which I hear is for 1.2 for gadam?) use the 1.1 bootloader.
Stock recovery (update.zip and command file) , will update both ROM and bootloader, and is the preferred way to go between 1.1 and 1.2 based ROMs
CWM 0.8 will update ROM but *not* the bootloader.
So CWM cannot be used to go between 1.1 and 1.2 based ROMs.
If you currently use CWM, you can nvflash to a stock ROM (eg 3588), you get stock recovery back, and you should be then able to update to any ROM.
There is also a recovery pack for some 3588 based ROMS (maybe also for the 4349 ROMs) that has scripts to switch between stock and CWM recovery, although I do not know how well they work. Doing this would not require NV flashing.
My guess as to why different ROMs go with different Bootloaders, is that the newer Bootloaders, provide new functionality for new ROMs (due to which, new ROMs do not work with old bootloaders) and delete functionality needed by older ROMs (due to which, older ROMs do not work with newer bootloaders). However if the ROM could be made to not rely on these changes of services, they could in theory be made to work with both bootloaders. I have no idea if this is possible in practice.
joshtb86 said:
i know these questions can probably be found somewhere but would someone be able to give me a quick run down of what 1.1 and 1.2 stock is and how does that relate to 3588 and 4349? also what is the bootloader and why do some things require the stock bootloader and not CWM? and also, how do you go back to the stock bootloader, just nvflash the stock 1.1 or 1.2? and also why are 1.1 and 1.2 bootloaders not compatible with certain roms and such?
thanks in advance!
Click to expand...
Click to collapse
3588 use the 1.1 bootloader
The recovery is only able to start an update.zip
4349 use the 1.2 bootloader (same as Honeycomb based rom)
4349 also install a new recovery that look like CWM but is Honeycomb blue
Bootloader in this case is actually a combination of 2 thing, bootloader and kernel they are save on 2 different part of the nvflash image (2-3)
The stock bootloader is needed to be able to move from a rom using version version 1.1 to 1.2 or back, the proper method is to use an update.zip since this is the only method know to update the bootloader (NVFLASH doesnt flash partition 2 and 3)
To go back use UPDATE.ZIP with a STOCK 1.1 recovery, you can even nvflash the recovery directly using nvflash (position #9)
Why are they incompatible? good question, mostly kernel related afaik, there's now cross compatible kernel available that allow you to use a 1.2 bootloader with a 1.1 rom (see Clemsyn thread) this also provide the capacity to use similar rom from other brand (seem like the gtab was using an older bootloader)
very interesting subject that do require reading a few thread to be safe...
cbay, Thanks that was very informative. I had been wondering the same question.
well, now you know the what and how, but what about the why and the history...
Viewsonic is a basically a repackager. they put their name on a product and sell it to the masses. US Merchants is the US company that imports these products from China. The Chinese company that actually builds them is called Malata.
Malata is also responsible for the Notion Ink Adam as well as some other Tegra 2 based tablets.
The odd part comes in to play when you look at the bootlaoders for each device. Notion Ink always used a 1.2 bootloader for their Adam updates and firmwares. Viewsonic, though, was using what is assumed to be an older version of firmware based on the 1.1 branch. There is a lot of speculation as to why this is, and there is no real answer.
Now, back in February, one of the devs got a hold of a firmware labelled 3391. He discovered that it was on a different bootloader than the G-Tablet was currently using. he messed around with it a bit, but it proved to be difficult to crack at the time, since everyone was on 1.1 and it wasn't an official update, so nobody really had it.
Then, Viewsonic hadn't released an official update for a while. Users were getting irritated, and a mass request went out for Viewsonic to do SOMETHING...they did, they released the 4349 firmware, but then pulled it 24 hours later. It's still known as the most recent officla firmware, thought it's not available anymore (officially) 4349 also ended up being a 1.2 firmware. SO, now since this was an official update, the developer that was messing with 3391 figured that this was the direction that Viewsonic/Malata was going to go. He made his opinions known but was rejected by some of the mods here at XDA.
Since then, he has graciously moved to another forum where he houses all of his 1.2 roms. He took it upon himself ot convert his older roms to the newer 1.2 bootloader (Brilliant Corners, Mountain Laurel). He also created a seperate Clockwork mod that will work on 1.2 bootlaoder as well.
It was discovered that the new 1.2 bootloader from Viewsonic was the same bootloader that Adam had been using all along. It seemed that Viewsonic was either using, or getting outdated software from Malata. So, now we can also use Adam Roms and Kernels on our G-Tablets as well.
Honeycomb was ported from another device, but enabled to use the 1.2 bootloader. It's still in Alpha stages, but does require the 1.2 bootloader to flash.
Essentially, 3588 was the LAST 1.1 official updated firmware directly from Viewsonic. The only way that it can be improved upon is if we get more 1.1 official updates from Viewsonic. But, since we haven't recieved ANY updates from Viewsonic, we're not holding our breath.
4349 was the FIRST (and as of now ONLY) 1.2 official update from Viewsonic.
Fortunately for G-Tablet users, the Adam bootloader being compatible with our 1.2 bootlaoder opens the door for infinate possibilities. We are no longer dependant on VS to provide updates, as updates from Notion Ink can be ported more easily.
it's been suggested that the older 1.1 roms e converted to 1.2 roms ot avoid confusion and unexpected softbricks caused by such confusion, but there is resistence.
cbay said:
I can answer some ...
If you nvflash to stock (ie without CWM), you should be able to update to any ROM.
Click to expand...
Click to collapse
wrong, Nvflash doesn't update the bootloader, so the only correct way to move from one version of bootloader to the other is the update.zip method with a STOCK recovery (it also need a rom with the command "write_bootloader_image("/tmp/bootloader.bin", "EBT"" in the updater script )
Like you mentioned CWM doesn't flash the bootloader
if you check the process during nvflash, partition #2 and 3 (actually it's all the same partition only splitted in parts) are not flashed...
they can however be read using the correct command
Everything else is right, hey 2 answer for the same lazy question he's a lucky guy...
p00r, I'm very curious about that. Have you done a binary compare before and after nvflashing with different bootloaders to confirm it? If not, I may try it myself. I use nvflash to move between 1.1 and 1.2 based ROMs all the time and have never had any trouble with it. I do agree that it is probably better and safer to use stock recovery for normal usage but I've never had an nvflash fail on my tablet due to a difference in bootloaders so I'd like to learn more about it so I can use that information to avoid trouble.
P00r said:
wrong, Nvflash doesn't update the bootloader, so the only correct way to move from one version of bootloader to the other is the update.zip method with a STOCK recovery (it also need a rom with the command "write_bootloader_image("/tmp/bootloader.bin", "EBT"" in the updater script )
Click to expand...
Click to collapse
What I meant was, nvflash to a stock ROM like 3588 and then use stock recovery to update to a 1.2 based ROM, instead of CWM.
As far as I know this should work, as nvflashing to a stock ROM like 3588 would get you to stock recovery as well. (Right?)
Also, at any point when updating to a ROM using stock recovery, it is good to read the thread of instructions for the particular ROM as, it may contain more steps of wiping data/ cache etc. Some ROMs may also require a change in partitioning.
K J Rad said:
p00r, I'm very curious about that. Have you done a binary compare before and after nvflashing with different bootloaders to confirm it? If not, I may try it myself. I use nvflash to move between 1.1 and 1.2 based ROMs all the time and have never had any trouble with it. I do agree that it is probably better and safer to use stock recovery for normal usage but I've never had an nvflash fail on my tablet due to a difference in bootloaders so I'd like to learn more about it so I can use that information to avoid trouble.
Click to expand...
Click to collapse
What do you want to compare exactly ?
There's plenty of post that explain the issue to move between 1.2 and 1.1 roebeet used to call this softbrick when he discovered the 3991 leaked viewsonic rom that used 1.2 bootloader...
cbay said:
What I meant was, nvflash to a stock ROM like 3588 and then use stock recovery to update to a 1.2 based ROM, instead of CWM.
As far as I know this should work, as nvflashing to a stock ROM like 3588 would get you to stock recovery as well. (Right?)
Also, at any point when updating to a ROM using stock recovery, it is good to read the thread of instructions for the particular ROM as, it may contain more steps of wiping data/ cache etc. Some ROMs may also require a change in partitioning.
Click to expand...
Click to collapse
Yes as soon as you nvflash a stock recovery over anything and then use the recovery to do an update.zip of another rom type it will work.
wow thanks for the help everyone! i hit the thanks button to everyone who replied.
im running the clemsyn + calkulin version 5. does anyone know how to find out what version of the bootloader that is? there is a version 6 released requiring 1.2 and i also wanted to tryout the honeycomb version.
also, a backup image created with CWM - does it back up the bootloader, rom, and kernel? or just the rom
thanks again!
P00r said:
What do you want to compare exactly ?
There's plenty of post that explain the issue to move between 1.2 and 1.1 roebeet used to call this softbrick when he discovered the 3991 leaked viewsonic rom that used 1.2 bootloader...
Click to expand...
Click to collapse
Compare the bootloader before and after the nvflash. I've seen all the threads on moving between 1.1 and 1.2 and quite frankly I've never had any trouble using nvflash to do it regardless of which ROM I'm going to or from as long as I use the appropriate bootloader in the nvflash command. Based on that experience I would say the bootloader is being updated on the tablet or else I would have had considerably more trouble. The only time I've seen any trouble moving between the two is when trying to use ClockworkMod.
P00r said:
Everything else is right, hey 2 answer for the same lazy question he's a lucky guy...
Click to expand...
Click to collapse
Err, that wasn't really a "lazy question."
Everything on here and elsewhere assumes you know what "1.1" vs. "1.2" means without explanation. There's hardly anything anywhere that explains what they mean to new users.
I'm not sure how asking a question which isn't answered anywhere else is "lazy."

[Q] Can't flash to Honeycomb style ROM, but can w/all others?

I'm fairly experienced at flashing various roms. I've done it with G Harmony Gingerbread, Vegan 7.0 Gingerbread and TNT Lite 4.x. All were successful. Sometimes I used NVram (1.2), sometimes not. I always wiped user data etc.
When I try to flash Android Illuminate Alpha 2.1 or Bottle of Smoke 6.0 all I get is stuck at the VS splash screen. I've tried everything and no matter what I do the end result is the splash screen.
I know I'm not doing the process wrong and it's a pretty good coincidence that the only ones that freeze are honeycomb based. So my question is, is there something I could try different or are some G Tablet's hardware such that honeycomb simply won't flash?
1) What ROM are you flashing from?
2) Which bootloader is it based on?
3) Are you using CWM or stock recovery (or, god forbid, ROM Manager)?
The symptom you have is common for someone trying to flash directly from a 1.1 bootloader ROM to a 1.2 bootloader ROM using CWM. Since CWM doesn't update the bootloader the new ROM can't load.
Honeycomb has a different data structure than everything else. If you want to flash into or flash out of a honeycomb rom, you need to follow my code red in the "start here" page of my website. Link in signature. Even experienced users will brick their gtab if they don't follow my instructions there.
The bootloader ROM i'm flashing from is 1.2 (I think). Before I flash, I do an NVflash 1.2. Then flash to the new ROM. I use CWM and have the NVflash setup where it automatically installs CWM.
My Kernel version is 2.6.32.9 so I'm pretty sure my stock bootloader ROM is 1.2, hence the NVram 1.2.
However, when I bought this tablet, it already had TNT Lite on it, so I really have no idea what the stock ROM was 1.1 or 1.2. I'm doing an NVflash 1.1 now and am going to try to flash Honeycomb Flashback. Fingers crossed.
goodintentions,
Problem solved because of your fantastic website. I really appreciate the hard work you put into it. When I looked at your ROM compatibility page and saw that TNT Lite was only compatible with 1.1, I new I had 1.1. So...I did a 1.1 NVflash and flashed GtabComb. I followed your instructions to the letter and it worked perfect. Man is Honeycomb nice.
I'll probably partition my SD card and upgrade to bootloader 1.2 so I can try BoS etc.
Thanks again. You rock!
tevamarc said:
goodintentions,
Problem solved because of your fantastic website. I really appreciate the hard work you put into it. When I looked at your ROM compatibility page and saw that TNT Lite was only compatible with 1.1, I new I had 1.1. So...I did a 1.1 NVflash and flashed GtabComb. I followed your instructions to the letter and it worked perfect. Man is Honeycomb nice.
I'll probably partition my SD card and upgrade to bootloader 1.2 so I can try BoS etc.
Thanks again. You rock!
Click to expand...
Click to collapse
Just so you know, you don't have to stay with 1.1. You can nvflash to either branch. That's the purpose of nvflash, to allow you to jump branch the easy way. There's another way to jump branch, but I've decided that that way is a bit too risky for beginners and so I have not mentioned it at all.
You are indeed right. I did that and it works great. I've tried Illuminate, BoS, and Flashback. I found Flashback to be the most stable with very few lockups compared to the others.

[Q] good unbricking / 1.2 update tutorial?

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?

[Q] My gtab needs rehab....

So I gave my son a gtab in April 2011 as a birthday gift. The first thing I did was root, install CWM, and vegan tab. Nothing has been changed since then. Even my CWM is 2.5 something.
Now 1 year later it is time to update it and see what has improved. I have a few questions that I'm hoping someone can answer.
I'm pretty sure I have bl 1.1. I have never used NV Flash but I think I can get it working.
I would love for the tablet to sleep and not kill the battery. That was a god send on my Nook Color when the Devs got it working. Do any current ROM's have a good deep sleep?
Am I better off staying on the 1.1 bl or moving to 1.2? If I want ICS I need to go to 1.2?
Thanks.
Steve
Yes, you will need to be on the 1.2 bootloader to run ICS. The NvFlash file you will need is in the instructions at the ICS thread (in the Gtablet > Development section). You will need to use that one, as it increases the system partition size to accommodate the larger ICS Rom and Gapps. Make sure you read the ICS threads and know what to expect, as it is a beta release. I have been running it for a few days and it looks/runs great, no serious problems so far. TeamDRH has done a great job and it will keep getting better!
Regardless, if you want to run a newer Rom you will probably want to upgrade you bootloader to 1.2. 1.1 development has pretty much ended, and even Viewsonic is finally moving to 1.2. If you aren't going to use ICS you can probably upgrade without using NvFlash, Visit this thread and follow the instructions to install the 1.1.3588 .zip to get back to stock (of course, wipe your data/cache), then just take the OTA update to get to 1.2. However, if you do decide to use NvFlash, please visit this thread first.

Categories

Resources