Hey guys. I've had my G Tab for about 2 weeks with TNT Lite 4.4 installed, and it has been running beautifully. The day before yesterday, I quickly tapped the power button to turn the screen off, and it shut the whole thing down (without going through the normal shutdown process where it asks you to confirm, etc). Every time I have turned it on since then, once it boots up I get force close message after force close message for several apps, and am unable to do anything.
Some examples of the apps that are repeatedly force closing are:
Google Services Framework
Launcher Pro
Titanium Backup
Pandora
Tapatalk
Dropbox
Once I manage to get all the force close messages closed for a moment, there is usually enough time for me to hold the power button and bring up the shutdown menu. Then I get a bunch more force closes and I can usually get them to close long enough to power it off eventually, but it is a struggle.
I am able to boot into CWM fine, but whenever I select any of the options on the top level menu in CWM, it switches to a black screen and I am unable to do anything until I hold the power button and turn it off.
Any ideas? Thanks!
Bumping this thread to see if anybody has any ideas. I tried NVFlashing the tablet, but that didn't fix the problem. I think it might be connected to this thread:
http://forum.xda-developers.com/showthread.php?t=962545&highlight=process+android.acore
But now when I try to turn the tablet back on, nothing happens. I am at a total loss.
You probably only needed a data wipe. But since we're beyond that now...
You say it does nothing. How much nothing does it do? Backlight come on? Splash screen? gTablet Screen? Fade to black? Have you tried pluggin it back into your computer to see if it's booting into APX Mode (likely)?
Most likely the nvflash failed in some way. Make sure you have bekit's 1105 image, the correct version of nvflash and the appropriate drivers for your version of windows (if that's what you are using). Then try again. If it doesn't work. Let us know.
Yes, it looks like my tablet is now stuck in an APX loop as described here:
http://forum.xda-developers.com/showthread.php?t=1038689&page=1
Reading through this thread and several others it links to to see if I can find a solution.
Follow these instructions exactly.
http://forum.xda-developers.com/showthread.php?t=861950
Use bekit's 1105 image (nvflash_gtablet_2010110500.zip)
Following those instructions exactly is what got me into this situation in the first place
I was just about to send you a PM because in the thread I quoted in my last post, you asked whether anybody experiencing the APX loop problem happened to live near the FL panhandle. I am Tallahassee. If you are still interested in getting your hands on a tablet with this problem, let me know and I am sure we can work something out.
Ok... in the thread you referenced we got one fixed by doing this:
1) Go into APX mode and connect to the computer.
2) enter the following command from the appropriate directory on your computer.
nvflash --bl bootloader.bin --format_partition 12
3) reboot
4) if the tablet does not boot properly repeat the nvflash with bekit's stock 1105 image.
If that doesn't fix it then I really would like to see that tablet. I'll PM you an email contact address.
Thanks! I am kind of new to all this, so... How do I enter that command?
Edit: I tried copying and pasting that line into NotePad and saving it as a .bat file in my NVFlash directory. It opened a command prompt which said something like "NVFlash started" but it closed VERY quickly after that, and didn't appear to do anything else. I tried reflashing stock 1105 after that, and it is still in APX loop.
From command line or copy and paste the following two lines into a text editor and save it as a .bat in your nvflash directory.
"nvflash.exe" —bl bootloader.bin —format_partition 12
@set /p batuserinput=Press enter to continue:
I am basically the world's biggest idiot. I thought I was so careful about following the NVFlash directions exactly, but the whole time I was using the nvflash_gtablet_46_whatevernumbers download instead of the correct one. I downloaded the right one, followed your instructions, and now I can boot correctly! Thanks so so so so so much for your help!
Okay, so I followed the instructions in your other thread to use a micro SD card to wipe my cache and data. I then downloaded the OTA update. However, my original problem of lots of various things force closing still seems to be happening. I rebooted the tablet so I could get an accurate list of which apps/processes were crashing on boot, and I got stuck in a boot loop (birds -> g tab logo -> birds -> g tab logo -> etc).
I NVFlashed it again a couple more times, and it is still stuck in a boot loop.
Related
So I successfully (I think) took my gtab back to stock rom using NVFlash. Then When i try to install clockwork mod (to eventually move to TNT lite 4.4) I killed it. I copied over the update.zip and recovery folder when attempting to do clockwork. Then I powered down. Now it won't do anything. ie. The screen doesn't even turn on. I tried disconnecting the main battery and letting it sit for up to 20 sec but that doesn't help either. Won't turn on while holding +Vol either (that's how I tried first).
Connect it to your computer via USB and see if it's in APX mode. If it is then you'll likely need to nvflash again. If you do make sure that you are using the right drivers and bekit's 1105 image. Then once you have it up and running you'll likely need to repartition it.
ok. And if that works Can I update the tablet with the new viewsonic release or do I have to keep the old version to run clockwork and then tnt 4.4? I guess 5 has been taken down?
The latest Viewsonic release (build 4349) is NOT compatible with the standard clockworkmod.
TnTLite has been retired and replaced by it's developer with Mountain Laurel which you can find over at SlateDroid. It is based on the latest stock build so you could upgrade to that with no trouble if you choose to.
Alright. Thanks for the help so far. It was indeed still in apx mode. Any Idea's on how to get it out? I can NVFlash it with no problem but every time I reboot (update or just power down) it comes back in APX and I have to re-NVFlash.
You have an APX brick. Unless KJ Rad has come up with a fix yet your stuck right nnow nvflashing everytime you boot
starfltcdrjr said:
Alright. Thanks for the help so far. It was indeed still in apx mode. Any Idea's on how to get it out? I can NVFlash it with no problem but every time I reboot (update or just power down) it comes back in APX and I have to re-NVFlash.
Click to expand...
Click to collapse
1) nvflash - bekit's 1105 image (nvflash _gtablet_2010110500.zip)
2) wipe data/cache
3) Install CWM
4) reboot into CWM
5) repartition 2048 and 0
6) nvflash bekit's 1105 image again
7) wipe data/cache
If you get any error at any step (especially during the nvflash) stop and let me know. If you're not sure how to do any of those steps I'll be happy to point you in the right direction.
I'm hoping to have something better than this in the next few days but for now this is the best we have to get you working at a good factory load.
Ok. What do I do for steps 2-5 thanks for the help.
2) Wipe Data: This can be done either through "Settings - Security - Factory Data Reset" or Method I from http://forum.xda-developers.com/showthread.php?t=1030915
3) Install ClockworkMod (CWM): The first part of this post: http://forum.xda-developers.com/showthread.php?t=865245 (Just do the CWM install)
4) Shutdown the tablet then restart it while holding down the Volume Up key until the words "Recovery Key Detected" appear in the upper left hand corner of the VS Birds Logo screen.
5) Once in CWM, Look for partitioning under Advanced menu. Select it and answer the two questions 2048 and 0. This will take a few minutes.
update: Ok I think its out of its APX loop (somehow) Now in version 1.0-2638.
Another update:
Boy am I a dumbass. When I put the thing back together I put the VOL key in backwards.... DOH! CW mod is working fine.
I'm guessing I need to update stock software to get best results now? Is that possiblcard if I can't get it to boot in anything but APX anyway???
The best I've been able to do is using the NVFlash found here: http://droidpirate.com/2011/03/10/g-tab-users/
I can see the viewsonic splash for a split second at startup when holding the Vol+ and power then back to APX
I was hoping the data wipe would clear the loop. What ROM did you have on the device before all this started?
starfltcdrjr said:
The best I've been able to do is using the NVFlash found here: http://droidpirate.com/2011/03/10/g-tab-users/
I can see the viewsonic splash for a split second at startup when holding the Vol+ and power then back to APX
Click to expand...
Click to collapse
Two things... First, I cannot help you effectively if you choose to use resources other than those I recommend. I have no idea what is in that nvflash from droidpirate nor do I have the time to research each and every one so please use the references I provide.
Second, Are you absolutely certain that you're holding down the Volume Up key to go into recovery? You'd be amazed how many folks (myself included) make a mistake here every now and then.
update: Ok I think its out of its APX loop (somehow) Now in version 1.0-2638.
Still can't boot into CW. (VOL+ + Power) DLed version 8 from here: http://forum.xda-developers.com/showthread.php?t=865017
I'm guessing I'm unbricked but just using wrong CWMod version
is this the one I need?
I guess it depends on which ROM I'd like to run correct? If you could reccommend one and help me get there that'd be great.
That one should work fine for the ROM's on here. If you're going to use the VS stock 4349 build or one of Roebeet's ROM's from slatedroid then you'll need to use the one compiled for the 1.2 development branch.
update: Ok I think its out of its APX loop (somehow) Now in version 1.0-2638.
Another update:
Boy am I a dumbass. When I put the thing back together I put the VOL key in backwards.... DOH! CW mod is working fine.
I'm guessing I need to update stock software to get best results now? Is that possible without wifi as I won't have that until the weekend?
I've re-partitioned the SD card.
I'm going to try and get TNT light 4.2.1 from droidpirate to run
looks like TNT Lite 4.2.1 went on OK. Thanks for the help and remember + is on the right
Glad you got it working. Enjoy!
K J Rad said:
2) Wipe Data: This can be done either through "Settings - Security - Factory Data Reset" or Method I from http://forum.xda-developers.com/showthread.php?t=1030915
3) Install ClockworkMod (CWM): The first part of this post: http://forum.xda-developers.com/showthread.php?t=865245 (Just do the CWM install)
4) Shutdown the tablet then restart it while holding down the Volume Up key until the words "Recovery Key Detected" appear in the upper left hand corner of the VS Birds Logo screen.
5) Once in CWM, Look for partitioning under Advanced menu. Select it and answer the two questions 2048 and 0. This will take a few minutes.
Click to expand...
Click to collapse
Hi,
I'm in the APX loop and have been unable to progress through these instructions.
My error was that I successfully flashed CWM v08 and Vegan, then tried to use ROM Manager to switch to Cyanogen. ROM Manager forced me to update the CWM to 2.xx, and then on the reboot it had the 'Magic' error.
I've done NVFlash and can get into TnT but can't get past the APX loop to install the CWM (as per step 3) - my holding down power + vol+ just results in a black screen, then when I check for APX mode, it is still in that mode.
Step 2 (clear cache) forces a reboot - is that right? I've tried the other method of clearing cache ('Method I').
Any ideas? I only got this thing a few hours ago, lol!
simmo35 said:
Any ideas? I only got this thing a few hours ago, lol!
Click to expand...
Click to collapse
Searched APX bootloop and got this:
http://forum.xda-developers.com/showthread.php?t=994046
Worked for me.
simmo35 said:
Hi,
I'm in the APX loop and have been unable to progress through these instructions.
My error was that I successfully flashed CWM v08 and Vegan, then tried to use ROM Manager to switch to Cyanogen. ROM Manager forced me to update the CWM to 2.xx, and then on the reboot it had the 'Magic' error.
I've done NVFlash and can get into TnT but can't get past the APX loop to install the CWM (as per step 3) - my holding down power + vol+ just results in a black screen, then when I check for APX mode, it is still in that mode.
Step 2 (clear cache) forces a reboot - is that right? I've tried the other method of clearing cache ('Method I').
Any ideas? I only got this thing a few hours ago, lol!
Click to expand...
Click to collapse
And stop using ROM Manager
I had installed TNT Lite v 4.3.0 a couple of weeks ago and it was working pretty good. But today my tablet has gone into a bad state. Every app that I run results in FC. Even the ADW launcher EX that I had selected default is crashing. It then gives me the options: ADW Laucher, ADW Launcher EX, and the regular Launcher. The plain ADW Launcher also fails, but fortunately the regular Launcher still works so I can access the apps.
But unfortunately almost every app that I am trying fails. The only one that doesn't fail is the Web browser. The Settings starts and I can access Applications menu but once I choose say System Applications, after that if I try to choose some other option such as Installed Application, it crashes as well.
Last night however when I started the tablet the battery was probably down and while it was powering it up, it turned off and then restarted by itself and then turned off, without reaching the lock screen. I don't know if it has something to do with all this.
What do I do now? Any help will be appreciated.
Thanks.
A well known issue.
http://forum.xda-developers.com/showthread.php?t=896395
This is why I'm an advocate of people doing the partitioning right before they flash their first custom rom. This way, they won't have to wipe everything later on.
I could only wonder why people aren't mentioning this in every custom rom thread.
Thank you so much. Will try it out tonight.
Unfortunately it seems I have run into a worse issue (without even doing anything yet). Now when I power it on, it starts and shuts off within a few seconds, just shows the birds for like 5 secs and bang, black screen.
The tablet is fully charged (if I put it on charge the light turns green in no time). Looks like the battery is dead.
You might be dropping into APX mode. Do you know how to use nvflash?
Thanks for the reply. You are absolutely right. After multiple tries it did boot up and I was able to install clockworkmod and it all worked great. It wiped off everything but I could live with that. And I turned it off and back on and it was working fine.
But then it went back into the same mode - shutting off immediately after turning on. I decided to return this tablet thinking that it is bad. But before I would do that I thought to restore it or else Viewsonic won't honor the warranty. So I started reading the thread about restoring the tablet to stock using nvram flash. In that procedure it requires me to put the tablet in APX mode and that's when I thought that maybe it is going into APX without pressing the volume - button.
Anyway I was successfully able to flash nvram. Or so it said. I still have the output from the batch file. But now my tablet is totally bricked. It does not boot at all. No pretty birds for me.
I hope there is some way out of it. Please help.
Edit: After re-flashing and using a different file, it seems to have made it a little better. At least I am seeing the birds again. But the original problem of shutting off, or going into the APX mode without pressing Volume button, has returned. All I am getting is the birds for a few seconds and then black screen. I will continue to retry, and if I see it booting up successfully to the stock, this thing is going back to the factory.
1) What image did you use to nvflash?
2) What happened when the flash was finished? Did it boot normally at least once?
3) Does the screen just stay dark all the time now?
1) First time nvflash_gtablet_46_2010112600.zip and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Later I flashed nvflash_gtablet_2010110500.zip. This at least recovered it enough that it shows the birds, but soon after the screen turns black. I have confirmed that it is going in APX mode. If I have USB cable connected to my PC, the PC reports discovering the NVIDEA APX device.
2) It hasn't booted normally since I flashed nvram.
3) No I get the birds, but after that it turns dark.
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Thanks for your response. I tried it. Did not work. When you say Replace part9.img with the recovery.img, does it mean copy recovery.img into the NVFlash directory and rename it to part9.img or leave it as recevery.img. I renamed it to part9.img and backed up the original part9.img to part9.img.tmp. The size of recovery.img and the original part9.img are very different. I am confused. Please help.
K J Rad said:
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Click to expand...
Click to collapse
Yes, that is exactly what I meant.
Are you sure you're holding the volume UP key? Birds and then black screen is APX mode which is normally entered by holding volume DOWN.
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Any ideas?
I was thinking about formatting the gtablet. Please let me know if this is the right move, or there is something else I could try first.
shah123 said:
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Click to expand...
Click to collapse
A little more than "It did not work" would be helpful.
What step failed? Please tell me what happened after each step.
Did you get into CWM and repartition?
Did you get everything cleared?
What happened when it rebooted?
What was the original filename of the image you tried to flash?
What version of clockworkmod do you have installed?
Have you ever used ROM Manager?
All of this is important and no one can help you if you don't provide enough information.
Oh, I am sorry. Here are the answers to the questions you asked:
What step failed? Please tell me what happened after each step.
Ans: Out of the 7 steps you provided, the steps 1, 2 and 3 worked fine. It is the step 4 that failed (and of course I can't proceed with the steps anymore). In other words I cannot go into clockworkmod recovery.
Did you get into CWM and repartition?
Ans: No I was not able to do so. If I press power and Volume Up key at the same time, nothing happens, screen remains black, not even birds come up.
Did you get everything cleared?
Ans: I believe you are referring to step 6. No, I could not get to that step.
What happened when it rebooted?
Ans: Nothing showed up. Because when Volume Up is pressed while it is powered on, nothing shows up on the screen.
What was the original filename of the image you tried to flash?
Ans: Actually first time nvflash_gtablet_46_2010112600.zip (and this is before you provided the 7-step recipe - see post #6, 7, 8 of this thread) and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Maybe that was my mistake. I chose a wrong file. Later I flashed nvflash_gtablet_2010110500.zip. This recovered it enough that it shows the birds now, but soon after the screen turns black (goes into APX mode).
What version of clockworkmod do you have installed?
Ans: v08
Have you ever used ROM Manager?
Ans: No. What is it?
I really appreciate your help.
What happened at the end of step 3?
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 seconds after the flash starts.
When the flash was done did it say "Recovery Key detected" on the screen? If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
It sounds to me like you did the nvflash then tried to reboot into recovery.
Its unbelievable. Tonight when I powered it on it started booting up normal instead of going into the APX mode. I was glad. The stock UI came up, but some of my apps like Quadrant, File Expert etc were still there. It also notified me of the Update 3588. So I downloaded it and started installing it. Pretty soon it rebooted itself (sooner than I thought - I don't know if the remaining installation was supposed to happen after the reboot).
But instead of booting up into 3588 it is unfortunately gone back to the same old issue - the birds followed by black screen - aka APX mode. It never booted up after that. No matter how many times I tried to reboot, it goes into APX mode just like before. I don't know what caused it to complete bootup. One thing I noticed was that the battery was totally drained when I started tonight. I don't know if the drained battery somehow took it out of the APX mode. But now it has a little bit of charge because of hooking up to power supply. I have disconnected the power supply and will leave it in APX mode over night and try it again tomorrow when the battery would be totally drained and see if it boots up fully.
To answer your questions though:
What happened at the end of step 3?
The screen went black and after that it stayed black. No CWM.
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Yes, I did.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 secondsafter the flash starts.
Yes, I continued to hold it all the way until the flash completed and the screen went black and quite some time after that.
When the flash was done did it say "Recovery Key detected" on the screen?
I don't think it did.
If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
So I guess I need to give it another try. Tomorrow I will try to reboot the tablet again and if it continued to go into APX I will do the nvflash one more time.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
A black dark screen. No CWM or stock recovery.
It sounds to me like you did the nvflash then tried to reboot into recovery.
No at the time of nvflash I held the Volume UP button and nothing happened. Since then I have been trying to bootup or put it in CWM Recovery but only thing the tablet wants to do is go into APX mode.
So I guess my theory of "drained battery takes it out of the APX mode" is correct. I tried to reboot the tablet several times but it just kept on going into the APX mode until the battery was completely drained. And then it started booting up normally but it went into some installation (probably the stock 3588 that I had downloaded in the previous successful bootup). And then the green android with the exclamation sign came and the exclamation sign was rotating for a second or two and then stopped. And it looked like it was hung. I waited for a minute or two but nothing happened, so I pressed one of the buttons, I don't know if it was Menu or Back button, and all of a sudden clockworkmod recovery screen came up.
I have attached the picture of the screen. It still shows the green android with the exclamation sign in the middle of the screen, along with the CWM Recovery.
One other thing I noticed and I am not sure if it is normal is that if I choose say Reboot System Now from CWM menu and it shows like 10 entries with many No's and only one Yes. I can only use the volume Up + button to go down, if I try to go up using volume Down - button it does not go up. Is that normal? Is the only way to go is go down using Voume Up button in CWM menus? I have a feeling that my Volume Down button has gone crazy and it is not functioning properly and that is what is causing it to go into APX mode at the startup as well.
Anyway I first attempted "Apply SDCARD:update.zip" hoping that it might continue with the stock 3588 installation, but that failed. You can see the messages in the picture. Then I tried the Factory Reset and it was successful. I then rebooted the tablet. But now again it keeps on going up into APX mode. I will have to wait until tomorrow for it to completely drain battery again and then try to reboot again.
Any ideas? I know it is overwhelming and the behavior is very weird. At this point I am trying to bring it back to the stock firmware so that I can get this tablet replaced under warranty.
There are quite a few things that are not acting normal from what I see here.
Did you try to repartition 2048 and 0? If not, I would start with that then I would format everything and re-nvflash a stock ROM onto it. That might clear things up. If not you could be looking at a hardware reset.
I installed clockworkmod per instructions.
When I press the on and volume up buttons I get the appropriate message and then the system boots with the tap n tap (ugh) rom.
I never see a clockworkmod menu
What am I doing wrong?
I am having the same issue!!! I am beyond frustrated right now. I have downgraded to 1.1 and had success during one try and from now on trying to boot into Clockwork it won't let me. All it does is say booting from kernal image and then goes to the splash screen then to the box with the down arrow and continues until it goes right back to the viewsonic birds and boots to the normal rom again.
What the He!! am I doing wrong here? I have already done a factory reset with data wipe...
Instructional video
See if this helps.
How to install Clockwork mid and tnt lite - Pensacola computers
http://www.youtube.com/watch?v=27oDBi-x760
argusvision said:
See if this helps.
How to install Clockwork mid and tnt lite - Pensacola computers
http://www.youtube.com/watch?v=27oDBi-x760
Click to expand...
Click to collapse
That is exactly what I was watching and following when this happened to me. Any other ideas? I did however just return the other one after clearing the data and got another one so I am going to try and avoid doing that again.. I am going to try and tread slowly here so I can get things right....
I've had 100% success using the instructions here:
http://forum.xda-developers.com/showthread.php?t=861950
Go to the first link (Dropbox) and, if Windows, download the 2 zipped files. I will say I bought a Viewsonic G tablet back in December and I had to used the older zipped file in the DEPRECATED folder. My latest Viewsonic G tablet works with the latest files.
Unzip the 2 files, combine into one folder, plug in the USB cable, and reboot by holding the POWER button *and* the Vol- button. You should see the initial boot screen but should quickly see a black screen. Run the .bat file (nvflash_gtablet.bat). If the computer doesn't see the tablet, read the above link on how to make sure you've installed the drivers for the tablet. Once the batch file ends, your tablet will automatically reboot. I would suggest powering off the tablet before it reboots as you can install CW_Mod via NVFlash, which is what I do. Grab CW_Mod 1.1 (not 1.2). Unzip the UPDATE.ZIP file and copy RECOVERY.IMG to the folder where you combined the 2 zipped files from Dropbox. Connect your tablet to your PC via the USB cable. Reboot the tablet again by pressing the POWER button while holding the Vol- button. Same thing--i.e. initial boot screen, then a black screen. Either create a batch file or run the following command (sorry cannot remember the thread where I found this, so I take no credit for this):
nvflash.exe --bl bootloader.bin --download 9 recovery.img
This is a quick process. Once the command finishes. Unplug your USB cable from your tablet and hold down the POWER button to turn off your tablet. You can either power it back on or power it back on and check to make sure CW_Mod is installed (recommended). For this, press the POWER button while holding down the Vol+ key until you see the line of text appear in the upper left hand corner of the screen.
Again, on one of my Viewsonic G tablets, I had to use the zipped file contained in the DEPRECATED folder on the Dropbox. I can't remember what the current files did (think soft-brick).
Good luck. As I've said, I've used these steps so many times as I went through every 1.1 ROM and 1.2 ROM trying to find the one I liked and the steps were perfect. At this point, though, while in CW_Mod, I would go through the process of partitioning your system and formatting stuff.
Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do
Yes, I know this is a common issue. But My Gtab is really stuck. I tried days of following the stock Bekit install. Everything installs just fine and after the nvflash it goes right into the opening screen and starts up normally. Never see birds.
The issue is if I power off, it cannot reboot, always goes to APX mode. I tried several times.
If I run a command such as nvflash --bl bootloader.bin --sync --go I can get back into the startup screen and the tablet runs normally.
There must be a file missing that is part of the normal booting sequence. Is there something missing that the stock install doesn't do?
Yes I have installed CWM and repartitioned and cleared the data. Many times.
Can run the tablet fine if I start it from APX mode, just can't start it from the power button.
I also tried to update to 3588 with same results. Nothing allows a boot from the power button.
I also tried all the files on the "dummies" site. 1.1 and 1.2 install and run just fine, It's just if I power down the tablet. I only get APX mode when powering up.
I also let the tablet update over the internet to version 1.2.5699. It downloaded, then did a restart and went into APX mode. When I forced a boot in APX mode it came up with an android and a red triangle. Another APX boot got me back into version 1.2.4349
Even if I do a reboot from CWM it shuts off tablet and then the power button goes into APX mode
Any help is greatly appreiated.
Try this. My old Gtablet got stuck in APX mode....was like that for about 8 or 9 months until I followed the link in this thread here...
http://forum.xda-developers.com/showpost.php?p=19175683&postcount=106
Possible vol rocker internally stuck
dcol said:
Yes, I know this is a common issue. But My Gtab is really stuck. I tried days of following the stock Bekit install. Everything installs just fine and after the nvflash it goes right into the opening screen and starts up normally. Never see birds.
The issue is if I power off, it cannot reboot, always goes to APX mode. I tried several times.
If I run a command such as nvflash --bl bootloader.bin --sync --go I can get back into the startup screen and the tablet runs normally.
There must be a file missing that is part of the normal booting sequence. Is there something missing that the stock install doesn't do?
Yes I have installed CWM and repartitioned and cleared the data. Many times.
Can run the tablet fine if I start it from APX mode, just can't start it from the power button.
I also tried to update to 3588 with same results. Nothing allows a boot from the power button.
I also tried all the files on the "dummies" site. 1.1 and 1.2 install and run just fine, It's just if I power down the tablet. I only get APX mode when powering up.
I also let the tablet update over the internet to version 1.2.5699. It downloaded, then did a restart and went into APX mode. When I forced a boot in APX mode it came up with an android and a red triangle. Another APX boot got me back into version 1.2.4349
Any help is greatly appreiated.
Click to expand...
Click to collapse
Could be the contact portion of the volume rocker is stuck (I've heard of one user with this issue). Remove the back cover & disconnect the volume switch connector at the motherboard (see attachment) and then try booting.
Al
Tried tcrews suggestion. Same result. APX only on power on. Only thing different was the partitioining 3 times. Didn't work.
Volume button works perfectly. When I am in the tablet, it adjusts volume up and down correctly.
Give K J Rad's technique a whirl.
Tried that one already. Think I am going to just toss it and give up on this and just assume there is some sort of hardware problem with this Gtablet.
I must have reflashed it at least 25 times and spent days on it. I give up. Shame it works fine if you boot it from the APX mode, just not from the power button.
dcol said:
Tried tcrews suggestion. Same result. APX only on power on. Only thing different was the partitioining 3 times. Didn't work.
Volume button works perfectly. When I am in the tablet, it adjusts volume up and down correctly.
Click to expand...
Click to collapse
Did you do all the partitionings ?
Like I said, mine was stuck for near 9 months (just kept it charged and running...if it shutdown would APX boot it).
I tried every nvflash fix that was posted but when I followed the one I linked exactly, it worked. Shocked me since I had tried so many other sure fire methods didn't.
dcol said:
Think I am going to just toss it and give up on this and just assume there is some sort of hardware problem with this Gtablet.
Click to expand...
Click to collapse
Before you give up, do this for me.
Get bekit's standard 2010110500 zip file. Edit the batch file (or shell script) in it and remove the ``--go'' parameter if there is one. Flash the images. The tablet should remain in APX mode. Now run this command:
Code:
C:\SOME\PATH> [B].\nvflash -r --read 2 a2.img --read 3 a3.img --read 4 a4.img --read 5 a5.img[/B]
After the command completes power the tablet off and immediately boot it back into APX mode. Run this command:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --read 2 b2.img --read 3 b3.img --read 4 b4.img --read 5 b5.img --go[/B]
Let the tablet boot into the Tap 'N Tap desktop, then power off. Put the tablet into APX mode and run the previous command again (change the file names to cn.img). Now you will have 3 sets of img files. Upload all of them somewhere so I can compare them with each other and with my bekit img files.
If everything checks out ok, I'll give you another nvflash command to run and if that fails, you can give up.
I've tried all techniques posted and I can't boot anymore and don't see birds either.
I can nvflash all day long but once it shuts down, I need to use nvflash to boot it up again.
Go it.
I used nvflash to stock 1.2-4349 as I had been doing according to these instructions:
slatedroid com/topic/22124-how-to-recovery-when-gtab-does-not-turn-on-and-stay-in-apx-mode/
Then, after booting to the main screen, I let it download 1.2-5699 and shutdown.
I'm still in APX mode at this point.
Then, I referred back to those instructions and and held Vol+ along with power but I never let Vol+ go. It brought me to the blue Android recovery. I ran 'update.zip' right from that menu and it brought up something different I had never seen at the bottom in yellow text (unfortunately I was so suprised that when I grabbed the tab, I hit the home button to reboot) but it said something like /tmp/bootloader.bin=[0]....
I pressed power by itself and I finally saw birds. 4 days of this **** I'm leaving it alone for a while. :-D