Viewsonic G Tablet lock up @ g-tablet screen - G Tablet Q&A, Help & Troubleshooting

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]

Related

[Q] Stuck in Boot screen!

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

[q] >>help tried rooting>stuck in hboot >need my phone back help!!

OK well I have trying my best as a noob to research for 2 days not in and out on how to fix my issue
My friend tried rooting my phone and to install a different rom. I am on 2.1 and unfortunately I got the phone used with 2.1 already on it so I don't know if it was a leaked or legit 2.1 rom, and I am learning as I go here to fix this issue as I have never new how to do this stuff nor have I ever done it.
Where I am at now:
only thing that happens when I hit power is the phone "vibrates then stays on the 3 skateboard screen" or press "volume down + power" and it goes to the Hboot screen. I go into recovery and it goes to clockworkmod and from there after trying to install any roms from the sd card it says on the last 3 lines
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
and every time I go back or power up to the Hboot screen it does not have any "update bar" (I guess if this was done right as I read on other threads there should be some type of update bar) on the right corner or any other options "for me to select" accept:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
and then with some other info above the Hboot highlighted in blue
I have tried formatting the sd card a bunch of times, I did the clearing of the "wipe data, wipe cache partition, wipe dalvikcache" as I read to do over my reading, but I see that if I go under any restore options under clockwork, no files are found for me to back up too so I am seeing he did not back up any of my info, I also have tried using 2 different ds cards.
So more less it looks like my options are to get this fixed from the only place my phone will boot to with options and thats when I press volume + and power so I guess loading whatever I need to my sd card>>if thats an option or am I screwed, I have seen many tutorials but none of them start where my particular position is stuck at in Hboot. this is my only phone and I had to buy a prepaid which is just about out of minutes, I put an add on craigslist trying to get someone I will pay to fix my issue but no luck, please I need help and I will pay u somehow to guide me through this of my exact issue, I was trying to get to rom 2.3 but if it's easier to get back to 2.1 rom then so be it.
PLEASE!~~
Please HELP!
Cheeva316 said:
Please HELP!
Click to expand...
Click to collapse
Got a solution in the making for you, just give me about 30 minutes.
Edit: Maybe 45 minutes lol, sorry i'm testing this before I have you do it to see if it works.
Ok download the following files:
http://www.mediafire.com/?njwqa7axwzyaqgb
http://www.mediafire.com/?f69cl8dc747h0l9
http://www.mediafire.com/?xg8nnqs177xggx4
http://www.mediafire.com/?qxpi5wsx5lzbhbo
http://www.mediafire.com/?4tg67hck7vh1xxs
Edit: Flash the "rootme.zip" first then follow the rest.
Now what you need to do first is extract the "nandroid" file to somewhere you can easily find it.
Now take the folder called "nandroid" along with all the other zip files you downloaded and place them on your sd card. Put your sd card in your phone and power on with volume down+end. Press volume up. Use the trackball to select "Backup/Restore". Use the trackball again to select "Nand Restore". Use it again to select "HT9BGHG01402". Use it again to select "BDS-20110125-0901". Let the restore run, then power off your phone. Turn your phone back on with just the power button, let it run (might even take up to 10 minutes for the phone to start up). Let me know if the phone boots up or not after about 10-15 minutes. This should work and if it does then we can go from there, even to getting you 2.3 if you want.
You might be asking, what the hell is he having me do ? Here's what i'm doing. I made a nandroid backup a few months ago of when I had kaosfroyov39 which is a 2.2 rom. I am going to have you flash MY backup to YOUR phone which when done right, CAN work. Anyway, let me know what happens and remember to give the phone about 10-15 minutes to boot all the way.
Cheeva316 said:
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
Click to expand...
Click to collapse
( Another phone on the precipice of being ruined by someone's cobbled-together "clockwork" recovery. )
If the /system flash memory partition got corrupted in a way that left a lot of pages marked as bad pages, then the /system partition will be "short", and only small ROMs will successfully load into it, if at all. That might be the cause of the above error messages.
But - because you are using Clockwork, there is really no way to know if that is the case, or if you simply have a whole bunch of corrupted ROM files on your SD card. That's because Clockwork does not verify ROM files before it starts flashing them - which allows total garbage to be flashed to the phone. (That's why Clockwork should never be used by newbs).
Here's what I would suggest you do.
- Make sure you are keeping the phone well charged. (Leaving the phone in HBOOT mode will discharge the battery quickly, even if it is plugged in to the charger, BTW).
- Report the exact bootloader version you have - probably 1.47.0000 or 1.49.0000, but it could be something other. Please be precise.
- With the power off, eject the SD card out of the slot and see if you can boot into the normal HBOOT menu with no SD card in the slot. Report your result.
- Boot into the recovery menu and tell us what version # of the recovery you have. If you can determine the details of how your friend attempted to root the phone, that might be pertinent. Again - precise details are valuable; vague hand-waving not so much.
- The Amon_RA recovery has a mode ("USB-MS toggle") which allows you to mount the SD card to the PC. Does your "Clockwork" recovery have this feature, or are you able to put files onto the micro-SD card using a media slot on a PC?
- Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
What I would suggest you do at the moment is to find the SMALLEST Eris** ROM you can find, get it onto your SD card, verify that you didn't corrupt it, and then perform a "wipe data/factory reset" in your recovery and attempt to install it. If you get the same errors as above, then you should definitely NOT try to do a PB00IMG.ZIP or RUU installation. (The current gingerbread ROMs (e.g. GSB v1.4) are pretty small - they only use about 65% of the /system partition.)
I have a flashable "repair" file which might be applicable. It is not a "ROM" per se - it uses some low-level MTD (flash memory) repair techniques, and also flashes into place the original Amon_RA (v1.6.2) recovery, instead of whatever p.o.s. "Clockwork" recovery you currently have on the phone; but I regard it as something which should only be used as a last resort. But - without some more details and testing on your part, I don't feel comfortable about posting it up.
Let me know.
**PS I wanted to ask one more question - this is an Eris we are talking about, right? (I note you were posting in the Hero CDMA forum not so long ago).
Well I want to thank you for replying with such info but it seems that the recovery image file that I reinstalled on the phone was bad cause when it was updating the bar was going up but as it was going through each item it was updating.. I noticed "bootloader in red letters" with I believe saying "error" next to it and then same on another item it tried updating then the phone powered off and now it's dead, tried everything, no charging light comes on, computer (2 different computers) wont reconize it, it's doing nothing at all, I will try to get my hands on another battery but I am broke, but I doubt it's the battery cause I heard with a bootloader error (or damaged) then the phone won't boot up or do anything so I guess the phone is scrap for parts which sucks cause now my friend who started this deal killed my only phone me n my family had, another lesson learned...time to try n sell some stuff on craigslist..damn
Yes it's a Droid Eris...or was! damnnnn...
Again thank you for your help very much appreciated...
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Cheeva316 said:
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Click to expand...
Click to collapse
Well, I am very sorry that this happened to you and my advice to you didn't reach you in time. From the details that you added, I am pretty sure that you indeed have a hard brick.
BUT - the death of your Eris can still help others avoid the same fate. If you can reconstruct the rooting process you went through,
[SIZE=+2]PLEASE LET US KNOW EXACTLY WHAT ROOTING METHOD YOU USED[/SIZE] - and then we can wave people away from it.
When I say exactly, I mean extremely specific: do you still have the download file that you used? If so, push it up to an uploader site and give a link to it. (I think you mentioned unrevoked or something). Do you still have the exact link you used to download that rooting software? Was it Unrevoked? Z4root?
bftb0
I will tomorrow as I saved all the files on my laptop n I am on my pc now, but will do try my best as I am a newb to this phone stuff
Did you try what I suggested or is it too late ?
phone wont do anything so cant do nothing...
Did you find out any more details about the rooting method you used?
might be a couple more days till I can get to it, my laptop is messing up now...all the saved info was on it

