after i nvfalsh my tablet it wont boot it gets stuck on the tap and tap logo after a few minutes it turns black. i cant even get into cwn it freeze on the viewsonic logo. i reallt need help
d9700380 said:
after i nvfalsh my tablet it wont boot it gets stuck on the tap and tap logo after a few minutes it turns black. i cant even get into cwn it freeze on the viewsonic logo. i reallt need help
Click to expand...
Click to collapse
Did you re-flash CWM?
Do you know what bootloader you're on?
I'm not an expert (so take my advice for what it's worth), but if it were me, I'd boot into apx mode again, re-NVFlash it with the version of NVFlash that doesn't have CWM just to eliminate a possible issue. If that works, then I'd either NVFlash it with the version with CWM, or just install CWM.
If you're not sure which BL you're on, I'd just try one, then the other if the first one doesn't work. I've always been very careful about following the instructions about only NVFlashing from OEM 1.1. to 1.2 and vice versa, but yesterday I forgot which version of Clemsym I was on and NVFlash-ed 1.1 over 1.2 aftermarket ROM. So at least in my instance it wasn't the end of the world.
This is the exact issue I'm having. EEK! Trying hard not to freak out.
Glad to have some good responses. Now to figure out where things went horribly wrong. and since the Tablet was originally my husbands, I don't know which OEM it was on originally (and he doesn't recall). Any of the ROMs that have been placed onto it are on both branches.
I've tried re-NVFlashing based on the one I downloaded (from the main thread on the topic). Guess my best bet is to try one from the other branch.
Related
Hello, I just bought my G-tablet and I have severely screwed it over. First, I rooted it and installed CWM, (It went fine). Then I flashed Cyanogen 7, following their wiki full update instructions. It was running fine till I found out that for some reason, my computer nor the tablet even knew it had an SD (Computer found nothing, File explorer on tablet had nothing) coupled with the fact Gapps refused to install, I figured this would be solved in a wipe then another flash. Nothing was different. So I wiped again (seemed to have froze during) but the flash of Vegan 5.1 seemed to have went well... for now. However, trying to install Adobe Flash via the preinstalled android market, it wouldn't install. It kept saying download unsuccessful, for every single app I tried. (no it's not an network problem). Being the noob I am I started following random googled XDA threads on how to fix this. I partioned 4gig from my sd to see if that would fix the market problem. I got stuck in a bootloop so I was forced to reflash vegan. When I did, I found out that when I tried to install anything it said something along the lines of "Not enough space" knowing I had 13 gigs of memory leftover, I figured I'd try rebooting. Got stuck in bootloop. Then followed yet ANOTHER googled guide (droidpirate brick fix) and now I can't even access CWM. It just loads as IF it were going to CWM but then shows me a /!\ caution sign then instantly turns off. When I normally start it, it goes into bootloop. when I try to get to CWM (holding volume up, power) it goes to a useless flash that I presume just fails, then brings me back into the bootloop. As far as I see, I have no way of fixing this...
I know this is so much to read, so in a brief explanation.. I'm in a bootloop, cannot get into CWM (brings me to a failed flash then back into boot loop) and am in dire need of assistance Please help me
Go read the posts on nvflash and learn how to use it. It is your friend!!
IndyLateNite said:
Go read the posts on nvflash and learn how to use it. It is your friend!!
Click to expand...
Click to collapse
NvFlash is currently not working for me, I don't know exactly where I messed up but my computer already has the drivers to read the tablet. when I run the .bat, it doesn't seem to do anything.
Scratch that, got it to work. I didn't extract one of the folders entirely. But my tablet is still stuck in bootloop even after this? what now?
IndyLateNite said:
Go read the posts on nvflash and learn how to use it. It is your friend!!
Click to expand...
Click to collapse
Take this with a grain of salt, as I learned it is not 'always' your friend
Now it's just on the stock Viewsonic birds and Gtablet logo bootloop...
Even after I NvFlashed it... Still can't access CMW.
Any suggestions?
Nvm, I got it to what appears to be working. (and I just about jizzed all over my tab.) Thanks so much. Saved me a beating from my parents.
Hi,
Ok so I have a g-tablet that I got stock/retail box. I flashed it with VeganTab 7 RC1 Stable (The latest one) and it was working fine for a few weeks. I wanted to give it away as a present so I decided to go into the settings and "Restore Factory/ Completely wipe data" in Gingerbread and delete all data because I didnt want the new owner to have my google login and stuff.
After this, the tablet rebooted and was since STUCK on the VeganTab booting animation. I tried everything... I reflashed it with CWM ... nothing
I tried using nvFlash to just put the damn thing into Factory defaults (the viewsonic interface) and after nvFlash I just get a Viesonic/Gtablet splash screen boot loop. I cant seem to get this device to work.
Is this a expensive paperwight now???
SOLUTION IS HERE: http://forum.xda-developers.com/showthread.php?t=932157
Found it myself,
Sorry for the thread lol but it may help people who have identical problem.
I NEED looping help
lambergino said:
Hi,
Ok so I have a g-tablet that I got stock/retail box. I flashed it with VeganTab 7 RC1 Stable (The latest one) and it was working fine for a few weeks. I wanted to give it away as a present so I decided to go into the settings and "Restore Factory/ Completely wipe data" in Gingerbread and delete all data because I didnt want the new owner to have my google login and stuff.
After this, the tablet rebooted and was since STUCK on the VeganTab booting animation. I tried everything... I reflashed it with CWM ... nothing
I tried using nvFlash to just put the damn thing into Factory defaults (the viewsonic interface) and after nvFlash I just get a Viesonic/Gtablet splash screen boot loop. I cant seem to get this device to work.
Is this a expensive paperwight now???
Click to expand...
Click to collapse
I cannot get out of this same loop. I am so confused as to what to do. I have nvflashed and it just keeps looping.
Can someone please help me? I am begging.
My site start here code red. Look at signature.
Are you doing a factory rest after nvflash? I think it is impossible to hard brick....or near it anyway
Sent from my HERO200 using Tapatalk
Can't get CWM to even install
goodintentions said:
My site start here code red. Look at signature.
Click to expand...
Click to collapse
I've followed all the instructions for installing CWM to a T but the the boot recover kernal image won't do anything. It just sits there and won't load CWM from the microSD card. Does the card need to have some sort of special formatting (FAT, FAT32, NTFS) to be recognized?
My Vewsonic G-Tablet is just stuck in the boot loop with the birds screen and then the G-tablet initialization screen and then it reboots.
Gary
I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
Thank You in advance for any help.
I have a stock GTablet with the latest updates. This morning while watching an mp4 file the tablet powered off.
Now when I try to power on the tablet, the Viewsonic logo appears then the TapNTap starts to load, the N logo apears then disappears then appears again then the tablet shuts off.
I tried wiping/factory reset the tablet but it still does the same thing.
I have no idea how to remedy this.
daytron1 said:
Thank You in advance for any help.
I have a stock GTablet with the latest updates. This morning while watching an mp4 file the tablet powered off.
Now when I try to power on the tablet, the Viewsonic logo appears then the TapNTap starts to load, the N logo apears then disappears then appears again then the tablet shuts off.
I tried wiping/factory reset the tablet but it still does the same thing.
I have no idea how to remedy this.
Click to expand...
Click to collapse
Try going to the viewsonicgtabletfordummies website. Read the information there (lots of good info) and start at "Code Red" on "Start Here" page. I'm assuming you are on the 1.2 bootloader if you were on the latest stock update. If you don't mind having a non-stock recovery (CWM) use the NvFlash 1.2 with CWM pre-installed, otherwise use the one without. Follow steps 1-4 and stop at ROM (step 5, unless you want to try one of the great ROMs available for the gtablet! I am using Beastly-Clemsyn and Cyanogenmod 7.2 and they work great for me). If you want to install a ROM or want the advanced recovery features you will want CWM installed. For example, this could have possibly been fixed using a backup created with CWM, or with data wipes, etc without an NvFlash. Point is unless you are a "pure stock" type of person or you wish to return the tablet, CWM is a much better recovery.
When the tablet first boots back up (this can take a while the first time) let it sit for a while to rebuild the caches. Then try taking the OTA update again if you don't want to try out a ROM. Don't worry this all looks a lot more difficult/scary than it really is! Just make sure you read everything twice and don't skip any steps.
Thank You for the path to running again. Tried code red but it did not work. Going to try code double red but I need to charge the tablet first.
I think the easiest, but time consuming, way to recover would be to nvflash the stock rom, or a custom rom.
gTablets are good for being able to break, then rebuild.
Thank You again, following the double red instructions worked.
daytron1 said:
Thank You again, following the double red instructions worked.
Click to expand...
Click to collapse
Glad to hear I could be of some help and your tab is working again! Thank you also for reporting back with what worked for you.
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.