Database Info

Bricked? And options?

I think I'm posting to the right place. I have been playing around with the various mods, tnt lite, vegan, cyanogen, and somewhere along the way it got stuck to the point it is giving me an error right when I start the tablet saying "magic value mismatch". First time it happened I was able to get back to recovery. And I tried to restore, and didn't work. Tried clearing cache and it hung there for over thirty minutes. Now I can't even get into recovery and error reads the magic value mismatch. So am I bricked or is there a way out of this? And anyone try returning a bricked tablet to Sears? I'm still within my 30 day window.
Sent from my Droid using XDA App

Here's a nice link:
http://forum.xda-developers.com/showthread.php?t=860493

Thanks for the link. This seems to work, as I did not know the low level capabilities. Hopefully, I'll be mod'ing again soon! And for anyone in my position between these two links I figured it out where to get the files:
forum.tegratab.com/viewtopic.php?f=6&t=8
forum.tegratab.com/viewtopic.php?f=13&t=18&p=170

Did you use a newer version of clockworkmod (.12 or higher) with the device, and attempted a firmeware update? If so, it's a known issue and it's why I'm still using .8, right now.
It's not bricked, btw. This device is virtually unbrickable - you will probably need nvflash to fix it, and I have a post that can point you in the right direction:
http://forum.xda-developers.com/showthread.php?t=861950
Hope this helps!

Thanks, but I'm now getting the issue some others had in the other forums, but I don't see a fix where every boot ends up in APX mode. How do I get out of that?
As a side note, I did try the latest updated Clockwork recovery last night, which I believe is 2.5.1.8, that seemed like they added support from ROM Manager.

Sorry, I take it back used, the right zip file and everything is fine. I grabbed the one dated 2010112600 thinking it was a later version. Thanks for the help and the great threads and ROM's!

jkpatel79 said:
Sorry, I take it back used, the right zip file and everything is fine. I grabbed the one dated 2010112600 thinking it was a later version. Thanks for the help and the great threads and ROM's!
Click to expand...
Click to collapse
You might one of the newer devices with the swapped partitions (thats the 11/26 one you used). We still don't know why this is - very bizarre as to why VS (or whatever vendor they use) did this.

roebeet said:
This device is virtually unbrickable
Click to expand...
Click to collapse
Virtually is right. I accidentally bricked mine because I hit one of the devkit .bats while trying to reflash to stock

TnT UAT version 3991

Found this in my TnT site scan:
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3991-user.zip
Build date is 2/12, and it's still Froyo. It looks like a lot of stuff was touched, perhaps they incorporated some recent Nvidia libs.
EDIT: They have a Flash player script in here - that's new.
EDIT2: So far, this update has competely borked my device. It's the bootloader or boot.img, so just keep that in mind. It could be that my device is all messed with all the recent flashing, but just be aware.
EDIT3: In case this is not already clear, this is a VERY dangerous update. Tread carefully - it requires stock 3588 as a baseline, including recovery.
3/28/2011 EDIT: Looks like Viewsonic pulled it (a case of the Woot! heebie-jeebies, perhaps?)

Sry to hear about your device. Hopefully you can figure it out. Bricked a phone before and took me a few weeks before I accidentally fixed it, lol.
As for the tnt update does this mean we may see another viewsonic ota update finally? Matbe they finally resolved the sluggishness issues and tntui will finally be usable

I got around the issue with using an older boot.img and bootloader. One (or both) are causing issues with my system.
They added a lockscreen - that will make some people very happy.

How did you get around this. I tried this update and it borked my device as well and I can't get past the viewsonic boot screen or load clockworkmod to boot the recovery kernel

xdadev69 said:
How did you get around this. I tried this update and it borked my device as well and I can't get past the viewsonic boot screen or load clockworkmod to boot the recovery kernel
Click to expand...
Click to collapse
I used nvflash - I dropped the old bootloader and boot.img in there and ran it with that, and it booted up.
EDIT: I couldn't get wifi working for Quadrant, but Nenamark is ~40fps. My guess is that they updated a lot of the libs so that they in up-to-date with recent Nividia changes.
EDIT2: Camera is working, including rotation. Gsensor is still off for games, but that's not a surprise.

Thank god for nvflash. I thought I seriously boned myself today installing this new UAT version. I flashed back to stock, reinstalled clockworkmod, and then was able to get back up to TNT lite 4.2.4.
While I am posting, I would like to thank all the Devs for their time and efforts making these ROMS and instructional posts. Without your efforts this tablet would seriously blow donkey balls. I actually bought the G tablet with the full intention of getting rid of the stock ROM and unleashing the full potential of the underlying hardware with the ROMS here.
Thanks again

