Related
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.
Hi all -
I was attempting to load Cyanogen onto my Gtab. Seemed to be going well. I downgraded from TnT 4349, got clockworkmod on and tried flashing CM. Not exactly sure what happened but I never got CM running.
Now I can't boot into clockworkmod after running nvflash. Tried it dozens of different ways. Here's the cycle of what currently happens:
I power down my Gtab. Put it in APX mode (Power + Vol Down). Hear USB connect on my computer, dont' see the birds logo, just black screen.
Run NVFlash batch file. Gtab screen comes on, "Entering NVFlash recovery mode / Nv3p Server". NVFlash runs successfully according to its read outs.
Gtab reboots, goes through loader screens, and is up and running. TnT works fine.
Power down. Try to get into recovery (Power + Vol Up). Hear USB connect on my computer, nothing happens. Black screen. If I press power again, I hear the USB disconnect sound. If I hold it down for 10+ seconds, I hear the USB disconnect sound, a short pause, then the USB connect sound again.
Lather, rinse, repeat.
I've tried flashing every version of TnT I can find, with/without clockworkmod, nothing works. As soon as I power down my device, it won't turn back on. Just a black screen and the USB connect sound.
I've been searching xda-developers for a solution for days now. Every fix I try that sounds remotely like my problem has not worked. Tried the FORMAT Nvflash as well.
From what I've been reading, it sounds like I am "stuck" in APX mode. Is there any way to definitively get out of APX mode?
Running Windows 7 64 bit, going to try the process from Ubuntu but not very hopeful it's going to make a difference.
Any help would be sincerely appreciated!
Spoke a little too soon...
I must've finally entered the magical combination of search terms, because I finally stumbled across this post:
http://forum.xda-developers.com/showthread.php?t=1038689&page=12
K J Rad's method got me part of the way there... The big secret is:
Hold down the Volume Up before running NVFlash, and keep holding down for a few seconds after it starts.
Once NVFlash finishes, my GTab displayed that a recovery key had been detected! And I got into recovery!!
NVFlash hung up on Step 9 of Part II... and I started to panic... But after another round of repartitioning, clearing data/caches, and a little more fiddling... I am now the proud owner of a GTab running Bottle of Smoke Honeycomb! That reboots and everything HC is bad a$$... A little shaky stability wise but awesome to see what's to come.
Much thanks to this forum and all who spend their time troubleshooting tricky devices like these!
This could be a full bricked. The HP tablet wouldn't turn on.. I tried entering developer mode with special button combination, windows picks up palm but fail to install the drivers.. I've tried many things and nothing works..
The issue happened after installing android os..
The screen is pitch black.. If I connect the usb normally the middle button flashes with lights but the screen doesn't turn on..
Would someone be able to help?
Has it ever booted into android?
Edit: Either way, try holding power + home button from 15-30 seconds.
Sent from my HP Touchpad using Tapatalk
Sorry about the late reply
Yes it has booted into andriod for 20 min.. Then bricked. I tried power+home and nothing happens. I have to do power+home+volume up button while just putting in the usb cable and got a "found new driver" but it doesn't finish installing.. and listed as palm. I tried to enter QHSUSB_DLOAD and I download and install the driver but I'm unable to restore the os with webosdoctor or something similar.
I got the screen to flash for a quick 1 second once... by tempering around with the buttons.. Don't think that'll help much?
post edited from getting more info.
Ok I'm reading forum and they say it's hardware failure. I guess to call them....
try to install these novacom drivers:
http://forums.precentral.net/canuck-coding/278224-universal-novacom-installer-uni-v1-2-1-a.html
if you hold the power button and push 10 times the middle button it will make a reboot.
try to get into developer mode by pushing power up and volume up, maybe now it will recognize. what did webos doc say? what happens?
the flashing of the middle button happened to me often.if you charge your hp touchpad it should be gone.
Hey thanks.
The novacom driver I've installed that with WebOSQuickInstall though trying to enter recovery mode doesn't work as webos doc doesn't allow me to click next. The holding the power button and pushing 10 times the middle button seems to work kinda.. It shows a quick low battery image and shut off.. <strike>I'll try giving it another 30 min of charge and try again then..
good luck.
Over an hour have passed now. The screen can turn on now with holding power or wall charging.. It has stopped accepting charges from computer and asked for usb/adapter change. I don't see the battery power bar going up at all. Though I can't boot in OS.. I've tried WebOS Doc and still the same problem where the next is grey out.
I'm thinking it's software probs not hardware related for the battery..
Let it charge full if possible, can you get into developer mode? have you installed the drivers from the link i have given? do you use the usb cable from hp?
I'm not sure how long it'll take to fully charge but I've been charging for 1 hour and I don't see the battery bar advancing. I'll leave it on for 3 hours to charge.. I unno.. I can't get into developer mode, I have installed the drivers you gave me and I do use the usb cable from hp. I'm unable to boot up the HP logo..
http://i751.photobucket.com/albums/xx151/Erogiz/capture_003_18102011_091241.jpg
With out being able to install the driver I can't enter recover mode right? I've tried uninstalling it and plug it in.
I couldn't sleep last night not because of the tablet.. But I'm off to bed.. I'll check back when I wake up.
deinstall the palm drivers, reboot the pc and reinstall them,
then press power and volume up on your touchpad untill it is schown in windows. then i would do this:
go to the palm directory in program files in windows. copy the attached file i send you to this directory. ( unpack it first )
then start cmd in windows. go to the directory of palm. i hope you know some dos commands. ( cd c:\program files\ palm, inc\ ) and typ:
novacom boot mem:// <nova-installer-image-topaz.uImage
this should boot up novacom driver in your hp touchpad. and now webosdoctor should find it.
hope this will work
.... Your right let it fully charge... duh me... CHEEEEEEEEEEERRRRRRRRSSSSSSS! i panic too much... it just means kinda a lot...
so it booted?
Thank you for all the assistance as I've just expirenced that problem last night. I will try this once I get off from work. I will try to provide any assistance as well if your methods work. Thank you again in advance.
In my situation all I needed to do was hold the home and power button down for 60 seconds.
Also I noticed when left unattended it will "blackout" just repeat the process, and you should be good to go.
I might not have got enough sleep last night, so please excuse me if I missed this out right in the how to.. but I was up to 5 am last night putting Preware on my HP Touchpad and CM 2.1. The installing of Apps and playing in both ensued into the wee hours..
In my excitment I woke the wife.. and not thinking straight I thought I could get to the CWM via the same method as I used to building it. I pressed Vol Up and Power and it went back to USB bootie mode, and I couldnt get it out of that mode.. eventually I just reran the Acme installer. thewife went back to bed unimpressed.
So here is my question, I know how to boot from CM how via reboot into recovery mode, and then I can choose to boot to WebOS or CM. But from WebOS, how do I boot into Android? Or how do boot back into the Clock work menu so I can choose again ?
Thanks,
SorrowsTyr
.
There is an application in Preware called Cyboot that allows for what you want.
Or
You can install the patch that adds new buttons to the drop down power menu
Or
You can go to "Device Info" > "Reset Options" > Reboot
Yes! That us exactly what I want. Installed cyboot and Adv. Reset Options.
Thanjs!
Sent from my LG-P999 using XDA App
sorry for hijacking the thread,
but if i am stuck on the white usb screen, how do i get out of it?
Like for my phone, if i am in download mode i just take out the battery and restart my phone...but i dont we can remove battery in the Touchpad....
If you followed the instructions in the Dev section you should have installed Moboot, which give you the option to choose your OS when booting/rebooting.
viny2cool said:
sorry for hijacking the thread,
but if i am stuck on the white usb screen, how do i get out of it?
Like for my phone, if i am in download mode i just take out the battery and restart my phone...but i dont we can remove battery in the Touchpad....
Click to expand...
Click to collapse
Hold down power and home for about 30 sec.
Hello,
I am trying to get to developer mode on my HP 14 G3 and it gets stuck on the "preparing system for dev mode" screen. The progress wheel continues to spin but over an hour on the last attempt made no progress.
In recovery mode, ctrl+D, it goes to transitioning screen, then preparing system screen. Progress wheel freezes momentarily with "starting in 30" displayed top left (does not count down) and then "/sbin/clobber-state: 1: pv: Input/output error" is displayed and the progress wheel starts spinning.
Have made 3 attempts so far. No trouble booting back up normally, powerwash after 1st attempt. Anyone know what's going on?
Thank you in advance.
I have the same
I have the same error
What do you do with it ?
I have the same problem I can cancel the process by reverse proccess. I would really like to put liquid sky on my chromebook
Who knows.
Try going to settings then find about device, press build number 7 times. Done. ~P
Somebody found a workaround . scroll down to comments or search for 2clobber"
I might have a solution, but you’ll need to make a recovery USB first. When it stops working press escape, refresh, and the power button to bring you back to the Chrome OS has stopped working screen. Put in the USB and the chromebook will boot up normally, but OS verification will still be off since you never turned it on
Click to expand...
Click to collapse
sorry for digging up
NoDiskNoFun