First, thanks for all the amazing information on this site, it's an awesome resource to have.
I've been searching around for quite a while now trying to figure out how to get my gtablet working again and have hit a wall. Right now I can get into APX mode, but not CWM. First I tried restoring with nvflash following this thread:
http://forum.xda-developers.com/showthread.php?t=861950
Everything seems to work, but then I get stuck in a loop at the tapntap screen (It shows tapntap, then n, then tapntap, then n, etc). Next I tried to setup CWM with nvflash using this guide (other tapntap loop problems lead me to try this):
http://forum.xda-developers.com/showthread.php?t=1030042
But I have not been able to boot into CMW. The gtablet always goes back into APX mode. At the moment, it will boot into APX mode, and show the "NVIDIA USB Boot-recovery driver for Mobile devices" in device manager, even when I only press the power button (and don't hold down volume -). Holding Volume + while turning it on also goes into APX mode. Everything I have tried just leads to APX mode, except trying to restore with nvflash, which leads to tapntap loop.
All of the similar problems I have found where solved with these steps, so now I'm not sure what else to try. I've also tried to restore from an external SD card, but it doesn't seem to do anything. Every way I try to boot it it just goes into APX mode and ignores the SD card.
I've also tried this guide:
http://forum.xda-developers.com/showthread.php?t=974422
And I got the red message (which was exciting because it was finally something different ), but still got stuck in a tapntap loop after restoring with nvflash.
Anyone have any advice or something else for me to try? I would really appreciate it.
Thanks for reading
See this post.
After you've got CWM installed OK, boot into it, then partition the SD card (the internal one--remove any external microSD cards). This step will clear out the (internal) SD card. Misformatted or corrupted SD card partitions can also cause boot loops.
Thank you very much for the reply
K J Rad's procedure had a detail that I was missing. I had to hold the Volume + key BEFORE running the nvflash command to add CWM to get it to boot into CWM. After that started working the rest fell into place.
Thanks again!
Related
Hi,
My device started boot looping while trying to restore to stock ROM to update to a new ROM.
I wen't through the nvflash process successfully (meaning nvflash wrote the images to the device) but it continue with the loop.
Eventually, it powered down and now it will not power up at all. Battery is fully charged.
Any ideas?
Thanks.
OK, so I figured out that the device was stuck in APX mode.
nvflash doesn't seem to be fixing the problem, so I'm trying adb. It doesn't seem to see the device at all. I'm sure I'm missing step on how to work with adb.
Can anyone point me in the right direction for getting adb connected properly?
Thanks.
I'm trying to get adb working following this guide:
http://forum.xda-developers.com/showthread.php?t=902860
but it cannot see the device. The drive is installed fine but the device does not show up.
I know that if I can get into the device I can put it in debug mode, but I'm not sure how to do this now. I'm thinking this could be my problem, that the device is not in the correct "mode"
Any ideas?
Thanks.
did you get this resolved? i'm having the same problem.
williec30 said:
did you get this resolved? i'm having the same problem.
Click to expand...
Click to collapse
Nope, still playing with nvflash.
Trying this now:
http://forum.xda-developers.com/showthread.php?t=974422
pgonza02 said:
Nope, still playing with nvflash.
Trying this now:
http://forum.xda-developers.com/showthread.php?t=974422
Click to expand...
Click to collapse
i was able to get the device back into apx mode and run the nvflash utility again.
williec30 said:
i was able to get the device back into apx mode and run the nvflash utility again.
Click to expand...
Click to collapse
I've been able to do that a couple of times, but after nvflash completes, just get into a TapNTap logo loop and eventually just powers down. When I am able to turn it back on, it goes straight into APX mode.
http://forum.xda-developers.com/showpost.php?p=12089833&postcount=92
kostyamat said:
http://forum.xda-developers.com/showpost.php?p=12089833&postcount=92
Click to expand...
Click to collapse
Do you mean to install CW from external micro SD?
Thanks.
This is Where I Stand
1. nvflash from TNT lite post
2. Completes and reboots, goes into GTab screen, no Viewsonic screen
3. TapNTap screen and then to n animation
4. Reboot and go to #3. Haven't counted but at some point it just powers off.
I have tried installing CW from the external SD card but cannot get to it.
Have tried adb but cannot get it to connect.
I'm totally out of ideas...I'm thinking that if I just let it sit there, it'll just work
This is Where I Stand
1. nvflash from TNT lite post
2. Completes and reboots, goes into GTab screen, no Viewsonic screen
3. TapNTap screen and then to n animation
4. Reboot and go to #3. Haven't counted but at some point it just powers off.
I have tried installing CW from the external SD card but cannot get to it.
Have tried adb but cannot get it to connect.
I'm totally out of ideas...I'm thinking that if I just let it sit there, it'll just work
Finally Worked
I have no idea what made it work.
I decided to just take a break and left the tablet connected to the computer through USB but powered down. Came back a couple of hours later and when I turned it back on, I got the Viewsonic screen.
After that, I was able to reboot and go into CW and do a factory reset, which put it in a really old version. It was all easy from there.
pgonza02:
As I understand, you can now power off and reboot you GTab.
Can you recall what were your steps to get to this point?
I'm stuck in APX mode for almost a month! I don't know what else to try...
Thanks in advance.
I tried many things, including:
Install CW by replacing the image for partition 9 with the update.zip for CW (basically rename update.zip to whatever the img file is called)
Add CW to external SD card and attempt to reboot.
Eventually I just left the tablet alone and when I came back I turned it on I saw the Viewsonic birds (this seemed to be the key, when it was not working I never saw it)
I read a thread somewhere that mentioned that nvflash has the ability to redirect output through the HDMI out so you would not see it in the main screen. My guess is that what's happening is that the output of something, that is taking time to complete, is going out that way and I just could not see it. By leaving it alone, whatever it was, completed. This is just a guess, maybe someone with more knowledge can confirm.
Sorry I couldn't give you more details.
Boot loop and black screen
I'm having the same problem. In fact, I'm unable to boot into APX mode.
I have the cover off and read about a hardware reset button. I tried pushing the
reset button (k2) but nothing happened. I also read that I can disconnect
the batter. But, I don't see where the battery wire can be just disconnected
without soldering.
Any ideas?
I followed this guide http://forum.xda-developers.com/showthread.php?t=861950 (Roebeet's post) which brought me back to stock.
However, when I apply the 1.1-3588 the tablet shuts off and is unable to be turned back on. The only way to turn it back on is to run the nvflash_gtablet batch file. At which point a receive a notice saying 'The update to version 1.1-3588' was not successful. Please try again or contact customer support.'
Why is the tablet unresponsive after the failed update? Why must I NVFlash to reactivate the screen?
I searched through the forums for the past hour and although I found similar problems I have yet to run into my exact one. I am hoping to find some help.
Edit*
I have the same problem as another user which can be found here http://forum.xda-developers.com/showthread.php?t=903684
I can NVFlash the stock image (or even the NVFlash of TnT-lite 1.02) and the tablet will boot after the flash and function. Power it off (or do something that requires a reboot) and the tablet will no longer function. No power on (that I can tell), can't boot to recovery......and if I plug the tablet in to the PC I can NVFlash it and it boots. It's like it's stuck in APX mode now. I just have to plug it in to the PC, no Power + Volume- combo.....just plug the USB in and run NVFlash. It boots (to whatever I flashed) and will run until I power it off or try to reboot.
Getting APX mode to function is not a problem......so I can NVFlash it but what I've tried so far has not worked (it doesn't delete the data partition, etc..as I reflash and it's right where it was before I turned it off).
Click to expand...
Click to collapse
The fix posted by acidburn89 was unsuccessful for me
Citi,
I'm not sure exactly what you are doing, but if you are getting the message
you described, that sounds more like you are booting in recovery or a regular
boot and not APX (Power/Volume - to be the white, the black APX NVFlash screen).
My suggestion is to do the stock recovery NVFlash Procedure again. Check
everything step by step to make sure the right files are there and the right
things done.
See if you can complete that and get back to a working bekit 1105 (Stock
Version 2638).
If you can do that, go into Settings/Display and set it so the display does not
turn off).
THEN, if it offers you the OTA Update, let it run.
If it is unsuccessful again, post back here and I will see if I can find the file
and instructions to load 3588 manually.
Hope this helps,
Rev
Ok so I reread Roebeets NVFlash post and double checked my files. All of them are there and in the correct location. I set up my USB drivers, booted into APX mode and ran the nvflash_gtablet.bat
Then the tablet loads properly into the stock TNT 2638. After setting up my WiFi I get a notification that the 3588 update is available. I download the update and after it ask me if I would like to apply now or later. I have tried both options however both seem to fail.
At this point if I hit apply now it shuts down the tablet however it does not turn on. The only way to turn it on is using nvflash_gtablet.bat file. Which it then boots up properly (and it is not wiped, it's as if it is jut turning on normally)and I either get one of two errors.
'The update to version 1.1-3588' was not successful. Please try again or contact customer support.'
or
'The update process cannot proceed due to an unrecoverable error. More information about the error is below, 'Verify checksum: file was not found. Downloaded file does not exist.null'
Hope this helps, I am not new to rooting/flashing roms but this is a completely new error to me.
Citi,
Did you do what I said about setting the display not to go off?
I tell people to do that because I have heard that it can
interrupt the download.
Whatever is happening, it seems like the download is not happening
or not finishing.
You can go to the Developer Forum (or there may be one in General)
and find the thread that tells where to download the .zip version of
the OTA 3588 download.
Then go down to end of the top 4349 thread in General and I wrote a post there for a
guy on how to install an update from the .zip file.
Rev
Yup I set the display to never turn off. However, it seems as if I have this problem http://forum.xda-developers.com/showthread.php?t=999832
I am currently working on this method
Edit* Well I figured out the exact problem however the link I posted was unable to solve it
Another thread on my problem, and the fix found to work for others has not worked for me,
http://forum.xda-developers.com/showthread.php?t=903684
Just bumping this as it is still relevant and it seems to be a unique issue, as all past solutions have yet to fix this problem. I spent the whole day on IRC and have seemed to stump a few people. Looks like I may have the first fully bricked tablet
Have you tried re-partitioning?
Can't get into CWM to do so, stuck in an infinite APX mode and I can only turn the power on via an NVFlash
Citi said:
Can't get into CWM to do so, stuck in an infinite APX mode and I can only turn the power on via an NVFlash
Click to expand...
Click to collapse
get the recovery.img from from cwm .8 zip file and then use nvFlash to load that.
nvflash --bl bootloader.bin --download 9 recovery.img
(make sure you put the recovery.img in you nvFlash folder and then issue the command above. That will install cwm .8)
from what you wrote above it seems like you are getting stuck in apx mode when you reboot. So my question is what files did you download to setup your nvFlash????
I will attempt to load CWM using NVFlash, and I followed this guide EXACTLY http://forum.xda-developers.com/showthread.php?t=861950 for NVFlash for windows
Citi said:
I will attempt to load CWM using NVFlash, and I followed this guide EXACTLY http://forum.xda-developers.com/showthread.php?t=861950 for NVFlash for windows
Click to expand...
Click to collapse
which files did you download from his dropbox????? I am more interested in knowing if you used nvflash_gtablet_2010110500.zip or nvflash_gtablet_46_2010112600.zip????
I initially used that nvflash_gtablet_2010110500.zip and had the same problem as you few weeks ago. So I tried using nvflash_gtablet_46_2010112600.zip and that worked a lot better for me .
hope that helps...let me know if you stuck anywhere.
enjoy
Unfortunately I tried out both with the same result
So the problem has changed from not being able to load an update to being in an APX loop? If I understand your original post correctly you were indeed able to nvflash back to original stock and boot normally. Then it failed when you tried to do the update to 3588. If you can still do that...
1) nvflash to bekit's 1105 stock
2) do not install the update
3) clear cache and data with Method I from: http://forum.xda-developers.com/showthread.php?t=1030915 - If this fails due to not being able to enter recovery then your nvflash was no good. You'll need to verify that you have the correct drivers installed, you're using the correct version of nvflash and that your image is sound. Easiest way to do that is to download them again.
4) install ClockworkMod .8 using MicroSD card method.
5) Re-partition 2048 and 0
Were there any error messages in the output of your latest nvflash attempts?
I posted on how you can get cwm .8 installed on your tablet if you are stuck in apx mode. There are also other threads that are pinned under the development section that explain how you can get cwm .8 using nvFlash. You will need that to get out of the apx loop that you are stuck in.
The problem is found here http://forum.xda-developers.com/showthread.php?t=903684
I can NVFlash the stock image (or even the NVFlash of TnT-lite 1.02) and the tablet will boot after the flash and function. Power it off (or do something that requires a reboot) and the tablet will no longer function. No power on (that I can tell), can't boot to recovery......and if I plug the tablet in to the PC I can NVFlash it and it boots. It's like it's stuck in APX mode now. I just have to plug it in to the PC, no Power + Volume- combo.....just plug the USB in and run NVFlash. It boots (to whatever I flashed) and will run until I power it off or try to reboot.
Getting APX mode to function is not a problem......so I can NVFlash it but what I've tried so far has not worked (it doesn't delete the data partition, etc..as I reflash and it's right where it was before I turned it off).
Click to expand...
Click to collapse
And I attempted to install CWM using the NVFlash method with no success. It seemed to install however when I booted the system back up (using the batch file) I saw the "Android" screen and then the tablet went black, no green CWM menu appeared or anything
rbansal2 said:
I posted on how you can get cwm .8 installed on your tablet if you are stuck in apx mode. There are also other threads that are pinned under the development section that explain how you can get cwm .8 using nvFlash. You will need that to get out of the apx loop that you are stuck in.
Click to expand...
Click to collapse
Citi said:
The problem is found here http://forum.xda-developers.com/showthread.php?t=903684
And I attempted to install CWM using the NVFlash method with no success. It seemed to install however when I booted the system back up (using the batch file) I saw the "Android" screen and then the tablet went black, no green CWM menu appeared or anything
Click to expand...
Click to collapse
If the screen is blank then connect it to your computer and see if your tablet is in APX mode. You will probably hear the usb connect sound and you can go in device manager to see if it is connected. Let me know and then we can go from there
Yes it has been in a permanent APX mode since my original NVFlash, with the only way to turn the tablet on is to use the nvflash_gtablet.bat file. This will bring the tablet to TnT however my data has not wiped since my original NVFlash and the Wifi and other information is still present. It prompts me to download the new update however there is no need since once the tablet shuts down it will go to APX mode, with a rinse repeat of the cycle and I use .bat file to turn the tablet on.
ok try this...not sure if it will work but its worth a try
1. replace part9.img with the recovery.img ( i m sure u have done this already. this is so cwm .8 gets installed when you do a full nvFlash)
2. when you boot on for the first time.. press the power & + so you go in cwm .8.
let me know if you access cwm .8 if you do this ....we'll move forward from there
Failed first time I did it, but I just tried again and what do you know...success, unsure why.
Currently sitting in CWM looking at that beautiful green screen. I am in the IRC room if we could continue there that would probably work better and faster.
ya i m still at work and cant get on irc here :/...but if you are in cwm .8 then first thing i would do is wipe data then clear cache and then clear dalvik...then go under mounts menu and mount all the partiontions and then format all the partitions...once you are done with that i would mount your tablet so you can see is as a mass storage device on your computer and upload stock frimware 3588 on there...
use this link http://forum.xda-developers.com/showthread.php?t=861950 and go down to post nvflash and get the 3588.zip
from the 3588.zip get the update.zip and copy that to your tablet...once u have that go to the main menu of cwm .8 and choose the option to install update.zip form sdcard...i thikn thats the second one down
try that and see if it works...if not then i'll on irc in the evening today and i'll help you out ...dont stress we'll get your tablet up and running again
Ok, I did a NVflash using method on site and now the birds come on then gtab like it going to load and then off. Just continues the pattern. I tried to run Cwm through an eternal sd but it is not picking it up. I hold the recovery key and power button but it doesnt change the pattern. Can anyone help me.
Not enough info to help, but if you are using cwm, then why are you using nvflash? Or vice versa. Nvflash back to 3558.
You need to do a data wipe. Since you're looping you'll need to load CWM during your nvflash. Replace part9.img in your nvflash folder with recovery.img from the ClockworkMod install zip. Then do the nvflash. Then boot into recovery and clear cache, data, etc. When you reboot after that it should work fine.
Similar Issue
I'm experiencing a similar issue after loading Honeycomb. The system ran well for a while, then got stuck at the viewsonic boot screen. Recover does not load so I cannot perform a data wipe. Any thoughts?
You likely need to nvflash.
I tried NVFlash, but my PC won't detect the device anymore either. I also tried CWM for SD, but the tab still just sits at the Viewsonic boot screen
Update
I tried again from another PC and nvflash is working. It appears I have a usb issue on my first machine.
Hello there,
I accidentally installed a 1.2 ROM onto a 1.1 loader (I know. I know) When I turn my g tablet on, it just stays on a back-lit black screen. When I push the volume button to go into recovery it does this:
"Detect a recovery key pressed"
"Booting recovery kernel image"
It stops there. I have tried using an external SD Card and putting a recovery folder (and changing it to SDCARD2), and renaming tnt stock to update.zip. It doesn't work.
Also I tried looking into nflash. But, my computer doesn't recognize the tablet. IT DOES NOT EVEN RECOGNIZE THAT A DEVICE IS CONNECTED WHEN I PLUG IT IN. So I can't do the drivers thing. I am not sure what to do here.
I am not sure if I perm-bricked my tablet. I hope someone can help. Thank you in advance.
You need to NVFLASH your device back to BL 1.1 or with the one with BL 1.2 ... see this:
http://forum.xda-developers.com/showthread.php?t=842000
and
http://forum.xda-developers.com/showthread.php?t=861950
and
http://forum.xda-developers.com/showthread.php?t=844088
good luck
The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
WidePants said:
The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
Click to expand...
Click to collapse
I'm having the same problem. I downgraded from 1.4.3 to 1.4.0. I was able to boot it once and then shut it back down so I could root it. Now it won't start up at all and I have tried everything that I can find to boot it to no avail.
The NT can sometimes get stuck in limbo while booting up, especially with SD-based boot. To get out of it, hold down the power button for 20-30 sec to turn it off then power it on again. Also remove any "bootable" SD card from the card slot; if it boots then the card was not bootable and its non-bootability was the problem.
It's also possible that the NT battery is completely drained (battery readings on some CM builds can be quite off, sometimes as much as 20 points) in which case you'd need to use the BN wall-charger and charge it for 8-12 hours.