Hi, I need some help
I have a 32G touchpad and I let it totally discharge.
Now the unit does not boot past the big USB sign.
I do not mind losing the info on it, there wasn't anything really important.
I am using the Novacom Repair Android Tool.
I did the C/Boot and the Wipe All and it always came back to the USB sign.
Finally, I decided to try "Toolbox" (the one on the left) and finally I could get past the USB sign into Touchpad Toolbox.
I tried installing Android again, loaded the ROM, Gapp and Recovery
and when it had to reboot to finish installing android it went into the USB sign again.
Right now I executed again ToolBox.
Battery reads at 12% now
I want to think that the installation failed due to to the low battery, although it has been the whole time sitting on the wireless stand (Battery should have been around 3 to 4% when I tried the intall).
My plan right now is to let it charge to 100%, it seems to be rapid charging now that it is on the Touchpad Toolbox menu, instead of trickle charging.
If I try again to install, with a full charge, and It goes back to the USB sign, what can I do? Could it be a stuck volume up button and I would have to dissasemble (I'd rather not). What else could I try to recover the Touchpad?
Thanks
HI.
Still stuck.
Touchpad Toolbox reports 100% charge on the Touchpad.
1. Verified Android install files are on ttinstall subdirectory. Executed Install. Upon reboot, I was sent to the USB sign.
2. Applied ToolBox and regained the Toolbox on the Touchpad
3. Reflashed A6 Firmware. Upon reboot, I was sent back to USB sign
Do not know what else to try!
Still stuck
ran the Complete Data Reset of the Toolbox menu and ran WebosDoctor
WebosDoctor ran well without problem but upon boot it went back to the USB sign.
What can I do?
still stuck
Downloaded Flintsmant recovery
unzipped it
ran the novacom driver (linux system)
connected the touchpad to the usb port
issued "novacom boot mem://<uImage.Recovery"
The touchpad booted in recovery mode, installed the android and gapp that were in ttinstall and when it rebooted it went into the USB sign.
Could be a worn/stuck volume up button? I t seems to work normally when running tptoolbox.
Am I going to have to open up (gasp!) the touchpad?
Really need advice here
Related
Hey guys, I'm having an annoying problem here.
When I try to connect my phone to a computer, it just goes straight to charging, it doesn't even recognize on either end that a USB is connected to a computer. Now, sometimes I can force it to work, but that is like around 200 tries and it finally connects. I suspect it might be in test mode (but I'm not sure, I tried pressing # on the dialer to see if it pops up but nothing shows), so I've tried to follow the instructions to flash a .tot file by pressing power + volume up, unfortunately, the computer still doesn't recognize anything is connected, and neither does LGNPST. I have all the drivers properly installed (I was able to successfully downgrade to zv7/install gingervolt last week), and am out of ideas on how to get it to work. Any help would be appreciated.
So far I've tried about 6 different cables in four different USB ports to no success.
pow + vol down (hard reset) should work, phone has to be completely off. not even the charging animation. unplug from pc, pull and replace batt, put batt in then plug into usb then hard reset (hold until factory reset pops up) 10 secs or so
this has allways worked for me no matter how badly i messed up the phone.
Well, I tried your method of a hard reset and it still didn't work. Any other ideas? Is there any way to make the computer force to recognize the phone when its in emergency download mode?
I'm having a similar issue on a friend's phone
Edit: http://forum.xda-developers.com/showthread.php?t=1564941 I think this is the solution
I followed the instructions exactly, and LGNPST still isn't noticing anything and won't go into emergency mode......this is frustrating me....if I can just get this thing back to stock and lose cwm i can just take it to the store and get a new one.....
*EDIT* Well it randomly decided to connect to my computer again. The problem now is as soon as it goes into download mode(LGNPST is at around 11% complete and about to start on the Masterbin), it loses the connection to the computer and can't finish flashing the tot file....ugh..
Anyone have any ideas? I'm going crazy over here trying to figure out whats wrong. Every like 100th try, it will connect to the computer still, but if I try and run mt's revoallinone package it fails to unroot (says access is denied or folder not found), or try lgnpst it loses the usb connection the second it goes to that download screen.
Depending on what version your on or where your at as far as root stock etc this may or may not work i am at a loss, try this http://forum.xda-developers.com/showthread.php?t=1626198
Yeah I've tried that. On the occassion that the COM port reveals which port is the phone(usually on the 100th time of reconnecting the usb cord and successfully able to go into usb debug) I run that program, only for it to state that this is not a lg revo and auto close before I can get all the log data. Its frustrating...I only started to have this problem when I installed GingerVolt.....
Will adb recognize your device, because i had the same issue on a newer revo, you say your on gingervolt then you should be able to set up root acces and push cwm through adb then boot to cwm and flash sonething anything a recovery or do a wipe from there and i believe i saw a method in the forums for installing a stock os fron a zip. All depending on usb connection though
I have cwm already on there. I want it and the root off and back to stock, but I can never flash a tot and unfortunately I have no experience with adb, but I guess I'll google instructions to unroot via that and see if I can go back to stock via it as well.
A week ago I installed TWRP on my Hp Touchpad, via the GooManager App.
After I rebooted into TWRP it showed a error message. I cant remember what it said. First I just let it broken, but then I wanted to update SlickleROM from Version 1 to 1.1. But i couldnt use the Recovery System, because it didnt work.
So I tried to install the Clockworkmod Recovery and the new ROM with ACMEInstaller2 and ACMEInstaller3, but ACMEInstaller3 did nothing, it just showed the HP logo. ACMEInstaller2 showed a Error Message, that /boot is out of space. So i decided to reset my Touchpad.
First I used ACMEUninstaller to uninstall Android. Then i used WebosDoctor to remove all data, but it said it couldn't reset my phone after a few minutes. My Touchpad could'nt boot. It just shutdown everytime it was booting. I stopped the endless rebooting with holding Power Button and Pressing Home Button 10 Times. After that I tried to doctor serval times with older versions and tried to find out what was happening. But then the battery was too low. WebosDoctor could charge it and in the outlet it just charged until it was booting again, so i could charge enough to doctor the device. Now I have a not booting Touchpad with a too low battery to doctor.
I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work
Does anyone know what I can try to do?
ss0198 said:
A weekhttp://goo.im/devs/jcsullins/cmtouchpad/testing ago I installed TWRP on my Hp Touchpad, via the GooManager App.
After I rebooted into TWRP it showed a error message. I cant remember what it said. First I just let it broken, but then I wanted to update SlickleROM from Version 1 to 1.1. But i couldnt use the Recovery System, because it didnt work.
So I tried to install the Clockworkmod Recovery and the new ROM with ACMEInstaller2 and ACMEInstaller3, but ACMEInstaller3 did nothing, it just showed the HP logo. ACMEInstaller2 showed a Error Message, that /boot is out of space. So i decided to reset my Touchpad.
First I used ACMEUninstaller to uninstall Android. Then i used WebosDoctor to remove all data, but it said it couldn't reset my phone after a few minutes. My Touchpad could'nt boot. It just shutdown everytime it was booting. I stopped the endless rebooting with holding Power Button and Pressing Home Button 10 Times. After that I tried to doctor serval times with older versions and tried to find out what was happening. But then the battery was too low. WebosDoctor could charge it and in the outlet it just charged until it was booting again, so i could charge enough to doctor the device. Now I have a not booting Touchpad with a too low battery to doctor.
I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work
Does anyone know what I can try to do?
Click to expand...
Click to collapse
Try leaving the tp charging, at least overnight, till it's 100% charged. Then try the guide again. If you're having trouble with novaterm, there's a good work around on page 12.
If you're having trouble with the doctor, either the 8% or the 12%, do a search for either. Don't worry, there's a workaround. Also search the webos nation forum, you'll find answers there also.
Good luck.
Edit : use cwm. Myself and several others here have had problems with TWRP.
Here's the link for cwm : http://goo.im/devs/jcsullins/cmtouchpad/recovery
Use the 12/15 one.
AW: [Q] HP Touchpad no longer booting.
I already that, but it only charges until it tries to boot.
Are you using the cable that came with the TP?
AW: [Q] HP Touchpad no longer booting.
Yes.
AW: [Q] HP Touchpad no longer booting.
The problem is, that it tries to boot, but it can't boot.
Have you tried to power it down whilst still plugged in ?
AW: [Q] HP Touchpad no longer booting.
What do you mean with:
sstar said:
Have you tried to power it down whilst still plugged in ?
Click to expand...
Click to collapse
What I mean is you have your TP charging and it automatically boots when it has sufficient charge, while leaving still connected to the charger have /can you turn it off but leave it connected?
AW: [Q] HP Touchpad no longer booting.
I will try it now.
AW: [Q] HP Touchpad no longer booting.
I just tried it, but it instantly reboots after turning it off.
It's obviously stuck in some sort of loop, my final thought is to hold both power and volume to put it into recovery and leave it so that it hopefully continues to charge .
You said you had a problem with running chicle's suggestion with the restore your TP to factory condition, how far did you get ?
AW: [Q] HP Touchpad no longer booting.
I alreqdy tried to charge it in recovery mode, but the battery didn't charge either. I tried to reset it with serval versions of the webosdoctor, but as I said it didn't work. It just said it couln't reset the phone. In the console/log it crashed at charging. And it list connection.
When you say ' I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work "
Does that mean you were able to run all the instructions in command prompt and then failed with webos doctor 3.0.0 ?
sstar said:
When you say ' I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work "
Does that mean you were able to run all the instructions in command prompt and then failed with webos doctor 3.0.0 ?
Click to expand...
Click to collapse
Yes.
ss0198 said:
Yes.
Click to expand...
Click to collapse
Well I'm at a loss ,if or when you can try the factory restore commands followed by webos Doctor 3.0.0 again. I had to do it twice with mine.
That's all i can think of. Good luck.
sstar said:
Well I'm at a loss ,if or when you can try the factory restore commands followed by webos Doctor 3.0.0 again. I had to do it twice with mine.
That's all i can think of. Good luck.
Click to expand...
Click to collapse
I already did it twice
Now I finally got it working. I just charged it in Recovery Mode for a long time. Then I just used Webosdoctor and now it works!
Sent from my ss_tenderloin using xda app-developers app
Okay - so Im basically having this issue:
http://forum.cyanogenmod.org/topic/39863-bootloop-help/
Except that WebOS Doctor stalls and says it cant fix my problem. When it reboots it, it just takes me back to Moboot, and I can select something. If i pick recovery, it goes in then gets to 8% and fails.
I can rerun the Acmeinstaller, or uninstaller, but it starts to scroll the script and the screen goes blue. Locks up, then reboots eventually.
Everything WAS working fine until the battery died. Its got a charge now. It powers on instantly when I plug it in. I turn it off and leave it plugged into the wall for days. No change. Sat it on the touchstone for days. No change. Tried many different USB cables. Same thing. My computer recognizes it when I plug it in & I can run basic commands from terminal/command prompt. Ive tried a PC (win 7 x64) and a Macbook Pro (Lion)
Im at a loss for what to do now. Ive googled and searched the forums but I dont think Im using the right search criteria. Any help is appreciated.
I cannot boot to WebOS, it goes to a dark screen then eventually reboots after a few minutes.
I cannot boot cyanogenmod, it goes to a dark screen then eventually reboots after a few minutes.
I cannot boot to Clockwork recovery, it just reboots.
I can boot to WebOS Recovery.
redtxstar said:
I cannot boot to WebOS, it goes to a dark screen then eventually reboots after a few minutes.
I cannot boot cyanogenmod, it goes to a dark screen then eventually reboots after a few minutes.
I cannot boot to Clockwork recovery, it just reboots.
I can boot to WebOS Recovery.
Click to expand...
Click to collapse
Give this guide a try: http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a work around on page 12.
Make sure you have a full charge, you don't want to run out of power while doing the procedure.
Good luck.
So being the airhead I am I let my hp touchpad run out of battery. I charged it and when there was enough juice for it to come on(witch it does automatically) then it went to mooboot, a blue cyanogen mod robot face came on, and after a couple of seconds the screen just goes black, the screens on but black. I let it sit on the charger for a while and then it rebooted itself and did the same thing again. It has not restarted its self since then so I do not think it is a boot loop. anyways I let it boot up in webos so it could charge up to 100% in peace hoping that would solve it, but it did not. So basically webos runs, clockworkmod recovery runs(idk how cwm got on I like twrp better) and I can boot it into the webos recovery(big ass usb symbol). It was running the latest stable cm 10.2 I believe. I actually would perfer to run cm 10.1 because it has bluetooth and is compatible with minecraft pe. If you have any suggestions I would be very graitful. Also if we can avoid phoenix suite that would be preferable because I have a windows 8 laptop that is not very friendly towards that program, if I have to use it, thats fine.
rootedbuddha said:
So being the airhead I am I let my hp touchpad run out of battery. I charged it and when there was enough juice for it to come on(witch it does automatically) then it went to mooboot, a blue cyanogen mod robot face came on, and after a couple of seconds the screen just goes black, the screens on but black. I let it sit on the charger for a while and then it rebooted itself and did the same thing again. It has not restarted its self since then so I do not think it is a boot loop. anyways I let it boot up in webos so it could charge up to 100% in peace hoping that would solve it, but it did not. So basically webos runs, clockworkmod recovery runs(idk how cwm got on I like twrp better) and I can boot it into the webos recovery(big ass usb symbol). It was running the latest stable cm 10.2 I believe. I actually would perfer to run cm 10.1 because it has bluetooth and is compatible with minecraft pe. If you have any suggestions I would be very graitful. Also if we can avoid phoenix suite that would be preferable because I have a windows 8 laptop that is not very friendly towards that program, if I have to use it, thats fine.
Click to expand...
Click to collapse
Get the most recent version of the TWRP zip and put it into the /cminstall folder in WebOS. If you don't have the latest version of moboot (0.3.8) then put that zip in cminstall too. Run the latest version of ACMEInstaller using the appropriate script for your ROM version from your PC. That script should uninstall CWM and install TWRP. If you still have no joy then put the latest ROM and appropriate gapps zips into cminstall and run the script again. Clear the cache before rebooting into android.
Hope this helps.
I've had this issue before. All I did to solve it was to reflash the rom from recovery menu.
That should be all it needs. Its worth trying first before acme, etc etc.
Peace
So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
josh426 said:
So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
Click to expand...
Click to collapse
I have heard no reports of what you describe.
I suggest using TPToolbox v41 from here (download link in that post):
http://forum.xda-developers.com/showpost.php?p=54986968&postcount=293
and try again.
If it does it again, I will need to see a kernel log file to help diagnose what's happening.
To get that, following the instructions on this post:
http://forum.xda-developers.com/showpost.php?p=53258228&postcount=10
but replace steps 1-3 with:
1) Load Touchpad Toolbox
2) Start holding the Volume Up button
3) Continue to hold VolUP until you see the big USB symbol (i.e. webOS recovery)
Errgghh
Downloaded but not sure what is going on. I think the problem my be with something being overwritten during one of the first attempts. With the USB logo displayed, I connect it to the PC. The minute it starts to transfer, it resets and I see the hp logo and then the boot screen. At this point it is stuck in a rebooting loop for several times. I even just tried webos doctor and it starts at 1% and as soon as it hits 2% it reboots the same way.
Also will not mount as a USB drive on the PC. Just as a palm noobie or something so I can not access anything on the device manually.
While I have not experience your issue I have had other issues that were resolved by changing to a different USB cable. Might be worth a try.
Sent from my MT2L03 using Tapatalk 2
Having the same issue. From USB to HP logo, then 1.5 seconds of text and then reboot. Tried V41 and V42 and tried multiple USB cables.