I had Vegan Ginger Edition running and it was working great. I decided to Factory Reset the tablet. I used Settings|Privacy|Factory Reset.
But it went into endless reboots, I think. What it was doing is that the screen that says Vegan Tab Ginger Edition comes and it does the animation (shocking and flashing), and it does this like 3 times and then the screen goes blank for a second or so and then the animation starts again, and so on, and it keeps on repeating forever and then it would turn off automatically.
I booted into recovery Clockwork Recovery, and tried to do wipe data/factory reset, wipe cache partition, etc, but nothing helped.
I eventually ended up in doing Wipe Dalvik Cache. Now it does not even get to that Vegan Tab animation. It now gets stuck at "Powered by G-TABDEVS" screen.
Any suggestions? Do I need to re-install? If so I guess I will have to copy the zip to SDCARD and then install it, since I can't boot at all. Is there any other option?
Ya, just reflash vegan ginger.
I reflashed it. It now moves on and does not stop at G-TABDEVS screen, but it is exhibiting the same problem. Repeated VEGAN-TAB GingerEdition screens.
What do I do?
I just flashed CyanogenMod, and even that exhibits the same issue. I even went in and did mounts and storage>format system as well as format data. And then flashed it. But still the same.
More bad news. I nvflashed bekit's original image. It now is showing the original big eliptical g-tablet logo as it boots up, but it continues to cycle between the birds and the gtablet logo.
CWM is also gone. When I try to go into recovery all it displays is the big triangle with exclamation sign for a second or so and then restarts the tablet going back into the endless cycle.
I am now totally stuck. Please help.
have you ever repartitioned your device using Clockworkmod Recovery?
I've seen the tablet just bootloop on the bootanimiation if you have never repartitioned. Mine did it and so did a friends of mine. Tablet working great for weeks, installed different ROMs then one day a reboot and it just loops the bootanimation. Repartitioned in CWM (2048/0) and the problem never returned.
Of course you need to get CWM back on. Read the threads on NVFlash and you should be able to just nvflash the clockwork image to the device to boot in to CWM. Repartition and reinstall your ROM.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
tcrews said:
have you ever repartitioned your device using Clockworkmod Recovery?
I've seen the tablet just bootloop on the bootanimiation if you have never repartitioned. Mine did it and so did a friends of mine. Tablet working great for weeks, installed different ROMs then one day a reboot and it just loops the bootanimation. Repartitioned in CWM (2048/0) and the problem never returned.
Of course you need to get CWM back on. Read the threads on NVFlash and you should be able to just nvflash the clockwork image to the device to boot in to CWM. Repartition and reinstall your ROM.
Click to expand...
Click to collapse
Thank you so much. I got out of this mess. I clearly remember repartitioning 2048/0, but looks like Android Factory Reset corrupted it or something.
For the record, this post helped:
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
shah123 said:
Thank you so much. I got out of this mess. I clearly remember repartitioning 2048/0, but looks like Android Factory Reset corrupted it or something.
For the record, this post helped:
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
Click to expand...
Click to collapse
Hahaaha, and for the record, my start here page code double red takes care of your problem. Not only that, I've also provided nvflash files with cwm pre-installed.
I swear, it's like people don't read the directions properly anymore.
goodintentions said:
Hahaaha, and for the record, my start here page code double red takes care of your problem. Not only that, I've also provided nvflash files with cwm pre-installed.
I swear, it's like people don't read the directions properly anymore.
Click to expand...
Click to collapse
Hey goodintentions, I know you have good intentions , but I have been working with gtablet mods for quite some time now. Usually when you have a bricked gtablet, you are desperately looking for a solution. That's why I hopped from Vegan to Cyanogen to stock etc within an hour or so. And when you have been working on things for some time, you tend to not look at anything that says "start here". Honestly I had never seen your page before, which by the way is pretty good and would have been a life saver if I had known it.
I wonder... what should I name the page as?
I promise you, my instructions work for 99% of the problems people encounter.
goodintentions said:
I promise you, my instructions work for 99% of the problems people encounter.
Click to expand...
Click to collapse
I have no doubt.
Related
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
i'm stuck in bootloop too.
I'm no expert, but just out of curiosity, have you tried to get back into CW and format your SD to 2048/256? Maybe the partition is hosed?
1st, try to FORMAT with this tools: http://forum.xda-developers.com/showthread.php?t=974422
you can change the image #9 with CW, once format done, when it reboot, you will have a message error in RED just power it off and on again, you will be in recovery mode, now follow the NVFLASH here:
http://forum.xda-developers.com/showthread.php?t=861950
also you can change image#9 to CW this will get you back to the base of stock VS rom
good luck
Wysdym said:
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
Click to expand...
Click to collapse
Can you get back to a state where you can at least get into CWM, even if it is still bootlooping? If so, go into the advanced settings and perform a fix partition (use the settings 2048 / 0). Please note, this will wipe any data you have on your /SDCARD folder (which is the flash card disk installed on your gtab, not the microSD card you may be using)
I agree with butch1326.
You can't move on to other roms until you know the G-Tablet is working right.
I would try to either nvflash or load the regular way CWM and just get CWM working right.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
Once that is done, then I would nvflash the bekit image as is described in a bunch of threads. That will get you all the way back to one of the old, stock setups.
If you get that far successfully, the get on wifi and the OTA should update you to
3588.
Once there, you can take a deep breath, do a bunch of studying on what has been working and what has not, and then move ahead.
Rev
P. S. --- Changing too much too fast is poison in the IT world.
butchconner said:
I agree with butch1326.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
QUOTE]
I was under the impression that 2048/256 was the default for the Gtab and that 2048/0 was used primarily for TnT Lite builds. Was I mistaken on this? I'd hate to be giving out the wrong suggestions.
Click to expand...
Click to collapse
From what I gather android in general is 2048 0. I believe stock gtab may have come with something else but never saw a reason why.
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
butchconner said:
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
Click to expand...
Click to collapse
Damn....I must be getting old. 2048/0 it is. My apologies.
Ronin916,
No need for an apology. It was what it was and someone improved it and it is what it is.
Enjoy.
Rev
SOLVED
For the replies and more, No.. cwm was wiped out and did not exist any longer so that was not an option.
This took a LOT of doing. I'm talking about over 4 hours of nvflash, replacing parts of nvflash with other parts of cwm .8 and more. I was walked step by step through by a few devs. Because they tell me that mine had "other" issues, it would be specific to my machine alone and probably not help anyone else to post all of it. (However, I did find an IRC for the dev chat and that made all of the difference) Thank you to all of you Roebeet, EJ, Bad, and all the rest!
I was told that you haven't bricked it until you pitch it in the water, so keep your heads up.
Thank you to EVERYONE who replied to me.
You are a great community of helpful gents.
i have the same problem as you! I need help=(
Come on man you gotta close a thread like this out! It leaves everyone else stranded by not doing so. Glad you got this fixed though.
I'm STUCK in the same spot.. are you ablet to post your fix? PLLLLEEEAAASEEE
HELP!! HELP!! Stuck in bootloop for days!!
Hello all,
I have been stuck in boot loop for two days now!! I have nvflashed about 50 times (even used the format utility too in the mix) no luck!! I want to flash back to stock, then update to 3588 and use either Illuminate or Roebeets Honeycomb rom.
If some one has had this problem, can you help with some steps to fix??
Please please help!! I am ready to throw the G-tab out the window!!
THANKS!!
Anthony
Have you tried repartitioning?
Try installing clockworkmod and fixing permissions?
Sent from my Droid using XDA Premium App
I would love to be able to re-partition or install CWM, but I can't get by the boot screen.
Is there another method other than NVflash??
Thanks for responding!!
You need to nvflash...
1) Use bekit's 1105 nvflash image
2) replace part9.img with the recovery.img from clockworkmod install zip
3) type in the command to nvflash but hold down the volume up key on the tablet while you press the return key to start it. Continue holding the volume up while the nvflash starts.
4) When the flash ends you should enter CWM recovery mode. Repartition and wipe everything
5) swap part9.img back into the nvflash image and nvflash one more time.
If you are still looping after that you'll need to force the tablet to load a stock update. It will require a little more tinkering with nvflash. Let me know if you need the additional steps.
This is my first experience trying to mod a device but everything I read said it was easy so I bought the Gtab and spent 4 hours yesterday trying to flash VEGAn-TAB GingerEdition STABLE RC1 but it won't boot.
The first thing I did was root the device following instructions from driod pirate (before I found XDA). I now know I didn't need to do that step.
After rooting it, I found this post with great step by step instructions for installing clockworkmod and flashing a rom. I followed the instructions to install ClockwordMod and the VEGAn-TAB GingerEdition rom. After trying to boot, it stuck on the ViewSonic splash screen.
I did some more research and thought I might need to downgrade the bootloader/tnt version so I followed these instructions and was able to successfully load the stock rom. I then followed the same steps above to install clockworkmod and flash the vegan rom. Again, when trying to boot, it just sticks on the ViewSonic splash screen.
Any ideas what I might be doing wrong?
Do I need to do a nvflash and try the process from the beginning again?
dw21 said:
This is my first experience trying to mod a device but everything I read said it was easy so I bought the Gtab and spent 4 hours yesterday trying to flash VEGAn-TAB GingerEdition STABLE RC1 but it won't boot.
The first thing I did was root the device following instructions from driod pirate (before I found XDA). I now know I didn't need to do that step.
After rooting it, I found this post with great step by step instructions for installing clockworkmod and flashing a rom. I followed the instructions to install ClockwordMod and the VEGAn-TAB GingerEdition rom. After trying to boot, it stuck on the ViewSonic splash screen.
I did some more research and thought I might need to downgrade the bootloader/tnt version so I followed these instructions and was able to successfully load the stock rom. I then followed the same steps above to install clockworkmod and flash the vegan rom. Again, when trying to boot, it just sticks on the ViewSonic splash screen.
Any ideas what I might be doing wrong?
Do I need to do a nvflash and try the process from the beginning again?
Click to expand...
Click to collapse
You need to follow the nvflash instructions on the developer page. Your partitions need to be fixed before gb roms will work
I suggest the first thing you do is setup nvFlash. I can assure you that you will need to use this utility at some point. It is very usefull and powerfully utility and is very easy to setup and use. http://forum.xda-developers.com/showthread.php?t=861950
once you set that up..i suggest you start from scratch.
So this is what I would do if i was in your shoes.
1. Install nvFlash and go back to stock.
2. Update to 3588 using OTA
3. Install cwm .8 on your tablet
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
6. Mount your tablet using cwm .8 and upload the rom you want to install
7. Install the rom you want and you should be good to go
(dont forget to reboot your device after that first boot.)
What is the risk involved with NVFlash? I've read a few complaints that their devices were bricked after nvflash. How do I make sure I avoid that happening?
dw21 said:
What is the risk involved with NVFlash? I've read a few complaints that their devices were bricked after nvflash. How do I make sure I avoid that happening?
Click to expand...
Click to collapse
Anytime you brick it, you can use nvFlash to un-brick it. Its just a matter of knowing what you are doing and reflashing it with the correct files. From what I have experienced, its pretty much impossible to brick these tablets once you have nvFlash setup. No matter how bad that situation is, I have always been able to recover using nvFlash(and I have been in very terrible situtations where I got a blank screen when i booted...turns out I was stuck in apx mode when i booted)
rbansal2 said:
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
Click to expand...
Click to collapse
Can you go into more details on these two steps? I know it's done with cwm but I want to make sure I do it exactly right.
worked for me
Thanks guys this worked great! For some reason I couldn't upgrade to 3588 it would FC at 50% but it works now!
clayvikings said:
Thanks guys this worked great! For some reason I couldn't upgrade to 3588 it would FC at 50% but it works now!
Click to expand...
Click to collapse
Awesome, that's great news! Welcome to the club!
rbansal2 said:
I suggest the first thing you do is setup nvFlash. I can assure you that you will need to use this utility at some point. It is very usefull and powerfully utility and is very easy to setup and use. http://forum.xda-developers.com/showthread.php?t=861950
once you set that up..i suggest you start from scratch.
So this is what I would do if i was in your shoes.
1. Install nvFlash and go back to stock.
2. Update to 3588 using OTA
3. Install cwm .8 on your tablet
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
6. Mount your tablet using cwm .8 and upload the rom you want to install
7. Install the rom you want and you should be good to go
(dont forget to reboot your device after that first boot.)
Click to expand...
Click to collapse
I did exactly this (minus step 1. as it was already a stock device) and I had exactly the same problem - gtab stuck at viewsonic splash screen. My unit was fresh outta the box and fully charged, and this was the firstht hing I tried to do with it. CWM installed without a hitch (yes, 0.8) and I repartitioned without fear (I had no data on it anyway). Did the wipes, mounted the tab and copied over the rom... all instructions I found on XDA for doing it. It still sticks at the splash screen.
So, to get a working tablet again, I used nvflash to go back to stock (though I have a superuser app now, which is odd for 'stock'), did the ota update to 3588, loaded Spark+ on it for a launcher and add the amazon marketplace app (looking for more free apps).
I still want to get VEGAn installed though, just wish I new why it was freezing up/not booting/not correctly installing or whatever the problem is.
If you have run nvflash you can now install Gingerbread roms as it fixed your partitioning. When you got stuck on the vs birds it meant your partitioning was wrong and you needed to nflash. If you did then your fine now.
The nvflash provided does not bring you to complete stock. If you want complete stock just flash the 3588 update.
I did the exact same thing you did, with the same result. Then I nvflashed and walked through the rest of the steps and I was quickly able to flash VEGAn-TAB.
dw21 said:
I did the exact same thing you did, with the same result. Then I nvflashed and walked through the rest of the steps and I was quickly able to flash VEGAn-TAB.
Click to expand...
Click to collapse
I've been watching the VEGAn-TAB logo flash and pulse at me for the past hour. Think I'm going to try to flash the ROM again...
EDIT:
Scratch that. restarted into cwm, cleared user data again, booted right into V. Going through setup screens now. Question though... If this was writtne for the G-Tab, then why does it still have the phone stuff in it?
was working but now it isn't?
++++i had to use nvflash for my gtab and it worked. I loaded vegan-tab 7.0 GE and it took "literally HOURS" to boot to the tablet setup page, after that it was working great until I rebooted it after 1 day of use and now i can't get past the "powered by g-tabdevs" boot page?????? any thoughts?++++
UPDATE: I repartitioned the sd card 2048/0 and that didn't work, then i cleared the dalvik (?) cache and the other cache and it booted up successfully (warning to newbs like me, this did clear all my data so back up everything)
SIDE NOTE: I love this website!!!
Two things I always do before I decide to try a new ROM, backup anything I don't want to lose, then go do a factory reset. When you install a new ROM, it doesn't automatically wipes all the partitions, especially the user data and settings. By leaving that there, you are allowing the ROM have access to that information which in turn, can cause problems because not every ROM setups the same. I have seen many people run into problems because they don't do a data wipe. If you do this, you will see a lot less problems in the future and if you do get a new install running but seeing FCs with a lot of apps, do a factory reset.
VEGAn-TAB GingerEdition STABLE RC1 Still In Boot Loop
Hi, I've tried doing as per what the instructions said about clearing the cashes and partition SD card sizing. I've load VEGAn-Tab 6 times already and everytime I still end up with a boot loop error. I just decided to use tntlite instead, but I really want to get this working. I noticed one thing as I was loading tntlite and the stock rom that when I go back to ClockworkMod v08 to mount “/system” and “/data”.
I see the following:
“unmount/system”
and,
“unmount/data”
which is right, but when after I load VEGAn-Tab
I see the following:
“mount/system”
and,
“unmount/data”
From what I've been reading this should not be the case. I'm not sure it this is related to my problem with the boot loop or not.
Please help!
So this time I'm going to be a little preemptive. I ordered a GTab like a week ago, spent the time waiting for it to get here doing a ton of reading so I could go ahead and get it flashed right away. It got here and I immediately ran into problems. I got CWM on there no problem and first flashed [ROM-AOSP]G-Harmony Gingerbread 2.3.3 with Honeycomb elements(UPDATED 4/17) with no problem. Didn't like it so tried to flash the CM7 nightly (which I have running on my evo and hero) and it kept getting stuck on the black screen with that just had "android" written on it really small. Since I hadn't anticipated running into something like that, I did even more reading. Decided to try some more roms and see if I had similar problems. Ran into similar problems with the vegan GB except it would hang on the powered by the "gtabdevs" screen or whatever it said. Vegan 5.1 or whatever the other Vegan one is I could get booted up fine though. So I read some mroe since I really wanted CM7. Discovered that I might need to re-partition, so went into CWM and repatitioned to what everyone was saying was the correct settings. Still a no go and got stuck on android screen. So after even more reading I kept seeing everyone saying NVFlash. So I found it, downloaded everything, read the sticky post on how to do it like 4 times before trying it, then gave it a shot. Put the tab into APX mode (vol- and power) and flashed everything and then when it was done, it was stuck in the APX mode. Very irritating considering I had only had it for about 6 hours. Anyways, sent it back and am getting a new one. It will be here tomorrow morning.
Sooooo, after that long winded explanation of everything, here is my question... How the **** can I get CM7 on my tab without wrecking it again? I did a ton of reading, and nothing I had seen helped at all. Everyone says wipe this and wipe that, or mount these then wipe those, or nvflash then do it and so basically I'm just not sure what to do. I WILL NOT use the nvflsh again and risk getting the APX loop, so any good advice would be most appreciated.
Thanks in advance
I just email walked my sister through installing CM7 on her new gtablet.
Have CM7harmony7.02.zip (or whatever.....7.02 is latest stable release....there is a newer nightly though if you prefer that), the gapps.zip on your computer.
install Clockworkmod recovery on your tablet like you did before.
Boot into CWM and partition sd card, 2048 for first partition and 0 for the second one.
attache via USB to your computer, mount usb option in CWM and copy the ROM.zip and the Gapps.zip to your tablet. Eject tablet from computer (USB eject) and unmount in CWM.
- wipe data/cache (factory reset)
- advanced, - wipe davlik cache
install .zip from sd card
(install the ROM, then choose to install .zip from sd card again and install gapps).
Reboot.
Make sure your tablet is NOT running OS 3991 (very unlikely) or 4349 (possible though unlikely) before doing any of this. (ie...boot tablet out of box and check it's OS version in settings).
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
ix3u said:
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Correct, downgrade and then proceed.
Even though I'm 100% sure that at some point of me trying last time that I did in fact do all of those steps, it was a no go.....But this time, I'm sitting here watching the CM7 boot screen
Thanks a ton
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
venkavis said:
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
Click to expand...
Click to collapse
Hopefully a guru can answer this question. A guru I am not..
But what I think you did should not be an issue. I typically wipe data and then wipe cache partition when flashing a new ROM. sometimes I wipe cache and data just to get the ROM running from scratch again. But this should not affect booting..
One thing I think might be the problem is that you have a new kernel from one of the newer nightlys. Recently they added perhsoots May kernel. Whenever a new kernel is included in a nightly you usually need to clear dalvik cache. this is in CWM under advanced.
I hope this helps.
Tried clearing dalvik cache. No change.
Going back to stock and see.
Copied the stock ROM file and used the CWM to do the update. Now the g Tablet is gioing into a Boot loop. It Tap n Tap then displays a animated icon and after a minute repeats the same.
Tried the recovery option and its going into an installing loop again. Not sure how to get out of this.
Does anybody have this experience before?
Is this bricked now? Call viewsonic support? I am not sure if they support, They may say its nor under warranty.
Just to remind you, the last effort to resolve this is to NVFLash it...
Have you tried CWM method twice or repartition it and do it again? It's a tablet for you to enjoy your Internet, reading, video but not flashing all day long..etc
To pass it quick, if I were you, I would NVFlash it back to 3588, put back my favorite ROM, reinstall the Apps I like and start Internet browsing, converting movie (so I can watch on the road), reading news...
good luck!
rcjpth
After this I definitely agree. But seems I am stuck again. Hope this is the last time.
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Called Viewsonic support and the tech support person pointed me to below post on XDA
http://forum.xda-developers.com/showthread.php?t=1036956
When I read the article it talks about a locked boot loader. Does is mean if I use this and fix the tablet, I will not be able to do any more rooting?
venkavis said:
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Click to expand...
Click to collapse
So you also tried the alternate file, nvflash_gtablet_46_2010112600.zip? That's what worked for me, but I also have to swap partitions 7 & 8 to get CM7 working again.
Since I'm a glutton for punishment, I wiped my cache from nightly 75 and didn't run into any problem.
Just downloaded the alternate zip and flashed again. Having the same looping issue.
Seems like I Have to send it to viewsonic only. The technician said there is a $75 charge to fix.
OK:
Briefly, Running fine on VEGAn 7 RC 1 with Pershoot's latest. When the Tab was running and booting, I made a full backup in CWMod.
Screwed around with some permissions and once I rebooted, ended up at VEGAn Tab pulsating Boot Screen. It would do its thing for a minute or so, screen would go blank and then return immediately to the same VEGAn Tab screen (i.e., not a full boot).
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
I searched the forums a lot, so either I am not very good at searching or this has not been addressed.
Advice would be appreciated, as this is not the first time I have been here and want to learn if there is a way to repair it (obviously, I can reflash ROM+Kernel) restore via Titanium and only have a little manual recovery left to do.
Thanks!
I had the same thing happen to me while i was changing around roms. I know its not the exact thing but regardless. Anyways, try mounting your tab in cwm as USB and pull your back up off the tabs memory. Go back to cwm and wipe everything, then repartition to advised settings. Remount your tab as usb and put the back up back on your drive and restore again. It may work.
Sent from my VEGAn-TAB using Tapatalk
iamjakecali said:
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
Click to expand...
Click to collapse
If its something simple, clearing the Dalvik Cache in CWM might fix it.
I appreciate the ideas. Unfortunately i have tried then all. One of the times this has happened i was messing around with the old two taps xoom. Of i knew anything about the really technical stuff i might speculate something to do with boot loader.
Oh for anyone here who bricks, Don't freak... sometimes i do several times a day and have always come back from it ... mostly using the advice of all the brilliant people here, occassipnaly by messing around with adb, and once i let my monkey push random keys since he had already managed to compose a sonata...