Hi folks,
I was using Cyanogenmod 9 before the nightly releases and have installed ubuntu. Well, yesterday i tried to reset it to a factory condition to reinstall just cm9 nightly along with WebOS.
I used the WebOS Doctor 3.0.0, and after it the TouchPad won't boot anymore, just stuck on HP Logo reset loop. So i have tried again with WebOS Doctor 3.0.5 and got the same...
Also, i have tried to reinstall directly moboot and these things with ACMEInstaller, but it claims anything about lvm not found. Now, i just can't do anything to touchpad. I can enter on USB mode (Pwr + VolUP), and connect with novaterm, but i dont know what to do.
Anyone can try to help me? I'll post more details if you tell me how to catch these.
What you need to do is use the info from THIS THREAD to help you reset. It'll erase and recreate all of the partitions on the TP and allow you to flash 3.0.0 properly (then you can flash 3.0.5 and then install CM9 again).
I just did it last night (again). It's the best guide I've found, anywhere.
Hi,
I saw this and did this but i missed to flash the Recovery uImage before i created this thread, a bad mistaken.
Thanks for help.
Related
I am coming from OaT LnTJB 12/22 and upgraded to AcmeInstaller3 before flashing that ROM (as I came from CM9, although I didn't use AcmeUninstaller first) and also have moboot 3.8 and the latest TWRP and CWM.
However, when trying to flash the new CM10 build after doing a full wipe through recovery (i.e., System, Data, Cache) I keep coming up with the same errors, such as "damaged SD card" upon boot (even though I can browse the contents through file manager) and broken wallpaper (didn't dive too much into other errors after those, as I already knew something was amiss). Also, in trying to wipe cache/dalvik, upon reboot it gave me this weird screen where it usually would say "Android is upgrading..." and instead had some symbols (one was %) with a prompt that I can paraphrase as "touch to switch apps". Odd to say the least.
Any ideas as to what could be causing these errors? Should I just dirty flash over OaT (not my preference)? Any/all help is appreciated!
rg2 said:
I am coming from OaT LnTJB 12/22 and upgraded to AcmeInstaller3 before flashing that ROM (as I came from CM9, although I didn't use AcmeUninstaller first) and also have moboot 3.8 and the latest TWRP and CWM.
However, when trying to flash the new CM10 build after doing a full wipe through recovery (i.e., System, Data, Cache) I keep coming up with the same errors, such as "damaged SD card" upon boot (even though I can browse the contents through file manager) and broken wallpaper (didn't dive too much into other errors after those, as I already knew something was amiss). Also, in trying to wipe cache/dalvik, upon reboot it gave me this weird screen where it usually would say "Android is upgrading..." and instead had some symbols (one was %) with a prompt that I can paraphrase as "touch to switch apps". Odd to say the least.
Any ideas as to what could be causing these errors? Should I just dirty flash over OaT (not my preference)? Any/all help is appreciated!
Click to expand...
Click to collapse
I would run acmeuninstaller, then go through the cminstall and acmeinstaller3 thing.
Good luck.
Edit: make a backup, just in case. Use cwm, there's been cases where twrp has caused problems.
You say you have two both TWRP and CWM which one did you use? It's also probably one to many as the maximum size for the boot folder is 32mb which you are probably quite close to.
chicle_11 said:
I would run acmeuninstaller, then go through the cminstall and acmeinstaller3 thing.
Good luck.
Edit: make a backup, just in case. Use cwm, there's been cases where twrp has caused problems.
Click to expand...
Click to collapse
Thanks for the advice. Going to have to do this I guess.
sstar said:
You say you have two both TWRP and CWM which one did you use? It's also probably one to many as the maximum size for the boot folder is 32mb which you are probably quite close to.
Click to expand...
Click to collapse
I used them both, although I generally use TWRP. I got rid of CWM and tried again to no avail. Thanks for the reply.
Running ACMEuninstall and reinstalling did nothing to fix the problem. Still have "damaged SD card" prompt upon boot, still have broken wallpaper functionality as well as crippled launcher functionality. Any ideas?
How is webOS running? If you get problems in that also then I would run acmeuninstaller and then run remove android from preware followed by webos doctor 3.00 then 3.0.5 if you want to actually use it.
sstar said:
How is webOS running? If you get problems in that also then I would run acmeuninstaller and then run remove android from preware followed by webos doctor 3.00 then 3.0.5 if you want to actually use it.
Click to expand...
Click to collapse
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
reset webos
rg2 said:
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
Click to expand...
Click to collapse
I was having trouble installing cm9 when I bought my touchpad. Got an error that said drive needed to be formatted when connected to my pc. I did a reset in webos and it fixed the problems. Try that.
rg2 said:
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
Click to expand...
Click to collapse
Did you use webOS doctor 3.00?
Sent from my cm_tenderloin using Tapatalk 2
johna2u said:
I was having trouble installing cm9 when I bought my touchpad. Got an error that said drive needed to be formatted when connected to my pc. I did a reset in webos and it fixed the problems. Try that.
Click to expand...
Click to collapse
Thanks for the tip. Will have to try this.
sstar said:
Did you use webOS doctor 3.00?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
No did 3.0.5. Gonna try 3.00. Thanks again for all the help!
**EDIT** After downgrading to 3.00 via WebOS Doctor and doing a Secure Full Wipe through WebOS, I was able to install the new JCSullins CM10 build w/o issues! Thanks again to all for the help
rg2 said:
Thanks for the tip. Will have to try this.
No did 3.0.5. Gonna try 3.00. Thanks again for all the help!
**EDIT** After downgrading to 3.00 via WebOS Doctor and doing a Secure Full Wipe through WebOS, I was able to install the new JCSullins CM10 build w/o issues! Thanks again to all for the help
Click to expand...
Click to collapse
Glad you have sorted it I'm using this Rom http://goo.im/devs/SGA/CM10/CM10_UnOfficial_Mar0813.zip with http://goo.im/gapps/gapps-jb-20121011-signed.zip and extremely happy with it.
If you are going to try it do a system,/factory wipe and then flash with your recovery.
I'm assuming you originally used acmeuninstaller 3
sstar said:
Glad you have sorted it I'm using this Rom http://goo.im/devs/SGA/CM10/CM10_UnOfficial_Mar0813.zip with http://goo.im/gapps/gapps-jb-20121011-signed.zip and extremely happy with it.
If you are going to try it do a system,/factory wipe and then flash with your recovery.
I'm assuming you originally used acmeuninstaller 3
Click to expand...
Click to collapse
Thank you for the suggestion! I will try this since I seem to be cursed using the JCSullins build :/
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
Hey guys!
I recently resized the partitions of my touchpad via the recommended cwm zips, in order to install latest 4.3.1.
Everything worked as expected.
After experiencing quite high battery drain I decided to reflash the A6 firmware, as I already did several times.
When I try to boot up WebOS, I'm stuck in a bootloop. The HP sign is flashing/blinking but it never boots up!
Seems the resizing deleted an important file or similar.
Is there any safe possibility to workaround this? Android is working normal, when I connect to a PC I can only see the MTP Media device, no other partitions.
Should I use WebOS doctor?
Hope somebody has a helpful idea.
Thank you in advance.
spica123 said:
Hey guys!
I recently resized the partitions of my touchpad via the recommended cwm zips, in order to install latest 4.3.1.
Everything worked as expected.
After experiencing quite high battery drain I decided to reflash the A6 firmware, as I already did several times.
When I try to boot up WebOS, I'm stuck in a bootloop. The HP sign is flashing/blinking but it never boots up!
Seems the resizing deleted an important file or similar.
Is there any safe possibility to workaround this? Android is working normal, when I connect to a PC I can only see the MTP Media device, no other partitions.
Should I use WebOS doctor?
Hope somebody has a helpful idea.
Thank you in advance.
Click to expand...
Click to collapse
EDIT: Okay. at least acmeuninstaller brought webos back to life.
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.
OK so I'm just going to explain everything I did and ask how we can fix this. I was following the guide to install LuneOS and I got lost somehow and could not put the new boot image and new moboot image on after I removed the old boot image, so I tried to reboot (I know that was dumb) but then I got a error message about no Palm ROM. So I booted into the only thing I could boot into WebOS Recovery. Now I figured I would try out jcsullins Touchpad Toolbox I was able to load it and I figured the only way I could make it work would be to remove and reinstall WebOS to get the boot image back, so I wiped the touchpad (again probably not the best thing to have done). I then went to go and reinstall WebOS and the WebOSdoctor(webosdoctor305) I used failed after 8%(should I try a different doctor?). I then tried to install Android with Toolbox and it failed after checking the files(not sure if that was just bad files or issue with touchpad). I can still access WebOS recovery and use novaterm by finding the batch file on my computer and running it and I can still use Toolbox. Any help would be greatly appreciated and if you have any questions of what steps I took I will be happy to answer if it can help my touchpad.
spenser715 said:
OK so I'm just going to explain everything I did and ask how we can fix this. I was following the guide to install LuneOS and I got lost somehow and could not put the new boot image and new moboot image on after I removed the old boot image, so I tried to reboot (I know that was dumb) but then I got a error message about no Palm ROM. So I booted into the only thing I could boot into WebOS Recovery. Now I figured I would try out jcsullins Touchpad Toolbox I was able to load it and I figured the only way I could make it work would be to remove and reinstall WebOS to get the boot image back, so I wiped the touchpad (again probably not the best thing to have done). I then went to go and reinstall WebOS and the WebOSdoctor(webosdoctor305) I used failed after 8%(should I try a different doctor?). I then tried to install Android with Toolbox and it failed after checking the files(not sure if that was just bad files or issue with touchpad). I can still access WebOS recovery and use novaterm by finding the batch file on my computer and running it and I can still use Toolbox. Any help would be greatly appreciated and if you have any questions of what steps I took I will be happy to answer if it can help my touchpad.
Click to expand...
Click to collapse
Wear exactly do you what with your tp webos or android or both? You could have saved yourself and just put moboot back on lol