This is not bad at all, I forgot how nice the weather dashboard looked because I was too busy cursing this thing for being sooo slow. I remember the first day I got this thing, I couldn't even stand to use it. It was so frustrating. You,gojimi and rothnic did an amazing job to get this tab where it is today. I think viewsonic even "borrowed" some of you guys work, lol.. Thanks Again for you guys work!
UPDATE: I went completely stock before this update, (no clockwork mod) this new update 3991 looks like it has a built in recovery menu. I don't remember that on older versions

what were you running prior to returning to stock?

lsu205 said:
what were you running prior to returning to stock?
Click to expand...
Click to collapse
vegaN 5.1.1

aver2one said:
This is not bad at all, I forgot how nice the weather dashboard looked because I was too busy cursing this thing for being sooo slow. I remember the first day I got this thing, I couldn't even stand to use it. It was so frustrating. You,gojimi and rothnic did an amazing job to get this tab where it is today. I think viewsonic even "borrowed" some of you guys work, lol.. Thanks Again for you guys work!
UPDATE: I went completely stock before this update, (no clockwork mod) this new update 3991 looks like it has a built in recovery menu. I don't remember that on older versions
Click to expand...
Click to collapse
I hadn't looked at their recovery - very nice. They are emulating what Notion Ink had done on their recovery.
This is going to be a nice update, once they shake out the bugs.
Here's a screenshot of the lockscreen, using the "classic" launcher:

Looks good, I like the changes.

2400 in Quadrant - and that's 3991 "stock", no changes. Normally stock is ~1900, I think.
I managed to get Wifi working by downleveling the Wifi drivers - that was needed to use the older kernel. I just don't understand why their new kernel doesn't work for me.

roebeet said:
2400 in Quadrant - and that's 3991 "stock", no changes. Normally stock is ~1900, I think.
I managed to get Wifi working by downleveling the Wifi drivers - that was needed to use the older kernel. I just don't understand why their new kernel doesn't work for me.
Click to expand...
Click to collapse
Wow looks like that next update is going to be great!
Btw I was averaging @1700 quadrant score earlier today stock before I went up to 3991

roebeet said:
2400 in Quadrant - and that's 3991 "stock", no changes. Normally stock is ~1900, I think.
I managed to get Wifi working by downleveling the Wifi drivers - that was needed to use the older kernel. I just don't understand why their new kernel doesn't work for me.
Click to expand...
Click to collapse
Looks/sounds very nice roebeet...can't wait for the push over OTA...I actually just went back to stock a few hours ago to mess with the enhancement pack with the January OTA update...it's actually fairly quick compared to the original stock...think I'll stick with it for a bit
I'm guessing that since it's a non-published update, then they may have an incomplete boot.img or possible they had to update the bootloader, who knows...could also be a "built-from-scratch" update that they are still working on, lol...doubtful but you never know
Good luck and here's hoping for an official push from Viewsonic here soon. The sooner they get this out, the sooner they can get to working on an official Viewsonic release of HC ;-) lol

Wow, that update is great! Though, sorry to hijack the thread, but I got no replies elsewhere, anyone had the "blank screen of dead" issue? I stop using my gtablet for a couple of weeks, and now that I boot it up again, the screen is white! (not even the VS birds..).
Keep pushing updates for us =)!
Thanks

pmcnano said:
Wow, that update is great! Though, sorry to hijack the thread, but I got no replies elsewhere, anyone had the "blank screen of dead" issue? I stop using my gtablet for a couple of weeks, and now that I boot it up again, the screen is white! (not even the VS birds..).
Keep pushing updates for us =)!
Thanks
Click to expand...
Click to collapse
Do you have a Backup in clockwork mod? Do you have clockwork mod?

aver2one said:
Do you have a Backup in clockwork mod? Do you have clockwork mod?
Click to expand...
Click to collapse
Yea, but again, thats not the issue. Theres nothing in the screen, not even booting to recovery, the screen is white, theres a thread about it, someone reported the same problem, I asked what happened to it, but got no reply! D:
Thanks

pmcnano said:
Yea, but again, thats not the issue. Theres nothing in the screen, not even booting to recovery, the screen is white, theres a thread about it, someone reported the same problem, I asked what happened to it, but got no reply! D:
Thanks
Click to expand...
Click to collapse
If you can't boot into recovery have you tried nvflash?

pmcnano said:
Yea, but again, thats not the issue. Theres nothing in the screen, not even booting to recovery, the screen is white, theres a thread about it, someone reported the same problem, I asked what happened to it, but got no reply! D:
Thanks
Click to expand...
Click to collapse
You may want to head over to the development forums and check out the nvflash thread by roebeet...sounds to me like you'll need it. Good luck.
Question for you roebeet...how stable is this? Just wondering if I should even attempt to install it. Let me know what you think and thanks for all the hard work.

