Hello,
I tried searching but the results all seemed like they were people who have rooted and have alternate ROM's.
I am completely stock with 3588, no clockwork, not rooted, nothing else.
A couple of days ago I turned it on and it went through it's normal routine until it got the point that it should have loaded the home screen. Instead it flashed something for a brief moment and the only thing I caught was 'Android System' in the top left, then it shut down. Prior to this I wasn't having any issues.
Now when I turn it on it shows the birds, then gtablet, then the tap'n'tap and peacock but instead of of then loading home screen it goes black for a moment then the tap'n'tap comes up again. It will do this 4 or 5 times then simply goes black.
I connect the USB to my PC but of course I can't access the tablet.
I opened it up and tried using the reset button, no help.
Disconnected the battery for a minute, no help.
So no clockwork or nvflash, can't copy files to it. Am I boned? Any suggestions on what I might try?
Thanks for any suggestions,
Neudle
Try a data wipe using Method I from this: http://forum.xda-developers.com/showthread.php?t=1030915
It will delete any apps you've downloaded and installed but it just might get you going again.
Up and running.
First off thank you very much for that help. The tablet is working again.
I didn't realize it would run a recovery from sdcard2 without the command file pointing to it specifically. I thought it only defaulted to the internal sdcard.
Does anyone have any idea how or why this might have happened and any advice on how I might avoid it in the future?
Thank you again,
Neudle
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.
Okay, I think I'm completely hosed. But I thought I would ask if anyone has a solution. Here's the deal.
I was running the new stock 5274 on 1.2, went to turn on the tab and it wouldn't power up. This has happened before so I cracked the case, pulled the battery connector and plugged it back in then shorted A4 and powered up into APX. I ran NVFlash for the stock 4349 based image, figuring that I could then update it again after I loaded Clockwork. I've done this a bunch of times before, never had a problem. Until this morning.
When I try and run NVFlash, every time on part7.img I get "Failed to verify partition command failure: create failed" and NV stops dead in its tracks. I also tried to run the Format tool, which I've also done before, and get the same error at the same place. In fact, no matter what flash and try to run, 1.1 or 1.2 BL, NV bombs out at part7.img.
I'm at a loss. The only way to get the tab to power on is to short A4 into APX, but I can't flash anything. Any advice would be greatly appreciated.
Ronin916 said:
When I try and run NVFlash, every time on part7.img I get "Failed to verify partition command failure: create failed" and NV stops dead in its tracks.
Click to expand...
Click to collapse
Looks like you've developed some bad blocks on the NAND flash. Just skip loading that part7.img, then.
On most gTabs, partition 7 is the /misc (MSC in nvflash) partition which is not used by most ROMs (GtabComb uses it to create a single log file). So, it doesn't matter if this partition is not written by nvflash.
On some gTabs (like mine), partition 7 holds the .bmp file for the first splash screen (VS's 3 Gouldian finches). This, too, is not important. You'll just not get that first splash screen.
Just erase the partition, if you can, using the erase_image program in CWM after you restore the remaining partitions using nvflash.
Thanks for the tip. I tried removing part7.img from NV, but now it bombs on part9.img with a NvError 0x30012. So, that's a no-go, and now I can't even get into APX. Maybe the battery died, so I'm going to charge to full and see what happens. Still could use suggestions, though.
EDIT: Well, color me confused. The battery was dead, so I gave it a good 4 hour charge to full. Then I cracked the case and was able to get back into APX. I have NVFlash and the 1.2 4349 load here, so I figured I'd give it a shot. Sure enough, it ran through NV without an issue, and I'm back to stock 4349. Not one hint of an error. Dunno....maybe the tablet gods decided to smile down upon my today. All I know is, I'm back up. Don't know how....don't know why....just is.
so im pretty much a noob to this website and my g tablet but heres my problem
i was stuck at the bootloader (those frickin birds) so i decided to nvflash to get it back to normal, i followed the instructions step by step and it seemed to work, it booted normally and i thought all was good untill it randomly turned off, so i plugged it back into the computer and held the power button and i heard it connect so i nvflashed again and the white writing popped up, it finished, it got to the g tab screen then turned off again. i let it die last night and i just went to turn it on and nothing. help please
Sgt,
You may have to crack open the case and pull the power connection for a few seconds and then plug it back in. Seems like every tab is a little different, but you can reference this thread:
http://forum.xda-developers.com/showthread.php?t=1118087
Maybe that gets you back up into APX at least.
thanks for the help unfortunantly it didnt do anything, i think im stuck in apx mode because i can still nv flash, every time i do it goes straight to gtab screen then shuts off, i turn it back on and i can flash but nothing else
You may want to try this:
http://forum.xda-developers.com/showthread.php?t=1030042
It shows you how to NVFlash Clockwork. If you can then get into that, you could repartition and format you GTab, then load the ROM of your choice.
Posting here in hopes to expand help request.
deleted...
10char..
ok i nvflashed cwm and i believe it worked but i still cant get into it, the moment i turn on my tablet i dont get any load screens it just goes into apx mode thats it
Had my Prime 2 days, got it rooted.
After ICS install and camera update it worked for a while. Then it rebooted and it's stuck in a bootloop. I can't even power it off.
Yes, I've used the reset pinhole.
I've rebooted into Asus recovery but all I get is the "dead droid" screen. I'm assuming it's because I don't have my SD card in.
Any suggestions?
I'm thinking that if I can get my hands on the stock ICS zip direct from Asus I might be able to run that.
I suspect, from this thread that the issue might be that the Launcher has gotten corrupted.
Update:
Ran the battery till the unit shut off and didn't reboot.
Charged the battery for 4+ hours, unplugged it and tried to boot up. Same story, bootloop.
ADB sees my Prime and can issue commands.
Any suggestions? I'm getting desperate here.
Edit again: I can pull a logcat, any suggestions what I'm looking for? I'm not sure what subset of Linux commands are in Android, can I do a kill -9 if I identify a rogue process?
I'm pretty sure top won't work, and a lot of my Linux knowledge is pretty rusty.
Same here
I'm stuck in boot. I rooted it from zedo's instructions (that guy is a whoot!). Afterwards I installed "VM Heap Tool"(by martino), restarted the tab from the VM app and it got stuck in the boot screen.
I'm stuck and don't know what to do. I don't really know codes, so I'm pretty much up a creek without a paddle.
Any help would be MUCH appreciated!
Bumble-Bee has solved this issue for you on IRC but I figured we should post the solution to *your* specific problem here for others. Hopefully it helps them if they run into a simular issue.
With a boot loop try shutting down the tablet by holding power for 30 seconds. If it doesn't shut down then hold power for 30 seconds and after it vibrates hold power and volume down. This should get you into the recovery process.
The first thing to do in trying to resolve this issue (and what solved it for Col_kernel) was to do a data wipe using the recovery menu. Directions on how to perform this can be found here . this will solve the majority of bootloop issues.
The second thing to try to do is to perform a recovery using a signed zip from Asus. the ICS 9.4.2.11.1 is the latest one as of this thread and can be downloaded at the link provided there. Download that and place it on a microsd card. Load the card into your prime and boot into recovery and perform a recovery.
after that, start asking for help
I tried both solutions suggested and they didn't work for me, however I modified the services.jar in systems\framework. Looks like it tries to recover and then goes to an android on his back with an exclamation mark. I can't get adb to recognize my device either. I'm assuming my only options are to send it back to Asus or wait til I can flash at this point?
I should have said that I have already done the reset. Also, I cannot install anything on the tablet, since I cannot even access it. My PC won't even recognize it.
Update: I just spoke with Asus support. They said that if all these options are exhausted, I should return the tablet. That's what I'm going to do today. [good thing I have all my apps backed up. #TiBu!]
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
wells79 said:
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
Click to expand...
Click to collapse
Odd. I had the same issues. I started rooting mine on my mac, then finally moved to my pc. It rooted flawlessly on my pc.
So, I don't know if it was the root with a corrupted file, or the VM Heap Tool that I activated in it that caused it to get stuck in bootloop. But... I didn't restart the tablet until after the VM Heap Tool. In other words, it could have done the same thing without the VM Heap, I just wouldn't have known it, because I didn't restart it right after the root.
Make sense?
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 little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh: