I recently updated my Touchpad to 3.0.5 which was a terrible idea. Somehow it messed up my android side, so I decided to doctor the Touchpad. Unfortunately when I did, it would not boot up. It is stuck on the palm.com/rom screen and now when I try to doctor it, it gets stuck on 12%. I'm running OS 10.7.3. Can anyone help? I've googled solutions but none of them seem to help.
You should run ACMEUninstaller, that will remove Android.
Then run Doctor again and you might be lucky, if not it gets slightly more complicated.
the webos doctor will hang at 12% for a while , so give it time.
You may have to doctor with 3.0.2 to get the correct partition resizing, then re-doctor to 3.0.5, and then re-install android. I believe that 3.0.2 was the last doctor that adjusted the partition tables prior to installing, but check google/xda first on that, as it has been discussed before.
Can you still get into the usb loader screen when you power on/reboot and hold the volume up key?
pikeco94 said:
I recently updated my Touchpad to 3.0.5 which was a terrible idea. Somehow it messed up my android side, so I decided to doctor the Touchpad. Unfortunately when I did, it would not boot up. It is stuck on the palm.com/rom screen and now when I try to doctor it, it gets stuck on 12%. I'm running OS 10.7.3. Can anyone help? I've googled solutions but none of them seem to help.
Click to expand...
Click to collapse
Do you have a Windows virtual machine?
Related
Hello, I just bought my G-tablet and I have severely screwed it over. First, I rooted it and installed CWM, (It went fine). Then I flashed Cyanogen 7, following their wiki full update instructions. It was running fine till I found out that for some reason, my computer nor the tablet even knew it had an SD (Computer found nothing, File explorer on tablet had nothing) coupled with the fact Gapps refused to install, I figured this would be solved in a wipe then another flash. Nothing was different. So I wiped again (seemed to have froze during) but the flash of Vegan 5.1 seemed to have went well... for now. However, trying to install Adobe Flash via the preinstalled android market, it wouldn't install. It kept saying download unsuccessful, for every single app I tried. (no it's not an network problem). Being the noob I am I started following random googled XDA threads on how to fix this. I partioned 4gig from my sd to see if that would fix the market problem. I got stuck in a bootloop so I was forced to reflash vegan. When I did, I found out that when I tried to install anything it said something along the lines of "Not enough space" knowing I had 13 gigs of memory leftover, I figured I'd try rebooting. Got stuck in bootloop. Then followed yet ANOTHER googled guide (droidpirate brick fix) and now I can't even access CWM. It just loads as IF it were going to CWM but then shows me a /!\ caution sign then instantly turns off. When I normally start it, it goes into bootloop. when I try to get to CWM (holding volume up, power) it goes to a useless flash that I presume just fails, then brings me back into the bootloop. As far as I see, I have no way of fixing this...
I know this is so much to read, so in a brief explanation.. I'm in a bootloop, cannot get into CWM (brings me to a failed flash then back into boot loop) and am in dire need of assistance Please help me
Go read the posts on nvflash and learn how to use it. It is your friend!!
IndyLateNite said:
Go read the posts on nvflash and learn how to use it. It is your friend!!
Click to expand...
Click to collapse
NvFlash is currently not working for me, I don't know exactly where I messed up but my computer already has the drivers to read the tablet. when I run the .bat, it doesn't seem to do anything.
Scratch that, got it to work. I didn't extract one of the folders entirely. But my tablet is still stuck in bootloop even after this? what now?
IndyLateNite said:
Go read the posts on nvflash and learn how to use it. It is your friend!!
Click to expand...
Click to collapse
Take this with a grain of salt, as I learned it is not 'always' your friend
Now it's just on the stock Viewsonic birds and Gtablet logo bootloop...
Even after I NvFlashed it... Still can't access CMW.
Any suggestions?
Nvm, I got it to what appears to be working. (and I just about jizzed all over my tab.) Thanks so much. Saved me a beating from my parents.
After updating to webOS 3.0.4 I am unable to get ACMEInstaller to do install-reinstall Mboot or anyother zip to try and return the touchpad to dualboot status. As of now I can´t get into CM7 at all.
I´ve tried a factory reset of WebOS using webDoctor and then reInstalling CM7 but to no avail. Any advice?
What does the unit do when you reboot it?
it just boots webOS. One thing I've noticed that I think MIGHT BE different is that the HP icon flashes up on the screen right before the USB symbol pops up when holding down the vol up button.
This has been covered extensively, all you have to do is reinstall MOBOOT, and you will be able to get back to your unharmed previous installation of CM7
Yes that was done and wasn´t the problem. Thanks anyway. Figured out was was going on.
mmontanaa said:
Yes that was done and wasn´t the problem. Thanks anyway. Figured out was was going on.
Click to expand...
Click to collapse
So what was the problem and solution?
you HAVE TO re-enable developer mode on the touchpad when you have a fresh install of webos before acmeinstaller will work.
that's the solution.
New problem: is there a way to backup your Memo (stickies notes) without booting into webOS?
where are the text data files located?
Is there a way to restore/revert webOS system while leaving my Android portion untouched?
So after updating to 3.05 and installing a custom IME (which worked for 3.04) I've bricked the webOS portion of the touchpad.
The Android system still boots fine, and I don't want to wipe that just to get webOS working.
BTW this is what I don't like about HP, I never intended to update 3.05, simply left my touchpad charging overnight, then woke up in the morning & found out the bad news.
dindin223 said:
Is there a way to restore/revert webOS system while leaving my Android portion untouched?
So after updating to 3.05 and installing a custom IME (which worked for 3.04) I've bricked the webOS portion of the touchpad.
The Android system still boots fine, and I don't want to wipe that just to get webOS working.
BTW this is what I don't like about HP, I never intended to update 3.05, simply left my touchpad charging overnight, then woke up in the morning & found out the bad news.
Click to expand...
Click to collapse
It sounds like you have to doctor your TP.
Search 'doctor', there are several how to threads that should guide you through the process.
Mine too
My install of 3.0.5 did not complete, in the process it wiped out Moboot 0.3.4 What I did to recover is download the latest Doctor from the HP site and ran it. That updates the OS correctly. Then I looked at the files and found that all of the Android mods/files were still there.
So I just installed the new version of Moboot using ACMEInstaller and then I did the same thing for Clockwork recovery. Rebooting into Clockwork recovery, I reloaded Xron 2.9.1 from the zip file which was still on the Touchpad.
Everything Android is working fine right now.
I suspect that there is a better way, but I don't have 10 posts to ask in the developers section.
Using the "Doctor" wipes out WebOS settings and Apps so you have to reinstall those just FYI.
Thanks for the valuable information, it's good to know that I don't have to reinstall all the android apps.
Now I'm trying to find a way to back up my memo files in webOS...
Yeah, the doctor resets your device to factory...I used it often during my pre- days. Make a nandroid next time so if something does go wrong, of will be easier to restore what you had. Just copy the backup to your PC before using the doctor.
Sent from my GT-i9100 using Tapatalk
If u still have android and can boot into cwm , then make a nand.backup so you can restore your cm7 / xron exactly as it is.
now webosdoctor 3.0.5
then if needed install moboot0.3.5 and cwm with ACMEInstaller
IF Android not present in Moboot , restore nand.backup in cwm.
As long as u have a Nand.backup u can wipe Android as many times as u want.
I really must learn to type faster
They should be backed up automatically. They will restore after you set your account back up in web os. I had to run the doctor to fix my 3.0.5 update and all my stickies are still there.
I'm in the same boat as you guys here except that it worked fine yesterday (I needed it for work) and I forgot to charge it last night. I went to work and before my office meeting started I plugged it in, figuring it would have enough juice for me to use. Well... I realized it wasn't charging at all and its not the charger. No matter how long I held the power button I couldn't get anything to come on. I came home and placed it in the touchstone charger and nothing either. It seems like I'm screwed with a bricked 32gb touchpad. I did buy it direct so I guess I'm going to try to send it in (hopefully I'll get lucky, I'm going to deny any tampering with) to HP. I haven't connected it to my pc yet but if I get nothing there's no way to run Doctor, right?
Any constructive thoughts would be appreciated.
Update: You are not going to believe it, after messing with different combos of button pressing (which did nothing) all the sudden it just powered up (all I did was plug it back to the wall). And, as I was typying this it rebooted it self with boot screen which started CM7 again. Do you guys have any suggestions? Should I update the moboot?
The doctor does not erase your cm7/9 partition. It fixes the hp webos partion and sets it back up to what it auto saved. You just have to run the acme installer to get cwm and moboot back. even if you install android agian, if you don't wipe all your data should be there. That's what happened when I did it.
can't get into usb mode
I noticed that my hp touchpad was shutting down while in standby. I immediately thought it was a autoupgrade and so when it booted up and started installing the new webos I panicked and hit the power and home buttons to prevent the upgrade because I have CM7 alpha 3.5.
When I booted it up again I could only see a battery icon with a question mark in the middle. I can't make my win7 pc recognize the tablet and nor does the hp doctor for the same reason.
Does anyone have a clue how I can fix this? I know that some people in the past had this same issue that was caused by faulty usb cable or not having the battery correctly inserted (for other webos devices) but this is not the case. Just before I canceled the upgrade I had 20% battery and I had it plugged in and charging.
Thanks.
I am trying to unbrick my Touchpad at present. I was trying to wipe to sell and made a bit of a hash on things.
It won't boot and just hangs on the HP logo and WebOSDoctor hangs at 8%. I tried to run the ACME Uninstaller which crashed and seems to have knocked all sense out of my touchpad.
I am following these instructions for fixing :
http://rootzwiki.com/topic/14249-th...8-12-stopped-no-sd-opps-reformat-crap-thread/
The question I have is that when I run the ACME Installer on that it gets to a stage where I get a scroll of messages :
Bad File Name
Auto re-naming it
Yesterday I left this running for about 4 hours (maybe more) and it got to renaming about 6000 files before the battery went flat. I have started again this morning after leaving the Touchpad charging all night.
Any advice from anyone? I have no interest in any data on the Touchpad, I just want it wiped and booting back into WebOS.
Tried to repartition the touch pad...
Sent from my cm_tenderloin using XDA
I actually managed to fix this.
I was getting lots of trouble with Novaterm. I tried using it on my Mac and on my Windows machine. I was getting errors saying "command not recognised".
I actually managed to find one solution. I can't find where it was now but I just loaded up Novaterm and entered a single command which I believe reformatted the tablet. I was then able to use WebOS Doctor 3.0 and restore.
So my dad's touchpad recently started being weird. I thought that it was because it didn't have enough charge so I told him to charge it. Now that it has some amount of charge, the boot menu comes up (I installed AOKP for him) but whenever I select it, it bootloops into the boot menu again. The same problem occurs when I select WebOS under the menu. I tried to get into CWM recovery but that has problems too because I can get into it but no options actually come up and I can't select anything.
tl;dr, I can't boot into Android or WebOS.
Is there any guides that I can follow with this problem? I know some things about Webosdoctor but I just need some direction is all. Thank you.
chlehqls said:
So my dad's touchpad recently started being weird. I thought that it was because it didn't have enough charge so I told him to charge it. Now that it has some amount of charge, the boot menu comes up (I installed AOKP for him) but whenever I select it, it bootloops into the boot menu again. The same problem occurs when I select WebOS under the menu. I tried to get into CWM recovery but that has problems too because I can get into it but no options actually come up and I can't select anything.
tl;dr, I can't boot into Android or WebOS.
Is there any guides that I can follow with this problem? I know some things about Webosdoctor but I just need some direction is all. Thank you.
Click to expand...
Click to collapse
Try this link :
http://forum.xda-developers.com/showthread.php?t=1426244
Read the whole thing. Around page 12 there's a good work around if you're having trouble with novaterm.
Let the tablet charge for a few hours before trying the process.
chicle_11 said:
Try this link :
http://forum.xda-developers.com/showthread.php?t=1426244
Read the whole thing. Around page 12 there's a good work around if you're having trouble with novaterm.
Let the tablet charge for a few hours before trying the process.
Click to expand...
Click to collapse
Thank man. I looked at that guide too but wasn't sure if that would allow me to reach a resolution. I'll try it since at this point my dad's touchpad is a brick.
Here's another thread that could be helpful : http://forum.xda-developers.com/showthread.php?p=33669700#post33669700