Found this in my TnT site scan:
http://tapntap.http.internapcdn.net/...-3991-user.zip
Build date is 2/12, and it's still Froyo. It looks like a lot of stuff was touched, perhaps they incorporated some recent Nvidia libs.
EDIT: They have a Flash player script in here - that's new.
Is there an enhancement pack with this, or is it available, even ?
Great men do great things.... like our developers! Thanks guys ALL OF YUU!!!

Received WOOT Tablet - Answering Version Questions

Just got my G-Tablet off of WOOT and wanted to let everyone know that it shipped with version 1.1-3389. Just thought I would ease everyones mind around here.

A few others have said the same - thanks! 3389 is a good baseline for mods, FYI.
3588 is what you'd get with the OTA updater, and I would actually recommend doing that first - 3588 came out in January and is a pretty rock-solid stock ROM. It's an even better baseline than 3389, imo. And the 3588 recovery is the only recovery that works with the 3991 UAT, so it might be a requirement for future stock ROMs. We don't know this for a fact yet, but better safe than sorry.

The first thing mine did was update to 1.1-3588. I'm off to figure out how to get the Market on it.

roebeet said:
A few others have said the same - thanks! 3389 is a good baseline for mods, FYI.
3588 is what you'd get with the OTA updater, and I would actually recommend doing that first - 3588 came out in January and is a pretty rock-solid stock ROM. It's an even better baseline than 3389, imo. And the 3588 recovery is the only recovery that works with the 3991 UAT, so it might be a requirement for future stock ROMs. We don't know this for a fact yet, but better safe than sorry.
Click to expand...
Click to collapse
Well apparently there will be a second batch, which I guess mine will be a part of, so there is still a chance for 3991 to still be used.

Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.

I'm guessing they are all 3389 - I'm sure they work off the same image.
However, I'd check it anyway - better safe than sorry, imo.

Tonydiv said:
Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.
Click to expand...
Click to collapse
Yeah I agree your tablet will be like the rest from woot!!!! So if we even see 3991 it will be a ota update!!!!

sigvader said:
Yeah I agree your tablet will be like the rest from woot!!!! So if we even see 3991 it will be a ota update!!!!
Click to expand...
Click to collapse
If you see 3991 on your Woot tablet, please tell us immediately. I would very shocked at this point if that happened, but then again I didn't expect 3389 either. I really thought they were going to be 3588.

Tonydiv said:
Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.
Click to expand...
Click to collapse
One of the woot staffers gave an unofficial update the day after the purchasing ended and said that they were getting a rush shipment on Monday from the vendor to fulfill the second half of the orders. So they are physically a separate set from the first batch.

Just FYI, I got mine today and it was 3389.
Is there a point to doing the update?
Going to flash Vegan and the 5.1.1 add on now.
I copied the update.zip and all the files off the Gtab before I did anything. I'm betting that's a restore to 3389.
Edit: Updater-script says it's 3389.

theroblog.com said:
Just FYI, I got mine today and it was 3389.
Is there a point to doing the update?
Going to flash Vegan and the 5.1.1 add on now.
I copied the update.zip and all the files off the Gtab before I did anything. I'm betting that's a restore to 3389.
Edit: Updater-script says it's 3389.
Click to expand...
Click to collapse
It's not a requirement, but I think it's a good idea to flash to 3588 first. The reason is that you'll get the latest bootloader and recovery, which ROMs like VEGAn don't touch.
Recovery is the one that concerns me, as 3588 recovery seems to be a kind of "gateway" recovery that might (and I stress "might") be needed to get you to a future firmware level. So, imo, I would flash to 3588 first, THEN start using ROMs if you want. It's a safer bet, again imo.
Thanks for the confirm on that update.zip -- sounds like it's stock 3389, like you mentioned.

received my tablet from woot today. ill post back as soon as its charged and powered up with the version.

roebeet said:
It's not a requirement, but I think it's a good idea to flash to 3588 first. The reason is that you'll get the latest bootloader and recovery, which ROMs like VEGAn don't touch.
Recovery is the one that concerns me, as 3588 recovery seems to be a kind of "gateway" recovery that might (and I stress "might") be needed to get you to a future firmware level. So, imo, I would flash to 3588 first, THEN start using ROMs if you want. It's a safer bet, again imo.
Thanks for the confirm on that update.zip -- sounds like it's stock 3389, like you mentioned.
Click to expand...
Click to collapse
I am new to all this, so excuse me for some newbie questions.
Most of the walkthroughs to install a moded ROM, seem to install Clockworkmod first. How is that different from what you call "recovery" here. Will it replace the stock 3588 recovery? Or by the "3588 recovery" do you mean the bootloader part that calls the Clockworkmod. Is there a way to install a ROM without Clockworkmod? This is specifically for 3588.
I ask because I see some discussions about TNT Lite 5 where it seems to break with Clockworkmod. So if we want to get to TNT Lite 5 in the near future, should we now install Clockworkmod?
I am asking this specifically for the woot buyers who it looks like get 3389->3588
Any pointers would be very helpful.
thanks

