Everything was great.. did the update rebooted gtab worked great. Has always been stock. I shut it down and when I got home from work i hit the power button and I get the viewsonic birds then the tap n tap logo then the n just stays there and that is it has been stuck on the n for hours. I turn it off and back on and the same thing. Any advice would be appreciated.
Thank you
Have the same problem on stock Gtab.Mine gets to the birds and sticks.Tried holding power and volume up at the same time, but won't reset.Can't discharge the battery because it still goes into sleep mode after 10 min.Computer won't read when plugged into USB.Bought on Woot so a return will be a major p.i.t.a. I am new to Android devices
and was just getting enough balls to try rooting and flashing!!! FML
Yea bought mine from woot also... I liked the stock rom was also afraid to try to load a new rom. Looks like I will be sending it back
hvideo1 and sepder,
You have a choice to make. What both of you have is called a "boot loop".
Sometimes they happen because somebody does something wrong -- and
sometimes like in your case they just seem to happen.
You can return them if that is your desire -- or you can try to fix them.
Usually if one partitions the tablet and cleans it up, it can be fixed. But
that means you have to do some quick learning.
First, you have to get back to a fully stock, hopefully working version. Look
at the following procedure -- which we wrote hoping everyone would be able
to understand and use:
http://forum.xda-developers.com/showthread.php?t=861950
If you complete this procedure and the reflashed stock version works, then
we can load a program called CWM and do the partitioning and cleaning. If
the boot loops persist, then a second choice is to nvflash CWM and use it
to partition/clean up.
http://forum.xda-developers.com/showthread.php?t=865245
http://forum.xda-developers.com/showthread.php?t=1030042
The threads above give you more info on the various procedures.
Post back here what you decide to do or if you have questions.
Rev
I would try a simple data wipe first. Much easier and less invasive.
http://forum.xda-developers.com/showthread.php?t=1030915
Thanks for the replies. I don't want to send my gtab back so I'm reading both post and going to see what happens. I will reply back (hopefully with the gtab) Thanks again
I'm in the same boat as hvideo1 and sepde
Already tried the nvFlash first method mentioned by butchconner but can't get past the "Booting recovery kernel image" message, just sits there on the viewsonic splash.
Going to read and try the "CWM and do the partitioning and cleaning" next.
Appreciate everyone's help!
lrgche,
To NVFlash, you have to press Power/Volume - to activate APX. It will usually come
up with the white screen and then turn black.
"Booting recovery kernel image" indicates you may be pressing Power/Volume + , which
starts up Recovery -- a different process.
Go back through the procedure again and double check that everything is right and
it should work.
Rev
K J Rad said:
I would try a simple data wipe first. Much easier and less invasive.
http://forum.xda-developers.com/showthread.php?t=1030915
Click to expand...
Click to collapse
This worked for me. Thank you back up and working. the only reason I didn't go the other way was because I didn't understand alot of reading and just confused me (not hard to do)
Lol. Thanks to both of u
hvideo1 said:
This worked for me. Thank you back up and working. the only reason I didn't go the other way was because I didn't understand alot of reading and just confused me (not hard to do)
Lol. Thanks to both of u
Click to expand...
Click to collapse
Glad to help. You should learn that other procedure if you plan on doing any serious modding in the future though. It may become necessary next time.
Related
Im going to lose my mind! I've searched and read and found no real answer..... Is there anyway that I can get my phone out of the boot screen?
Ive downloaded and rooted before and never had a prblm! I download this certain Rom Lastnight and all of a sudden my phone is stuck on the boot screen! I've tried everything i can with it and no luck. Does anyone have some type of info on what i can do or is there no hope for my poor lil droid?
Please let me know!
Thanx in advance!
Have you tried a battery pull? Pop that out and back in, reboot into recovery and restore your nandroid back up. Should be fine from there...
What I do when this happens to me is pull the battery, wipe my phone, re-apply the rom, then reboot.
-If that does not work, then revert back to your nand backup.
Thanks for the ideas but I tried both of those actions first and got nothing in return. This sukks! I even tried to go back and load the PB00img zip tha i had and no go. I'm guessing that i Bricked this dam Phone!
Back to the Blackberry! Damn!
Do you think its possible that i can load a new Rom and try to boot the phone into recovery and flash that zip? The problem seems to be my boot screen! I've seen post with people with similar "situations" <--------lol (not From Jersey shore) and tried those methods and once again nothing.
Sucks that you are still having this issue. The next step I can think of would be if you have SDK set up then once it is stuck on the boot screen, run a logcat and post it here so someone that is smarter than I can figure out where you are running into problems at. You'll need to navigate to your SDK/tools folder (in the Command window of course...) and then once there just type in: adb logcat .
This will result in a myriad of crazy computer language stuff. Should be able to tell us something at least.
First, take a deep breath; your phone is not bricked. Far from it in fact.
Second, prove to yourself that it isn't bricked by booting it into the custom recovery:
Power it off, and then hold down Vol-Up (first) and the End (second); keep pressing both buttons until the three skating droids have appeared. The custom recovery menu should pop up about 10-12 seconds after that.
Third, download "some other certain ROM" (I get to be as vague as you are, right?) to your PC, and get it to the root folder of your SD card somehow. Look up "USB-MS toggle Amon_RA" if you don't already know what that is.
Fourth, flash that "some other certain ROM" and prove to yourself that your phone is not bricked, making sure that you perform a "Wipe data/factory reset" first before you flash the ROM.
Then, after you've shown yourself how it is possible to do these steps, go back and try to figure out why the other "certain ROM" doesn't work on it's first boot. Try popping out the SD card before you boot it to see if that is the trouble.
bftb0
@es0tericcha0s, Thanks for the response but instead of doing more harm to the phone i just took it to VZW, (Kinda) Explained what happen and they switched it out no prob.
@bftb0 lol Be as Vague as possible.... I didn't want to say any particular Rom for the simple fact that who ever did the Rom i'm sure worked hard at it, And evevn tho i'm not new at this, it could very possibly be my mistake somewhere in installing it! SO I choose to respect the XDA and The Dev But thanks for your awesome response! (no Sarcasm intended) lol
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.
I have gotten a g tab from my father in law after he tried to fix it and ended up buying a new one saying "if u can fix it you can have it" I have tried for hours and days to fix it on my own and have now tried to reach out for help
Basic problem:
-When I got the device it would boot to birds and go to g-tablet screen and no further
-Found viewsonic gtablet for dummies tried nearly everything (i believe correctly)
-Called G Tablet Support and got the "send it in to us and we can add the correct software for $60 if there is no problems otherwise the $$ may go up"
-went back to trying to fix on my own
-failed
Basic info:
-able to NVFlash with 0 errors on any packet
-can boot to g-tablet screen but no further
-can boot power & Vol+/vol- no issue
-cannot partition
-cannot wipe data/ factory reset
-can install zip from SD
Help! any ideas are worth a shot when it means (possibly) a free tablet. Eager to fix and try most ideas to get this thing fixed!
Also, This seemed to me a repost but i have looked at, tried, and failed to fix with several different posts/ideas from this site
I've seen a number of posts suggesting that you power off, open the back, pull the battery, wait a few minutes, plug the battery back in and turn it back on. It seemed to work for a number of people.
There is also a reset switch under the back cover.
I honestly don't know if one of these will work, but it's worth a try.
Can't suggest which rom you might try, since there's no way to tell which bootloader you have (v1.1 or 1.2).
I'll have to try pulling the battery plug tomorrow I don't have small enough tools. But I do know that im running 1.2 got that much outta tech support before they went grabbing for mytwallet lol
Here's a thread that explains how to open the GTab. http://forum.xda-developers.com/showthread.php?t=994881
If you are on 1.2 (and are absolutely sure) you might want to start with http://forum.xda-developers.com/showthread.php?t=1525424 to get the latest recovery ClockWork. Do this after you "pull the plug".
If it doesn't work after that, come back and let me know and I'll try to do some more troubleshooting with you. Since you said you actually had NVFlash working before, this might actually get you up and running on the latest stock rom. From there, you can move up to just about anything you want, upto and including Ice Cream Sandwich (ICS). Just remember to check the forum information about what does not work. For example, if you move up to Gingerbread (3.x) or greater, there is a pretty good chance that you won't have camera or mic support at this time. Some roms don't support hardware acceleration at this point, but many do.
Anyway, come back and let me know how it went.
Awesome thanks. I'll be getting into that soon (after I finish cleaning) just wanted to thank you for your interest in helping me
Hey! finally got around to it but pulled the plug and grabbed that cwm recovery u had linked but i'm still hangin on the g-tablet screen. any other ideas?
I'm guessing that the tech support for GTab was wrong and you actually have a 1.1 boot loader.
Try following the thread here http://forum.xda-developers.com/showthread.php?t=974422 on formatting the gtablet and starting over from scratch.
Gregwa
what 1.1 should i use?
Cmdrbubbles said:
what 1.1 should i use?
Click to expand...
Click to collapse
There is no reason to go out of the way to figure out what Bootloader you have. the NVflash files that you found on the ViewSonic Gtablet for Dummies guide will be your best bet. If you can get grab the NVflash files that include CWM recovery those are the ones you need. After NVflash is complete and you see the Gtablet splash screen press and hold the power button till the tablet shuts down. Once shut down you need to reboot into recovery by pressing down the volume + and press the power button to boot up. That should get you into CWM where you need to do a wipe data fatory reset, wipe cache and also wipe dalvic cache under the advance menu. Once that is complete then you need to back out to the main menu in CWM and reboot. Make sure that you do not select Reboot Recovery. Give the device some time and it should boot into the Stock TapUI where you can mess around with it from there.
I would choose 1.2 build 4349 w/CWM preinstalled (Old) NVflash file found here http://viewsonic-gtablet-for-dummie...65610&fw_sig_premium=0&fb_sig_network=fw#2310
Many times in the past the wipe data/ factory reset and wipe dalvik and most anybody those options lock up the tablet. It will just hang on the screen (depending on the option chosen) and not move from there for hours on end... Thoughts on why? Hoping not a hard drive problem
Cmdrbubbles said:
Basic info:
-cannot partition
-cannot wipe data/ factory reset
-can install zip from SD
Help! any ideas are worth a shot when it means (possibly) a free tablet. Eager to fix and try most ideas to get this thing fixed!
Also, This seemed to me a repost but i have looked at, tried, and failed to fix with several different posts/ideas from this site
Click to expand...
Click to collapse
You will need to get your partitioning working. You can boot into recovery? And what happens when you attempt to partition.
If you are able to go past the 3 birds splash screen and see the gtablet screen, then you're on the stock ROM and the problem is most likely with the partitions on the internal SD card (or the card itself). In which case, nvflash will not help you.
Set up ADB and then run these 2 commands and post the output after you've tried one of those operations you mentioned in your 1st post:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
C:\SOME|PATH> [B]adb pull /tmp/recovery.log[/B]