After update will not load

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.

[Q] APX Brick/Loop

Update: Hallelujah, we have seen the birds!
Just for future reference to those of you who may be stuck in an "APX loop", where NVFlashing and even repartioning do not work for you. I tried many things, and only one thing worked.
Didn't work:
1) NVFlashing to anything
2) Repartioning or wiping
3) Wiping out all storage on the SD card
After doing many, many rinse and repeats on the above, the only thing that did work were these instructions:
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Click to expand...
Click to collapse
Now, I don't know of too many cases like mine where APX was the only thing that was working and that no amount of CWM or NVFlashing could bring back whatever was wrong with the bootloader, but this method forced a recovery image restore and got me back to the point where I can now power down and reboot. And for that, I thank this fine community!
I think we need a better guide somewhere on... Stages of recovery. If this doesn't work, here's the next deeper level. (Example: Level 1, wipe data/cache and reflash the rom. Level 2: Repartition and fix permissions. Level 3: NVFlash for 1.1 or 1.2 back to stock. Level 4: run the steps I have listed above. Level 5: fixing the bootloader. Level 6: Remove the case cover and short the back.)
Anyways, thanks again guys. Hopefully someone else will search with the same issue I had and get fixed as I have.
try this (not a developer here) when it boots up use your computer to delete all the files on the sd card so it looks blank- not sure if it will fix your issue but if there is a file on there messing your reboot into cwm that should will get rid of it. let me know how it goes. (standard at your own risk disclaimer) i have done this before just to see what would happen and nvflash brought it back up.
Hey, thanks for the reply. The sdcard was already blanked out through my various steps, so that doesn't appear to be the problem. Same things happen.
Now, that's just the app data and such on the sdcard, so I am guessing if I was able to see/delete all the system files instead via USB and delete it that way, I'd see something else.
just to bee clear i would delete everything on there not just the system files- so when you go to the drive from your computer it shows nothing at all.
here are the steps i would take start to finish.
1 nvflash rom
2 connect to computer, mount usb, then highlight and delete all files on gtab.
3 nv flash again (preferably with a stock rom with cmw pre loaded
4 reboot and pray that this fixed it.
OP - What size is the nvflash file you are using? I have run into a similar issue before with the larger nvflash.exe (like 152kb). It should be 140KB.
Just something else to check.
So to clarify, when you nvflash the 3588 stock image, it will automatically reboot at the end of the nvflash_gtablet.bat batch file?
pugsby said:
Hey all. Little frustrated since I've tried most of the tricks and still have a soft-bricked device. Not sure how it happened originally, but one way or another, I have a bad bootloader and no access to CWM.
APX works. I can NVFlash 1.1 or 1.2-based Stock or otherwise roms, and they boot (once, and only once...) . I can get USB mount. I've tried them with and without CWM pre-installed and see no differences.
But as soon as I reboot or power off, it just returns to APX mode. It is only a black screen, however. No birds, no logo, no nothing. The only way to make it boot again is to NVFlash it again.
All the instructions say to enter CWM to re-partition or to wipe data. That's great, but I have no access to CWM. Pressing the buttons during bootup does nothing because the device never makes it that far through bootup. And the format utility doesn't wipe enough data to return this back to a truly blank device, because when I nvflash, my apps still show to be there and I want it back to a blank slate.
I've tried pressing the buttons directly after a NVFlash to enter CWM that way, but it just goes straight into the rom.
Others have suggested popping off the back of the case and grounding out things to reset that way, but I thought that was just if APX didn't work, but APX is the only thing that DOES work, so not sure if it applies. (Let me know if I'm wrong there)
More things to try?
Click to expand...
Click to collapse
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
After you repartition, wipe data, clear cache, etc. it might still loop into APX. If it does you'll need to force it to install a new bootloader. I'll dig up a link to the procedure if you need it.
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
K J Rad said:
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
Click to expand...
Click to collapse
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Acidburn find out a solution for this problem
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
K J Rad said:
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
Click to expand...
Click to collapse
This got me into CWM (Yay!). This, however, did not fix the APX looping (boo).
I repartitioned, wiped, nvflashed, wiped, repeat. Even though I have more options now with CWM, the end outcome is still the same that after the initial boot, it won't boot again.
BUT, I did find a working method. See the original post.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I was hoping you'd respond, goodintentions, as I used your NVFlash files and instructions this last time around from your very handy site.
I'm not sure exactly what happened. I do know that Rom manager was involved somehow, trying to use that integration with recovery. (I know, not recommended, but at first it acted like it would work).
Also, I think a 1.2 Rom was mistakenly flashed on top of a 1.1 bootloader somehow.
The details are fuzzy. It's been so many things since then that who knows..
goodintentions said:
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Click to expand...
Click to collapse
I am a tech. Been working with/on/in electronics and computers for roughly 35 years. I had a hard time believing the problem was real until I had one in my hands that was doing it. I've tried doing it to my own tablet but a simple nvflash always got me going again.
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
Click to expand...
Click to collapse
This is successful in some cases but not all. In some cases the bootloader has to be updated using factory stock recovery. ClockworkMod and nvflash don't update the bootloader (and I suspect some other system related partitions/information) properly. For those cases the fix is a little more complex. This process...
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
has worked on all but one of the tablets I've recovered. The odd one out required an extra reboot (though I was doing the steps from memory and on an unfamiliar computer so I could be mistaken). However... as noted above... a subsequent nvflash of even the same image resulted in another APX loop. The end result was I had to craft a custom nvflash for each of those machines to avoid the problem in the future. That may or may not be necessary for all cases but since it's relatively easy I just do it out of habit now.
Keep in mind that serious APX looping issues are very rare in the grand scheme of things. Many times folks get confused and fail to follow directions properly and think they have a bigger problem than they really do. The overwhelming majority of times a simple nvflash and repartitioning will fix these things right up.
Added: BTW, the best way I've found to avoid the APX loop issue entirely... do a data wipe before you flash a new ROM and then again immediately after and before you boot it for the first time. I know... one should be enough... but if you make it a habit to do two... then you'll probably remember to do at least one of them ;-)
Great info. I shall try not to enter another painful APX loop. I was shocked how many things I had to try and places I had to go before I found a working method. I guess I really did a number on this thing somehow. But I'm happy that it's back.
I didn't have to do the more painful one you mentioned, but honestly I was ready to try about anything short of slaying a dragon.

Help: Totally Dead G Tablet

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.

Categories

Resources