cbay said:
I am new to all this, so excuse me for some newbie questions.
Most of the walkthroughs to install a moded ROM, seem to install Clockworkmod first. How is that different from what you call "recovery" here. Will it replace the stock 3588 recovery? Or by the "3588 recovery" do you mean the bootloader part that calls the Clockworkmod. Is there a way to install a ROM without Clockworkmod? This is specifically for 3588.
I ask because I see some discussions about TNT Lite 5 where it seems to break with Clockworkmod. So if we want to get to TNT Lite 5 in the near future, should we now install Clockworkmod?
I am asking this specifically for the woot buyers who it looks like get 3389->3588
Any pointers would be very helpful.
thanks
Click to expand...
Click to collapse
Clockworkmod is non-vendor third party recovery replacement, wheras "standard recovery" is stock recovery (this is what the vendor supplies).
TNT Lite 5 was pulled after about a week, due to more than a few issues where users were soft bricking their devices. Going on metrics I tried to compile, the majority of the problems stemmed from the use of clockworkmod, thus my reasoning for not recommending its use anymore. This is despite the fact that the update it was based on was a non-released firmware. I will explain further. Btw, we are seeing similar issues over in the Notion Ink Adam forums in notioninkhacks.com, for the same exact reasons (clockworkmod).
In the case of the GTAB, the vendor (Viewsonic) adds the bootloader.bin to its stock update firmware. And it has been updated at least twice tmk - once in a November firmware update, once in a December firmware update. And also with this 3991 UAT update, but for the sake of argument we won't count that one. But they have updated it in released firmware.
But clockworkmod users do not get that update, as the program doesn't support updating the bootloader.
3388 to 3588 seems to have the same bootloader so, for the short term, using clockworkmod is probably OK. But there is no guarantee that a future update will not require a bootloader change. Again, we have already seen this happen with the NI Adam, and also the Viewsonic non-released UAT. So, with all that being said, I cannot recommend Clockworkmod as a flashing tool.
I've actually kept TNT Lite 5 (which is now TwoTapsX) on ICE specifically because of the expected surge of new Woot users. The last thing I want to happen is for a large number of inexperienced users with mixed information to flash that firmware with the wrong tool (clockworkmod) and then soft-brick their device.
I actually require clockworkmod for my gADAM mod because that mod requires a user data wipe, which standard recovery does not support. But gADAM has a "Recovery Pack" built-in - what this does is allow the user to easily flip between standard recovery and clockworkmod, as needed. Since gADAM is a 1.1-based mod, the use of clockworkmod to flash it is low risk. But if you later flashed to a mod that might require a new bootloader, the Recovery Tool allows you to put standard recovery back before you flash again.
I know this is all very confusing - believe me, it is for me as well. Suffice is to say that modded ROMs are risky business and you should read the instructions very carefully before proceeding. I have started to add the firmware type in my own ROMs as a guide - "1.1" for example. So, a "1.1" to "1.1" firmware mod change should be a low risk, for example. Right now, most of the stock ROMs and probably all the modded ROMs are "1.1" based.

