[HowTo] Upgrade from 1.1 to 1.2 based ROMs

[xKurzx]

aha i have CWM working again n i will try to at least re download everything

would like to get this working through CWM would be a huge help

 

[gadgetrants]

Oh, wonderful. Which bootloader are you on by the way, 1.1 or 1.2? Sounds like 1.2? I'd still try to nvflash 4349 (and also repartition...are you cool with that?) to make sure you start with a clean slate.

-Matt

 

[xKurzx]

i think i still have bootloader 1.1

the CWM is working which made me happy but nothing else is just been able to load CWM

and i have repartitoned twice i will try again hopefully in a couple hours

n matt is there a simple more OS specfic NVFlash [How to] cause i tryed that but got confused along the way

 

[gadgetrants]

Yeah I try to avoid referring androidtablets users to other how-tos but the one I posted above is from the "horse's mouth". Like I said, I really know the Win process, so I'll also avoid giving you Mac advice!

-Matt

 

[xKurzx]

ok did everything tablet loads starts android n then dies

 

[xKurzx]

Lost confused n kinda n ticked

 

[gadgetrants]

Lost confused n kinda n ticked

If you've got a chance, post an update!

-Matt

 

[xKurzx]

"Update" I am back to running 1.1 3588 stock n want to run alpha 7.3

 

[gadgetrants]

"Update" I am back to running 1.1 3588 stock n want to run alpha 7.3

e
Excellent. I assume you mean Flashback 7.2, right?

Since that's on the 1.2 bootloader (3588 is the 1.1 bootloader), your next step is to nvflash the 4349 stock image. Good place to get it is:

[RECOVERY] nvflash FULL restore, using either 1.1 or 1.2 based images - [G-TABLET] - SlateDroid.com

Let me know if already have it, or run into any trouble when you nvflash it!

-Matt

 

[xKurzx]

Done i am at 1.2 4349 Mydave put a zip which was crazily easy to update to 1.2 with MAJOR THANKS

so wats Next Good sir

 

[joe_mcp]

Can you link to the mydave post with the zip to go to 1.2?

Thanks,

Joe

 

[xKurzx]

Hey Joe heres the link to my HELP please thread n ull need to setup the APX driver on ur windows its a simple processjust ask if u need help

http://www.androidtablets.net/forum/viewsonic-gtablet-technical/20940-help-please.html#post122070

 

[ozgolith]

As an update to this thread in case someone else runs across it with the same issues stated in a few of the posts. If you are seeing what others reported where you boot and it looks like a quick update is happening but when TapnTap loads you are still at 1.1 the COMMAND file name issue is likely your problem.

I don't use Windows except for browser testing and trying to use a Windows VM as directed is what screwed me up. I realized after the fact that no matter what I did Windows kept naming the COMMAND file COMMAND.txt which will not work. Checking properties in Windows showed me it didn't have an extension but it did. Notepad added it and no matter what I couldn't seem to get Windows to show me that it was named COMMAND.txt.

After going through the process I didn't see any reason I couldn't do this under OSX so I retraced the steps and sure enough when I mounted the Tablet the file was named COMMAND.txt so all I had to do was rename it to get it to bootup under ClockWorkMod and finish the update. Change the file name and viola, everything worked as expected.

Thanks for the posts, I wish someone would edit the original post to reflect the much needed change about the specifics to the COMMAND file name.

 

[myzoo]

Link is now invalid is there another link? mydave can you update this link please?

 

[bjmarler]

As an update to this thread in case someone else runs across it with the same issues stated in a few of the posts. If you are seeing what others reported where you boot and it looks like a quick update is happening but when TapnTap loads you are still at 1.1 the COMMAND file name issue is likely your problem.

I don't use Windows except for browser testing and trying to use a Windows VM as directed is what screwed me up. I realized after the fact that no matter what I did Windows kept naming the COMMAND file COMMAND.txt which will not work. Checking properties in Windows showed me it didn't have an extension but it did. Notepad added it and no matter what I couldn't seem to get Windows to show me that it was named COMMAND.txt.

After going through the process I didn't see any reason I couldn't do this under OSX so I retraced the steps and sure enough when I mounted the Tablet the file was named COMMAND.txt so all I had to do was rename it to get it to bootup under ClockWorkMod and finish the update. Change the file name and viola, everything worked as expected.

Thanks for the posts, I wish someone would edit the original post to reflect the much needed change about the specifics to the COMMAND file name.

Wow, Thank you SO MUCH for this correction. I was banging my head for hours trying to figure out why I could not get my GTab to update from 1 to 2. Thank you again!

Mods, please update/change the original directions so others do not have this same problem. Basically the original directions state to create a "COMMAND.txt" file. This is very missleading as most readers will assume they can use Notepad which does add the .txt extension to the end of the file created. What should be said is to create a "COMMAND" text file with a program like Notepad++ and be sure to name it ONLY COMMAND, DO NOT name it COMMAND.txt.