I tried installing CM7 before, and screwed up the recovery but managed to fix it using NVflash. I then updated to 1.1 3588 or whatever, then flashed CM7, worked fine.
Saw Vegan ROM so I wanted to try it, and flashed it. I then wanted to check out the new market but the Market kept Force closing. So I tried using CWM to restore the previous Vegan rom but I got a boot loop.
So I nvflashed and tried over from the very beginning but now I can't even get the stock firmware to load. And now I can't even connect in APX mode.
NV Flash says USB device not found.
What do I do...
barqers said:
I tried installing CM7 before, and screwed up the recovery but managed to fix it using NVflash. I then updated to 1.1 3588 or whatever, then flashed CM7, worked fine.
Saw Vegan ROM so I wanted to try it, and flashed it. I then wanted to check out the new market but the Market kept Force closing. So I tried using CWM to restore the previous Vegan rom but I got a boot loop.
So I nvflashed and tried over from the very beginning but now I can't even get the stock firmware to load. And now I can't even connect in APX mode.
NV Flash says USB device not found.
What do I do...
Click to expand...
Click to collapse
So, you can get ot APX mode on the Gtablet, right? You might need to reinstall the drivers on your PC. This happened to me before. Try reinstalling the drivers and see if it detects it.
Okay I'll try that, thank you!
I don't think I'm going to attempt getting the newer market if I manage to fix this lmao
Update: I got stock firmware loaded and it turns on now thank god. But when I go to update the tablet to bootloader 1.1 3588, it downloads then reboots, but when it reboots it just shows an android guy with an exclamation mark in a triangle.
Anyone know what this means?
Edit:: Apparently you need an SDcard inserted. Maybe that was my issue this entire time :S
I'm stuck in a boot loop at the Vegan-Tab GingerEdition screen. I think I'll just leave it for a while? It's been playing the same animation for the past couple minutes.
Or is there something wrong with my installation?
Okay last update, finally fixed the tablet.
For anyone else having the same issues here's what I did to fix it.
I put in an SDCARD so that I could fix my nvflash of stock boot loop error. Finally loaded that ROM, rebooted and got bootloader 1.1 and moved vegan zip to my sdcard. I rebooted, installed vegan ROM, then as I was restarting my tablet I removed my sdcard and it works perfectly.
Of course I tried a bunch of random stuff in between, but I think that's what did it for me.
Thanks for your help TJ
Okay so I wanted to try Brilliant Corners 1.3 ROM so I decided to flash back to stock TNT, update to 1.1 3588 then flash 1.2.
But when I flashed stock TNT it now gets stuck in a bootloop and I have no access to boot into recovery. Just shows a triangle with an exclamation mark. I tried with and without a memory card inserted. Anyone got any clues what I should try flashing now?
Edit: reflashing CWM finally worked. Repartitioned the SDcard now trying to reflash stock TNT
It's curious to me why sometimes I have to flash 3 or 4 times before it will work?
Related
I install the clockworkmod for set up the GTAB rom...
but now i want to return to the stock recovery...so how to uninstall clockworkmod?
thanks!
savage,
You install CWM to replace the stock recovery. Therefore, you have to re-install the
stock recovery. If you were using a stock rom like say 3588, you would just reinstall
the rom again and let it overwrite CWM.
But since I don't know what rom you are using, you need to check the source of
your rom, make sure it contains the stock recovery -- and then inquire of the issuer
of the rom whether or not you should re-install or do some other special procedure.
Rev
thanks！ Now i am using the VEGAn-Tab Build rom~
so what should i do next?
sorry for the confusion~
GTAB ROM is not granular enough - you running stock or a modded ROM? If so, which ROM?
I can reply for TNT Lite 4.3.0+ or gADAM 1.3.0+ - there's a script setup to go back to standard recovery. If you are running either of these, please see my first posts on those ROMs for instructions on what to do. Again, this is only if you are running TNT Lite or gADAM.
You can also attempt to flash standard recovery using a build 3588 standard recovery firmware image in PART3 here: http://forum.xda-developers.com/showthread.php?t=1005080
savage,
EDIT: roebeet answered you first so I'll just stand by and see what y'all do.
Good luck!
Rev
thanks！ Now i am using the VEGAn-Tab Build rom 5.1.1~
so what should i do next?
sorry for the confusion~
problem with installing CWM
I got my gtablet yesterday and tried to install CWM v.8 using external micro SD card. It looked like it was half way done because it could not reboot by itself and stuck at a screen asking for reboot. So I selected reboot but it did not reboot. I had to force it to close. When I pressed volume+ and power, it had this message on the upper left coner: Recover key detected, booting recovery kernel image and 3 birds in the middle of the screen. It stuck there forever without doing anything. I only installed Z4root and nothing else. How can I remove the half-done CWM and redo it again. If I can do it again, what should I look out to avoid the same error?
yu203964 said:
I got my gtablet yesterday and tried to install CWM v.8 using external micro SD card. It looked like it was half way done because it could not reboot by itself and stuck at a screen asking for reboot. So I selected reboot but it did not reboot. I had to force it to close. When I pressed volume+ and power, it had this message on the upper left coner: Recover key detected, booting recovery kernel image and 3 birds in the middle of the screen. It stuck there forever without doing anything. I only installed Z4root and nothing else. How can I remove the half-done CWM and redo it again. If I can do it again, what should I look out to avoid the same error?
Click to expand...
Click to collapse
If you got your tablet yesterday, then it probqbly had firmware 1.2.4349 on it, which is a 1.2 bootloader firmware. You tried installing a CWM made for a 1.1 bootloader. how much research did you do prior to modding? Seeing as you installed Z4root, I'd imagine that you didn't do much, as it's not needed at all to root your G-tab.
go to http://viewsonic-gtablet-for-dummies.webs.com/ and start reading at "START HERE" to get an idea of what your dealing with, and what you can and can't do...look through the entire site!
to get out of where you are now, and back to a workable base, follow the "CODE RED" instructions here: http://viewsonic-gtablet-for-dummies.webs.com/
Lastly...don't do anything else silly until you've read and understand all of the instructions on Goodintentions site...it's a GREAT resource and should be a pre-requisite for all new G-Tab owners.
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!
Okay, here's the story.
I rooted my phone, turned S-ON, and installed Cyanogen 7 RC-1. So far so good.
Next I threw on ROM Manager, and got the premium version. I updated CWR to 5.0.2.0. And then went to play.
Well, first thing I noticed was ROM Manager kept erroring out when it rebooted into recovery. The error report is something about being "unable to locate dev/tty0". That was when I noticed something.
In ROM Manager, it says Clockwork is updated to 5.0.2.0
But in Recovery Mode it says 2.5.1.2
So far, I've tried "Erase Recovery", flashing to 3.0.0.8 and seeing if that worked (it didnt'). Then i tried going back up to 5.0.2.0. That didn't work either.
I tried a manual instal of 5.0.2.0 and the system didn't even recognize the file, so I probably did something wrong there.
I'm just lost. Can anyone help me figure out what I'm doing wrong? I just want to flash some ROMs with up to date soft-/firm-ware.
new version is buggy
i had an update for my clockwork mod when i tried to download a rom so installed the updated clockwork but in the end i found the new version 5 to be very buggy but if you want to try just try installing another rom (do a nandroid backup first) and it should install the new recovery but in my oppinion i wouldnt bother upgrading why update something that works thats the common saying
Well, in this case, I'm trying to upgrade from Cyanogen (which I've backed up), to Synergy's GingerSense RS1 for the Droid Incredible. However, while it flashes the ROM, it hangs on the boot up screen when rebooting, so I have to go back to Cyanogen. What got this whole thing started was figuring out what I had to do to get that working.
I'm on HBOOT 079, CWR 2.5.1.2, and none of ROM Managers automated features work because of the "Can't located /dev/tty0" function. The only advice I could find online for that was that 2.5.x is too old, and I need at least 3.0.0.8 to load some of these ROMs.
Small error, I didn't run "unrevoked-forever" so I'm not S-OFF yet.
shadowfyre26 said:
Small error, I didn't run "unrevoked-forever" so I'm not S-OFF yet.
Click to expand...
Click to collapse
You did say you "turned S-ON" but really you just, as you said, didn't have S-OFF. So I'm guessing your problem was solved when you got S-OFF and tried again right?
Yup, I just fixed the S-ON issue into S-OFF, and lo and behold it worked.
*looks around sheepishly* Let us never speak of this again.
i installed cm7 on my touchpad last week and everything went fine. so i tried to install it on my friends 32 gb touchpad and i get stuck in a bootloop. moboot seemed to install fine becuase i have the boot menu working, cwm works, but when i try to load cm7 i get the green pic that says cyanogenmod loading but after that it goes back to the hp logo and starts over. i can boot into webos just fine but cm7 gives me the run around. ive tried doing a factory reset, wiping the cache and dalvik cache from cwm but nothing. i even tried making a nandroid backup from my 32 gb touchpad and tried to copy that to my friends touchpad but i got an error in the restoring process. ive also tried reinstalling the zip through cwm and through the acmeinstaller. do i have to doctor it and try again? has anyone run into this problem?
thanks
I have the exact same problem on my touchpad. I've tried every single option I can think of (I've reset everything, re-installed WebOS 5 times, cleared all caches, attempted to install from zip, etc.), at one point I did have it boot into Android once, but when I came back the next morning it had rebooted and was sitting at the CM7 screen frozen and wouldn't boot back into CM7. I'm thinking it has something to do with corrupt memory on a certain sector of the flash, so I've been looking for a way to format the entire partition and then try a WebOS doctor, but there doesn't seem to be any information on it. So... I'd say we're stuck for now.
I installed alpha 1 and it was working well with the usual hiccups. Then I backed up alpha 1 and flashed alpha 2.1 and it installed.
The update was working great and then I decided to check the reboot to Web OS to check how things work. Web OS worked great then I booted to cm7 and got the dreaded boot loop.
Tried reflashing over and over but same result. Luckily I had backed up first alpha so I restored it and it did boot loop again, but only once this time,before booting into rom.
So I believe the issue has something to do with alpha 2.1.
Sent from my HP Touchpad using xda premium
Could be, my one successful boot in Android was in Alpha 1. I may be experiencing a somewhat different issue as mine only boot loops sometimes, others it just sits with the CM7 circle spinning until I force it to restart. I'll see if I can get Alpha 1 to work again.
Doin some Googling I found a thread on Google code with people that have the same problem, no fix as of last night when I checked but I subscribed to the thread to Ger notified when it is updated. Don't know if xda will allow a link to the thread so if you want the link pm me and ill send it to you
Sent from my PC36100 using xda premium
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2