If it is possible, maybe some admin could update the last message in the thread (http://forum.xda-developers.com/showthread.php?t=1006571) you had posted on woot's discussion page. Either link here, or just update and say: hey, people got some woot gTabs in already and they are the 3389 version.
I read this above post, but have not received my woot gTab (so no idea what version I'm getting). Good thing I searched first and found this post. Just to put my mind at ease

eak0703 said:
If it is possible, maybe some admin could update the last message in the thread (http://forum.xda-developers.com/showthread.php?t=1006571) you had posted on woot's discussion page. Either link here, or just update and say: hey, people got some woot gTabs in already and they are the 3389 version.
I read this above post, but have not received my woot gTab (so no idea what version I'm getting). Good thing I searched first and found this post. Just to put my mind at ease
Click to expand...
Click to collapse
i can't update it as the moderators locked it (trust me, I want to update it). I already PM'd jerdog to either open it up or delete it, as I don't think it's needed anymore. I'm not a moderator so I cannot do this, myself.
EDIT: It's been unstickied and updated. TheImpaler handled the unsticky / unlock.

roebeet said:
Clockworkmod is non-vendor third party recovery replacement, wheras "standard recovery" is stock recovery (this is what the vendor supplies).
But clockworkmod users do not get that update, as the program doesn't support updating the bootloader.
Click to expand...
Click to collapse
Thanks for the detailed answer Roebeet!
CWM not updating the bootloader is the main problem isnt it?
Also that it overwrites stock recovery.(True?)
If CWM overwites stock recovery, reverting to 3588 using CWM, might still not enable things like OTA update, right?
So, I see that CWM will work with current ROMS (except TNT Lite 5) and everyone will be happy till the newer ROMS come along based on 3991 or later. At that point, it will become a lot harder for people to get to the new ROM as the new bootloader will have certainly changed.
Alternatively, if people wait for a Viewsonic 3991 or later OTA update from Viewsonic, CWM will work again for some time until the bootloader changes significantly. (possibly).
So how does one get a new ROM without CWM?
I have searched some on the forums and I see
1. Use CWM, but comment out some "assert". This was used by people reverting to stock, and seems sketchy.
2. Use nvflash. Is there a walkthrough for this for Vegan/TNT Lite? I see one for going to bekit 's original image but not to any arbitrary ROM. Also this repartitions the SD, has this caused problems with OTA updates?
3.Using adb. Maybe 2 and 3 are related, but I think did see somewhere to get back to stock recovery using adb. Can we do a new rom update through adb, without risking breaking stock recovery?
I wish I had bought 2 gtablets, one to enjoy and one to tinker with

cbay said:
Thanks for the detailed answer Roebeet!
CWM not updating the bootloader is the main problem isnt it?
Click to expand...
Click to collapse
Correct.
cbay said:
Also that it overwrites stock recovery.(True?)
Click to expand...
Click to collapse
Yes, they cannot co-exist. Stock recovery (specifically 3588) will update the bootloader, I've tested this repeatedly. clockworkmod .8 does not.
cbay said:
If CWM overwites stock recovery, reverting to 3588 using CWM, might still not enable things like OTA update, right?
Click to expand...
Click to collapse
Not exactly. If you have cwm and revert to stock 3588, you might not have the latest bootloader (since clockworkmod doesn't touch that) but everything else should be reverted back to stock. But an important note: I've heard stories from users who used clockworkmod to revert to 3588 stock and, although it worked, recovery was actually broken. This happened to a lot of users who were trying to get back to 3588 stock before they upgraded to my later-pulled TNT Lite 5. This is actually the reason why I created the 3588 Recovery Pack.
cbay said:
So, I see that CWM will work with current ROMS (except TNT Lite 5) and everyone will be happy till the newer ROMS come along based on 3991 or later. At that point, it will become a lot harder for people to get to the new ROM as the new bootloader will have certainly changed.
Alternatively, if people wait for a Viewsonic 3991 or later OTA update from Viewsonic, CWM will work again for some time until the bootloader changes significantly. (possibly).
Click to expand...
Click to collapse
Possibly. Lets assume for a moment that the new firmware is a released "1.2" with a new bootloader. Once everyone moves off the "1.1" to "1.2", the issues with the bootloader will probably stabilize. Until there's a "1.3", of course.
And yes, this is all speculation. Viewsonic could throw us a curve balll with their next firmware.
cbay said:
So how does one get a new ROM without CWM?
I have searched some on the forums and I see
1. Use CWM, but comment out some "assert". This was used by people reverting to stock, and seems sketchy.
2. Use nvflash. Is there a walkthrough for this for Vegan/TNT Lite? I see one for going to bekit 's original image but not to any arbitrary ROM. Also this repartitions the SD, has this caused problems with OTA updates?
3.Using adb. Maybe 2 and 3 are related, but I think did see somewhere to get back to stock recovery using adb. Can we do a new rom update through adb, without risking breaking stock recovery?
I wish I had bought 2 gtablets, one to enjoy and one to tinker with
Click to expand...
Click to collapse
Right as the Wooters were buying their GTABs, I did a few things to help users out with recovery options.
1) I created a "3588 Recovery Pack". This is a flash update.zip that will add few sripts to your rooted 1.1-based ROM and will allow you to flip between clockworkmod and 3588 stock recovery with a minimum of fuss.
2) I added the Recovery Pack to TNT Lite 4.3.0 and gADAM 1.3.0, the two active mods that I support. So it's built-in there.
nvflash is a different animal. Think of it as a low-level format tool for when your device is messed up and cannot boot anymore. It's good to know about it and learn how to use it, imo - some devices like the Advent VEGA and even Viewsonic's Viewpad10s offer nvflash updates, only. nvflash is a tool specifically for Tegra 2 devices.
adb is a generic "remote shell" tool that is part of the Android SDK. You can find information about adb here or on other Android sites, and that would apply to the GTAB as well. you can make changes via adb, including flash updates, but you need to know what you're doing.

roebeet said:
2) I added the Recovery Pack to TNT Lite 4.3.0 and gADAM 1.3.0, the two active mods that I support. So it's built-in there.
Click to expand...
Click to collapse
That is great! I dont think I will have the patience to wait for Viewsonic to release an update beyond a few weeks.
I was debating between Vegan and TNT Lite, the Recovery Pack will push me towards TNT Lite, at least till I can get a 1.2 bootloader.
Thanks for all the help
--

Recently received G tablet from woot
I'm new to this and would like to know what the best thing to do to my viewsonic g tablet purchased from woot that makes it run the best way. I'm not sure how many and what mod's are recommneded. I've read alot of the posts here and figure TNT Lite (version?) is highly recommended. It is 3588, build frf91. Please give me the best mod's to do, what versions, and where I can find the step-by-step to make it all happen. thanks

[Q] I think I killed my Nexus S! Please help! (unlocking process/rooting stuff)

So, this is what has happened so far:
I googled for a small and easy to follow guide to unlock my phone so that I can later on install a custom rom. I followed the steps provided here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
What I didn't notice on the first place was the "UPDATE: DO NOT FOLLOW THIS GUIDE INSTEAD Please see new root method which works on all Nexus S and Nexus S 4G!" link. Don't ask why - really don't know.
The result was having my Nexus S stuck on a screen that shows Google logo on the middle and an unlocked padlock on the bottom.
It seemed, or to be exact, I figured out that, the problem was the .img file mentioned on some point in the middle of this.. tutorial.
So, I decided to follow the newer guide that can be found here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
Although all went well (didn't have to go all over the same processes up to the .img installatin point), I ended up with the same screen that shows Google logo on the middle and an unlocked padlock on the bottom.
I figured out that I could just install a rom at this point, and decided that I should go back to stock. So, I followed this guide here:
http://nexusshacks.com/nexus-s-hacks/how-to-unroot-nexus-s-i9020ti9020ai9023/
But, when I choose to install the .zip file, I get this error:
assert failed: "getprop ("ro.product.device") == "crespo" || "getprop ("ro.product.device") == "crespo"
E: Error in /sdcard/i9020t_i9023.zip
(status 7)
Installation aborded
..let me add to this point that I have bought my Nexus S from EU, it is an i9023. Let me also add that all I wanted is to flash an ICS rom and I think I have ended with a f****d device I don't know what to do with!
Any help, really, would be so much appreciated since I need to use this phone. I have a backup for calls etc but I need some smartphone features!

I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.

nickmv said:
I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.
Click to expand...
Click to collapse
Yes, I can enter this menu - there already. My model is an i9023GSM.

OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?

nickmv said:
OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?
Click to expand...
Click to collapse
You gave me the good news so, thank you for that. Now, I should follow this guide and come back in case I have a problem.
As far as the rom, I wanted to flash an ICS since I cannot wait any longer for Google to release the official update. But right now, anything that can get my device up and running would be really good!

Edit: nvm. >_<

kijp15 said:
Why don't you just use shabby's one click root. Simple & much easier. Saves all sorts of troubles.
Click to expand...
Click to collapse
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!

nickmv said:
but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
Click to expand...
Click to collapse
OK, stuck already. On Part 2 what I understand is that I have to open the CMD and copy-paste the path to the "tools" folder? Because this is what I do, and after - since this is what I have understand - I type "fastboot oem unlock" and I get "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
What do I do wrong?
EDIT:
Tottaly stuck on Part 2. It seems that there is no fastboot.exe file inside "tools" folder. I don't think the problem is something else - I'm sure I give the right commands since I tryied for fun another folder I have with fastboot.exe inside and it worked - to be exact it just gave me a FAILED messsage since device is already unlocked. Plus, regarding Part 3, Step 1, the first file for download is missing so I used the second link and downloaded 5023-cyan file. Hope this was a right move to do.
EDIT 2:
Ok, here is the story so far: I followed the guide given step by step. The USB drivers has been installed correctly so the device can be connected to the PC.
In the "tools" folder there was no such fastboot.exe file so I manually added one that I've found on the newer guide given on the 1st post. The unlocking process is failing because the device is already unlocked.
I did manage to install after this, the 5023-cyan.img file since this is the only link working from Part 3, Step 1. This gone well too!
Now, I couldn't go on with Part 4, I mean, I could not install the .zip file as it describes so through recovery mode I installed the .zip file succesfully (confirmation message to Nexus S screen).
I reboot and still get the same Google logo on the middle and an unlocked padlock on the bottom.
I cannot understand what I do so wrong? Oh, I'm so disappointed..

OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?

http://forum.xda-developers.com/showthread.php?t=1063664 or use ROM manager and select Stock ROM (you should then receive OTA upgrades to 2.3.6).
On the latter: You colud just back up different ROMs and switch between them using CW.

skatastamoutrasas said:
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!
Click to expand...
Click to collapse
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness

mixtapes08 said:
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness
Click to expand...
Click to collapse
Can you give me a CM9 kangs link since as new here, I'm kinda lost?

Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?

skatastamoutrasas said:
Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?
Click to expand...
Click to collapse
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img

kijp15 said:
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img
Click to expand...
Click to collapse
Worked just fine! Thank you!

skatastamoutrasas said:
OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?
Click to expand...
Click to collapse
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.

nickmv said:
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.
Click to expand...
Click to collapse
It did worth the hassle, that's for sure. Now I think it's so easy to unlock a Nexus plus I now have a little more knowledge regarding Android .
I will stick with CM 2.3.7 as it looks just fine. I don't care about warranty, I don't think I will ever need the official service for a software issue. Now I have to re-install my apps, re-sync my accounts and setup the phone the way I want it. It will take a little more time.
But I'm glad that I pulled this through - with your help of course! Guys, you rock!
I wish that I'll be as helpful as you at the near future.

Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
MAKE SURE THAT YOU HAVE CLOCKWORKMOD PERMANENTLY INSTALLED BEFORE DOING THIS. It saves time if you mess up. Also, make sure you get the latest gapps HERE
Instructions:
1. Go to clockwork recovery
2. Select data/factory reset/wipe
3. Select clear cache as well
4. Adv Mounts and Storage > wipe /system (note, this wipes android off the phone. It's a good idea since youre going from ver 2.x to 4.x)
5. Choose "flash from zip" (or whatever it's called.....NOT flash from update.zip)
6. Flash the cm9 update file first, then flash the kernel of your choice, then flash the gapps file.
7. Back out of the menu and select reboot.
Take note though, that the new ICS OS has incompatibilities with certain apps while GPU rendering is turned on, etc. It'll prob reboot on you sometimes, etc. For the most part it's stable, but that's completely subjective.
If you do run ICS, make sure you turn on GPU rendering in Dev Options. It takes full advantage of the GPU for UI animations, etc. Sometimes there's a stray app here and there that doesnt play nice, and you'll notice if the window looks really tiny or funny. Turning it off will fix the problem.

nickmv said:
Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
Click to expand...
Click to collapse
Two questions:
The link you give me to download the ICS rom keeps loading for ever. So, I choosed this one instead:
http://forum.xda-developers.com/showthread.php?t=1356228
Right or wrong thing to do?
It it essential to install a custom kernel? I ask because I forgot to copy/paste the .zip file and due to lack of time, I procceded without it, installing the ROM and G-APPS.

Firmware 5699 Released OTA

Viewsonic has finally released a update OTA for the GTablet:
http://www.viewsonic.com/gtablet/support.htm

Guess what this one bricks
Just like the one we had last April, this new one bricks as well. Mine doesn't even want to read the external sd card. I tried nvflash and it doesn't recognize it. Save this one and try it later.

Installed the Firmware 5699 OTA this morning. Upgraded with no problem.
After 10 months of no support from VS, I wonder why now? I wish there was a changelog for this...

No changelog. Wow. Never update firmware without at least reading the changelog....esp if system is stable

Great. Now give us official ICS or source code

Pawnty said:
Great. Now give us official ICS or source code
Click to expand...
Click to collapse
That would be very interesting.
EDIT: not going to happen though.

Your cool Viewsonic, STILLLLLLLLL android 2.2...

I feel like this is a more of a low blow than anything. Us as users ***** for literally an entire year and Viewsonic labels the gTablet as an archived product on their website basically fully dropping support for it. Now 2012 rolls around and ICS is finally making its way onto a slew of devices and Viewsonic drops another update to a Froyo rom? Really? That was 2 generations ago... Like the hardware is still there to do something with this device. Team Drh has been proving this as we continue development with ICS. Now if Viewsonic wants to help us push ahead with this mission, by all means please help us out. But dropping updates to Froyo is BS if you ask me. But hey, what do I know...I'm just a user with an "outdated" tablet.

fosser2 said:
But hey, what do I know...I'm just a user with an "outdated" tablet.
Click to expand...
Click to collapse
LOL! That's funny!

Changelog is up. Looks like everyone is being pushed to BL 1.2 now.
http://www.viewsonic.com/gtablet/support.htm

Ok I NVflashed my Gtab just for shticks and smiggles to see what this 5699 update was really all about...
Conclusion...GARBAGE! Plus it tells you to restart your Gtab and ends up having a broken android icon with an exclamation mark on the screen!!
Oh well...now Imma flash my PreAlpha ICS rom again! YEY!

ml_boston said:
Changelog is up. Looks like everyone is being pushed to BL 1.2 now.
http://www.viewsonic.com/gtablet/support.htm
Click to expand...
Click to collapse
Not much of a change log. They state over 40 enhancements, but then only list four.

arveeee said:
Ok I NVflashed my Gtab just for shticks and smiggles to see what this 5699 update was really all about...
Conclusion...GARBAGE! Plus it tells you to restart your Gtab and ends up having a broken android icon with an exclamation mark on the screen!!
Oh well...now Imma flash my PreAlpha ICS rom again! YEY!
Click to expand...
Click to collapse
Sounds like your GTab didn't take the update. It sounds a lot like the OTA update failures on Xoom's and TF's when its been rooted or modded.
Honestly though I do not see any visible changes. All code enhancements is my guess.

I am new and have only had the gtab for two months. I thought this is an update and I should download. Now my gtab doesn't work. I am not a techy by and stretch of the imagination.
I have done the power and +volume and it said recovery and had a wrench/screwdriver on it. Then it was coming on but stuck in the tap n tap screen and then turning off.
I only use to read and play games and will be nice to have on vacations or when away from home/work but now it doesn't work. I could use help.
Any help is appreciated. Wish I could take a class. Looked at viewsonic for dummies but even that is over my head.
Thanks for any help.

dleem said:
I am new and have only had the gtab for two months. I thought this is an update and I should download. Now my gtab doesn't work. I am not a techy by and stretch of the imagination.
I have done the power and +volume and it said recovery and had a wrench/screwdriver on it. Then it was coming on but stuck in the tap n tap screen and then turning off.
I only use to read and play games and will be nice to have on vacations or when away from home/work but now it doesn't work. I could use help.
Any help is appreciated. Wish I could take a class. Looked at viewsonic for dummies but even that is over my head.
Thanks for any help.
Click to expand...
Click to collapse
Do you know if your tablet was modified (custom rom, rooted, etc.) when you took the update? People with modified stock roms and recovery seem to be having this issue on another forum.
I would say the easiest fix to try would be to drain the battery completely (might take a while) if you can boot into recovery (power) + (volume+) or apx (power) + (volume-) and leave it on till it dies (edit - if you can boot into recovery try the wipe data/factory reset option if there is one, then try to reboot. That might fix it also). Keep doing that till the tablet won't turn on anymore. Then charge it and try turning it on again. If you are lucky it will reset your tablet to stock without any complicated fixing or flashing.
Remove your SD card if you have one before you do this. You will also loose any data not stored on your SD if you do reset it but hopefully it will work again.

Same Problem
I had this same problem yesterday after downloading the OTA update. I was able to restore the bricked device by holding the power for 5 seconds (figured it was shutting down in that amount of time) restarting in APX mode (power button and volume - simultaneously) and I did not see a screen response, I plugged in the USB cord and checked the safely remove hardware widget on the bottom right of windows system tray and could see NIVIDIA device. Therefore, I knew the GTAB was on and in APX mode. I then went to the rom of choice (stock tapntap) and double clicked the batch file for the ROM and watched as it went to the CMD prompt screen and transferred the file. I did have to run the batch file several times to get it to work...but it did. I downloaded the OTA again, and discovered the same results with the same fix. I will not download the OTA update a third time. Good Luck.

I had just put my VS GTab back to complete stock 1.2 4349 in anticipation of the ICS Rom release coming soon. My GTab showed a OTA update was available and I accepted the update. It downloaded and ran through the process with no issues at all. Some of the people having issues must have modified or rooted devices.
---------- Post added at 08:36 AM ---------- Previous post was at 08:34 AM ----------
dleem said:
I am new and have only had the gtab for two months. I thought this is an update and I should download. Now my gtab doesn't work. I am not a techy by and stretch of the imagination.
I have done the power and +volume and it said recovery and had a wrench/screwdriver on it. Then it was coming on but stuck in the tap n tap screen and then turning off.
I only use to read and play games and will be nice to have on vacations or when away from home/work but now it doesn't work. I could use help.
Any help is appreciated. Wish I could take a class. Looked at viewsonic for dummies but even that is over my head.
Thanks for any help.
Click to expand...
Click to collapse
http://viewsonic-gtablet-for-dummies.webs.com/
dleem this is not difficult. Sit down, focus and read. It has step-by-step instructions. Go to Code Red.

ml_boston said:
Changelog is up. Looks like everyone is being pushed to BL 1.2 now.
http://www.viewsonic.com/gtablet/support.htm
Click to expand...
Click to collapse
Yes. I can confirm this on my old device ( was running 1.1.3588 ). I went ahead and updated the tablet, and found out the exact upgrade path.
I'm for devices using firmwares older than mine, the first update will probably be to version 1.1.3588, and then from there, the rest of the updates.
The first update after 1.1.3588 is 1.1.3588+. After installing this update, the tablet will have be able to update to 1.2.5699 using the update program, or waiting for the notification.

yup.. downloaded find and dies on the install....I wonder if I take CWM off and do a factory restore if it would work.

Clear data/cache
To upgrade, you have to use stock recovery with 1.2 bootloader. Not rooted. No CWM.
In stock recovery clear data/factory reset, clear cache; otherwise, you'll get stuck. You will lose everything so backup with Titanium Backup.
I keep a copy of Titanium Backup and Amazon Appstore Apps on my SDCARD and SDCARD2 to install after installation and restore apps.
Plants vs Zombies crashes on this.
Pixel Rider on Slatedroid will eventually mod this with market and root to be named Detonator.
If you like stock, stability and camera, this ROM has a niche.